draft-ietf-tsvwg-sctp-padding-01.txt   draft-ietf-tsvwg-sctp-padding-02.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
Intended status: Standards Track R. Stewart Intended status: Standards Track R. Stewart
Expires: March 29, 2007 P. Lei Expires: April 19, 2007 P. Lei
Cisco Systems, Inc. Cisco Systems, Inc.
September 25, 2006 October 16, 2006
Padding Chunk and Parameter for SCTP Padding Chunk and Parameter for SCTP
draft-ietf-tsvwg-sctp-padding-01.txt draft-ietf-tsvwg-sctp-padding-02.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 March 29, 2007. This Internet-Draft will expire on April 19, 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. The padding chunk describes the required receiver side procedures. The padding chunk
is used to pad an SCTP packet to an arbitrary size. The padding is used to pad an SCTP packet to an arbitrary size. The padding
skipping to change at page 2, line 16 skipping to change at page 2, line 16
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Padding Chunk (PAD) . . . . . . . . . . . . . . . . . . . . . . 3 3. Padding Chunk (PAD) . . . . . . . . . . . . . . . . . . . . . . 3
4. Padding Parameter (PAD) . . . . . . . . . . . . . . . . . . . . 4 4. Padding Parameter (PAD) . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
5.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 5 5.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 5
5.2. A New Parameter Type . . . . . . . . . . . . . . . . . . . 5 5.2. A New Parameter Type . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
8. Normative References . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . . . 8
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 padding chunk describes the required receiver side procedures. The padding chunk
is used to pad an SCTP packet to an arbitrary size. The padding 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. parameter is used to pad an SCTP INIT chunk to an arbitrary size.
The PAD chunk can be used for path MTU discovery. The usage of the PAD chunk for path MTU discovery is described in
PMTU [3]. The inappropriate usage of the PAD parameter or PAD chunk
can result in wasted bandwidth.
2. Conventions 2. Conventions
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when they appear in this document, are to be interpreted "OPTIONAL", when they appear in this document, are to be interpreted
as described in RFC2119 [1]. as described in RFC2119 [1].
3. Padding Chunk (PAD) 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. A PAD chunk can be used to
enlarge the packet by 4 to 65536 bytes in steps of 4 bytes. An SCTP
packet MAY contain multiple PAD chunks.
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 /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1 Figure 1
Type: 1 byte (unsigned integer) Type: 1 byte (unsigned integer)
This value MUST be set to 0x84 for all PAD-chunks. This value MUST be set to 0x84 for all PAD-chunks.
Flags: 1 byte (unsigned integer) Flags: 1 byte (unsigned integer)
Set to zero on transmit and ignored on receipt. This value SHOULD be set to zero on transmit and MUST be ignored
on receipt.
Length: 2 bytes (unsigned integer) 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.
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 MUST be ignored by
receiver. the 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 any unknown chunk
it is unknown by the receiver. having the same highest order two bits of the type as the PAD chunk.
4. 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. A PAD parameter can be
used to enlarge the INIT chunk by 4 bytes as the minimum to the
maximum size of the INIT chunk in steps of 4 bytes. An INIT chunk
MAY contain multiple PAD parameters.
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 45 skipping to change at page 5, line 8
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.
5. IANA Considerations 5. IANA Considerations
[NOTE to RFC-Editor: [NOTE to RFC-Editor:
"RFCXXXX" is to be replaced by the RFC number you assign this "RFCXXXX" is to be replaced by the RFC number you assign this
document. 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 This document (RFCXXX) is the reference for all registrations
described in this section. All registrations need to be listed in described in this section. All registrations need to be listed in
the document available at sctp-parameters [3]. The suggested changes the document available at sctp-parameters [4]. The suggested changes
are described below. are described below.
5.1. A New Chunk Type 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 in Figure 1. This requires an suggested to use the value given in Figure 1. This requires an
additional line in the "CHUNK TYPES" table of sctp-parameters [3]: additional line in the "CHUNK TYPES" table of sctp-parameters [4]:
CHUNK TYPES CHUNK TYPES
ID Value Chunk Type Reference ID Value Chunk Type Reference
-------- ---------- --------- -------- ---------- ---------
132(0x84) Padding Chunk (PAD) [RFCXXXX] 132(0x84) Padding Chunk (PAD) [RFCXXXX]
5.2. A New Parameter Type 5.2. A New Parameter Type
A parameter type has to be assigned for the PAD parameter by IANA. 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 It is suggested to use the values given in Figure 2. This requires a
modification in the "CHUNK PARAMETER TYPES" table in sctp- modification in the "CHUNK PARAMETER TYPES" table in sctp-
parameters [3]: Add a new line to the "INIT Chunk Parameter Types" parameters [4]: Add a new line to the "INIT Chunk Parameter Types"
table: table:
Chunk Parameter Type Value Chunk Parameter Type Value
-------------------- ----- -------------------- -----
Padding 32773(0x8005) Padding 32773(0x8005)
6. Security Considerations 6. Security Considerations
This document does not add any additional security considerations in This document does not add any additional security considerations in
addition to the ones given in RFC2960 [2]. addition to the ones given in RFC2960 [2].
7. Acknowledgments 7. Acknowledgments
The authors wish to thank Matthew J. Zekauskas for his invaluable The authors wish to thank Matthew J. Zekauskas, and Lars Eggert for
comments. his invaluable comments.
8. Normative References 8. References
8.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, [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> 8.2. Informative References
[3] Mathis, M. and J. Heffner, "Packetization Layer Path MTU
Discovery", draft-ietf-pmtud-method-10 (work in progress),
September 2006.
URIs
[4] <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
 End of changes. 20 change blocks. 
25 lines changed or deleted 42 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/