idnits 2.17.1 draft-tuexen-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 209. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 186. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 193. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 199. ** 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 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 80: '... This value MUST be set to 0x84 f...' RFC 2119 keyword, line 92: '...of the PAD chunk MUST discard this chu...' RFC 2119 keyword, line 114: '... This value MUST be set to 0x8005...' RFC 2119 keyword, line 119: '...he PAD parameter MAY be included only ...' RFC 2119 keyword, line 121: '... parameter MUST silently discard thi...' (2 more instances...) 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 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 (May 31, 2006) is 6533 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) ** Obsolete normative reference: RFC 2960 (ref. '1') (Obsoleted by RFC 4960) Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 7 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 Expires: December 2, 2006 R. Stewart 5 P. Lei 6 Cisco Systems, Inc. 7 May 31, 2006 9 Padding Chunk and Parameter for SCTP 10 draft-tuexen-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 December 2, 2006. 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. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Padding Chunk (PAD) . . . . . . . . . . . . . . . . . . . . . . 3 50 3. Padding Parameter (PAD) . . . . . . . . . . . . . . . . . . . . 3 51 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 52 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 53 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 54 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 55 Intellectual Property and Copyright Statements . . . . . . . . . . 7 57 1. Introduction 59 This document defines a padding chunk and a padding parameter and 60 describes the required receiver side procedures. The PAD chunk can 61 be used for path MTU discovery. 63 2. Padding Chunk (PAD) 65 This chunk is used to pad an SCTP packet to an arbitrary size. 67 0 1 2 3 68 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 69 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 70 | Type = 0x84 | Flags=0 | Length | 71 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 72 | | 73 \ Padding Data / 74 / \ 75 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 77 Figure 1 79 Type: 1 byte (unsigned integer) 80 This value MUST be set to 0x84 for all PAD-chunks. 82 Flags: 1 byte (unsigned integer) 83 Set to zero on transmit and ignored on receipt. 85 Length: 2 bytes (unsigned integer) 86 This value holds the length of the Padding Data plus 4. 88 Padding Data: n bytes (unsigned integer) 89 This holds the Padding Data. The Padding Data is ignored by the 90 receiver. 92 The receiver of the PAD chunk MUST discard this chunk and continue 93 processing the rest of the chunks in the packet. Please note that 94 this is also the required processing behavior for the PAD chunk when 95 it is unknown by the receiver. 97 3. Padding Parameter (PAD) 99 This parameter is used to pad an INIT chunk to an arbitrary size. 101 0 1 2 3 102 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 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | Parameter Type = 0x8005 | Parameter Length | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 / / 107 \ Padding Data \ 108 / / 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 Figure 2 113 Parameter Type: 2 bytes (unsigned integer) 114 This value MUST be set to 0x8005. 116 Parameter Length: 2 bytes (unsigned integer) 117 This value holds the length of the Padding Data plus 4. 119 The PAD parameter MAY be included only in the INIT chunk. It MUST 120 NOT be included in any other chunk. The receiver of the PAD 121 parameter MUST silently discard this parameter and continue 122 processing the rest of the INIT chunk. This means that the size of 123 the generated COOKIE parameter in the INIT-ACK MUST NOT depend on the 124 existence of the PAD parameter in the INIT chunk. A receiver of a 125 PAD parameter MUST NOT include the PAD parameter within any State 126 Cookie parameter it generates 128 4. IANA Considerations 130 A chunk type for the PAD chunk has to be assigned by IANA. It is 131 suggested to use the value given above. It is required that the high 132 order bits of the chunk type are 10. 134 A parameter type for the PAD parameter has to be assigned by IANA. 135 It is suggested to use the value given above. It is required that 136 the high order bits of the parameter type are 10. 138 5. Security Considerations 140 This document does not require any security considerations in 141 addition to the one given in RFC2960 [1]. 143 6. Normative References 145 [1] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, 146 H., Taylor, T., Rytina, I., Kalla, M., Zhang, L., and V. Paxson, 147 "Stream Control Transmission Protocol", RFC 2960, October 2000. 149 Authors' Addresses 151 Michael Tuexen 152 Muenster Univ. of Applied Sciences 153 Stegerwaldstr. 39 154 48565 Steinfurt 155 Germany 157 Email: tuexen@fh-muenster.de 159 Randall R. Stewart 160 Cisco Systems, Inc. 161 4875 Forest Drive 162 Suite 200 163 Columbia, SC 29206 164 USA 166 Email: rrs@cisco.com 168 Peter Lei 169 Cisco Systems, Inc. 170 955 Happfield Dr. 171 Arlington Heights, IL 60004 172 US 174 Phone: +1 847 870 7201 175 Email: peterlei@cisco.com 177 Intellectual Property Statement 179 The IETF takes no position regarding the validity or scope of any 180 Intellectual Property Rights or other rights that might be claimed to 181 pertain to the implementation or use of the technology described in 182 this document or the extent to which any license under such rights 183 might or might not be available; nor does it represent that it has 184 made any independent effort to identify any such rights. Information 185 on the procedures with respect to rights in RFC documents can be 186 found in BCP 78 and BCP 79. 188 Copies of IPR disclosures made to the IETF Secretariat and any 189 assurances of licenses to be made available, or the result of an 190 attempt made to obtain a general license or permission for the use of 191 such proprietary rights by implementers or users of this 192 specification can be obtained from the IETF on-line IPR repository at 193 http://www.ietf.org/ipr. 195 The IETF invites any interested party to bring to its attention any 196 copyrights, patents or patent applications, or other proprietary 197 rights that may cover technology that may be required to implement 198 this standard. Please address the information to the IETF at 199 ietf-ipr@ietf.org. 201 Disclaimer of Validity 203 This document and the information contained herein are provided on an 204 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 205 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 206 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 207 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 208 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 209 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 211 Copyright Statement 213 Copyright (C) The Internet Society (2006). This document is subject 214 to the rights, licenses and restrictions contained in BCP 78, and 215 except as set forth therein, the authors retain all their rights. 217 Acknowledgment 219 Funding for the RFC Editor function is currently provided by the 220 Internet Society.