draft-ietf-tsvwg-sctp-padding-00.txt   draft-ietf-tsvwg-sctp-padding-01.txt 
Network Working Group M. Tuexen Network Working Group M. Tuexen
Internet-Draft Muenster Univ. of Applied Sciences Internet-Draft Muenster Univ. of Applied Sciences
Expires: December 2, 2006 R. Stewart Intended status: Standards Track R. Stewart
P. Lei Expires: March 29, 2007 P. Lei
Cisco Systems, Inc. Cisco Systems, Inc.
May 31, 2006 September 25, 2006
Padding Chunk and Parameter for SCTP Padding Chunk and Parameter for SCTP
draft-ietf-tsvwg-sctp-padding-00.txt draft-ietf-tsvwg-sctp-padding-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://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 December 2, 2006. This Internet-Draft will expire on March 29, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a padding chunk and a padding parameter and This document defines a padding chunk and a padding parameter and
describes the required receiver side procedures. describes the required receiver side procedures. The padding chunk
is used to pad an SCTP packet to an arbitrary size. The padding
parameter is used to pad an SCTP INIT chunk to an arbitrary size.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Padding Chunk (PAD) . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Padding Parameter (PAD) . . . . . . . . . . . . . . . . . . . . 3 3. Padding Chunk (PAD) . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 4. Padding Parameter (PAD) . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 5.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 5
5.2. A New Parameter Type . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
8. Normative References . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . . . 7
1. Introduction 1. Introduction
This document defines a padding chunk and a padding parameter and This document defines a padding chunk and a padding parameter and
describes the required receiver side procedures. The PAD chunk can describes the required receiver side procedures. The padding chunk
be used for path MTU discovery. is used to pad an SCTP packet to an arbitrary size. The padding
parameter is used to pad an SCTP INIT chunk to an arbitrary size.
The PAD chunk can be used for path MTU discovery.
2. Padding Chunk (PAD) 2. Conventions
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when they appear in this document, are to be interpreted
as described in RFC2119 [1].
3. Padding Chunk (PAD)
This chunk is used to pad an SCTP packet to an arbitrary size. This chunk is used to pad an SCTP packet to an arbitrary size.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = 0x84 | Flags=0 | Length | | Type = 0x84 | Flags=0 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
\ Padding Data / \ Padding Data /
skipping to change at page 3, line 45 skipping to change at page 4, line 7
Padding Data: n bytes (unsigned integer) Padding Data: n bytes (unsigned integer)
This holds the Padding Data. The Padding Data is ignored by the This holds the Padding Data. The Padding Data is ignored by the
receiver. receiver.
The receiver of the PAD chunk MUST discard this chunk and continue The receiver of the PAD chunk MUST discard this chunk and continue
processing the rest of the chunks in the packet. Please note that processing the rest of the chunks in the packet. Please note that
this is also the required processing behavior for the PAD chunk when this is also the required processing behavior for the PAD chunk when
it is unknown by the receiver. it is unknown by the receiver.
3. Padding Parameter (PAD) 4. Padding Parameter (PAD)
This parameter is used to pad an INIT chunk to an arbitrary size. This parameter is used to pad an INIT chunk to an arbitrary size.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Type = 0x8005 | Parameter Length | | Parameter Type = 0x8005 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ / / /
\ Padding Data \ \ Padding Data \
skipping to change at page 4, line 30 skipping to change at page 4, line 36
Parameter Length: 2 bytes (unsigned integer) Parameter Length: 2 bytes (unsigned integer)
This value holds the length of the Padding Data plus 4. This value holds the length of the Padding Data plus 4.
The PAD parameter MAY be included only in the INIT chunk. It MUST The PAD parameter MAY be included only in the INIT chunk. It MUST
NOT be included in any other chunk. The receiver of the PAD NOT be included in any other chunk. The receiver of the PAD
parameter MUST silently discard this parameter and continue parameter MUST silently discard this parameter and continue
processing the rest of the INIT chunk. This means that the size of processing the rest of the INIT chunk. This means that the size of
the generated COOKIE parameter in the INIT-ACK MUST NOT depend on the the generated COOKIE parameter in the INIT-ACK MUST NOT depend on the
existence of the PAD parameter in the INIT chunk. A receiver of a existence of the PAD parameter in the INIT chunk. A receiver of a
PAD parameter MUST NOT include the PAD parameter within any State PAD parameter MUST NOT include the PAD parameter within any State
Cookie parameter it generates Cookie parameter it generates.
4. IANA Considerations 5. IANA Considerations
[NOTE to RFC-Editor:
"RFCXXXX" is to be replaced by the RFC number you assign this
document.
The reference to sctp-parameters [3] should be removed from the
"Normative References" section after the IANA section has been
removed.
]
This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed in
the document available at sctp-parameters [3]. The suggested changes
are described below.
5.1. A New Chunk Type
A chunk type for the PAD chunk has to be assigned by IANA. It is A chunk type for the PAD chunk has to be assigned by IANA. It is
suggested to use the value given above. It is required that the high suggested to use the value given in Figure 1. This requires an
order bits of the chunk type are 10. additional line in the "CHUNK TYPES" table of sctp-parameters [3]:
A parameter type for the PAD parameter has to be assigned by IANA. CHUNK TYPES
It is suggested to use the value given above. It is required that
the high order bits of the parameter type are 10.
5. Security Considerations ID Value Chunk Type Reference
-------- ---------- ---------
132(0x84) Padding Chunk (PAD) [RFCXXXX]
This document does not require any security considerations in 5.2. A New Parameter Type
addition to the one given in RFC2960 [1].
6. Normative References A parameter type has to be assigned for the PAD parameter by IANA.
It is suggested to use the values given in Figure 2. This requires a
modification in the "CHUNK PARAMETER TYPES" table in sctp-
parameters [3]: Add a new line to the "INIT Chunk Parameter Types"
table:
[1] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, Chunk Parameter Type Value
-------------------- -----
Padding 32773(0x8005)
6. Security Considerations
This document does not add any additional security considerations in
addition to the ones given in RFC2960 [2].
7. Acknowledgments
The authors wish to thank Matthew J. Zekauskas for his invaluable
comments.
8. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] 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.
[3] <http://www.iana.org/assignments/sctp-parameters>
Authors' Addresses Authors' Addresses
Michael Tuexen Michael Tuexen
Muenster Univ. of Applied Sciences Muenster Univ. of Applied Sciences
Stegerwaldstr. 39 Stegerwaldstr. 39
48565 Steinfurt 48565 Steinfurt
Germany Germany
Email: tuexen@fh-muenster.de Email: tuexen@fh-muenster.de
skipping to change at page 6, line 30 skipping to change at page 6, line 34
USA USA
Email: rrs@cisco.com Email: rrs@cisco.com
Peter Lei Peter Lei
Cisco Systems, Inc. Cisco Systems, Inc.
955 Happfield Dr. 955 Happfield Dr.
Arlington Heights, IL 60004 Arlington Heights, IL 60004
US US
Phone: +1 847 870 7201 Phone: +1 773 695-8201
Email: peterlei@cisco.com Email: peterlei@cisco.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
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 Rights or other rights that might be claimed to Intellectual Property Rights 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; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 7, line 29 skipping to change at page 7, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 22 change blocks. 
45 lines changed or deleted 101 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/