|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3095 (2001)
|
|
Title:
|
RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed
|
|
|
2.
|
Status of approval:
|
|
|
Approved by IESG (Internet Engineering Steering Group)
|
|
3.
|
Justification for the specific reference:
|
|
|
This reference explains the concept of Robust Header Compression (almost mandatory for VoLTE) and how it is used in practice. RoHC has a direct impact on call set up performance.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3095
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFC are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[1] IETF STD 6, RFC 768 (1980), User Datagram Protocol /
[2] IETF STD 5, RFC 791 (1981), Internet Protocol/
[3] IETF RFC 2460 (1998), Internet Protocol, Version 6 (IPv6) Specification/
[4] IETF RFC 1889 (1996), RTP: A Transport Protocol for Real-Time Applications/
[5] IETF RFC 1662 (1994), PPP in HDLC-like framing/
[6] IETF RFC 2406 (1998), IP Encapsulating Security Payload/
[7] IETF RFC 2410 (1998), The NULL Encryption Algorithm and Its Use With Ipsec/
[8] IETF RFC 2402 (1998), IP Authentication Header/
[9] IETF RFC 2004 (1996), Minimal Encapsulation within IP/
[10] IETF RFC 2784, (2000), Generic Routing Encapsulation (GRE)/
[11] IETF RFC 2890 (2000), Key and Sequence Number Extensions to GRE /
[12] IETF STD 2, RFC 1700 (1994), Assigned Numbers/
Informative References/
[1] IETF RFC 1144 (1990), Compressing TCP/IP Headers for Low-Speed Serial Links/
[2] IETF RFC 2507 (1999), IP Header Compression /
[3] IETFRFC 2508 (1999), Compressing IP/UDP/RTP Headers for Low-Speed Serial Links/
[4] Degermark, M., Hannu, H., Jonsson, L.E., Svanbro, K., "Evaluation of CRTP Performance over Cellular Radio Networks", IEEE Personal Communication Magazine, Volume 7, number 4, pp. 20-25, August 2000./
[5] IETF RFC 3096 (2001), Requirements for robust IP/UDP/RTP header compression /
[6] Svanbro, K., "Lower Layer Guidelines for Robust RTP/UDP/IP Header Compression", Work in Progress/
[7] IETF BCP 26, RFC 2434 (1998), Guidelines for Writing an IANA Considerations Section in RFCs /
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
