draft-ietf-rohc-sctp-requirements-02.txt   draft-ietf-rohc-sctp-requirements-03.txt 
Network Working Group Ch. Schmidt Network Working Group Ch. Schmidt
Internet-Draft M. Tuexen Internet-Draft Siemens AG
Expires: August 14, 2003 Siemens AG Expires: March 26, 2004 M. Tuexen
February 13, 2003 Univ. of Applied Sciences Muenster
September 26, 2003
Requirements for RoHC IP/SCTP Robust Header Compression Requirements for RoHC IP/SCTP Robust Header Compression
draft-ietf-rohc-sctp-requirements-02.txt draft-ietf-rohc-sctp-requirements-03.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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 31 skipping to change at page 1, line 32
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 August 14, 2003. This Internet-Draft will expire on March 26, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). 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
skipping to change at page 11, line 13 skipping to change at page 11, line 13
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", Dynamic Address Reconfiguration",
draft-ietf-tsvwg-addip-sctp-06 (work in progress), October 2002. draft-ietf-tsvwg-addip-sctp-08 (work in progress), September
2003.
[3] Ramalho, M. and R. Stewart, "SCTP Partial Reliability [3] Ramalho, M. and R. Stewart, "SCTP Partial Reliability
Extension", draft-stewart-tsvwg-prsctp-02 (work in progress), Extension", draft-stewart-tsvwg-prsctp-04 (work in progress),
January 2003. May 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-05 (work in progress), October draft-ietf-rohc-tcp-requirements-06 (work in progress), June
2002. 2003.
Authors' Addresses Authors' Addresses
Christian Schmidt Christian Schmidt
Siemens AG Siemens AG
Hofmannstr. 51 St.-Martin-Str. 76
81359 Munich 81541 Munich
Germany Germany
Phone: +49 89 722 27822 Phone: +49 89 63675192
EMail: Christian-Schmidt@siemens.com EMail: Christian-Schmidt@siemens.com
Michael Tuexen Michael Tuexen
Siemens AG Univ. of Applied Sciences Muenster
Hofmannstr. 51 Stegerwaldstr. 39
81359 Munich 48565 Steinfurt
Germany Germany
Phone: +49 89 722 47210 Phone: +49 2551 962550
EMail: michael.tuexen@siemens.com EMail: tuexen@fh-muenster.de
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
skipping to change at page 13, line 7 skipping to change at page 13, line 7
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 assignees. 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 Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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