| 1 |
<pre>Network Working Group G. Fairhurst |
| 2 |
Request for Comments: 5163 University of Aberdeen |
| 3 |
Category: Standards Track B. Collini-Nocker |
| 4 |
University of Salzburg |
| 5 |
April 2008 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">Extension Formats for Unidirectional Lightweight Encapsulation (ULE)</span> |
| 9 |
<span class="h1">and the Generic Stream Encapsulation (GSE)</span> |
| 10 |
|
| 11 |
Status of This Memo |
| 12 |
|
| 13 |
This document specifies an Internet standards track protocol for the |
| 14 |
Internet community, and requests discussion and suggestions for |
| 15 |
improvements. Please refer to the current edition of the "Internet |
| 16 |
Official Protocol Standards" (STD 1) for the standardization state |
| 17 |
and status of this protocol. Distribution of this memo is unlimited. |
| 18 |
|
| 19 |
Abstract |
| 20 |
|
| 21 |
This document describes a set of Extension Headers for the |
| 22 |
Unidirectional Lightweight Encapsulation (ULE), <a href="./rfc4326">RFC 4326</a>. |
| 23 |
|
| 24 |
The Extension Header formats specified in this document define |
| 25 |
extensions appropriate to both ULE and the Generic Stream |
| 26 |
Encapsulation (GSE) for the second-generation framing structure |
| 27 |
defined by the Digital Video Broadcasting (DVB) family of |
| 28 |
specifications. |
| 29 |
|
| 30 |
Table of Contents |
| 31 |
|
| 32 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 33 |
<a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-3">3</a> |
| 34 |
<a href="#section-3">3</a>. Description of the Method .......................................<a href="#page-4">4</a> |
| 35 |
<a href="#section-3.1">3.1</a>. MPEG-2 TS-Concat Extension .................................<a href="#page-5">5</a> |
| 36 |
<a href="#section-3.2">3.2</a>. PDU-Concat Extension .......................................<a href="#page-8">8</a> |
| 37 |
<a href="#section-3.3">3.3</a>. TimeStamp Extension .......................................<a href="#page-12">12</a> |
| 38 |
<a href="#section-4">4</a>. IANA Considerations ............................................<a href="#page-13">13</a> |
| 39 |
<a href="#section-5">5</a>. Acknowledgments ................................................<a href="#page-13">13</a> |
| 40 |
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-14">14</a> |
| 41 |
<a href="#section-7">7</a>. References .....................................................<a href="#page-14">14</a> |
| 42 |
<a href="#section-7.1">7.1</a>. Normative References ......................................<a href="#page-14">14</a> |
| 43 |
<a href="#section-7.2">7.2</a>. Informative References ....................................<a href="#page-14">14</a> |
| 44 |
<a href="#appendix-A">Appendix A</a>. The Second-Generation DVB Transmission |
| 45 |
Specifications .................................................<a href="#page-16">16</a> |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 58 |
|
| 59 |
This document describes three Extension Headers that may be used with |
| 60 |
both the Unidirectional Lightweight Encapsulation (ULE) [<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>] and |
| 61 |
the Generic Stream Encapsulation (GSE) [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. ULE is defined for |
| 62 |
links that employ the MPEG-2 Transport Stream, and supports a wide |
| 63 |
variety of physical-layer bearers [<a href="./rfc4259" title=""A Framework for Transmission of IP Datagrams over MPEG-2 Networks"">RFC4259</a>]. |
| 64 |
|
| 65 |
GSE has been designed for the Generic Mode (also known as the Generic |
| 66 |
Stream (GS)), offered by second-generation DVB physical layers, and |
| 67 |
in the first instance for DVB-S2 [<a href="#ref-ETSI-S2" title=""Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications"">ETSI-S2</a>]. The requirements for the |
| 68 |
Generic Stream are described in [<a href="#ref-S2-REQ" title=""A Design Rationale for Providing IP Services over DVB-S2 Links"">S2-REQ</a>]. The important |
| 69 |
characteristics of this encapsulation are described in the appendix |
| 70 |
of this document. GSE maintains a design philosophy that presents a |
| 71 |
network interface that is common to that presented by ULE and uses a |
| 72 |
similar construction for SubNetwork Data Units (SNDUs). |
| 73 |
|
| 74 |
The first Extension Header defines a method that allows one or more |
| 75 |
TS Packets [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>] to be sent within a ULE SNDU. This method may |
| 76 |
be used to provide control plane information including the |
| 77 |
transmission of MPEG-2 Program Specific Information (PSI) for the |
| 78 |
Multiplex. In GSE, there is no native support for Transport Stream |
| 79 |
packets and this method is therefore suitable for providing an MPEG-2 |
| 80 |
control plane. |
| 81 |
|
| 82 |
A second Extension Header allows one or more PDUs to be sent within |
| 83 |
the same ULE SNDU. This method is designed for cases where a large |
| 84 |
number of small PDUs are directed to the same Network Point of |
| 85 |
Attachment (NPA) address. The method may improve transmission |
| 86 |
efficiency (by removing duplicated MAC layer overhead). It can also |
| 87 |
reduce processing overhead for a receiver that is not configured to |
| 88 |
receive the NPA address associated with an SNDU, allowing this |
| 89 |
receiver to then skip several PDUs in one operation. The method is |
| 90 |
defined as a generic Extension Header and may be used for IPv4 or |
| 91 |
IPv6 packets. If, and when, a compression format is defined for ULE |
| 92 |
or Ethernet, the method may also be used in combination with this |
| 93 |
method. |
| 94 |
|
| 95 |
A third Extension Header provides an optional TimeStamp value for an |
| 96 |
SNDU. Examples of the use of this TimeStamp option include |
| 97 |
monitoring and benchmarking of ULE and GSE links. Receivers that do |
| 98 |
not wish to decode (or do not support) the TimeStamp extension may |
| 99 |
discard the extension and process the remaining PDU or Extension |
| 100 |
Headers. |
| 101 |
|
| 102 |
The appendix includes a summary of key design issues and |
| 103 |
considerations relating to the GSE Specification defined by the DVB |
| 104 |
Technical Module [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span> |
| 114 |
|
| 115 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 116 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 117 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 118 |
|
| 119 |
b: bit. For example, one byte consists of 8b. |
| 120 |
|
| 121 |
B: byte. Groups of bytes are represented in Internet byte order. |
| 122 |
|
| 123 |
BBFrame payload: The data field part of a Baseband frame [<a href="#ref-ETSI-S2" title=""Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications"">ETSI-S2</a>] |
| 124 |
that may be used for the communication of data. Typical BBFrames |
| 125 |
range in size from 3072 to 58192 bits according to the choice of |
| 126 |
modulation format and Forward Error Correction (FEC) in use. |
| 127 |
|
| 128 |
DVB: Digital Video Broadcasting. A framework and set of associated |
| 129 |
standards published by the European Telecommunications Standards |
| 130 |
Institute (ETSI) for the transmission of video, audio, and data. |
| 131 |
|
| 132 |
E: A one-bit flag field defined in GSE [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. |
| 133 |
|
| 134 |
Encapsulator: A network device [<a href="./rfc4259" title=""A Framework for Transmission of IP Datagrams over MPEG-2 Networks"">RFC4259</a>] that receives PDUs and |
| 135 |
formats these into Payload Units (known here as SNDUs) for output in |
| 136 |
DVB-S or the Generic Mode of DVB-S2. |
| 137 |
|
| 138 |
GS: Generic Stream. A stream of BBFrames identified by a common |
| 139 |
Input Stream Identifier, and which does not use the MPEG-2 TS format |
| 140 |
[<a href="#ref-ETSI-S2" title=""Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications"">ETSI-S2</a>]. It represents layer 2 of the ISO/OSI reference model. |
| 141 |
|
| 142 |
GSE: Generic Stream Encapsulation [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. A method for encapsulating |
| 143 |
PDUs to form a Generic Stream, which is sent using a sequence of |
| 144 |
BBFrames. This encapsulation format shares the same extension format |
| 145 |
and basic processing rules of ULE and uses a common IANA Registry. |
| 146 |
|
| 147 |
LT: A two-bit flag field defined in GSE [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. |
| 148 |
|
| 149 |
MAC: Medium Access Control [<a href="#ref-IEEE-802.3" title=""Local and metropolitan area networks - Specific requirements Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications"">IEEE-802.3</a>]. A link-layer protocol |
| 150 |
defined by the IEEE 802.3 standard. |
| 151 |
|
| 152 |
MPEG-2: A set of standards specified by the Motion Picture Experts |
| 153 |
Group (MPEG), and standardized by the International Organization for |
| 154 |
Standardization (ISO/IEC 113818-1) [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>], and ITU-T (in H.220). |
| 155 |
|
| 156 |
Next-Header: A Type value indicating an Extension Header [<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>]. |
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 167 |
|
| 168 |
|
| 169 |
NPA: Network Point of Attachment [<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>]. In this document, refers |
| 170 |
to a destination address (resembling an IEEE MAC address) within the |
| 171 |
DVB-S/S2 transmission network that is used to identify individual |
| 172 |
Receivers or groups of Receivers. |
| 173 |
|
| 174 |
PID: Packet Identifier [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>]. A 13-bit field carried in the |
| 175 |
header of each TS Packet. This identifies the TS Logical Channel to |
| 176 |
which a TS Packet belongs [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>]. The TS Packets that form the |
| 177 |
parts of a Table Section or other Payload Unit must all carry the |
| 178 |
same PID value. The all-ones PID value indicates a Null TS Packet |
| 179 |
introduced to maintain a constant bit rate of a TS Multiplex. There |
| 180 |
is no required relationship between the PID values used for TS |
| 181 |
Logical Channels transmitted using different TS Multiplexes. |
| 182 |
|
| 183 |
PDU: Protocol Data Unit [<a href="./rfc4259" title=""A Framework for Transmission of IP Datagrams over MPEG-2 Networks"">RFC4259</a>]. Examples of a PDU include |
| 184 |
Ethernet frames, IPv4 or IPv6 datagrams, and other network packets. |
| 185 |
|
| 186 |
PSI: Program Specific Information [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>]. |
| 187 |
|
| 188 |
S: A one-bit flag field defined in [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. |
| 189 |
|
| 190 |
SI Table: Service Information Table [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>]. In this document, |
| 191 |
this term describes a table that is been defined by another standards |
| 192 |
body to convey information about the services carried on a DVB |
| 193 |
Multiplex. |
| 194 |
|
| 195 |
SNDU: SubNetwork Data Unit [<a href="./rfc4259" title=""A Framework for Transmission of IP Datagrams over MPEG-2 Networks"">RFC4259</a>]. In this document, this is an |
| 196 |
encapsulated PDU sent using ULE or GSE. |
| 197 |
|
| 198 |
Stream: A logical flow from an Encapsulator to a set of Receivers. |
| 199 |
|
| 200 |
TS: Transport Stream [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>], a method of transmission at the |
| 201 |
MPEG-2 level using TS Packets; it represents layer 2 of the ISO/OSI |
| 202 |
reference model. |
| 203 |
|
| 204 |
ULE: Unidirectional Lightweight Encapsulation (ULE) [<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>]. A |
| 205 |
method that encapsulates PDUs into SNDUs that are sent in a series of |
| 206 |
TS Packets using a single TS Logical Channel. The encapsulation |
| 207 |
defines an extension format and an associated IANA Registry. |
| 208 |
|
| 209 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Description of the Method</span> |
| 210 |
|
| 211 |
In ULE, a Type field value that is less than 1536 in decimal |
| 212 |
indicates an Extension Header. This section describes a set of three |
| 213 |
extension formats for the ULE encapsulation. [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>] uses a Type field |
| 214 |
that adopts the same semantics as specified by <a href="./rfc4326">RFC 4326</a>. The |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 223 |
|
| 224 |
|
| 225 |
encapsulation format differs in that GSE does not include a Cyclic |
| 226 |
Redundancy Check (CRC) for each SNDU, has different header flags, and |
| 227 |
utilizes a different SNDU length calculation [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. |
| 228 |
|
| 229 |
There is a natural ordering of Extension Headers, which is determined |
| 230 |
by the fields upon which the Extension Header operates. A suitable |
| 231 |
ordering for many applications is presented in the list below (from |
| 232 |
first to last header within an SNDU). This does not imply that all |
| 233 |
types of Extensions should be present in a single SNDU. The |
| 234 |
presented ordering may serve as a guideline for optimization of |
| 235 |
Receiver processing. |
| 236 |
|
| 237 |
+----------------------------------+-------------------------------+ |
| 238 |
|Fields related to Extension Header| Example Extension Headers | |
| 239 |
+----------------------------------+-------------------------------+ |
| 240 |
| Link framing and transmission | TimeStamp Extension | |
| 241 |
+----------------------------------+-------------------------------+ |
| 242 |
| Entire remaining SNDU Payload | Encryption Extension | |
| 243 |
+----------------------------------+-------------------------------+ |
| 244 |
| Group of encapsulated PDUs | PDU-Concat or TS-Concat | |
| 245 |
+----------------------------------+-------------------------------+ |
| 246 |
| Specific encapsulated PDU | IEEE-defined type | |
| 247 |
| | Test or MAC bridging Extension| |
| 248 |
+----------------------------------+-------------------------------+ |
| 249 |
|
| 250 |
Table 1: Recommended ordering of Extension Headers |
| 251 |
|
| 252 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. MPEG-2 TS-Concat Extension</span> |
| 253 |
|
| 254 |
The MPEG-2 TS-Concat Extension Header is specified by an IANA- |
| 255 |
assigned H-Type value of 0x0002 in hexadecimal. This is a Mandatory |
| 256 |
Extension Header. |
| 257 |
|
| 258 |
The extension is used to transport one or more MPEG-2 TS Packets |
| 259 |
within a ULE SNDU. The number of TS Packets carried in a specific |
| 260 |
SNDU is determined from the size of the remainder of the payload |
| 261 |
following the MPEG-2 TS Extension Header. The number of TS Packets |
| 262 |
contained in the SNDU is therefore (Length-N-10+D*6) / 188, where N |
| 263 |
is the number of bytes associated with Extension Headers that precede |
| 264 |
the MPEG-2 TS-Concat Extension (zero if there are none) and D is the |
| 265 |
value of the D-bit. |
| 266 |
|
| 267 |
A Receiver MUST check the validity of the Length value prior to |
| 268 |
processing the payload. A valid Length corresponds to an integral |
| 269 |
number of TS Packets. An invalid Length (a remainder from the |
| 270 |
division by 188) MUST result in the discard of all encapsulated TS |
| 271 |
Packets and SHOULD be recorded as TS-Concat size mismatch error. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 279 |
|
| 280 |
|
| 281 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 282 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 283 |
|0| Length (15b) | Type = 0x0002 | |
| 284 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 285 |
| Receiver Destination NPA Address (6B) | |
| 286 |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 287 |
| | | |
| 288 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| 289 |
| TS-Packet 1 | |
| 290 |
= = |
| 291 |
| | |
| 292 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 293 |
| TS-Packet 2 (if Length > 2*188) | |
| 294 |
= = |
| 295 |
| etc. | |
| 296 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 297 |
| (CRC-32) | |
| 298 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 299 |
|
| 300 |
Figure 1: ULE/SNDU Format for a TS-Packet Payload (D=0) |
| 301 |
|
| 302 |
Figure 1 illustrates the format of this Extension Header for ULE with |
| 303 |
a value D=0, which indicates the presence of an NPA address |
| 304 |
[<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>]. In this case, the valid payload Length for a ULE SNDU |
| 305 |
with no other extensions is (Length-10) / 188. |
| 306 |
|
| 307 |
The method used to define the Length in GSE differs to that of ULE. |
| 308 |
The equivalent case for GSE would result in a payload Length value of |
| 309 |
(Length-6) / 188 (Figure 2). |
| 310 |
|
| 311 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 312 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 313 |
|S|E|0 0| Length (12b) | Type = 0x0002 | |
| 314 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 315 |
| Receiver Destination NPA Address (6B) | |
| 316 |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 317 |
| | | |
| 318 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| 319 |
| TS-Packet 1 | |
| 320 |
= = |
| 321 |
| | |
| 322 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 323 |
| TS-Packet 2 (if Length > 2*188) | |
| 324 |
= = |
| 325 |
| etc. | |
| 326 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 327 |
|
| 328 |
Figure 2: GSE/SNDU Format for a TS-Packet Payload (LT=00) |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 335 |
|
| 336 |
|
| 337 |
Fragmented GSE SNDUs are protected by a CRC-32 carried in the final |
| 338 |
fragment. After reassembly, this CRC-32 is removed and the resulting |
| 339 |
SNDU carries a Total Length field. The fields labeled S and E are |
| 340 |
defined by [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>] and contain control flags used by the GSE link |
| 341 |
layer. The Label Type (LT) field specifies the presence and format |
| 342 |
of the GSE label. The LT field is only specified for the first |
| 343 |
fragment (or a non-fragmented) GSE SNDU (i.e., when S=1). |
| 344 |
|
| 345 |
In ULE, a value of D=1 is also permitted and indicates the absence of |
| 346 |
an NPA address (Figure 3). A similar format is supported in GSE. |
| 347 |
|
| 348 |
0 1 2 3 |
| 349 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 350 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 351 |
|1| Length (15b) | Type = 0x0002 | |
| 352 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 353 |
| TS-Packet 1 | |
| 354 |
= = |
| 355 |
| | |
| 356 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 357 |
| TS-Packet 2 (if Length > 2*188) | |
| 358 |
= = |
| 359 |
| etc. | |
| 360 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 361 |
| (CRC-32) | |
| 362 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 363 |
|
| 364 |
Figure 3: ULE/SNDU Format for a TS-Packet Payload (D=1) |
| 365 |
|
| 366 |
The TS-Concat extension may be used to transport one or more MPEG-2 |
| 367 |
TS Packets of arbitrary content, interpreted according to [ISO- |
| 368 |
MPEG2]. One expected use is for the transmission of MPEG-2 SI/PSI |
| 369 |
signalling [<a href="./rfc4259" title=""A Framework for Transmission of IP Datagrams over MPEG-2 Networks"">RFC4259</a>]. |
| 370 |
|
| 371 |
NULL TS Packets [<a href="#ref-ISO-MPEG2" title=""Information Technology; Generic Coding of Moving Pictures and Associated Audio Information Systems"">ISO-MPEG2</a>] SHOULD NOT be sent using this |
| 372 |
encapsulation. To reduce transmission overhead and processing, an |
| 373 |
Encapsulator SHOULD specify a maximum period of time that it can wait |
| 374 |
before sending all queued TS Packets. This is known as the TS |
| 375 |
Packing Threshold. This value MUST be bounded and SHOULD be |
| 376 |
configurable in the Encapsulator. A larger value can improve |
| 377 |
efficiency, but incurs higher jitter and could increase the |
| 378 |
probability of corruption. If additional TS Packets are NOT received |
| 379 |
within the TS Packing Threshold, the Encapsulator MUST immediately |
| 380 |
send any queued TS Packets. |
| 381 |
|
| 382 |
The use of this format to transfer MPEG-2 clock references (e.g., a |
| 383 |
Network Clock Reference, NCR) over ULE/GSE framing raises timing |
| 384 |
considerations at the encapsulation gateway, including the need to |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 391 |
|
| 392 |
|
| 393 |
update/modify the timing information prior to transmission by the |
| 394 |
physical layer. These issues are not considered here, but this |
| 395 |
operation may be simplified in GSE by ensuring that all SNDUs that |
| 396 |
carry this Extension Header are placed before other data within the |
| 397 |
BBFrame DataField [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. |
| 398 |
|
| 399 |
This document does not specify how TS Packets are to be handled at |
| 400 |
the Receiver. However, it notes: |
| 401 |
|
| 402 |
* A Receiver needs to consistently associate all TS Packets in a |
| 403 |
Stream with one TS Logical Channel (Stream). If an Encapsulator |
| 404 |
transmits more than one Stream of TS Packets each encapsulated at a |
| 405 |
different level or with a different NPA address, a Receiver needs |
| 406 |
to ensure that each is independently demultiplexed as a separate |
| 407 |
Stream (<a href="./rfc4259#section-3.2">Section 3.2 [RFC4259]</a>). |
| 408 |
|
| 409 |
* If an Encapsulator transmits service information encapsulated at |
| 410 |
different levels or with different NPA addresses, the Receivers |
| 411 |
need to ensure each Stream is related to the corresponding SI table |
| 412 |
information (if any). A RECOMMENDED way to reduce signaling |
| 413 |
interactions is to ensure each PID value uniquely identifies a |
| 414 |
Stream within a TS Multiplex carrying ULE and also any TS Packets |
| 415 |
encapsulated by a ULE/GSE Stream. |
| 416 |
|
| 417 |
The need for consistency in the use of PIDs and the related service |
| 418 |
information is described in <a href="./rfc4947#section-4.2">section 4.2 of [RFC4947]</a>. |
| 419 |
|
| 420 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. PDU-Concat Extension</span> |
| 421 |
|
| 422 |
The PDU-Concat Extension Header is specified by an IANA-assigned |
| 423 |
H-Type value of 0x0003 in hexadecimal. This is a Mandatory Next- |
| 424 |
Header Extension. It enables a sequence of (usually short) PDUs to |
| 425 |
be sent within a single SNDU Payload. |
| 426 |
|
| 427 |
The base header contains the Length of the entire SNDU. This carries |
| 428 |
the value of the combined length of all PDUs to be encapsulated, |
| 429 |
including each set of encapsulation headers. The base header MAY be |
| 430 |
followed by one or more additional Extension Headers that precede the |
| 431 |
PDU-Concat Extension Header. These Extension Headers (e.g., a |
| 432 |
TimeStamp Extension) apply to the composite concatenated PDU. |
| 433 |
|
| 434 |
The Extension Header also contains a 16-bit ULE Type field describing |
| 435 |
the encapsulated PDU, PDU-Concat-Type. Although any Type value |
| 436 |
specified in the ULE Next-Header Registry (including Extension Header |
| 437 |
Types) may be assigned to the encapsulated PDU (except the recursive |
| 438 |
use of a PDU-Concat type), all concatenated PDUs MUST have a common |
| 439 |
ULE Type (i.e., all concatenated PDUs passed by the network layer |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 447 |
|
| 448 |
|
| 449 |
must be associated with the same Type value). This simplifies the |
| 450 |
receiver design, and reduces the transmission overhead for common use |
| 451 |
cases. |
| 452 |
|
| 453 |
Each PDU is prefixed by its length in bytes (shown in the following |
| 454 |
diagrams as PDU-x-Length for the xth PDU). Encapsulated PDUs are of |
| 455 |
arbitrary length (in bytes) and are not necessarily aligned to 16-bit |
| 456 |
or 32-bit boundaries within the SNDU (as shown in the figures 4, 5, |
| 457 |
and 6). The most significant bit of the first byte is reserved, R, |
| 458 |
and this specification requires that this MUST be set to zero. |
| 459 |
Receivers MUST ignore the value of the R bit. The length of each PDU |
| 460 |
MUST be less than 32758 bytes, but will generally be much smaller. |
| 461 |
|
| 462 |
When the SNDU header indicates the presence of an SNDU Destination |
| 463 |
Address field (i.e., D=0 in ULE), a Network Point of Attachment, NPA, |
| 464 |
field directly follows the fourth byte of the SNDU header. NPA |
| 465 |
destination addresses are 6 byte numbers, normally expressed in |
| 466 |
hexadecimal, used to identify the Receiver(s) in a transmission |
| 467 |
network that should process a received SNDU. When present, the |
| 468 |
Receiver MUST associate the same specified MAC/NPA address with all |
| 469 |
PDUs within the SNDU Payload. This MAC/NPA address MUST also be |
| 470 |
forwarded with each PDU, if required by the forwarding interface. |
| 471 |
|
| 472 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 473 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 474 |
|0| Length (15b) | Type = 0x0003 | |
| 475 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 476 |
| Receiver Destination NPA Address (6B) | |
| 477 |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 478 |
| | PDU-Concat-Type | |
| 479 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 480 |
|R| PDU-1-Length (15b) | | |
| 481 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |
| 482 |
= PDU-1 = |
| 483 |
| | |
| 484 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 485 |
|R| PDU-2-Length (15b) | | |
| 486 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |
| 487 |
= PDU-2 = |
| 488 |
| | |
| 489 |
More PDUs as required |
| 490 |
|
| 491 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 492 |
| (CRC-32) | |
| 493 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 494 |
|
| 495 |
Figure 4: ULE/SNDU Format for a PDU-Concat Payload (D=0) |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 503 |
|
| 504 |
|
| 505 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 506 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 507 |
|S|E|0 0| Length (12b) | Type = 0x0003 | |
| 508 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 509 |
| Receiver Destination NPA Address (6B) | |
| 510 |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 511 |
| | PDU-Concat-Type | |
| 512 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 513 |
|R| PDU-1-Length (15b) | | |
| 514 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |
| 515 |
= PDU-1 = |
| 516 |
| | |
| 517 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 518 |
|R| PDU-2-Length (15b) | | |
| 519 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |
| 520 |
= PDU-2 = |
| 521 |
| | |
| 522 |
More PDUs as required |
| 523 |
|
| 524 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 525 |
|
| 526 |
Figure 5: GSE/SNDU Format for a PDU-Concat Payload (LT=00) |
| 527 |
|
| 528 |
When the SNDU header indicates the absence of an SNDU Destination |
| 529 |
Address field (i.e., D=1 in ULE), all encapsulated PDUs MUST be |
| 530 |
processed as if they had been received without an NPA address. |
| 531 |
|
| 532 |
The value of D in the ULE header indicates whether an NPA/MAC address |
| 533 |
is in use [<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>]. A similar format is supported in GSE (using the |
| 534 |
LT field). |
| 535 |
|
| 536 |
|
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 559 |
|
| 560 |
|
| 561 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 562 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 563 |
|1| Length (15b) | Type = 0x0003 | |
| 564 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 565 |
| PDU-Concat-Type |R| PDU-1-Length (15b) | |
| 566 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 567 |
= PDU-1 = |
| 568 |
| | |
| 569 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 570 |
|R| PDU-2-Length (15b) | | |
| 571 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |
| 572 |
= PDU-2 = |
| 573 |
| | |
| 574 |
More PDUs as required |
| 575 |
|
| 576 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 577 |
| (CRC-32) | |
| 578 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 579 |
|
| 580 |
Figure 6: ULE/SNDU Format for a PDU-Concat Payload (D=1) |
| 581 |
|
| 582 |
To reduce transmission overhead and processing, an Encapsulator |
| 583 |
SHOULD specify a maximum period of time it will wait before sending a |
| 584 |
Concatenated PDU. This is known as the PDU Packing Threshold. This |
| 585 |
value MUST be bounded and SHOULD be configurable in the Encapsulator. |
| 586 |
A larger value can improve efficiency, but incurs higher jitter and |
| 587 |
could increase the probability of corruption. If additional PDUs are |
| 588 |
NOT received within the PDU Packing Threshold, the Encapsulator MUST |
| 589 |
immediately send all queued PDUs. |
| 590 |
|
| 591 |
The Receiver processes this Extension Header by verifying that it |
| 592 |
supports the specified PDU-Concat Type (unsupported Types MUST be |
| 593 |
discarded, but the receiver SHOULD record a PDU-Type error |
| 594 |
[<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>]). It then extracts each encapsulated PDU in turn. The |
| 595 |
Receiver MUST verify the Length of each PDU. It MUST also ensure |
| 596 |
that the sum of the Lengths of all processed PDUs equals the Length |
| 597 |
specified in the SNDU base header. A Receiver SHOULD discard the |
| 598 |
whole SNDU if the total and PDU sizes are not consistent and this |
| 599 |
|
| 600 |
|
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 615 |
|
| 616 |
|
| 617 |
event SHOULD be recorded as a PDU-Concat size mismatch error. A |
| 618 |
receiver MUST NOT forward a partial PDU with an indicated PDU-Length |
| 619 |
greater than the number of unprocessed bytes remaining in the SNDU |
| 620 |
payload field. |
| 621 |
|
| 622 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. TimeStamp Extension</span> |
| 623 |
|
| 624 |
The TimeStamp Extension Header is an Optional Extension Header that |
| 625 |
permits an Encapsulator to add a TimeStamp field to an SNDU. The |
| 626 |
TimeStamp Extension Header is specified by the IANA-assigned H-Type |
| 627 |
value of 257 decimal. This extension is an Optional Extension Header |
| 628 |
(<a href="./rfc4326#section-5">[RFC4326], Section 5</a>). |
| 629 |
|
| 630 |
This extension is designed to support monitoring and measurement of |
| 631 |
the performance of a link to indicate the quality of an operational |
| 632 |
ULE link. This may be useful for GSE links (e.g., where significant |
| 633 |
complexity exists in the scheduling provided by the lower layers). |
| 634 |
Possible uses of this extension include: |
| 635 |
|
| 636 |
* Validation of in-sequence ordering per Logical Channel |
| 637 |
* Measurement of one-way delay (when synchronized with the sender) |
| 638 |
* Measurement of PDU Jitter introduced by the link |
| 639 |
* Measurement of PDU loss (with additional information from sender) |
| 640 |
|
| 641 |
Figure 7 shows the format of this extension with a HLEN value of 3 |
| 642 |
indicating a TimeStamp of length 4B with a Type field (there is no |
| 643 |
implied byte-alignment). |
| 644 |
|
| 645 |
0 7 15 23 31 |
| 646 |
+---------------+---------------+---------------+---------------+ |
| 647 |
| 0x03 | 0x01 | TimeStamp HI | |
| 648 |
+---------------+---------------+---------------+---------------+ |
| 649 |
| TimeStamp LO | Type | |
| 650 |
+---------------+---------------+---------------+---------------+ |
| 651 |
|
| 652 |
Figure 7: Format of the 32-bit TimeStamp Extension Header |
| 653 |
|
| 654 |
The extension carries a 32-bit value (TimeStamp HI plus TimeStamp |
| 655 |
LO). The specified resolution is 1 microsecond. The value therefore |
| 656 |
indicates the number of 1-microsecond ticks past the hour in |
| 657 |
Universal Time when the PDU was encapsulated. This value may be |
| 658 |
earlier than the time of transmission, due for example to Packing, |
| 659 |
queuing, and other Encapsulator processing. The value is right- |
| 660 |
justified to the 32-bit field. Systems unable to insert TimeStamps |
| 661 |
at the specified resolution MUST pad the unused least-significant |
| 662 |
bits with a value of zero. |
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 671 |
|
| 672 |
|
| 673 |
The last two bytes carry a 16-bit Type field that indicates the type |
| 674 |
of payload carried in the SNDU or the presence of a further Next- |
| 675 |
Header (<a href="./rfc4326#section-4.4">[RFC4326], Section 4.4</a>). |
| 676 |
|
| 677 |
Receivers MAY process the TimeStamp when the PDU encapsulation is |
| 678 |
removed. Receivers that do not implement, or do not wish to process, |
| 679 |
the TimeStamp Extension MAY skip this Extension Header. Receivers |
| 680 |
MUST continue to process the remainder of the SNDU, forwarding the |
| 681 |
encapsulated PDU. |
| 682 |
|
| 683 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span> |
| 684 |
|
| 685 |
IANA has assigned three new Next-Header Type values from the IANA ULE |
| 686 |
Next-Header Registry. These options are defined for specific use |
| 687 |
cases envisaged by GSE, but are compatible with ULE. |
| 688 |
|
| 689 |
The following assignments have been made in this document and |
| 690 |
registered by IANA: |
| 691 |
|
| 692 |
Type Name Reference |
| 693 |
|
| 694 |
2: TS-Concat <a href="#section-3.1">Section 3.1</a> |
| 695 |
3: PDU-Concat <a href="#section-3.2">Section 3.2</a> |
| 696 |
|
| 697 |
Type Name H-LEN Reference |
| 698 |
|
| 699 |
257: TimeStamp 3 <a href="#section-3.3">Section 3.3</a> |
| 700 |
|
| 701 |
The TS-Concat Extension is a Mandatory next-type Extension Header, |
| 702 |
specified in <a href="#section-3.1">Section 3.1</a> of this document. The value of this next- |
| 703 |
header is defined by an IANA assigned H-Type value of 0x0002. |
| 704 |
|
| 705 |
The PDU-Concat Extension is a Mandatory next-type Extension Header |
| 706 |
specified in <a href="#section-3.2">Section 3.2</a> of this document. The value of this next- |
| 707 |
header is defined by an IANA assigned H-Type value of 0x0003. |
| 708 |
|
| 709 |
The TimeStamp Extension is an Optional next-type Extension Header |
| 710 |
specified in <a href="#section-3.3">Section 3.3</a> of this document. The value of this next- |
| 711 |
header is defined by an IANA assigned H-Type value of 257 decimal. |
| 712 |
This documents defines the format for an HLEN value of 0x3. |
| 713 |
|
| 714 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span> |
| 715 |
|
| 716 |
The authors gratefully acknowledge the inputs, comments, and |
| 717 |
assistance offered by the members of the DVB-GBS ad hoc group on |
| 718 |
DVB-S2 encapsulation, in particular contributions on DVB-S2 |
| 719 |
transmission aspects from Rita Rinaldo, Axel Jahn, and Ulrik De Bie. |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 727 |
|
| 728 |
|
| 729 |
Juan Cantillo provided a significant contribution to the informative |
| 730 |
appendix. The authors thank Christian Praehauser for his insight and |
| 731 |
contribution on Extension Header processing issues. |
| 732 |
|
| 733 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 734 |
|
| 735 |
Security considerations for ULE are described in [<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>], and |
| 736 |
further information on security aspects of using ULE are described in |
| 737 |
the security considerations of [<a href="./rfc4259" title=""A Framework for Transmission of IP Datagrams over MPEG-2 Networks"">RFC4259</a>] and [<a href="#ref-Sec-Req" title=""Security requirements for the Unidirectional Lightweight Encapsulation (ULE) protocol"">Sec-Req</a>]. |
| 738 |
|
| 739 |
An attacker that is able to inject arbitrary TS Packets in a ULE or |
| 740 |
GSE Stream may modify layer 2 signalling information transmitted by |
| 741 |
the MPEG-2 TS-Concat extension. Since this attack requires access to |
| 742 |
the link and/or layer 2 equipment, such an attack could also directly |
| 743 |
attack signalling information sent as native TS Packets (not |
| 744 |
encapsulated by ULE/GSE). Security issues relating to the |
| 745 |
transmission and interpretation of layer 2 signalling information |
| 746 |
(including Address Resolution) within a TS Multiplex are described in |
| 747 |
[<a href="./rfc4947" title=""Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks"">RFC4947</a>]. The use of security mechanisms to protect the MPEG-2 |
| 748 |
signalling information is discussed by [<a href="#ref-Sec-Req" title=""Security requirements for the Unidirectional Lightweight Encapsulation (ULE) protocol"">Sec-Req</a>]. |
| 749 |
|
| 750 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 751 |
|
| 752 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 753 |
|
| 754 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 755 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 756 |
|
| 757 |
[<a id="ref-RFC4326">RFC4326</a>] Fairhurst, G. and B. Collini-Nocker, "Unidirectional |
| 758 |
Lightweight Encapsulation (ULE) for Transmission of IP |
| 759 |
Datagrams over an MPEG-2 Transport Stream (TS)", <a href="./rfc4326">RFC</a> |
| 760 |
<a href="./rfc4326">4326</a>, December 2005. |
| 761 |
|
| 762 |
[<a id="ref-GSE">GSE</a>] TS 102 606 "Digital Video Broadcasting (DVB); Generic |
| 763 |
Stream Encapsulation (GSE) Protocol, "European |
| 764 |
Telecommunication Standards, Institute (ETSI), 2007. |
| 765 |
|
| 766 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 767 |
|
| 768 |
[<a id="ref-ETSI-S2">ETSI-S2</a>] EN 302 307, "Digital Video Broadcasting (DVB); Second |
| 769 |
generation framing structure, channel coding and |
| 770 |
modulation systems for Broadcasting, Interactive |
| 771 |
Services, News Gathering and other broadband satellite |
| 772 |
applications", European Telecommunication Standards |
| 773 |
Institute (ETSI). |
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 783 |
|
| 784 |
|
| 785 |
[<a id="ref-S2-REQ">S2-REQ</a>] Cantillo, J. and J. Lacan, "A Design Rationale for |
| 786 |
Providing IP Services over DVB-S2 Links", Work in |
| 787 |
Progress, December 2006. |
| 788 |
|
| 789 |
[<a id="ref-Sec-Req">Sec-Req</a>] Cruickshank, H., Iyengar, S., and P. Pillai, "Security |
| 790 |
requirements for the Unidirectional Lightweight |
| 791 |
Encapsulation (ULE) protocol", Work in Progress, |
| 792 |
November 2007. |
| 793 |
|
| 794 |
[<a id="ref-IEEE-802.3">IEEE-802.3</a>] "Local and metropolitan area networks - Specific |
| 795 |
requirements Part 3: Carrier sense multiple access with |
| 796 |
collision detection (CSMA/CD) access method and physical |
| 797 |
layer specifications", IEEE 802.3, IEEE Computer |
| 798 |
Society, (also ISO/IEC 8802-3), 2002. |
| 799 |
|
| 800 |
[<a id="ref-ISO-MPEG2">ISO-MPEG2</a>] ISO/IEC DIS 13818-1:2000, "Information Technology; |
| 801 |
Generic Coding of Moving Pictures and Associated Audio |
| 802 |
Information Systems", International Organization for |
| 803 |
Standardization (ISO), 2000. |
| 804 |
|
| 805 |
[<a id="ref-RFC4259">RFC4259</a>] Montpetit, M.-J., Fairhurst, G., Clausen, H., Collini- |
| 806 |
Nocker, B., and H. Linder, "A Framework for Transmission |
| 807 |
of IP Datagrams over MPEG-2 Networks", <a href="./rfc4259">RFC 4259</a>, |
| 808 |
November 2005. |
| 809 |
|
| 810 |
[<a id="ref-RFC4947">RFC4947</a>] Fairhurst, G. and M. Montpetit, "Address Resolution |
| 811 |
Mechanisms for IP Datagrams over MPEG-2 Networks", <a href="./rfc4947">RFC</a> |
| 812 |
<a href="./rfc4947">4947</a>, July 2007. |
| 813 |
|
| 814 |
|
| 815 |
|
| 816 |
|
| 817 |
|
| 818 |
|
| 819 |
|
| 820 |
|
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. The Second-Generation DVB Transmission Specifications</span> |
| 842 |
|
| 843 |
This section provides informative background to the network-layer |
| 844 |
requirements of the second-generation DVB Transmission |
| 845 |
Specifications. The second-generation waveforms specified by the |
| 846 |
Digital Video Broadcasting project offer two main enhancements. |
| 847 |
First, more efficient physical-layer methods that employ higher-order |
| 848 |
modulation with stronger FEC and permit adaptive coding and |
| 849 |
modulation response to changes in traffic and propagation conditions. |
| 850 |
Second, at the link layer, they offer greater flexibility in framing. |
| 851 |
Support is provided for a range of stream formats including the |
| 852 |
classical Transport Stream (TS) [<a href="./rfc4259" title=""A Framework for Transmission of IP Datagrams over MPEG-2 Networks"">RFC4259</a>]. In addition, a new method |
| 853 |
called Generic Stream (GS) (or the Generic Mode) is supported. A GS |
| 854 |
can be packetized or continuous and is intended to provide native |
| 855 |
transport of other network-layer services. One such method is that |
| 856 |
provided by the Generic Stream Encapsulation (GSE) [<a href="#ref-GSE" title=""Digital Video Broadcasting (DVB); Generic Stream Encapsulation (GSE) Protocol, "">GSE</a>]. |
| 857 |
|
| 858 |
For example, the DVB-S2 [<a href="#ref-ETSI-S2" title=""Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications"">ETSI-S2</a>] transmission link sequentially |
| 859 |
multiplexes a series of baseband frames (BBFrames). Each BBFrame |
| 860 |
comprises a fixed-size 10B header and a payload. The payload carries |
| 861 |
a DataField and uses padding to fill any unused space. A stream |
| 862 |
comprises a sequence of BBFrames associated with an Input Stream |
| 863 |
Identifier (ISI) that is carried in the header of each BBFrame. The |
| 864 |
simplest scheme uses a single stream (with just one ISI value), but |
| 865 |
multiple streams are permitted. The BBFrames forming a stream may be |
| 866 |
of variable size (selected from a set of allowed sizes), and must use |
| 867 |
the same stream format (i.e., TS or GSE). Each stream represents an |
| 868 |
independent link with independent address resolution [<a href="./rfc4947" title=""Address Resolution Mechanisms for IP Datagrams over MPEG-2 Networks"">RFC4947</a>]. |
| 869 |
|
| 870 |
GSE provides functions that are equivalent to those of the |
| 871 |
Unidirectional Lightweight Encapsulation (ULE) [<a href="./rfc4326" title=""Unidirectional Lightweight Encapsulation (ULE) for Transmission of IP Datagrams over an MPEG-2 Transport Stream (TS)"">RFC4326</a>]. It |
| 872 |
supports the transmission of IP packets and other network-layer |
| 873 |
protocols. The network-layer interface resembles that of ULE, where |
| 874 |
it adopts common mechanisms for a Length field, a 16-bit Type field, |
| 875 |
and support for Extension Headers. As in ULE, GSE permits multiple |
| 876 |
address formats, indicated by the LT field (functionally equivalent |
| 877 |
to the D field in ULE). The default addressing mode uses a 6-byte |
| 878 |
NPA and a suppressed NPA address (functionally equivalent to D=1 in |
| 879 |
ULE). |
| 880 |
|
| 881 |
GSE also provides more flexible fragmentation at the interface to the |
| 882 |
physical layer (using the S and E flags). This adapts the SNDUs to a |
| 883 |
variable-sized link-layer frame, and reflects the more complex |
| 884 |
requirements in terms of fragmentation and assembly that arise when |
| 885 |
using point-to-multipoint adaptive physical layers. The integrity of |
| 886 |
a reassembled SNDU is validated using a CRC-32 in the last fragment |
| 887 |
for the corresponding PDU. |
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 895 |
|
| 896 |
|
| 897 |
Authors' Addresses |
| 898 |
|
| 899 |
Godred Fairhurst |
| 900 |
School of Engineering, |
| 901 |
University of Aberdeen, |
| 902 |
Aberdeen, AB24 3UE |
| 903 |
UK |
| 904 |
|
| 905 |
EMail: [email protected] |
| 906 |
URI: <a href="http://www.erg.abdn.ac.uk/users/gorry">http://www.erg.abdn.ac.uk/users/gorry</a> |
| 907 |
|
| 908 |
|
| 909 |
Bernhard Collini-Nocker |
| 910 |
Department of Computer Sciences, |
| 911 |
University of Salzburg, |
| 912 |
Jakob Haringer Str. 2, |
| 913 |
5020 Salzburg, |
| 914 |
Austria |
| 915 |
|
| 916 |
EMail: [email protected] |
| 917 |
URI: <a href="http://www.cosy.sbg.ac.at">http://www.cosy.sbg.ac.at</a> |
| 918 |
|
| 919 |
|
| 920 |
|
| 921 |
|
| 922 |
|
| 923 |
|
| 924 |
|
| 925 |
|
| 926 |
|
| 927 |
|
| 928 |
|
| 929 |
|
| 930 |
|
| 931 |
|
| 932 |
|
| 933 |
|
| 934 |
|
| 935 |
|
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Fairhurst & Collini-Nocker Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc5163">RFC 5163</a> Extension Formats for the ULE Encapsulation April 2008</span> |
| 951 |
|
| 952 |
|
| 953 |
Full Copyright Statement |
| 954 |
|
| 955 |
Copyright (C) The IETF Trust (2008). |
| 956 |
|
| 957 |
This document is subject to the rights, licenses and restrictions |
| 958 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 959 |
retain all their rights. |
| 960 |
|
| 961 |
This document and the information contained herein are provided on an |
| 962 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 963 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND |
| 964 |
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS |
| 965 |
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF |
| 966 |
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 967 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 968 |
|
| 969 |
Intellectual Property |
| 970 |
|
| 971 |
The IETF takes no position regarding the validity or scope of any |
| 972 |
Intellectual Property Rights or other rights that might be claimed to |
| 973 |
pertain to the implementation or use of the technology described in |
| 974 |
this document or the extent to which any license under such rights |
| 975 |
might or might not be available; nor does it represent that it has |
| 976 |
made any independent effort to identify any such rights. Information |
| 977 |
on the procedures with respect to rights in RFC documents can be |
| 978 |
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>. |
| 979 |
|
| 980 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 981 |
assurances of licenses to be made available, or the result of an |
| 982 |
attempt made to obtain a general license or permission for the use of |
| 983 |
such proprietary rights by implementers or users of this |
| 984 |
specification can be obtained from the IETF on-line IPR repository at |
| 985 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 986 |
|
| 987 |
The IETF invites any interested party to bring to its attention any |
| 988 |
copyrights, patents or patent applications, or other proprietary |
| 989 |
rights that may cover technology that may be required to implement |
| 990 |
this standard. Please address the information to the IETF at |
| 991 |
[email protected]. |
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
Fairhurst & Collini-Nocker Standards Track [Page 18] |
| 1005 |
</pre> |