anchor.diff:  [[RSL_IE_CHAN_NR]]
   ==== RSL_IE_CHAN_NR
   
  -This information element is coded like 3GPP TS 08.58 Section 9.3.1,
  +This information element is coded like 3GPP TS 48.058 Section 9.3.1,
   but in addition supports the following extended coding:
   
   * C5..C1 bits 0b11000 for PDCH type channels
   
   The TN-Bits are not re-defined in this case but use the same encoding
  -as specified in TS 08.58 Section 9.3.1.
  +as specified in TS 48.058 Section 9.3.1.
   
   NOTE:: The above extension is only valid on an Osmocom-style dynamic
   channel, having configured the 'NM_CHANC_IPAC_TCHFull_PDCH' channel
  
positive.code: [cols="30%,25%,15%,15%,15%"]
  |===
  | INFORMATION ELEMENT | REFERENCE | PRESENCE | FORMAT | LENGTH 
  | Message discriminator | 08.58 9.1 | M | V | 1
  | Message type | <<own_msg_types>> | M | V | 1
  | Channel number | 08.58 9.3.1 | M | TV | 2
  |===
  
  NOTE:: This message is *not* used by Osmocom style dynamic channels
  
negative.code: [[RF_RESOURCE_INDICATION]]
  ==== RF Resource Indication
  
  This message does not conform to 3GPP TS 48.058 § 8.6.1, in that it omits the
  _Resource Information_ IE that would contain the actual payload data, which
  renders this message void.
  
  ._RF Resource Indication_ message IE exceptions
  [options="header",cols="10%,30%,60%"]
  |===
  | TS 48.058 § | IE Name | Handling
  | 9.3.21 | Resource Information | OsmoBTS omits this IE, though TS 48.058
                                    specifies it as mandatory.
  |===
  
  