idnits 2.17.1 draft-ietf-tsvwg-sctp-chunk-flags-00.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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC4960, but the abstract doesn't seem to mention this, which it should. 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 (June 6, 2010) is 5072 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 (==), 3 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: December 8, 2010 June 6, 2010 8 Stream Control Transmission Protocol (SCTP) Chunk Flags Registration 9 draft-ietf-tsvwg-sctp-chunk-flags-00.txt 11 Abstract 13 The current definition of the Stream Control Transmission Protocol 14 (SCTP) is missing a procedure for registering chunk flags for already 15 defined chunk types. This document defines this procedure. It does 16 not change SCTP in any other way. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on December 8, 2010. 35 Copyright Notice 37 Copyright (c) 2010 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 55 3.1. Updated IETF Chunk Extension . . . . . . . . . . . . . . . 3 56 3.2. New IETF Chunk Flags Registration . . . . . . . . . . . . . 4 57 3.3. Initial Registrations . . . . . . . . . . . . . . . . . . . 4 58 3.3.1. DATA Chunk Flags . . . . . . . . . . . . . . . . . . . 4 59 3.3.2. INIT Chunk Flags . . . . . . . . . . . . . . . . . . . 4 60 3.3.3. INIT ACK Chunk Flags . . . . . . . . . . . . . . . . . 5 61 3.3.4. SACK Chunk Flags . . . . . . . . . . . . . . . . . . . 5 62 3.3.5. HEARTBEAT Chunk Flags . . . . . . . . . . . . . . . . . 5 63 3.3.6. HEARTBEAT ACK Chunk Flags . . . . . . . . . . . . . . . 5 64 3.3.7. ABORT Chunk Flags . . . . . . . . . . . . . . . . . . . 5 65 3.3.8. SHUTDOWN Chunk Flags . . . . . . . . . . . . . . . . . 5 66 3.3.9. SHUTDOWN ACK Chunk Flags . . . . . . . . . . . . . . . 5 67 3.3.10. ERROR Chunk Flags . . . . . . . . . . . . . . . . . . . 6 68 3.3.11. COOKIE ECHO Chunk Flags . . . . . . . . . . . . . . . . 6 69 3.3.12. COOKIE ACK Chunk Flags . . . . . . . . . . . . . . . . 6 70 3.3.13. ECNE Chunk Flags . . . . . . . . . . . . . . . . . . . 6 71 3.3.14. CWR Chunk Flags . . . . . . . . . . . . . . . . . . . . 6 72 3.3.15. SHUTDOWN COMPLETE Chunk Flags . . . . . . . . . . . . . 6 73 3.3.16. AUTH Chunk Flags . . . . . . . . . . . . . . . . . . . 6 74 3.3.17. ASCONF ACK Chunk Flags . . . . . . . . . . . . . . . . 7 75 3.3.18. PAD Chunk Flags . . . . . . . . . . . . . . . . . . . . 7 76 3.3.19. FORWARD TSN Chunk Flags . . . . . . . . . . . . . . . . 7 77 3.3.20. ASCONF Chunk Flags . . . . . . . . . . . . . . . . . . 7 78 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 79 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 80 6. Normative References . . . . . . . . . . . . . . . . . . . . . 7 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 83 1. Introduction 85 [RFC4960], which currently defines the Stream Control Transmission 86 Protocol (SCTP), provides a procedure to define new chunk types. 87 However, several protocol extensions currently being discussed need 88 to define new chunk flags for existing chunks. The only way to do 89 this is to obsolete [RFC4960], which is not appropriate. 91 This document overcomes this limitation and provides the procedure to 92 register chunk flags for existing chunk types. The protocol is not 93 changed in any other way. Therefore only Section 14.1 of [RFC4960] 94 is affected. 96 2. Conventions 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [RFC2119]. 102 3. IANA Considerations 104 Section 3.1 describes the updated procedure for chunk type 105 registration and replaces Section 14.1 of [RFC4960]. Section 3.2 106 adds a new procedure for chunk flag registration to the updated 107 section 14.1 of [RFC4960]. 109 The IANA is requested to create a Chunk Flag registry. The initial 110 contents of the registry should be assigned using the values 111 specified in Section 3.3. 113 3.1. Updated IETF Chunk Extension 115 The assignment of new chunk parameter type codes is done through an 116 IETF Review action, as defined in [RFC5226]. Documentation of a new 117 chunk MUST contain the following information: 119 a) A long and short name for the new chunk type; 121 b) A detailed description of the structure of the chunk, which MUST 122 conform to the basic structure defined in section 3.2 of 123 [RFC4960]; 125 c) A detailed definition and description of intended use of each 126 field within the chunk, including the chunk flags if any. 127 Defined chunk flags will be used as initial entries in the chunk 128 flags table for the new chunk type; 130 d) A detailed procedural description of the use of the new chunk 131 type within the operation of the protocol. 133 The last chunk type (255) is reserved for future extension if 134 necessary. 136 IANA creates for each new chunk type a registration table for the 137 chunk flags for this type. The procedure for registering particular 138 chunk flags is described in the following Section 3.2. 140 3.2. New IETF Chunk Flags Registration 142 The assignment of new chunk flags is done through an RFC required 143 action, as defined in [RFC5226]. Documentation of the chunk flags 144 MUST contain the following information: 146 a) A name for the new chunk flag; 148 b) A detailed procedural description of the use of the new chunk 149 flag within the operation of the protocol. It MUST be considered 150 that implementations not supporting the flag will just ignore it. 152 IANA selects a chunk flags value, exactly one of 0x01, 0x02, 0x04, 153 0x08, 0x10, 0x20, 0x40, or 0x80, which MUST be unique within the 154 chunk flag values for the specific chunk type. 156 3.3. Initial Registrations 158 This section describes the initially defined chunk flag tables, one 159 table per chunk. Most of the tables are currently empty. 161 3.3.1. DATA Chunk Flags 163 +------------------+-----------------+-----------+ 164 | Chunk Flag Value | Chunk Flag Name | Reference | 165 +------------------+-----------------+-----------+ 166 | 0x01 | E bit | [RFC4960] | 167 | 0x02 | B bit | [RFC4960] | 168 | 0x04 | U bit | [RFC4960] | 169 +------------------+-----------------+-----------+ 171 3.3.2. INIT Chunk Flags 173 +------------------+-----------------+-----------+ 174 | Chunk Flag Value | Chunk Flag Name | Reference | 175 +------------------+-----------------+-----------+ 177 3.3.3. INIT ACK Chunk Flags 179 +------------------+-----------------+-----------+ 180 | Chunk Flag Value | Chunk Flag Name | Reference | 181 +------------------+-----------------+-----------+ 183 3.3.4. SACK Chunk Flags 185 +------------------+-----------------+-----------+ 186 | Chunk Flag Value | Chunk Flag Name | Reference | 187 +------------------+-----------------+-----------+ 189 3.3.5. HEARTBEAT Chunk Flags 191 +------------------+-----------------+-----------+ 192 | Chunk Flag Value | Chunk Flag Name | Reference | 193 +------------------+-----------------+-----------+ 195 3.3.6. HEARTBEAT ACK Chunk Flags 197 +------------------+-----------------+-----------+ 198 | Chunk Flag Value | Chunk Flag Name | Reference | 199 +------------------+-----------------+-----------+ 201 3.3.7. ABORT Chunk Flags 203 +------------------+-----------------+-----------+ 204 | Chunk Flag Value | Chunk Flag Name | Reference | 205 +------------------+-----------------+-----------+ 206 | 0x01 | T bit | [RFC4960] | 207 +------------------+-----------------+-----------+ 209 3.3.8. SHUTDOWN Chunk Flags 211 +------------------+-----------------+-----------+ 212 | Chunk Flag Value | Chunk Flag Name | Reference | 213 +------------------+-----------------+-----------+ 215 3.3.9. SHUTDOWN ACK Chunk Flags 217 +------------------+-----------------+-----------+ 218 | Chunk Flag Value | Chunk Flag Name | Reference | 219 +------------------+-----------------+-----------+ 221 3.3.10. ERROR Chunk Flags 223 +------------------+-----------------+-----------+ 224 | Chunk Flag Value | Chunk Flag Name | Reference | 225 +------------------+-----------------+-----------+ 227 3.3.11. COOKIE ECHO Chunk Flags 229 +------------------+-----------------+-----------+ 230 | Chunk Flag Value | Chunk Flag Name | Reference | 231 +------------------+-----------------+-----------+ 233 3.3.12. COOKIE ACK Chunk Flags 235 +------------------+-----------------+-----------+ 236 | Chunk Flag Value | Chunk Flag Name | Reference | 237 +------------------+-----------------+-----------+ 239 3.3.13. ECNE Chunk Flags 241 +------------------+-----------------+-----------+ 242 | Chunk Flag Value | Chunk Flag Name | Reference | 243 +------------------+-----------------+-----------+ 245 3.3.14. CWR Chunk Flags 247 +------------------+-----------------+-----------+ 248 | Chunk Flag Value | Chunk Flag Name | Reference | 249 +------------------+-----------------+-----------+ 251 3.3.15. SHUTDOWN COMPLETE Chunk Flags 253 +------------------+-----------------+-----------+ 254 | Chunk Flag Value | Chunk Flag Name | Reference | 255 +------------------+-----------------+-----------+ 256 | 0x01 | T bit | [RFC4960] | 257 +------------------+-----------------+-----------+ 259 3.3.16. AUTH Chunk Flags 261 +------------------+-----------------+-----------+ 262 | Chunk Flag Value | Chunk Flag Name | Reference | 263 +------------------+-----------------+-----------+ 265 3.3.17. ASCONF ACK Chunk Flags 267 +------------------+-----------------+-----------+ 268 | Chunk Flag Value | Chunk Flag Name | Reference | 269 +------------------+-----------------+-----------+ 271 3.3.18. PAD Chunk Flags 273 +------------------+-----------------+-----------+ 274 | Chunk Flag Value | Chunk Flag Name | Reference | 275 +------------------+-----------------+-----------+ 277 3.3.19. FORWARD TSN Chunk Flags 279 +------------------+-----------------+-----------+ 280 | Chunk Flag Value | Chunk Flag Name | Reference | 281 +------------------+-----------------+-----------+ 283 3.3.20. ASCONF Chunk Flags 285 +------------------+-----------------+-----------+ 286 | Chunk Flag Value | Chunk Flag Name | Reference | 287 +------------------+-----------------+-----------+ 289 4. Security Considerations 291 This document does not add any additional security considerations in 292 addition to the ones given in [RFC4960]. 294 5. Acknowledgments 296 The authors wish to thank Gorry Fairhurst for his invaluable 297 comments. 299 6. Normative References 301 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 302 Requirement Levels", BCP 14, RFC 2119, March 1997. 304 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 305 RFC 4960, September 2007. 307 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 308 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 309 May 2008. 311 Authors' Addresses 313 Michael Tuexen 314 Muenster Univ. of Applied Sciences 315 Stegerwaldstr. 39 316 48565 Steinfurt 317 Germany 319 Email: tuexen@fh-muenster.de 321 Randall R. Stewart 322 Huawei 323 Chapin, SC 29036 324 USA 326 Email: rstewart@huawei.com