draft-ietf-rohc-sctp-requirements-01.txt   draft-ietf-rohc-sctp-requirements-02.txt 
Network Working Group Ch. Schmidt Network Working Group Ch. Schmidt
Internet-Draft M. Tuexen Internet-Draft M. Tuexen
Expires: February 18, 2003 Siemens AG Expires: August 14, 2003 Siemens AG
August 20, 2002 February 13, 2003
Requirements for RoHC IP/SCTP Robust Header Compression Requirements for RoHC IP/SCTP Robust Header Compression
draft-ietf-rohc-sctp-requirements-01.txt draft-ietf-rohc-sctp-requirements-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that other
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 18, 2003. This Internet-Draft will expire on August 14, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document contains requirements for the IP/SCTP header This document contains requirements for the IP/SCTP header
compression scheme (profile) to be developed by the ROHC WG. The compression scheme (profile) to be developed by the ROHC WG. The
structure of this document is inherited from the document defining structure of this document is inherited from the document defining
IP/TCP requirements for ROHC. IP/TCP requirements for ROHC.
Table of Contents Table of Contents
skipping to change at page 2, line 19 skipping to change at page 2, line 19
2.1 Impact on Internet infrastructure . . . . . . . . . . . . . . 4 2.1 Impact on Internet infrastructure . . . . . . . . . . . . . . 4
2.2 Supported headers . . . . . . . . . . . . . . . . . . . . . . 4 2.2 Supported headers . . . . . . . . . . . . . . . . . . . . . . 4
2.3 SCTP specific requirements . . . . . . . . . . . . . . . . . . 5 2.3 SCTP specific requirements . . . . . . . . . . . . . . . . . . 5
2.4 Performance issues . . . . . . . . . . . . . . . . . . . . . . 6 2.4 Performance issues . . . . . . . . . . . . . . . . . . . . . . 6
2.5 Capability requirements related to link layer 2.5 Capability requirements related to link layer
characteristics . . . . . . . . . . . . . . . . . . . . . . . 7 characteristics . . . . . . . . . . . . . . . . . . . . . . . 7
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 12 Intellectual Property and Copyright Statements . . . . . . . . 12
1. Introduction 1. Introduction
The goal of the ROHC WG is to develop header compression schemes that The goal of the ROHC WG is to develop header compression schemes that
perform well over links with high error rates and long link round perform well over links with high error rates and long link round
trip times. The schemes must perform well for cellular links, using trip times. The schemes must perform well for cellular links, using
technologies such as WCDMA, EDGE, and CDMA-2000. However, the technologies such as WCDMA, EDGE, and CDMA-2000. However, the schemes
schemes should also be applicable to other future link technologies should also be applicable to other future link technologies with high
with high loss and long round trip times. loss and long round trip times.
The main objective for ROHC has been robust compression of IP/UDP/ The main objective for ROHC has been robust compression of IP/UDP/
RTP. Next step was IP/TCP compression. RTP. Next step was IP/TCP compression.
SCTP is the new reliable transport protocol from the IETF. It offers SCTP is the new reliable transport protocol from the IETF. It offers
a number of features not available in other reliable transport a number of features not available in other reliable transport
protocols such as TCP, including multi-streaming, multi-homing and protocols such as TCP, including multi-streaming, multi-homing and
resistance to flooding and masquerade attacks. SCTP is designed to resistance to flooding and masquerade attacks. SCTP is designed to
transport PSTN signaling messages over IP networks but its rich transport PSTN signaling messages over IP networks but its rich
feature set makes it capable of many broader applications. Main feature set makes it capable of many broader applications.
known application today is the transport of SIP signaling messages. Additionally, SCTP is required for reliable server pooling (transport
between name servers and between pool elements and name servers) and
recommended for SIP signaling. The selection of SCTP for this purpose
will improve the quality of these services.
One of the most important innovations of SCTP is the multi-streaming One of the most important innovations of SCTP is the multi-streaming
function. This feature allows data to be partitioned into multiple function. This feature allows data to be partitioned into multiple
streams where each stream is delivered independently, so in-sequence streams where each stream is delivered independently, so in-sequence
delivery can be guaranteed for data sent within a single stream. The delivery can be guaranteed for data sent within a single stream. The
advantage of this technique is that when a packet is lost, only advantage of this technique is that when a packet is lost, only
certain streams are affected. certain streams are affected.
From the header compression point of view the multi-streaming From the header compression point of view the multi-streaming
function raises a number of new issues to solve. Most importantly a function raises a number of new issues to solve. Most importantly a
skipping to change at page 6, line 16 skipping to change at page 6, line 16
Case 2: The verification of the decompression via CRC compression Case 2: The verification of the decompression via CRC compression
checksum fails. In this case, the release of the related SCTP checksum fails. In this case, the release of the related SCTP
packet could influence unrelated streams as well. The only way packet could influence unrelated streams as well. The only way
to avoid this would be the generation of a new SCTP packet by to avoid this would be the generation of a new SCTP packet by
the decompressor (without the data chunks from the involved the decompressor (without the data chunks from the involved
stream) - in violation to the transparency transport stream) - in violation to the transparency transport
requirement. requirement.
The compression stream must support the multiple streams feature The compression stream must support the multiple streams feature
in a way that head of line blocking is introduced by RoHC only in in a way that head of line blocking is introduced by RoHC only in
very rare cases. Context update should be restricted to a very rare cases. Context update should be restricted to a minimum.
minimum.
Extensions: Extensions:
SCTP extensions as described in ADDIP [2] and PRSCTP [3] should be SCTP extensions as described in ADDIP [2] and PRSCTP [3] should be
compressed efficiently. compressed efficiently.
Justification: SCTP extensions will be a normal part of the Justification: SCTP extensions will be a normal part of the
protocol. To reach good efficiency for SCTP, these extension have protocol. To reach good efficiency for SCTP, these extension have
to be handled in an appropriate way. to be handled in an appropriate way.
skipping to change at page 11, line 12 skipping to change at page 11, line 12
influenced by encrypted protocol header elements. This document by influenced by encrypted protocol header elements. This document by
itself, however, does not add any security risks. itself, however, does not add any security risks.
References References
[1] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, [1] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer,
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson, H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson,
"Stream Control Transmission Protocol", RFC 2960, October 2000. "Stream Control Transmission Protocol", RFC 2960, October 2000.
[2] Stewart, R., "Stream Control Transmission Protocol (SCTP) [2] Stewart, R., "Stream Control Transmission Protocol (SCTP)
Dynamic Address Reconfiguration", draft-ietf-tsvwg-addip-sctp- Dynamic Address Reconfiguration",
05 (work in progress), May 2002. draft-ietf-tsvwg-addip-sctp-06 (work in progress), October 2002.
[3] Ramalho, M. and R. Stewart, "SCTP Partial Reliability [3] Ramalho, M. and R. Stewart, "SCTP Partial Reliability
Extension", draft-stewart-tsvwg-prsctp-01 (work in progress), Extension", draft-stewart-tsvwg-prsctp-02 (work in progress),
July 2002. January 2003.
[4] Degermark, M., "Requirements for robust IP/UDP/RTP header [4] Degermark, M., "Requirements for robust IP/UDP/RTP header
compression", RFC 3096, July 2001. compression", RFC 3096, July 2001.
[5] Jonsson, L., "Requirements for ROHC IP/TCP Header Compression", [5] Jonsson, L., "Requirements for ROHC IP/TCP Header Compression",
draft-ietf-rohc-tcp-requirements-04 (work in progress), May draft-ietf-rohc-tcp-requirements-05 (work in progress), October
2002. 2002.
Authors' Addresses Authors' Addresses
Christian Schmidt Christian Schmidt
Siemens AG Siemens AG
Hofmannstr. 51 Hofmannstr. 51
81359 Munich 81359 Munich
Germany Germany
Phone: +49 89 722 27822 Phone: +49 89 722 27822
EMail: Christian.Schmidt@icn.siemens.de EMail: Christian-Schmidt@siemens.com
Michael Tuexen Michael Tuexen
Siemens AG Siemens AG
Hofmannstr. 51 Hofmannstr. 51
81359 Munich 81359 Munich
Germany Germany
Phone: +49 89 722 47210 Phone: +49 89 722 47210
EMail: michael.tuexen@siemens.com EMail: michael.tuexen@siemens.com
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/