idnits 2.17.1 draft-ietf-tsvwg-sctp-chunk-flags-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4960, updated by this document, for RFC5378 checks: 2006-02-17) -- 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 (October 8, 2010) is 4949 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 4960 (Obsoleted by RFC 9260) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 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 Updates: 4960 (if approved) R. Stewart 5 Intended status: Standards Track Huawei 6 Expires: April 11, 2011 October 8, 2010 8 Stream Control Transmission Protocol (SCTP) Chunk Flags Registration 9 draft-ietf-tsvwg-sctp-chunk-flags-02.txt 11 Abstract 13 This document defines the procedure for registering chunk flags with 14 the Internet Assigned Numbers Authority (IANA) for the Stream Control 15 Transmission Protocol (SCTP). It updates RFC 4960, and also defines 16 the IANA registry for contents for currently defined chunk types. It 17 does not change SCTP in any other way. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 11, 2011. 36 Copyright Notice 38 Copyright (c) 2010 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 56 3.1. Updated IETF-Defined Chunk Extension . . . . . . . . . . . 3 57 3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4 58 3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4 59 3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4 60 3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 5 61 3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5 62 3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5 63 3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5 64 3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5 65 3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5 66 3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5 67 3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 6 68 3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6 69 3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6 70 3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6 71 3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6 72 3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6 73 3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6 74 3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 7 75 3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7 76 3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7 77 3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7 78 3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7 79 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 80 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 81 6. Normative References . . . . . . . . . . . . . . . . . . . . . 7 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 84 1. Introduction 86 [RFC4960], which currently defines the Stream Control Transmission 87 Protocol (SCTP), provides a procedure to define new chunk types. 88 However, several protocol extensions currently being discussed need 89 to define new chunk flags for existing chunks. 91 This document updates RFC 4960 to overcome this limitation. It 92 defines the procedure to register chunk flags, and specifies the 93 registry entries for existing chunk types. The protocol is not 94 changed in any other way. Therefore only Section 14.1 of [RFC4960] 95 is affected. 97 2. Conventions 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 101 document are to be interpreted as described in [RFC2119]. 103 3. IANA Considerations 105 Section 3.1 provides the updated procedure for SCTP Chunk Type 106 registration; it replaces Section 14.1 of [RFC4960]. 108 Section 3.2 provides a new procedure for SCTP Chunk Flag 109 registration. A registry entry must be created for each SCTP Chunk 110 Type. 112 Section 3.3 provides the SCTP Chunk Flag registry values for the SCTP 113 Chunk Types specified in [RFC3758], [RFC4820], [RFC4960], [RFC4895], 114 and [RFC5061]. 116 3.1. Updated IETF-Defined Chunk Extension 118 The assignment of new chunk parameter type codes is done through an 119 IETF Review action, as defined in [RFC5226]. Documentation of a new 120 chunk MUST contain the following information: 122 a) A long and short name for the new chunk type; 124 b) A detailed description of the structure of the chunk, which MUST 125 conform to the basic structure defined in section 3.2 of 126 [RFC4960]; 128 c) A detailed definition and description of intended use of each 129 field within the chunk, including the chunk flags if any. 130 Defined chunk flags will be used as initial entries in the chunk 131 flags table for the new chunk type; 133 d) A detailed procedural description of the use of the new chunk 134 type within the operation of the protocol. 136 The last chunk type (255) is reserved for future extension if 137 necessary. 139 IANA creates for each new chunk type a registration table for the 140 chunk flags for this type. The procedure for registering particular 141 chunk flags is described in the following Section 3.2. 143 3.2. New IETF Chunk Flags Registration 145 The assignment of new chunk flags is done through an RFC required 146 action, as defined in [RFC5226]. Documentation of the chunk flags 147 MUST contain the following information: 149 a) A name for the new chunk flag; 151 b) A detailed procedural description of the use of the new chunk 152 flag within the operation of the protocol. It MUST be considered 153 that implementations not supporting the flag will send '0' on 154 transmit and just ignore it on receipt. 156 IANA selects a chunk flags value. This must be one of 0x01, 0x02, 157 0x04, 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within 158 the chunk flag values for the specific chunk type. 160 3.3. Initial Registrations 162 This section describes the initial values of the chunk flag tables, 163 one table for each chunk. Most tables are currently empty. IANA is 164 to use these values to create the new registry. 166 3.3.1. DATA Chunk Flags 168 +------------------+-----------------+-----------+ 169 | Chunk Flag Value | Chunk Flag Name | Reference | 170 +------------------+-----------------+-----------+ 171 | 0x01 | E bit | [RFC4960] | 172 | 0x02 | B bit | [RFC4960] | 173 | 0x04 | U bit | [RFC4960] | 174 +------------------+-----------------+-----------+ 176 3.3.2. INIT Chunk Flags 178 +------------------+-----------------+-----------+ 179 | Chunk Flag Value | Chunk Flag Name | Reference | 180 +------------------+-----------------+-----------+ 182 3.3.3. INIT ACK Chunk Flags 184 +------------------+-----------------+-----------+ 185 | Chunk Flag Value | Chunk Flag Name | Reference | 186 +------------------+-----------------+-----------+ 188 3.3.4. SACK Chunk Flags 190 +------------------+-----------------+-----------+ 191 | Chunk Flag Value | Chunk Flag Name | Reference | 192 +------------------+-----------------+-----------+ 194 3.3.5. HEARTBEAT Chunk Flags 196 +------------------+-----------------+-----------+ 197 | Chunk Flag Value | Chunk Flag Name | Reference | 198 +------------------+-----------------+-----------+ 200 3.3.6. HEARTBEAT ACK Chunk Flags 202 +------------------+-----------------+-----------+ 203 | Chunk Flag Value | Chunk Flag Name | Reference | 204 +------------------+-----------------+-----------+ 206 3.3.7. ABORT Chunk Flags 208 +------------------+-----------------+-----------+ 209 | Chunk Flag Value | Chunk Flag Name | Reference | 210 +------------------+-----------------+-----------+ 211 | 0x01 | T bit | [RFC4960] | 212 +------------------+-----------------+-----------+ 214 3.3.8. SHUTDOWN Chunk Flags 216 +------------------+-----------------+-----------+ 217 | Chunk Flag Value | Chunk Flag Name | Reference | 218 +------------------+-----------------+-----------+ 220 3.3.9. SHUTDOWN ACK Chunk Flags 222 +------------------+-----------------+-----------+ 223 | Chunk Flag Value | Chunk Flag Name | Reference | 224 +------------------+-----------------+-----------+ 226 3.3.10. ERROR Chunk Flags 228 +------------------+-----------------+-----------+ 229 | Chunk Flag Value | Chunk Flag Name | Reference | 230 +------------------+-----------------+-----------+ 232 3.3.11. COOKIE ECHO Chunk Flags 234 +------------------+-----------------+-----------+ 235 | Chunk Flag Value | Chunk Flag Name | Reference | 236 +------------------+-----------------+-----------+ 238 3.3.12. COOKIE ACK Chunk Flags 240 +------------------+-----------------+-----------+ 241 | Chunk Flag Value | Chunk Flag Name | Reference | 242 +------------------+-----------------+-----------+ 244 3.3.13. ECNE Chunk Flags 246 +------------------+-----------------+-----------+ 247 | Chunk Flag Value | Chunk Flag Name | Reference | 248 +------------------+-----------------+-----------+ 250 3.3.14. CWR Chunk Flags 252 +------------------+-----------------+-----------+ 253 | Chunk Flag Value | Chunk Flag Name | Reference | 254 +------------------+-----------------+-----------+ 256 3.3.15. SHUTDOWN COMPLETE Chunk Flags 258 +------------------+-----------------+-----------+ 259 | Chunk Flag Value | Chunk Flag Name | Reference | 260 +------------------+-----------------+-----------+ 261 | 0x01 | T bit | [RFC4960] | 262 +------------------+-----------------+-----------+ 264 3.3.16. AUTH Chunk Flags 266 +------------------+-----------------+-----------+ 267 | Chunk Flag Value | Chunk Flag Name | Reference | 268 +------------------+-----------------+-----------+ 270 3.3.17. ASCONF ACK Chunk Flags 272 +------------------+-----------------+-----------+ 273 | Chunk Flag Value | Chunk Flag Name | Reference | 274 +------------------+-----------------+-----------+ 276 3.3.18. PAD Chunk Flags 278 +------------------+-----------------+-----------+ 279 | Chunk Flag Value | Chunk Flag Name | Reference | 280 +------------------+-----------------+-----------+ 282 3.3.19. FORWARD TSN Chunk Flags 284 +------------------+-----------------+-----------+ 285 | Chunk Flag Value | Chunk Flag Name | Reference | 286 +------------------+-----------------+-----------+ 288 3.3.20. ASCONF Chunk Flags 290 +------------------+-----------------+-----------+ 291 | Chunk Flag Value | Chunk Flag Name | Reference | 292 +------------------+-----------------+-----------+ 294 4. Security Considerations 296 This document does not add any additional security considerations in 297 addition to the ones given in [RFC4960]. 299 5. Acknowledgments 301 The authors wish to thank Anna Brunstroem, Gorry Fairhurst, Russ 302 Housley, Suresh Krishnan, and Dan Romascanu for their invaluable 303 comments. 305 6. Normative References 307 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 308 Requirement Levels", BCP 14, RFC 2119, March 1997. 310 [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. 311 Conrad, "Stream Control Transmission Protocol (SCTP) 312 Partial Reliability Extension", RFC 3758, May 2004. 314 [RFC4820] Tuexen, M., Stewart, R., and P. Lei, "Padding Chunk and 315 Parameter for the Stream Control Transmission Protocol 316 (SCTP)", RFC 4820, March 2007. 318 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 319 RFC 4960, September 2007. 321 [RFC4895] Tuexen, M., Stewart, R., Lei, P., and E. Rescorla, 322 "Authenticated Chunks for the Stream Control Transmission 323 Protocol (SCTP)", RFC 4895, August 2007. 325 [RFC5061] Stewart, R., Xie, Q., Tuexen, M., Maruyama, S., and M. 326 Kozuka, "Stream Control Transmission Protocol (SCTP) 327 Dynamic Address Reconfiguration", RFC 5061, 328 September 2007. 330 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 331 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 332 May 2008. 334 Authors' Addresses 336 Michael Tuexen 337 Muenster University of Applied Sciences 338 Stegerwaldstr. 39 339 48565 Steinfurt 340 DE 342 Email: tuexen@fh-muenster.de 344 Randall R. Stewart 345 Huawei 346 Chapin, SC 29036 347 US 349 Email: rstewart@huawei.com