idnits 2.17.1 draft-ietf-tsvwg-sctp-padding-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5 on line 247. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 258. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 265. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 271. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 25, 2006) is 6421 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: 'RFCXXXX' on line 170 ** Obsolete normative reference: RFC 2960 (ref. '2') (Obsoleted by RFC 4960) -- Possible downref: Non-RFC (?) normative reference: ref. '3' Summary: 4 errors (**), 0 flaws (~~), 2 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Tuexen 3 Internet-Draft Muenster Univ. of Applied Sciences 4 Intended status: Standards Track R. Stewart 5 Expires: March 29, 2007 P. Lei 6 Cisco Systems, Inc. 7 September 25, 2006 9 Padding Chunk and Parameter for SCTP 10 draft-ietf-tsvwg-sctp-padding-01.txt 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on March 29, 2007. 37 Copyright Notice 39 Copyright (C) The Internet Society (2006). 41 Abstract 43 This document defines a padding chunk and a padding parameter and 44 describes the required receiver side procedures. The padding chunk 45 is used to pad an SCTP packet to an arbitrary size. The padding 46 parameter is used to pad an SCTP INIT chunk to an arbitrary size. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. Padding Chunk (PAD) . . . . . . . . . . . . . . . . . . . . . . 3 53 4. Padding Parameter (PAD) . . . . . . . . . . . . . . . . . . . . 4 54 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 55 5.1. A New Chunk Type . . . . . . . . . . . . . . . . . . . . . 5 56 5.2. A New Parameter Type . . . . . . . . . . . . . . . . . . . 5 57 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 58 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 59 8. Normative References . . . . . . . . . . . . . . . . . . . . . 5 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 61 Intellectual Property and Copyright Statements . . . . . . . . . . 7 63 1. Introduction 65 This document defines a padding chunk and a padding parameter and 66 describes the required receiver side procedures. The padding chunk 67 is used to pad an SCTP packet to an arbitrary size. The padding 68 parameter is used to pad an SCTP INIT chunk to an arbitrary size. 69 The PAD chunk can be used for path MTU discovery. 71 2. Conventions 73 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 75 "OPTIONAL", when they appear in this document, are to be interpreted 76 as described in RFC2119 [1]. 78 3. Padding Chunk (PAD) 80 This chunk is used to pad an SCTP packet to an arbitrary size. 82 0 1 2 3 83 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 84 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 85 | Type = 0x84 | Flags=0 | Length | 86 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 87 | | 88 \ Padding Data / 89 / \ 90 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 92 Figure 1 94 Type: 1 byte (unsigned integer) 95 This value MUST be set to 0x84 for all PAD-chunks. 97 Flags: 1 byte (unsigned integer) 98 Set to zero on transmit and ignored on receipt. 100 Length: 2 bytes (unsigned integer) 101 This value holds the length of the Padding Data plus 4. 103 Padding Data: n bytes (unsigned integer) 104 This holds the Padding Data. The Padding Data is ignored by the 105 receiver. 107 The receiver of the PAD chunk MUST discard this chunk and continue 108 processing the rest of the chunks in the packet. Please note that 109 this is also the required processing behavior for the PAD chunk when 110 it is unknown by the receiver. 112 4. Padding Parameter (PAD) 114 This parameter is used to pad an INIT chunk to an arbitrary size. 116 0 1 2 3 117 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 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | Parameter Type = 0x8005 | Parameter Length | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 / / 122 \ Padding Data \ 123 / / 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 Figure 2 128 Parameter Type: 2 bytes (unsigned integer) 129 This value MUST be set to 0x8005. 131 Parameter Length: 2 bytes (unsigned integer) 132 This value holds the length of the Padding Data plus 4. 134 The PAD parameter MAY be included only in the INIT chunk. It MUST 135 NOT be included in any other chunk. The receiver of the PAD 136 parameter MUST silently discard this parameter and continue 137 processing the rest of the INIT chunk. This means that the size of 138 the generated COOKIE parameter in the INIT-ACK MUST NOT depend on the 139 existence of the PAD parameter in the INIT chunk. A receiver of a 140 PAD parameter MUST NOT include the PAD parameter within any State 141 Cookie parameter it generates. 143 5. IANA Considerations 145 [NOTE to RFC-Editor: 147 "RFCXXXX" is to be replaced by the RFC number you assign this 148 document. 150 The reference to sctp-parameters [3] should be removed from the 151 "Normative References" section after the IANA section has been 152 removed. 154 ] 155 This document (RFCXXX) is the reference for all registrations 156 described in this section. All registrations need to be listed in 157 the document available at sctp-parameters [3]. The suggested changes 158 are described below. 160 5.1. A New Chunk Type 162 A chunk type for the PAD chunk has to be assigned by IANA. It is 163 suggested to use the value given in Figure 1. This requires an 164 additional line in the "CHUNK TYPES" table of sctp-parameters [3]: 166 CHUNK TYPES 168 ID Value Chunk Type Reference 169 -------- ---------- --------- 170 132(0x84) Padding Chunk (PAD) [RFCXXXX] 172 5.2. A New Parameter Type 174 A parameter type has to be assigned for the PAD parameter by IANA. 175 It is suggested to use the values given in Figure 2. This requires a 176 modification in the "CHUNK PARAMETER TYPES" table in sctp- 177 parameters [3]: Add a new line to the "INIT Chunk Parameter Types" 178 table: 180 Chunk Parameter Type Value 181 -------------------- ----- 182 Padding 32773(0x8005) 184 6. Security Considerations 186 This document does not add any additional security considerations in 187 addition to the ones given in RFC2960 [2]. 189 7. Acknowledgments 191 The authors wish to thank Matthew J. Zekauskas for his invaluable 192 comments. 194 8. Normative References 196 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 197 Levels", BCP 14, RFC 2119, March 1997. 199 [2] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, 200 H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Paxson, 201 "Stream Control Transmission Protocol", RFC 2960, October 2000. 203 [3] 205 Authors' Addresses 207 Michael Tuexen 208 Muenster Univ. of Applied Sciences 209 Stegerwaldstr. 39 210 48565 Steinfurt 211 Germany 213 Email: tuexen@fh-muenster.de 215 Randall R. Stewart 216 Cisco Systems, Inc. 217 4875 Forest Drive 218 Suite 200 219 Columbia, SC 29206 220 USA 222 Email: rrs@cisco.com 224 Peter Lei 225 Cisco Systems, Inc. 226 955 Happfield Dr. 227 Arlington Heights, IL 60004 228 US 230 Phone: +1 773 695-8201 231 Email: peterlei@cisco.com 233 Full Copyright Statement 235 Copyright (C) The Internet Society (2006). 237 This document is subject to the rights, licenses and restrictions 238 contained in BCP 78, and except as set forth therein, the authors 239 retain all their rights. 241 This document and the information contained herein are provided on an 242 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 243 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 244 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 245 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 246 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 247 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 249 Intellectual Property 251 The IETF takes no position regarding the validity or scope of any 252 Intellectual Property Rights or other rights that might be claimed to 253 pertain to the implementation or use of the technology described in 254 this document or the extent to which any license under such rights 255 might or might not be available; nor does it represent that it has 256 made any independent effort to identify any such rights. Information 257 on the procedures with respect to rights in RFC documents can be 258 found in BCP 78 and BCP 79. 260 Copies of IPR disclosures made to the IETF Secretariat and any 261 assurances of licenses to be made available, or the result of an 262 attempt made to obtain a general license or permission for the use of 263 such proprietary rights by implementers or users of this 264 specification can be obtained from the IETF on-line IPR repository at 265 http://www.ietf.org/ipr. 267 The IETF invites any interested party to bring to its attention any 268 copyrights, patents or patent applications, or other proprietary 269 rights that may cover technology that may be required to implement 270 this standard. Please address the information to the IETF at 271 ietf-ipr@ietf.org. 273 Acknowledgment 275 Funding for the RFC Editor function is provided by the IETF 276 Administrative Support Activity (IASA).