| 1 |
<pre>Network Working Group L-E. Jonsson |
| 2 |
Request for Comments: 4362 G. Pelletier |
| 3 |
Obsoletes: <a href="./rfc3242">3242</a> K. Sandlund |
| 4 |
Category: Standards Track Ericsson |
| 5 |
January 2006 |
| 6 |
|
| 7 |
<span class="h1">RObust Header Compression (ROHC):</span> |
| 8 |
<span class="h1">A Link-Layer Assisted Profile for IP/UDP/RTP</span> |
| 9 |
|
| 10 |
Status of This Memo |
| 11 |
|
| 12 |
This document specifies an Internet standards track protocol for the |
| 13 |
Internet community, and requests discussion and suggestions for |
| 14 |
improvements. Please refer to the current edition of the "Internet |
| 15 |
Official Protocol Standards" (STD 1) for the standardization state |
| 16 |
and status of this protocol. Distribution of this memo is unlimited. |
| 17 |
|
| 18 |
Copyright Notice |
| 19 |
|
| 20 |
Copyright (C) The Internet Society (2006). |
| 21 |
|
| 22 |
Abstract |
| 23 |
|
| 24 |
This document defines a ROHC (Robust Header Compression) profile for |
| 25 |
compression of IP/UDP/RTP (Internet Protocol/User Datagram |
| 26 |
Protocol/Real-Time Transport Protocol) packets, utilizing |
| 27 |
functionality provided by the lower layers to increase compression |
| 28 |
efficiency by completely eliminating the header for most packets |
| 29 |
during optimal operation. The profile is built as an extension to |
| 30 |
the ROHC RTP profile. It defines additional mechanisms needed in |
| 31 |
ROHC, states requirements on the assisting layer to guarantee |
| 32 |
transparency, and specifies general logic for compression and |
| 33 |
decompression related to the usage of the header-free packet format. |
| 34 |
This document is a replacement for <a href="./rfc3242">RFC 3242</a>, which it obsoletes. |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 60 |
<a href="#section-1.1">1.1</a>. Differences from <a href="./rfc3242">RFC 3242</a> ..................................<a href="#page-5">5</a> |
| 61 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-5">5</a> |
| 62 |
<a href="#section-3">3</a>. Overview of the Link-Layer Assisted Profile .....................<a href="#page-6">6</a> |
| 63 |
<a href="#section-3.1">3.1</a>. Providing Packet Type Identification .......................<a href="#page-7">7</a> |
| 64 |
<a href="#section-3.2">3.2</a>. Replacing the Sequence Number ..............................<a href="#page-7">7</a> |
| 65 |
<a href="#section-3.3">3.3</a>. CRC Replacement ............................................<a href="#page-8">8</a> |
| 66 |
<a href="#section-3.4">3.4</a>. Applicability of This Profile ..............................<a href="#page-8">8</a> |
| 67 |
<a href="#section-4">4</a>. Additions and Exceptions Compared to ROHC RTP ...................<a href="#page-9">9</a> |
| 68 |
<a href="#section-4.1">4.1</a>. Additional Packet Types ....................................<a href="#page-9">9</a> |
| 69 |
<a href="#section-4.1.1">4.1.1</a>. No-Header Packet (NHP) ..............................<a href="#page-9">9</a> |
| 70 |
<a href="#section-4.1.2">4.1.2</a>. Context Synchronization Packet (CSP) ................<a href="#page-9">9</a> |
| 71 |
<a href="#section-4.1.3">4.1.3</a>. Context Check Packet (CCP) .........................<a href="#page-11">11</a> |
| 72 |
<a href="#section-4.2">4.2</a>. Interfaces Towards the Assisting Layer ....................<a href="#page-12">12</a> |
| 73 |
<a href="#section-4.2.1">4.2.1</a>. Interface, Compressor to Assisting Layer ...........<a href="#page-13">13</a> |
| 74 |
<a href="#section-4.2.2">4.2.2</a>. Interface, Assisting Layer to Decompressor .........<a href="#page-13">13</a> |
| 75 |
<a href="#section-4.3">4.3</a>. Optimistic Approach Agreement .............................<a href="#page-14">14</a> |
| 76 |
<a href="#section-4.4">4.4</a>. Fast Context Initialization, IR Redefinition ..............<a href="#page-15">15</a> |
| 77 |
<a href="#section-4.5">4.5</a>. Feedback Option, CV-REQUEST ...............................<a href="#page-16">16</a> |
| 78 |
<a href="#section-4.6">4.6</a>. Periodic Context Verification .............................<a href="#page-16">16</a> |
| 79 |
<a href="#section-4.7">4.7</a>. Use of Context Identifier .................................<a href="#page-16">16</a> |
| 80 |
<a href="#section-5">5</a>. Implementation Issues ..........................................<a href="#page-17">17</a> |
| 81 |
<a href="#section-5.1">5.1</a>. Implementation Parameters and Signals .....................<a href="#page-17">17</a> |
| 82 |
<a href="#section-5.1.1">5.1.1</a>. Implementation Parameters at the Compressor ........<a href="#page-17">17</a> |
| 83 |
<a href="#section-5.1.2">5.1.2</a>. Implementation Parameters at the Decompressor ......<a href="#page-19">19</a> |
| 84 |
<a href="#section-5.2">5.2</a>. Implementation over Various Link Technologies .............<a href="#page-19">19</a> |
| 85 |
<a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-20">20</a> |
| 86 |
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-20">20</a> |
| 87 |
<a href="#section-8">8</a>. Acknowledgements ...............................................<a href="#page-20">20</a> |
| 88 |
<a href="#section-9">9</a>. References .....................................................<a href="#page-20">20</a> |
| 89 |
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-20">20</a> |
| 90 |
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-21">21</a> |
| 91 |
|
| 92 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 93 |
|
| 94 |
Header compression is a technique used to compress and transparently |
| 95 |
decompress the header information of a packet on a per-hop basis, |
| 96 |
utilizing redundancy within individual packets and between |
| 97 |
consecutive packets within a packet stream. Over the years, several |
| 98 |
protocols [<a href="#ref-VJHC" title=""Compressing TCP/IP headers for low-speed serial links"">VJHC</a>, <a href="#ref-IPHC" title=""IP Header Compression"">IPHC</a>] have been developed to compress the network |
| 99 |
and transport protocol headers [<a href="#ref-IPv4" title=""Internet Protocol"">IPv4</a>, <a href="#ref-IPv6" title=""Internet Protocol, Version 6 (IPv6) Specification"">IPv6</a>, <a href="#ref-UDP" title=""User Datagram Protocol"">UDP</a>, <a href="#ref-TCP" title=""Transmission Control Protocol"">TCP</a>], and these |
| 100 |
schemes have been successful in improving efficiency over many wired |
| 101 |
bottleneck links, such as modem connections over telephone networks. |
| 102 |
In addition to IP, UDP, and TCP compression, an additional |
| 103 |
compression scheme called Compressed RTP [<a href="#ref-CRTP" title=""Compressing IP/UDP/RTP Headers for Low-Speed Serial Links"">CRTP</a>] has been developed to |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 111 |
|
| 112 |
|
| 113 |
improve compression efficiency further for real-time traffic using |
| 114 |
the Real-Time Transport Protocol [<a href="#ref-RTP" title=""RTP: A Transport Protocol for Real-Time Applications"">RTP</a>]. |
| 115 |
|
| 116 |
The schemes mentioned above have all been designed by taking into |
| 117 |
account normal assumptions about link characteristics, which |
| 118 |
traditionally have been based on wired links only. However, with an |
| 119 |
increasing number of wireless links in the Internet paths, these |
| 120 |
assumptions are no longer generally valid. In wireless environments, |
| 121 |
especially wide-coverage cellular environments, relatively high error |
| 122 |
rates are tolerated in order to allow efficient usage of the radio |
| 123 |
resources. For real-time traffic, which is more sensitive to delays |
| 124 |
than to errors, such operating conditions will be norm over, for |
| 125 |
example, 3rd generation cellular links, and header compression must |
| 126 |
therefore tolerate packet loss. However, with the previously |
| 127 |
mentioned schemes, especially for real-time traffic compressed by |
| 128 |
CRTP, high error rates have been shown to significantly degrade |
| 129 |
header compression performance [<a href="#ref-CRTPC" title=""Evaluation of CRTP Performance over Cellular Radio Networks"">CRTPC</a>]. This problem was the driving |
| 130 |
force behind the creation of the RObust Header Compression (ROHC) WG |
| 131 |
in the IETF. |
| 132 |
|
| 133 |
The ROHC WG has developed a header compression framework on top of |
| 134 |
which profiles can be defined for different protocol sets, or for |
| 135 |
different compression strategies. Due to the limited packet-loss |
| 136 |
robustness of CRTP and the demands of the cellular industry for an |
| 137 |
efficient way of transporting voice over IP over wireless, the main |
| 138 |
focus of ROHC has so far been on compression of IP/UDP/RTP headers, |
| 139 |
which are generous in size, especially when compared to the payloads |
| 140 |
often carried by packets with such headers. |
| 141 |
|
| 142 |
ROHC RTP has become a very efficient, robust, and capable compression |
| 143 |
scheme, able to compress the headers down to a total size of one |
| 144 |
octet only. Also, transparency is guaranteed to an extremely great |
| 145 |
extent, even when residual bit errors are present in compressed |
| 146 |
headers delivered to the decompressor. The requirements for RTP |
| 147 |
compression [<a href="#ref-RTP-REQ" title=""Requirements for robust IP/UDP/RTP header compression"">RTP-REQ</a>], defined by the WG before and during the |
| 148 |
development process, have thus been fulfilled. |
| 149 |
|
| 150 |
As mentioned above, the 3rd generation cellular systems, where IP |
| 151 |
will be used end-to-end, have been one of the driving forces behind |
| 152 |
ROHC RTP, and the scheme has also been designed to suit new cellular |
| 153 |
air interfaces, such as WCDMA, making it possible to run even speech |
| 154 |
services with spectrum efficiency insignificantly lower than for |
| 155 |
existing one-service circuit switched solutions [<a href="#ref-VTC2000" title=""Wireless real time IP-services enabled by header compression"">VTC2000</a>]. However, |
| 156 |
other air interfaces (such as those based on GSM and IS-95) will also |
| 157 |
be used in all-IP networks, with further implications for the header |
| 158 |
compression issue. These older air interfaces are less flexible, |
| 159 |
with radio bearers optimized for specific payload sizes. This means |
| 160 |
that not even a single octet of header can be added without using the |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 167 |
|
| 168 |
|
| 169 |
next higher fixed packet size supported by the link, something that |
| 170 |
is obviously very costly. For the already deployed speech vocoders, |
| 171 |
the spectrum efficiency over these links will thus be low compared to |
| 172 |
existing circuit-switched solutions. To achieve high spectrum |
| 173 |
efficiency overall with any application, more flexible air interfaces |
| 174 |
must be deployed, and then the ROHC RTP scheme will perform |
| 175 |
excellently, as shown for WCDMA [<a href="#ref-MOMUC01" title=""Experimental field trials results of Voice-over IP over WCDMA links"">MOMUC01</a>]. However, for deployment |
| 176 |
reasons, it is important to also provide a suitable header |
| 177 |
compression strategy for already existing vocoders and air |
| 178 |
interfaces, such as for GERAN and for CDMA2000, with minimal effects |
| 179 |
on spectral efficiency. |
| 180 |
|
| 181 |
This document describes a link-layer-assisted ROHC RTP profile, |
| 182 |
originally defined by [<a href="#ref-LLA" title=""RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP"">LLA</a>], extending ROHC RTP (profile 0x0001) |
| 183 |
[<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>], and compliant with the ROHC 0-byte requirements [<a href="#ref-0B-REQ" title=""RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression"">0B-REQ</a>]. |
| 184 |
The purpose of this profile is to provide a header-free packet format |
| 185 |
that, for a certain application behavior, can replace a majority of |
| 186 |
the 1-octet header ROHC RTP packets during normal U/O-mode operation, |
| 187 |
while still being fully transparent and complying with all the |
| 188 |
requirements of ROHC RTP [<a href="#ref-RTP-REQ" title=""Requirements for robust IP/UDP/RTP header compression"">RTP-REQ</a>]. For other applications, |
| 189 |
compression will be carried out as with normal ROHC RTP. |
| 190 |
|
| 191 |
To completely eliminate the compressed header, all functionality |
| 192 |
normally provided by the 1-octet header has to be provided by other |
| 193 |
means, typically by utilizing functionality provided by the lower |
| 194 |
layers and sacrificing efficiency for less-frequently occurring |
| 195 |
larger compressed headers. The latter is not a contradiction, since |
| 196 |
the argument for eliminating the last octet for most packets is not |
| 197 |
overall efficiency in general. It is important to remember that the |
| 198 |
purpose of this profile is to provide efficient matching of existing |
| 199 |
applications to existing link technologies, not efficiency in |
| 200 |
general. The additional complexity introduced by this profile, |
| 201 |
although minimized by a tight integration with already-existing ROHC |
| 202 |
functionality, implies that it should therefore only be used to |
| 203 |
optimize performance of specific applications over specific links. |
| 204 |
|
| 205 |
When implementing this profile over various link technologies, care |
| 206 |
must be taken to guarantee that all the functionality needed is |
| 207 |
provided by ROHC and the lower layers together. Therefore, |
| 208 |
additional documents should specify how to incorporate this profile |
| 209 |
on top of various link technologies. |
| 210 |
|
| 211 |
The profile defined by this document was originally specified by <a href="./rfc3242">RFC</a> |
| 212 |
<a href="./rfc3242">3242</a> [<a href="#ref-LLA" title=""RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP"">LLA</a>], but to address one technical flaw and clarify one |
| 213 |
implementation issue, this document has been issued to replace <a href="./rfc3242">RFC</a> |
| 214 |
<a href="./rfc3242">3242</a>, which becomes obsolete. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Differences from <a href="./rfc3242">RFC 3242</a></span> |
| 226 |
|
| 227 |
This section briefly summarizes the differences of this document from |
| 228 |
<a href="./rfc3242">RFC 3242</a>. Acronyms and terminology can be found in <a href="#section-2">Section 2</a>. |
| 229 |
|
| 230 |
The format of the CSP packet, as defined in [<a href="#ref-LLA" title=""RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP"">LLA</a>], was identified as |
| 231 |
non-interoperable when carrying a RHP header with a 3-bit or 7-bit |
| 232 |
CRC. This problem occurs because the payload has been dropped by the |
| 233 |
compressor, and the decompressor is supposed to use the payload |
| 234 |
length to infer certain fields in the uncompressed header. These |
| 235 |
fields are the IPv4 total length, the IPv6 payload length, the UDP |
| 236 |
length, and the IPv4 header checksum field (all INFERRED fields in |
| 237 |
[<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>]). To correct this flaw, the CSP packet must carry information |
| 238 |
about the payload length of the RHP packet. Therefore, the length of |
| 239 |
the RTP payload has been included in the CSP packet. |
| 240 |
|
| 241 |
This document also clarifies an unclear referencing in <a href="./rfc3242">RFC 3242</a>, |
| 242 |
where Section 4.1.3 of [<a href="#ref-LLA" title=""RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP"">LLA</a>] states that upon CRC failure, the |
| 243 |
actions of [<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>], Section 5.3.2.2.3 MUST be taken. That section |
| 244 |
specifies that detection of SN wraparound and local repair must be |
| 245 |
performed, but neither of these steps apply when the failing packet |
| 246 |
is a CCP. Therefore, upon CRC failure, actions to be taken are the |
| 247 |
ones specified in <a href="#section-5.3.2.2.3">Section 5.3.2.2.3</a>, but steps a-d only. |
| 248 |
|
| 249 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 250 |
|
| 251 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 252 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 253 |
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>]. |
| 254 |
|
| 255 |
CCP Context Check Packet |
| 256 |
CRC Cyclic Redundancy Check |
| 257 |
CSP Context Synchronization Packet |
| 258 |
LLA Link Layer Assisted ROHC RTP profile |
| 259 |
NHP No Header Packet |
| 260 |
ROHC RObust Header Compression |
| 261 |
RHP ROHC Header Packet (a non-NHP packet; i.e., RRP, CSP, or CCP) |
| 262 |
RRP ROHC RTP Packet as defined in [ROHC, profile 0x0001] |
| 263 |
|
| 264 |
Assisting layer |
| 265 |
|
| 266 |
"Assisting layer" refers to any entity implementing the interface |
| 267 |
to ROHC (<a href="#section-4.2">Section 4.2</a>). It may, for example, refer to a sub-layer |
| 268 |
used to adapt the ROHC implementation and the physical link layer. |
| 269 |
This layer is assumed to have knowledge of the physical layer |
| 270 |
synchronization. |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 279 |
|
| 280 |
|
| 281 |
Compressing side |
| 282 |
|
| 283 |
"Compressing side" refers to the combination of the header |
| 284 |
compressor, operating with the LLA profile, and its associated |
| 285 |
assisting layer. |
| 286 |
|
| 287 |
Lower layers |
| 288 |
|
| 289 |
"Lower layers", in this document, refers to entities located below |
| 290 |
ROHC in the protocol stack, including the assisting layer. |
| 291 |
|
| 292 |
ROHC RTP |
| 293 |
|
| 294 |
"ROHC RTP" refers to the IP/UDP/RTP profile as defined in [<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>]. |
| 295 |
|
| 296 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview of the Link-Layer Assisted Profile</span> |
| 297 |
|
| 298 |
The ROHC IP/UDP/RTP profile defined in [<a href="#ref-LLA" title=""RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP"">LLA</a>] and updated by this |
| 299 |
document, profile 0x0005 (hex), is designed to be used over channels |
| 300 |
that have been optimized for specific payload sizes and that |
| 301 |
therefore cannot efficiently accommodate header information when |
| 302 |
transmitted together with payloads corresponding to these optimal |
| 303 |
sizes. |
| 304 |
|
| 305 |
The LLA profile extends, and thus also inherits all functionality |
| 306 |
from, the ROCH RTP profile by defining some additional functionality |
| 307 |
and an interface from the ROHC component towards an assisting lower |
| 308 |
layer. |
| 309 |
|
| 310 |
+---------------------------------------+ |
| 311 |
| | |
| 312 |
The LLA | ROHC RTP, | |
| 313 |
profile | Profile #1 +-----------------+ |
| 314 |
| | LLA Additions | |
| 315 |
+---------------------+-----------------+ |
| 316 |
|
| 317 |
By imposing additional requirements on the lower layers compared to |
| 318 |
[<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>], it is possible to infer the information needed to maintain |
| 319 |
robust and transparent header compression, even though the headers |
| 320 |
are completely eliminated during most of the operation time. |
| 321 |
|
| 322 |
Basically, this profile replaces the smallest and most frequent ROHC |
| 323 |
U/O-mode headers with a no-header format, for which the header |
| 324 |
functionality must be provided by other means. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 335 |
|
| 336 |
|
| 337 |
Smallest header in Smallest header in |
| 338 |
ROHC RTP (profile #1) LLA (profile #5) |
| 339 |
+--+--+--+--+--+--+--+--+ ++ |
| 340 |
| 1 octet | -----> || No Header |
| 341 |
+--+--+--+--+--+--+--+--+ ++ |
| 342 |
| |
| 343 |
| Header field functionality |
| 344 |
+-------------------> provided by other means |
| 345 |
|
| 346 |
The fields present in the ROHC RTP headers for U/O-mode PT0 are the |
| 347 |
packet type identifier, the sequence number, and the CRC. The |
| 348 |
subsequent sections elaborate more on how the functionality of these |
| 349 |
fields is replaced for NHP. |
| 350 |
|
| 351 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Providing Packet Type Identification</span> |
| 352 |
|
| 353 |
All ROHC headers carry a packet type identifier, indicating to the |
| 354 |
decompressor how the header should be interpreted. This is a |
| 355 |
function that must be provided by some means in 0-byte header |
| 356 |
compression. It will be possible to distinguish ROHC RTP packets |
| 357 |
with compressed headers thanks to the packet type identifier, but a |
| 358 |
mechanism is needed to separate packets with a header from packets |
| 359 |
without a header. This function MUST therefore be provided by the |
| 360 |
assisting layer in one way or another. |
| 361 |
|
| 362 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Replacing the Sequence Number</span> |
| 363 |
|
| 364 |
From the sending application, the RTP sequence number is increased by |
| 365 |
one for each packet sent. The purpose of the sequence number is to |
| 366 |
cope with packet reordering and packet loss. If reordering or loss |
| 367 |
has occurred before the transmission point, the compressing side, if |
| 368 |
needed, can easily avoid problems by not allowing the use of a |
| 369 |
header-free packet. |
| 370 |
|
| 371 |
However, at the transmission point, loss or reordering that may occur |
| 372 |
over the link can not be anticipated and covered for. Therefore, for |
| 373 |
NHP, the assisting layer MUST guarantee in-order delivery over the |
| 374 |
link (already assumed by [<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>]), and at the receiving side, it MUST |
| 375 |
provide an indication for each packet loss over the link. This is |
| 376 |
basically the same principle as that which the VJ header compression |
| 377 |
[<a href="#ref-VJHC" title=""Compressing TCP/IP headers for low-speed serial links"">VJHC</a>] relies on. |
| 378 |
|
| 379 |
Note that guaranteeing in-order delivery and packet loss indication |
| 380 |
over the link not only makes it possible to infer the sequence number |
| 381 |
information, but also supersedes the main function of the CRC, which |
| 382 |
normally takes care of errors due to link losses and bit errors in |
| 383 |
the compressed sequence number. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. CRC Replacement</span> |
| 394 |
|
| 395 |
All context-updating RRP packets carry a CRC calculated over the |
| 396 |
uncompressed header. The CRC is used by the decompressor to verify |
| 397 |
that the updated context is correct. This verification serves three |
| 398 |
purposes in U/O-mode: |
| 399 |
|
| 400 |
1) Detection of longer losses than can be covered by the sequence |
| 401 |
number LSBs. |
| 402 |
|
| 403 |
2) Protection against failures caused by residual bit errors in |
| 404 |
compressed headers. |
| 405 |
|
| 406 |
3) Protection against faulty implementations and other causes of |
| 407 |
error. |
| 408 |
|
| 409 |
Since this profile defines an NHP packet without this CRC, care must |
| 410 |
be taken to fulfill these purposes by other means when an NHP is used |
| 411 |
as a replacement for a context-updating packet. Detection of long |
| 412 |
losses (1) is already covered, since the assisting layer MUST provide |
| 413 |
an indication of all packet losses. Furthermore, the NHP packet has |
| 414 |
one important advantage over RHP packets in that residual bit errors |
| 415 |
(2) cannot damage a header that is not even sent. |
| 416 |
|
| 417 |
It is thus reasonable to assume that compression and decompression |
| 418 |
transparency can be assured with high confidence, even without a CRC |
| 419 |
in header-free packets. However, to provide additional protection |
| 420 |
against damage propagation due to undetected residual bit errors in |
| 421 |
context-updating packets (2) or other unexpected errors (3), periodic |
| 422 |
context verifications SHOULD be performed (see <a href="#section-4.6">Section 4.6</a>). |
| 423 |
|
| 424 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Applicability of This Profile</span> |
| 425 |
|
| 426 |
The LLA profile can be used with any link technology capable of |
| 427 |
providing the required functionality described in previous sections. |
| 428 |
Thus, whether LLA or ROHC RTP should be implemented depends on the |
| 429 |
characteristics of the link itself. For most RTP packet streams, LLA |
| 430 |
will work exactly as ROHC RTP, and it will have a higher compression |
| 431 |
efficiency for packet streams with certain characteristics. LLA will |
| 432 |
never have a lower compression efficiency than ROHC RTP. |
| 433 |
|
| 434 |
Note as well that LLA, like all other ROHC profiles, is fully |
| 435 |
transparent to any packet stream reaching the compressor. LLA does |
| 436 |
not make any assumptions about the packet stream but will perform |
| 437 |
optimally for packet streams with certain characteristics, e.g., |
| 438 |
synchronized streams exactly timed with the assisting link over which |
| 439 |
the LLA profile is implemented. |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 447 |
|
| 448 |
|
| 449 |
The LLA profile is obviously not applicable if the UDP checksum (2 |
| 450 |
bytes) is enabled, which is always the case for IPv6/UDP. For |
| 451 |
IPv4/UDP, the sender may choose to disable the UDP checksum. |
| 452 |
|
| 453 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Additions and Exceptions Compared to ROHC RTP</span> |
| 454 |
|
| 455 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Additional Packet Types</span> |
| 456 |
|
| 457 |
The LLA profile defines three new packet types to be used in addition |
| 458 |
to the RRP packet types defined by [<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>]. The following sections |
| 459 |
describe these packet types and their purpose in detail. |
| 460 |
|
| 461 |
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>. No-Header Packet (NHP)</span> |
| 462 |
|
| 463 |
A No-Header Packet (NHP) is a packet that consists only of the |
| 464 |
payload of the original packet. The NHP MAY be used when only the |
| 465 |
sequence information needs to be conveyed to the decompressor. In |
| 466 |
other words, the NHP can be used when all header fields are either |
| 467 |
unchanged or follow the currently established change pattern. In |
| 468 |
addition, there are some considerations for the use of the NHP (see |
| 469 |
sections <a href="#section-4.3">4.3</a>, <a href="#section-4.5">4.5</a>, and <a href="#section-4.6">4.6</a>). An LLA compressor is not allowed to |
| 470 |
deliver NHP packets when operating in R-mode. |
| 471 |
|
| 472 |
The assisting layer MAY send the NHP for RTP SN = X only if an NHP |
| 473 |
was delivered by the LLA compressor AND the assisting layer can |
| 474 |
guarantee that the decompressor will infer the proper sequencing for |
| 475 |
this NHP. This guarantee is based on the confidence that the |
| 476 |
decompressor |
| 477 |
|
| 478 |
a) has the means to infer proper sequencing for the packet |
| 479 |
corresponding to SN = X-1, AND |
| 480 |
|
| 481 |
b) has either received a loss indication or the packet itself for |
| 482 |
the packet corresponding to SN = X-1. |
| 483 |
|
| 484 |
Updating properties: NHP packets update context (RTP Sequence |
| 485 |
Number). |
| 486 |
|
| 487 |
<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>. Context Synchronization Packet (CSP)</span> |
| 488 |
|
| 489 |
The case where the packet stream overruns the channel bandwidth may |
| 490 |
lead to discarded data, which may result in decompressor context |
| 491 |
invalidation. It might therefore be beneficial to send a packet with |
| 492 |
only the header information and to discard the payload. This would |
| 493 |
be helpful to maintain synchronization of the decompressor context |
| 494 |
while efficiently using the available bandwidth. |
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 503 |
|
| 504 |
|
| 505 |
This case can be handled with the Context Synchronization Packet |
| 506 |
(CSP), which has the following format: |
| 507 |
|
| 508 |
0 1 2 3 4 5 6 7 |
| 509 |
+---+---+---+---+---+---+---+---+ |
| 510 |
| 1 1 1 1 1 0 1 0 | Packet type identifier |
| 511 |
+===+===+===+===+===+===+===+===+ |
| 512 |
/ RTP Payload Length / 2 octets |
| 513 |
+---+---+---+---+---+---+---+---+ |
| 514 |
: ROHC header without padding : |
| 515 |
: see [ROHC, <a href="#section-5.7">Section 5.7</a>] : |
| 516 |
+---+---+---+---+---+---+---+---+ |
| 517 |
|
| 518 |
RTP Payload Length: This field is the length of the payload carried |
| 519 |
inside the RTP header, stored in network byte |
| 520 |
order. That is, this field will be set by the |
| 521 |
compressor to (UDP length - size of the UDP |
| 522 |
header - size of the RTP header including CSRC |
| 523 |
identifiers). |
| 524 |
|
| 525 |
Updating properties: CSP maintains the updating properties of the |
| 526 |
ROHC header it carries. |
| 527 |
|
| 528 |
The CSP is defined by one of the unused packet type identifiers from |
| 529 |
ROHC RTP, carried in the one-octet base header. As for any ROHC |
| 530 |
packet, except the NHP, the packet may begin with ROHC padding and/or |
| 531 |
feedback. It may also carry context identification after the packet |
| 532 |
type identifier. It is possible to have two CID fields present, one |
| 533 |
after the packet type ID and one within the encapsulated ROHC header. |
| 534 |
If a decompressor receives a CSP with two non-equal CID values |
| 535 |
included, the packet MUST be discarded. ROHC segmentation may also |
| 536 |
be applied to the CSP. |
| 537 |
|
| 538 |
In the CSP packet, the payload has been dropped by the compressor. |
| 539 |
However, the decompressor is supposed to use the payload length to |
| 540 |
infer certain fields in the uncompressed header (the IPv4 total |
| 541 |
length, the IPv6 payload length, the UDP length, and the IPv4 header |
| 542 |
checksum field). When dropping the payload, the CSP packet needs to |
| 543 |
contain information about the payload length carried in the RHP |
| 544 |
packet. Therefore, the length of the RTP payload is carried in the |
| 545 |
CSP packet. When the decompressor receives a CSP packet, it can use |
| 546 |
the RTP payload length field to calculate the value of fields |
| 547 |
classified as INFERRED in [<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>] when attempting to verify a 3- or |
| 548 |
7-bit CRC carried in the RHP header enclosed in the CSP. |
| 549 |
|
| 550 |
Note that when the decompressor has received and processed a CSP, the |
| 551 |
packet (including any possible data following the CSP encapsulated |
| 552 |
compressed header) MUST be discarded. |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h4"><a class="selflink" id="section-4.1.3" href="#section-4.1.3">4.1.3</a>. Context Check Packet (CCP)</span> |
| 562 |
|
| 563 |
A Context Check Packet (CCP), which does not carry any payload but |
| 564 |
only an optional CRC value in addition to the packet type identifier, |
| 565 |
is defined. |
| 566 |
|
| 567 |
The purpose of the CCP is to provide a useful packet that MAY be sent |
| 568 |
by a synchronized physical link layer in the case where data must be |
| 569 |
sent at fixed intervals, even if no compressed packet is available. |
| 570 |
Whether the CCP is sent over the link and delivered to the |
| 571 |
decompressor is decided by the assisting layer. The CCP has the |
| 572 |
following format: |
| 573 |
|
| 574 |
0 1 2 3 4 5 6 7 |
| 575 |
+---+---+---+---+---+---+---+---+ |
| 576 |
| 1 1 1 1 1 0 1 1 | Packet type identifier |
| 577 |
+===+===+===+===+===+===+===+===+ |
| 578 |
| C | CRC | |
| 579 |
+---+---+---+---+---+---+---+---+ |
| 580 |
|
| 581 |
C: C = 0 indicates that the CRC field is not used. |
| 582 |
C = 1 indicates that a valid CRC is present. |
| 583 |
|
| 584 |
Updating properties: CCP packets do not update context. |
| 585 |
|
| 586 |
The CCP is defined by one of the unused packet type identifiers from |
| 587 |
ROHC RTP, carried in the first octet of the base header. The first |
| 588 |
bit of the second octet, the C bit, indicates whether the CRC field |
| 589 |
is used. If C=1, the CRC field MUST be set to the 7-bit CRC |
| 590 |
calculated over the original uncompressed header defined in [ROHC, |
| 591 |
<a href="#section-5.9.2">Section 5.9.2</a>]. As for any ROHC packet, except NHP, the packet MAY |
| 592 |
begin with ROHC padding and/or carry context identification. |
| 593 |
|
| 594 |
The use of the CRC field to perform decompressor context verification |
| 595 |
is optional and is therefore a compressor implementation issue. |
| 596 |
However, a CCP MUST always be made available to the assisting layer. |
| 597 |
|
| 598 |
If the assisting layer receives CCPs with the C bit set (C=1) from |
| 599 |
the compressor, it MUST use the last CCP received if a CCP is to be |
| 600 |
sent, i.e., the CCP corresponding to the last non-CCP packet sent |
| 601 |
(NHP, RRP or CSP). An assisting layer MAY use the CCP for other |
| 602 |
purposes, such as signaling a packet loss before the link. |
| 603 |
|
| 604 |
The decompressor is REQUIRED to handle a CCP received with the C bit |
| 605 |
set (C=1), indicating a valid CRC field, and to perform context |
| 606 |
verification. The received CRC MUST then be applied to the last |
| 607 |
decompressed packet, unless a packet loss indication was previously |
| 608 |
received. Upon CRC failure, actions MUST be taken as specified in |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 615 |
|
| 616 |
|
| 617 |
[ROHC, <a href="#section-5.3.2.2.3">Section 5.3.2.2.3</a>, steps a-d only]. A CCP received with C=0 |
| 618 |
MUST be ignored by the decompressor. The decompressor is not allowed |
| 619 |
to make any further interpretation of the CCP. |
| 620 |
|
| 621 |
When using the 7-bit CRC in the CCP packet to verify the context, the |
| 622 |
decompressor needs to have access to the entire uncompressed header |
| 623 |
of the latest packet decompressed. Some implementations of [<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>] |
| 624 |
might not save the values of INFERRED fields. An implementation of |
| 625 |
ROHC LLA MUST save these fields in the decompressor context to be |
| 626 |
able to successfully verify CCP packets. |
| 627 |
|
| 628 |
The use of CCP by an assisting layer is optional and depends on the |
| 629 |
characteristics of the actual link. Whether it is used MUST |
| 630 |
therefore be specified in link-layer implementation specifications |
| 631 |
for this profile. |
| 632 |
|
| 633 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Interfaces Towards the Assisting Layer</span> |
| 634 |
|
| 635 |
This profile relies on the lower layers to provide the necessary |
| 636 |
functionality to allow NHP packets to be sent. This interaction |
| 637 |
between LLA and the assisting layer is defined as interfaces between |
| 638 |
the LLA compressor/decompressor and the LLA applicable link |
| 639 |
technology. |
| 640 |
|
| 641 |
| | |
| 642 |
+ + |
| 643 |
+-------------------------+ +-------------------------+ |
| 644 |
| ROHC RTP HC | | ROHC RTP HD | |
| 645 |
+-------------------------+ +-------------------------+ |
| 646 |
| LLA profile | | LLA profile | |
| 647 |
+=========================+ +=========================+ |
| 648 |
| Interface | | Interface | |
| 649 |
| ROHC to assisting layer | | Assisting layer to ROHC | |
| 650 |
+=========================+ +=========================+ |
| 651 |
| Applicable | | Applicable | |
| 652 |
| link technology | | link technology | |
| 653 |
+=========================+ +=========================+ |
| 654 |
| | |
| 655 |
+------>---- CHANNEL ---->-----+ |
| 656 |
|
| 657 |
The figure above shows the various levels, as defined in [<a href="#ref-ROHC" title=""RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed "">ROHC</a>] and |
| 658 |
this document, constituting a complete implementation of the LLA |
| 659 |
profile. The figure also underlines the need for additional |
| 660 |
documents to specify how to implement these interfaces for a link |
| 661 |
technology for which this profile is relevant. |
| 662 |
|
| 663 |
This section defines the information to be exchanged between the LLA |
| 664 |
compressor and the assisting layer for this profile to operate |
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 671 |
|
| 672 |
|
| 673 |
properly. While it does define semantics, it does not specify how |
| 674 |
these interfaces are to be implemented. |
| 675 |
|
| 676 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Interface, Compressor to Assisting Layer</span> |
| 677 |
|
| 678 |
This section defines the interface semantics between the compressor |
| 679 |
and the assisting layer, providing rules for packet delivery from the |
| 680 |
compressor. |
| 681 |
|
| 682 |
The interface defines the following parameters: RRP, RRP segmentation |
| 683 |
flag, CSP, CSP segmentation flag, NHP, and RTP Sequence Number. All |
| 684 |
parameters, except the NHP, MUST always be delivered to the assisting |
| 685 |
layer. This leads to two possible delivery scenarios: |
| 686 |
|
| 687 |
a. RRP, CSP, CCP, NHP, and RTP Sequence Number are delivered, |
| 688 |
along with the corresponding segmentation flags, set |
| 689 |
accordingly. |
| 690 |
|
| 691 |
This corresponds to the case when the compressor allows sending |
| 692 |
of an NHP packet, with or without segmentation applied to the |
| 693 |
corresponding RRP/CSP packets. |
| 694 |
|
| 695 |
Recall that delivery of an NHP packet occurs when the ROHC RTP |
| 696 |
compressor would have used a ROHC UO-0. |
| 697 |
|
| 698 |
b. RRP, CSP, CCP, and RTP Sequence Number are delivered, along |
| 699 |
with the corresponding segmentation flags, set accordingly. |
| 700 |
|
| 701 |
This corresponds to the case when the compressor does not allow |
| 702 |
sending of an NHP packet. Segmentation might be applied to the |
| 703 |
corresponding RRP and CSP packets. |
| 704 |
|
| 705 |
Segmentation may be applied independently to an RRP or a CSP packet |
| 706 |
if its size exceeds the largest value provided in the PREFERRED |
| 707 |
PACKET_SIZES list and if the LARGE_PACKET_ALLOWED parameter is set to |
| 708 |
false. The segmentation flags are explicitly stated in the interface |
| 709 |
definition to emphasize that the RRP and the CSP may be delivered by |
| 710 |
the compressor as segmented packets. |
| 711 |
|
| 712 |
The RTP SN MUST be delivered for each packet by the compressor to |
| 713 |
allow the assisting layer to maintain the necessary sequencing |
| 714 |
information. |
| 715 |
|
| 716 |
<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>. Interface, Assisting Layer to Decompressor</span> |
| 717 |
|
| 718 |
Here the interface semantics between the assisting layer and the |
| 719 |
decompressor are defined, providing simple rules for the delivery of |
| 720 |
received packets to the decompressor. The decompressor needs a way |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 727 |
|
| 728 |
|
| 729 |
to distinguish NHP packets from RHP packets. Also, when receiving |
| 730 |
packets without a header, the decompressor needs a way to infer the |
| 731 |
sequencing information to keep synchronization between the received |
| 732 |
payload and the sequence information of the decompressed headers. To |
| 733 |
achieve this, the decompressor MUST receive the following from the |
| 734 |
assisting layer: |
| 735 |
|
| 736 |
- an indication for each packet loss over the link between the |
| 737 |
compressing and decompressing sides for CID=0. |
| 738 |
|
| 739 |
- the received packet together with an indication of whether the |
| 740 |
packet received is an NHP. |
| 741 |
|
| 742 |
Note that the context is updated from a packet loss indication. |
| 743 |
|
| 744 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Optimistic Approach Agreement</span> |
| 745 |
|
| 746 |
ROHC defines an optimistic approach for updates to reduce the header |
| 747 |
overhead. This approach is fully exploited in the Optimistic and |
| 748 |
Unidirectional modes of operation. Due to the presence of a CRC in |
| 749 |
all compressed headers, the optimistic approach is defined as a |
| 750 |
compressor issue only because the decompressor will always be able to |
| 751 |
detect an invalid context through the CRC verification. |
| 752 |
|
| 753 |
However, no CRC is present in the NHP packet defined by the LLA |
| 754 |
profile. Therefore, the loss of an RHP packet updating the context |
| 755 |
may not always be detected. To avoid this problem, the compressing |
| 756 |
and decompressing sides must agree on the principles for the |
| 757 |
optimistic approach, and the agreed principles MUST be enforced not |
| 758 |
only by the compressor but also by the transmitting assisting layer. |
| 759 |
If, for example, three consecutive updates are sent to convey a |
| 760 |
header field change, the decompressor must know this and invalidate |
| 761 |
the context if three or more consecutive physical packets are lost. |
| 762 |
Note that the mechanism used to enforce the optimistic approach must |
| 763 |
be reinitialized if a new field change needs to be conveyed while the |
| 764 |
compressing side is already sending packets to convey non-linear |
| 765 |
context updates. |
| 766 |
|
| 767 |
An LLA decompressor MUST use the optimistic approach knowledge to |
| 768 |
detect possible context loss events. If context loss is suspected, |
| 769 |
it MUST invalidate the context and not forward any packets before the |
| 770 |
context has been synchronized. |
| 771 |
|
| 772 |
It is REQUIRED that all documents describing how the LLA profile is |
| 773 |
implemented over a certain link technology define how the optimistic |
| 774 |
approach is agreed to between the compressing side and the |
| 775 |
decompressing side. It could be handled with a fixed principle, with |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 783 |
|
| 784 |
|
| 785 |
negotiation at startup, or by other means, but the method must be |
| 786 |
unambiguously defined. |
| 787 |
|
| 788 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Fast Context Initialization, IR Redefinition</span> |
| 789 |
|
| 790 |
As initial IR packets might overrun the channel bandwidth and |
| 791 |
significantly delay decompressor context establishment, it might be |
| 792 |
beneficial to initially discard the payload. This allows state |
| 793 |
transitions and higher compression efficiency to be achieved with |
| 794 |
minimal delay. |
| 795 |
|
| 796 |
To serve this purpose, the D-bit from the basic structure of the ROHC |
| 797 |
RTP IR packet [ROHC, <a href="#section-5.7.7.1">Section 5.7.7.1</a>] is redefined for the LLA |
| 798 |
profile. For D=0 (no dynamic chain), the meaning of the D-bit is |
| 799 |
extended to indicate that the payload has been discarded when |
| 800 |
assembling the IR packet. All other fields keep their meanings as |
| 801 |
defined for ROHC RTP. |
| 802 |
|
| 803 |
The resulting structure, using small CIDs and CID=0, becomes: |
| 804 |
|
| 805 |
0 1 2 3 4 5 6 7 |
| 806 |
+---+---+---+---+---+---+---+---+ |
| 807 |
| 1 | 1 | 1 | 1 | 1 | 1 | 0 | D | |
| 808 |
+---+---+---+---+---+---+---+---+ |
| 809 |
| Profile | 1 octet |
| 810 |
+---+---+---+---+---+---+---+---+ |
| 811 |
| CRC | 1 octet |
| 812 |
+---+---+---+---+---+---+---+---+ |
| 813 |
| Static | variable length |
| 814 |
| chain | |
| 815 |
- - - - - - - - - - - - - - - - |
| 816 |
| Dynamic | not present if D = 0 |
| 817 |
| chain | present if D = 1, variable length |
| 818 |
- - - - - - - - - - - - - - - - |
| 819 |
| Payload | not present if D = 0 |
| 820 |
| | present if D = 1, variable length |
| 821 |
- - - - - - - - - - - - - - - - |
| 822 |
|
| 823 |
D: D = 0 indicates that the dynamic chain is not present |
| 824 |
and that the payload has been discarded. |
| 825 |
|
| 826 |
After an IR packet with D=0 has been processed by the decompressor, |
| 827 |
the packet MUST be discarded. |
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Feedback Option, CV-REQUEST</span> |
| 842 |
|
| 843 |
The CV-REQUEST option MAY be used by the decompressor to request an |
| 844 |
RRP or CSP for context verification. This option should be used if |
| 845 |
only NHPs have been received for a long time and the context |
| 846 |
therefore has not been verified recently. |
| 847 |
|
| 848 |
+---+---+---+---+---+---+---+---+ |
| 849 |
| Opt Type = 8 | Opt Len = 0 | |
| 850 |
+---+---+---+---+---+---+---+---+ |
| 851 |
|
| 852 |
If the compressor receives a feedback packet with this option, the |
| 853 |
next packet compressed SHOULD NOT be delivered to the assisting layer |
| 854 |
as an NHP. |
| 855 |
|
| 856 |
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. Periodic Context Verification</span> |
| 857 |
|
| 858 |
As described in <a href="#section-3.3">Section 3.3</a>, transparency is expected to be |
| 859 |
guaranteed by the functionality provided by the lower layers. This |
| 860 |
ROHC profile would therefore be at least as reliable as the older |
| 861 |
header compression schemes [<a href="#ref-VJHC" title=""Compressing TCP/IP headers for low-speed serial links"">VJHC</a>, <a href="#ref-IPHC" title=""IP Header Compression"">IPHC</a>, <a href="#ref-CRTP" title=""Compressing IP/UDP/RTP Headers for Low-Speed Serial Links"">CRTP</a>], which do not make use |
| 862 |
of a header compression CRC. However, since ROHC RTP normally is |
| 863 |
extremely safe to use from a transparency point of view, it would be |
| 864 |
desirable to be able to achieve this with LLA also. |
| 865 |
|
| 866 |
To provide an additional guarantee for transparency and also catch |
| 867 |
unexpected errors, such as errors due to faulty implementations, it |
| 868 |
is RECOMMENDED that context updating packets be sent periodically, |
| 869 |
even when the compressor logic allows NHP packets to be used. |
| 870 |
|
| 871 |
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. Use of Context Identifier</span> |
| 872 |
|
| 873 |
Since an NHP cannot carry a context identifier (CID), there is a |
| 874 |
restriction on how this profile may be used, related to context |
| 875 |
identification. Independent of which CID size has been negotiated, |
| 876 |
NHP packets can only be used for CID=0. If the decompressor receives |
| 877 |
an NHP packet, it can only belong to CID=0. |
| 878 |
|
| 879 |
Note that if multiple packet streams are handled by a compressor |
| 880 |
operating using LLA, the assisting layer must, in case of physical |
| 881 |
packet loss, be able to tell for which CID the loss occurred, or at |
| 882 |
least it MUST be able to tell if packets with CID=0 (packet stream |
| 883 |
with NHPs) have been lost. |
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Implementation Issues</span> |
| 898 |
|
| 899 |
This document specifies mechanisms for the protocol and leaves |
| 900 |
details on the use of these mechanisms to the implementers. The |
| 901 |
present section aims to provide guidelines, ideas, and suggestions |
| 902 |
for implementation of LLA. |
| 903 |
|
| 904 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Implementation Parameters and Signals</span> |
| 905 |
|
| 906 |
As described in [ROHC, <a href="#section-6.3">Section 6.3</a>], implementations use parameters |
| 907 |
to set up configuration information and to stipulate how a ROHC |
| 908 |
implementation is to operate. The following parameters are |
| 909 |
additions, useful to LLA, to the parameter set defined for ROHC RTP |
| 910 |
implementations. Note that if the PREFERRED_PACKET_SIZES parameters |
| 911 |
defined here are used, they obsolete all PACKET_SIZE and PAYLOAD_SIZE |
| 912 |
parameters of ROHC RTP. |
| 913 |
|
| 914 |
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Implementation Parameters at the Compressor</span> |
| 915 |
|
| 916 |
ALWAYS_PAD -- value: boolean |
| 917 |
|
| 918 |
This parameter may be set by an external entity to specify to the |
| 919 |
compressor that every RHP packet MUST be padded with ROHC padding |
| 920 |
of one octet, minimum. |
| 921 |
|
| 922 |
The assisting layer MUST provide a packet type identification. If |
| 923 |
no field is available for this purpose from the protocol at the |
| 924 |
link layer, then a leading sequence may be used to distinguish RHP |
| 925 |
packets from NHP packets. Although the use of a leading sequence |
| 926 |
is obviously not efficient, since it sacrifices efficiency for RHP |
| 927 |
packets, the efficiency loss should be insignificant because the |
| 928 |
leading sequence applies only to packets with headers in order to |
| 929 |
favor the use of packets without headers. If a leading sequence |
| 930 |
is desired for RHP identification, the lower layer MAY use ROHC |
| 931 |
padding for the leading sequence by setting the ALWAYS_PAD |
| 932 |
parameter. Note that in such cases, possible collisions of the |
| 933 |
padding with the NHP payload must be avoided. |
| 934 |
|
| 935 |
By default, this parameter is set to FALSE. |
| 936 |
|
| 937 |
PREFERRED_PACKET_SIZES -- list of: |
| 938 |
SIZE -- value: integer (octets) |
| 939 |
RESTRICTED_TYPE -- values: [NHP_ONLY, RHP_ONLY, NO_RESTRICTION] |
| 940 |
|
| 941 |
This parameter set governs which packet sizes are preferred by the |
| 942 |
assisting layer. If this parameter set is used, all RHP packets |
| 943 |
MUST be padded to fit the smallest possible preferred size. If |
| 944 |
the size of the unpadded packet (or, in the case of ALWAYS_PAD |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Jonsson, et al. 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="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 951 |
|
| 952 |
|
| 953 |
being set, the packet with minimal one-octet padding) is larger |
| 954 |
than the maximal preferred packet size, the compressor has two |
| 955 |
options. Either it may deliver this larger packet with an |
| 956 |
arbitrary size, or it may split the packet into several segments |
| 957 |
using ROHC segmentation and pad each segment to one of the |
| 958 |
preferred sizes. Which method to use depends on the value of the |
| 959 |
LARGE_PACKETS_ALLOWED parameter below. |
| 960 |
|
| 961 |
NHP packets can be delivered to the lower layer only if the |
| 962 |
payload size is part of the preferred packet size set. |
| 963 |
Furthermore, if RESTRICTED_TYPE is set to one of NHP_ONLY or |
| 964 |
RHP_ONLY for any of the preferred packet sizes, that size is |
| 965 |
allowed only for packets of the specified type. |
| 966 |
|
| 967 |
By default, no preferred packet sizes are specified. When sizes |
| 968 |
are specified, the default value for RESTRICTED_TYPE is |
| 969 |
NO_RESTRICTION. |
| 970 |
|
| 971 |
LARGE_PACKETS_ALLOWED -- value: boolean |
| 972 |
|
| 973 |
This parameter may be set by an external entity to specify how to |
| 974 |
handle packets that do not fit any of the preferred packet sizes |
| 975 |
specified. If it is set to TRUE, the compressor MUST deliver the |
| 976 |
larger packet as-is and MUST NOT use segmentation. If it is set |
| 977 |
to FALSE, the ROHC segmentation scheme MUST be used to split the |
| 978 |
packet into two or more segments, and each segment MUST further be |
| 979 |
padded to fit one of the preferred packet sizes. |
| 980 |
|
| 981 |
By default, this parameter is set to TRUE, which means that |
| 982 |
segmentation is disabled. |
| 983 |
|
| 984 |
VERIFICATION_PERIOD -- value: integer |
| 985 |
|
| 986 |
This parameter may be set by an external entity to specify to the |
| 987 |
compressor the minimum frequency with which a packet validating |
| 988 |
the context must be sent. This tells the compressor that a packet |
| 989 |
containing a CRC field MUST be sent at least once every N packets, |
| 990 |
where N=VERIFICATION_PERIOD (see <a href="#section-4.6">Section 4.6</a>). |
| 991 |
|
| 992 |
By default, this parameter is set to 0, which indicates that |
| 993 |
periodical verifications are disabled. |
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Jonsson, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. Implementation Parameters at the Decompressor</span> |
| 1010 |
|
| 1011 |
NHP_PACKET -- value: boolean |
| 1012 |
|
| 1013 |
This parameter informs the decompressor that the packet being |
| 1014 |
delivered is an NHP packet. The decompressor MUST accept this |
| 1015 |
packet type indicator from the lower layer. An assisting layer |
| 1016 |
MUST set this indicator to true for every NHP packet delivered, |
| 1017 |
and to false for any other packet. |
| 1018 |
|
| 1019 |
PHYSICAL_PACKET_LOSS -- signal |
| 1020 |
|
| 1021 |
This signal indicates to the decompressor that a packet has been |
| 1022 |
lost on the link between the compressing and the decompressing |
| 1023 |
sides, due to a physical link error. The signal is given once for |
| 1024 |
each packet that was lost, and a decompressor must increase the |
| 1025 |
sequence number accordingly when this signal is received. |
| 1026 |
|
| 1027 |
PRE_LINK_PACKET_LOSS -- signal |
| 1028 |
|
| 1029 |
This signal tells the decompressor to increase the sequence number |
| 1030 |
due to a gap in the sequencing not related to a physical link |
| 1031 |
error. A receiving assisting layer may, for example, use this |
| 1032 |
signal to indicate to the decompressor that a packet was lost |
| 1033 |
before the compressor, or that a packet was discarded by the |
| 1034 |
transmitting assisting layer. |
| 1035 |
|
| 1036 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Implementation over Various Link Technologies</span> |
| 1037 |
|
| 1038 |
This document provides the semantics and requirements of the |
| 1039 |
interface needed from the ROHC compressor and decompressor towards |
| 1040 |
the assisting layer to perform link-layer-assisted header |
| 1041 |
compression. |
| 1042 |
|
| 1043 |
However, this document does not provide any link-layer-specific |
| 1044 |
operational information, except for some implementation suggestions. |
| 1045 |
Further details about how this profile is to be implemented over |
| 1046 |
various link technologies must be described in other documents, where |
| 1047 |
specific characteristics of each link layer can be taken into account |
| 1048 |
to provide optimal usage of this profile. |
| 1049 |
|
| 1050 |
These specifications MAY use a packet-type bit pattern unused by this |
| 1051 |
profile to implement signaling on the lower layer. The pattern |
| 1052 |
available to lower layer implementations is [11111001]. |
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Jonsson, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 1066 |
|
| 1067 |
ROHC profile identifier 0x0005 has been reserved by the IANA for the |
| 1068 |
IP/UDP/RTP profile defined in this document. |
| 1069 |
|
| 1070 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 1071 |
|
| 1072 |
The security considerations of ROHC RTP [ROHC, <a href="#section-7">Section 7</a>] apply also |
| 1073 |
to this document, with one addition: in the case of a denial-of- |
| 1074 |
service attack scenario where an intruder injects bogus CCP packets |
| 1075 |
using random CRC values onto the link, the CRC check will fail for |
| 1076 |
incorrect reasons at the decompressor side. This would obviously |
| 1077 |
greatly reduce the advantages of ROHC and any extra efficiency |
| 1078 |
provided by this profile due to unnecessary context invalidation, |
| 1079 |
feedback messages, and refresh packets. However, the same remarks |
| 1080 |
related to the presence of such an intruder apply. |
| 1081 |
|
| 1082 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span> |
| 1083 |
|
| 1084 |
The authors would like to thank Lila Madour, Ulises Olvera-Hernandez, |
| 1085 |
and Francis Lupien for input regarding the typical links in which LLA |
| 1086 |
can be applied. Thanks also to Mikael Degermark for fruitful |
| 1087 |
discussions that led to improvements of this profile, and to Zhigang |
| 1088 |
Liu for many valuable comments. |
| 1089 |
|
| 1090 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 1091 |
|
| 1092 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span> |
| 1093 |
|
| 1094 |
[<a id="ref-ROHC">ROHC</a>] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H., |
| 1095 |
Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le, K., |
| 1096 |
Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, |
| 1097 |
T., Yoshimura, T., and H. Zheng, "RObust Header Compression |
| 1098 |
(ROHC): Framework and four profiles: RTP, UDP, ESP, and |
| 1099 |
uncompressed ", <a href="./rfc3095">RFC 3095</a>, July 2001. |
| 1100 |
|
| 1101 |
[<a id="ref-IPv4">IPv4</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>, September |
| 1102 |
1981. |
| 1103 |
|
| 1104 |
[<a id="ref-IPv6">IPv6</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6 |
| 1105 |
(IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998. |
| 1106 |
|
| 1107 |
[<a id="ref-UDP">UDP</a>] Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>, |
| 1108 |
August 1980. |
| 1109 |
|
| 1110 |
[<a id="ref-RTP">RTP</a>] Schulzrinne, H., Casner, S., Frederick, R., and V. |
| 1111 |
Jacobson, "RTP: A Transport Protocol for Real-Time |
| 1112 |
Applications", STD 64, <a href="./rfc3550">RFC 3550</a>, July 2003. |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Jonsson, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1122 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1123 |
|
| 1124 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span> |
| 1125 |
|
| 1126 |
[<a id="ref-LLA">LLA</a>] Jonsson, L-E. and G. Pelletier, "RObust Header Compression |
| 1127 |
(ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP", <a href="./rfc3242">RFC</a> |
| 1128 |
<a href="./rfc3242">3242</a>, April 2002. |
| 1129 |
|
| 1130 |
[<a id="ref-TCP">TCP</a>] Postel, J., "Transmission Control Protocol", STD 7, <a href="./rfc793">RFC</a> |
| 1131 |
<a href="./rfc793">793</a>, September 1981. |
| 1132 |
|
| 1133 |
[<a id="ref-RTP-REQ">RTP-REQ</a>] Degermark, M., "Requirements for robust IP/UDP/RTP header |
| 1134 |
compression", <a href="./rfc3096">RFC 3096</a>, July 2001. |
| 1135 |
|
| 1136 |
[<a id="ref-0B-REQ">0B-REQ</a>] Jonsson, L-E., "RObust Header Compression (ROHC): |
| 1137 |
Requirements and Assumptions for 0-byte IP/UDP/RTP |
| 1138 |
Compression", <a href="./rfc3243">RFC 3243</a>, April 2002. |
| 1139 |
|
| 1140 |
[<a id="ref-VJHC">VJHC</a>] Jacobson, V., "Compressing TCP/IP headers for low-speed |
| 1141 |
serial links", <a href="./rfc1144">RFC 1144</a>, February 1990. |
| 1142 |
|
| 1143 |
[<a id="ref-IPHC">IPHC</a>] Degermark, M., Nordgren, B., and S. Pink, "IP Header |
| 1144 |
Compression", <a href="./rfc2507">RFC 2507</a>, February 1999. |
| 1145 |
|
| 1146 |
[<a id="ref-CRTP">CRTP</a>] Casner, S. and V. Jacobson, "Compressing IP/UDP/RTP Headers |
| 1147 |
for Low-Speed Serial Links", <a href="./rfc2508">RFC 2508</a>, February 1999. |
| 1148 |
|
| 1149 |
[<a id="ref-CRTPC">CRTPC</a>] Degermark, M., Hannu, H., Jonsson, L-E. and K. Svanbro, |
| 1150 |
"Evaluation of CRTP Performance over Cellular Radio |
| 1151 |
Networks", IEEE Personal Communications Magazine, Volume 7, |
| 1152 |
number 4, pp. 20-25, August 2000. |
| 1153 |
|
| 1154 |
[<a id="ref-VTC2000">VTC2000</a>] Svanbro, K., Hannu, H., Jonsson, L-E. and M. Degermark, |
| 1155 |
"Wireless real time IP-services enabled by header |
| 1156 |
compression", proceedings of IEEE VTC2000, May 2000. |
| 1157 |
|
| 1158 |
[<a id="ref-MOMUC01">MOMUC01</a>] Liu, G., et al., "Experimental field trials results of |
| 1159 |
Voice-over IP over WCDMA links", MoMuC'01 - The |
| 1160 |
International Workshop on Mobile Multimedia Communications, |
| 1161 |
Conference proceedings, February 2001. |
| 1162 |
|
| 1163 |
|
| 1164 |
|
| 1165 |
|
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Jonsson, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
Authors' Addresses |
| 1178 |
|
| 1179 |
Lars-Erik Jonsson |
| 1180 |
Ericsson AB |
| 1181 |
Box 920 |
| 1182 |
SE-971 28 Lulea, Sweden |
| 1183 |
|
| 1184 |
Phone: +46 8 404 29 61 |
| 1185 |
Fax: +46 920 996 21 |
| 1186 |
EMail: [email protected] |
| 1187 |
|
| 1188 |
|
| 1189 |
Ghyslain Pelletier |
| 1190 |
Ericsson AB |
| 1191 |
Box 920 |
| 1192 |
SE-971 28 Lulea, Sweden |
| 1193 |
|
| 1194 |
Phone: +46 8 404 29 43 |
| 1195 |
Fax: +46 920 996 21 |
| 1196 |
EMail: [email protected] |
| 1197 |
|
| 1198 |
|
| 1199 |
Kristofer Sandlund |
| 1200 |
Ericsson AB |
| 1201 |
Box 920 |
| 1202 |
SE-971 28 Lulea, Sweden |
| 1203 |
|
| 1204 |
Phone: +46 8 404 41 58 |
| 1205 |
Fax: +46 920 996 21 |
| 1206 |
EMail: [email protected] |
| 1207 |
|
| 1208 |
|
| 1209 |
|
| 1210 |
|
| 1211 |
|
| 1212 |
|
| 1213 |
|
| 1214 |
|
| 1215 |
|
| 1216 |
|
| 1217 |
|
| 1218 |
|
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Jonsson, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc4362">RFC 4362</a> A Link-Layer Assisted ROHC RTP January 2006</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
Full Copyright Statement |
| 1234 |
|
| 1235 |
Copyright (C) The Internet Society (2006). |
| 1236 |
|
| 1237 |
This document is subject to the rights, licenses and restrictions |
| 1238 |
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors |
| 1239 |
retain all their rights. |
| 1240 |
|
| 1241 |
This document and the information contained herein are provided on an |
| 1242 |
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS |
| 1243 |
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET |
| 1244 |
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, |
| 1245 |
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE |
| 1246 |
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED |
| 1247 |
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 1248 |
|
| 1249 |
Intellectual Property |
| 1250 |
|
| 1251 |
The IETF takes no position regarding the validity or scope of any |
| 1252 |
Intellectual Property Rights or other rights that might be claimed to |
| 1253 |
pertain to the implementation or use of the technology described in |
| 1254 |
this document or the extent to which any license under such rights |
| 1255 |
might or might not be available; nor does it represent that it has |
| 1256 |
made any independent effort to identify any such rights. Information |
| 1257 |
on the procedures with respect to rights in RFC documents can be |
| 1258 |
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>. |
| 1259 |
|
| 1260 |
Copies of IPR disclosures made to the IETF Secretariat and any |
| 1261 |
assurances of licenses to be made available, or the result of an |
| 1262 |
attempt made to obtain a general license or permission for the use of |
| 1263 |
such proprietary rights by implementers or users of this |
| 1264 |
specification can be obtained from the IETF on-line IPR repository at |
| 1265 |
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>. |
| 1266 |
|
| 1267 |
The IETF invites any interested party to bring to its attention any |
| 1268 |
copyrights, patents or patent applications, or other proprietary |
| 1269 |
rights that may cover technology that may be required to implement |
| 1270 |
this standard. Please address the information to the IETF at |
| 1271 |
[email protected]. |
| 1272 |
|
| 1273 |
Acknowledgement |
| 1274 |
|
| 1275 |
Funding for the RFC Editor function is provided by the IETF |
| 1276 |
Administrative Support Activity (IASA). |
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
Jonsson, et al. Standards Track [Page 23] |
| 1285 |
</pre> |