idnits 2.17.1 draft-ietf-mpls-moving-iana-registries-04.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 -- The document date (January 26, 2014) is 3737 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group L. Andersson 3 Internet-Draft Huawei 4 Updates: 5586, 6374, 6378, 6427, 6428, C. Pignataro 5 RFC-ietf-mpls-gach-adv, Cisco 6 RFC-ietf-mpls-tp-ethernet-addressing January 26, 2014 7 (if approved) 8 Intended status: Standards Track 9 Expires: July 30, 2014 11 Moving Generic Associated Channel (G-ACh) IANA Registries to a New 12 Registry 13 draft-ietf-mpls-moving-iana-registries-04 15 Abstract 17 RFC 5586 generalized the applicability of the pseudowire Associated 18 Channel Header (PW-ACH) into the Generic Associated Channel G-ACh. 19 However, registries and allocations of G-ACh parameters had been 20 distributed throughout different, sometimes unrelated, registries. 21 This document coalesces these into a new "Generic Associated Channel 22 (G-ACh) Parameters" registry under the "Multiprotocol Label Switching 23 Architecture (MPLS)" heading. This document updates RFC 5586. 25 This document also updates RFC 6374, RFC 6428, RFC 6378, RFC 6427, 26 RFC-ietf-mpls-gach-adv, and RFC-ietf-mpls-tp-ethernet-addressing. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on July 30, 2014. 45 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 64 2.1. Creation of a New Generic Associated Channel (G-ACh) 65 Parameters IANA Registry . . . . . . . . . . . . . . . . . 3 66 2.2. Renaming and Moving the Pseudowire Associated Channel 67 Types Registry . . . . . . . . . . . . . . . . . . . . . . 4 68 2.3. Consolidating G-ACh Registries . . . . . . . . . . . . . . 4 69 3. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 71 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 72 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 73 6.1. Normative References . . . . . . . . . . . . . . . . . . . 6 74 6.2. Informative References . . . . . . . . . . . . . . . . . . 6 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 77 1. Introduction 79 RFC 5586 generalized the PW-ACH into the G-ACh. However, registries 80 and allocations of G-ACh namespaces had been distributed throughout 81 different registries. This document coalesces these into a new 82 "Generic Associated Channel (G-ACh) Parameters" registry in the 83 "Multiprotocol Label Switching Architecture (MPLS)" name space. This 84 reorganization achieves two purposes: it allocates the G-ACh 85 registries in their natural place in the MPLS names space, and it is 86 needed to get a single view of the G-ACh registries, to simplify 87 future assignments, and to avoid potential conflicts. This is an 88 update to RFC RFC 5586 [RFC5586]. 90 Further, the "Pseudowire Associated Channel Types" registry is 91 renamed to "MPLS Generalized Associated Channel (G-ACh) Types 92 (including Pseudowire Associated Channel Types)" to make its 93 generalized status explicit, and is moved into the newly created 94 registry. 96 Additionally, RFC 6374 [RFC6374], RFC 6428 [RFC6428], RFC 6378] 97 [RFC6378], RFC 6427 [RFC6427], RFC-ietf-mpls-gach-adv 98 [I-D.ietf-mpls-gach-adv], and RFC-ietf-mpls-tp-ethernet-addressing 99 [I-D.ietf-mpls-tp-ethernet-addressing] specify allocations within the 100 G-ACh that are now moved into the new registry. 102 With respect to where to find these IANA registries, the RFCs listed 103 above are updated as indicated in Section 3; however the registries 104 themselves are not changed (with the exception of one being renamed). 105 They are moved unchanged to the new registry. 107 Editor's note: 108 Need to fix the references to RFC-ietf-mpls-gach-adv and RFC-ietf- 109 mpls-tp-ethernet-addressing 111 2. IANA Considerations 113 IANA is requested to add this document as a reference for any 114 registry that is moved or renamed as a result of actions requested by 115 this document. 117 IANA is also requested to replace all the relocated registries with 118 pointers to the new URL or with a redirect. 120 2.1. Creation of a New Generic Associated Channel (G-ACh) Parameters 121 IANA Registry 123 IANA is requested to create a new "Generic Associated Channel (G-ACh) 124 Parameters" registry under the "Multiprotocol Label Switching 125 Architecture (MPLS)" heading. This is the common registry that will 126 include all the registries being moved in Sections 2.2 and 2.3. 128 2.2. Renaming and Moving the Pseudowire Associated Channel Types 129 Registry 131 This document renames the "Pseudowire Associated Channel Types" 132 registry [IANA-PWE3] into "MPLS Generalized Associated Channel 133 (G-ACh) Types (including Pseudowire Associated Channel Types)". This 134 registry is moved and included as the first registry in the "Generic 135 Associated Channel (G-ACh) Parameters" registry created in 136 Section 2.1 because any additional registries are dependent upon the 137 Associated Channel Header Type. 139 At the time of publishing this document and moving the registry, the 140 following RFCs have G-ACh Types allocated: [I-D.ietf-mpls-gach-adv], 141 [RFC4385], [RFC5586], [RFC5718], [RFC5885], [RFC6374], [RFC6378], 142 [RFC6426], [RFC6427], [RFC6428], [RFC6435], [RFC6478], and [RFC6671]. 144 2.3. Consolidating G-ACh Registries 146 This document further updates the following RFCs by moving the G-ACh 147 related registries to the common "MPLS Generic Associated Channel 148 (G-ACh) Parameters" registry created in Section 2.1: 150 o From the PWE Parameters Registry [IANA-PWE3]: 152 * MPLS Generalized Associated Channel (G-ACh) Types [RFC5586] 154 * G-ACh Advertisement Protocol Application Registry 155 [I-D.ietf-mpls-gach-adv] 157 * G-ACh Advertisement Protocol TLV Registry 158 [I-D.ietf-mpls-gach-adv] 160 * G-ACh Advertisement Protocol: Ethernet Interface Parameters 161 [I-D.ietf-mpls-tp-ethernet-addressing] 163 * CC/CV MEP-ID TLV Registry [RFC6428] 165 o From the MPLS LSP Ping Parameters Registry [IANA-LSP-Ping]: 167 * Measurement Timestamp Type [RFC6374] 169 * Loss/Delay Measurement Control Code: Query Codes [RFC6374] 170 * Loss/Delay Measurement Control Code: Response Codes [RFC6374] 172 * MPLS Loss/Delay Measurement TLV Object [RFC6374] 174 o From the MPLS OAM Parameters Registry [IANA-MPLS-OAM]: 176 * MPLS Fault OAM Message Type Registry [RFC6427] 178 * MPLS Fault OAM Flag Registry [RFC6427] 180 * MPLS Fault OAM TLV Registry [RFC6427] 182 * MPLS PSC Request Registry [RFC6378] 184 * MPLS PSC TLV Registry [RFC6378] 186 Note that all the sub-registries in [IANA-MPLS-OAM] are moved from 187 "Multiprotocol Label Switching (MPLS) Operations, Administration, 188 and Management (OAM) Parameters" registry. The IANA is therefore 189 requested to remove the "MPLS OAM" registry. 191 3. RFC Updates 193 This document updates [RFC5586] renaming the "Pseudowire Associated 194 Channel Types" [IANA-PWE3] into "MPLS Generalized Associated Channel 195 (G-ACh) Types (including Pseudowire Associated Channel Types)". 197 This document also updates the following RFCs by moving the G-ACh 198 related registries to a common "MPLS Generic Associated Channel 199 (G-ACh) Parameters" registry: RFC 6374, RFC 6428, RFC 6378, RFC 6427, 200 RFC-ietf-mpls-gach-adv, and RFC-ietf-mpls-tp-ethernet-addressing. 202 All the registries listed above are moved without any changes to 203 their content. The reason to move them is to create on single place 204 where it is possible to find all the G-ACh parameters. 206 4. Security Considerations 208 The IANA instructions in this document do not directly introduce any 209 new security issues. 211 5. Acknowledgements 213 The authors want to thank Amanda Barber and Scott Bradner for review 214 and valuable comments. 216 6. References 218 6.1. Normative References 220 [I-D.ietf-mpls-gach-adv] 221 Frost, D., Bryant, S., and M. Bocci, "MPLS Generic 222 Associated Channel (G-ACh) Advertisement Protocol", 223 draft-ietf-mpls-gach-adv-08 (work in progress), June 2013. 225 [I-D.ietf-mpls-tp-ethernet-addressing] 226 Frost, D., Bryant, S., and M. Bocci, "MPLS-TP Next-Hop 227 Ethernet Addressing", 228 draft-ietf-mpls-tp-ethernet-addressing-08 (work in 229 progress), July 2013. 231 [RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic 232 Associated Channel", RFC 5586, June 2009. 234 [RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay 235 Measurement for MPLS Networks", RFC 6374, September 2011. 237 [RFC6378] Weingarten, Y., Bryant, S., Osborne, E., Sprecher, N., and 238 A. Fulignoli, "MPLS Transport Profile (MPLS-TP) Linear 239 Protection", RFC 6378, October 2011. 241 [RFC6427] Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S., 242 and D. Ward, "MPLS Fault Management Operations, 243 Administration, and Maintenance (OAM)", RFC 6427, 244 November 2011. 246 [RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive 247 Connectivity Verification, Continuity Check, and Remote 248 Defect Indication for the MPLS Transport Profile", 249 RFC 6428, November 2011. 251 6.2. Informative References 253 [IANA-LSP-Ping] 254 Internet Assigned Numbers Authority, "Multi-Protocol Label 255 Switching (MPLS) Label Switched Paths (LSPs) Ping 256 Parameters", 257 . 260 [IANA-MPLS-OAM] 261 Internet Assigned Numbers Authority, "Multiprotocol Label 262 Switching (MPLS) Operations, Administration, and 263 Management (OAM) Parameters", 264 . 266 [IANA-PWE3] 267 Internet Assigned Numbers Authority, "Pseudowire Name 268 Spaces (PWE3)", 269 . 271 [RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson, 272 "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for 273 Use over an MPLS PSN", RFC 4385, February 2006. 275 [RFC5718] Beller, D. and A. Farrel, "An In-Band Data Communication 276 Network For the MPLS Transport Profile", RFC 5718, 277 January 2010. 279 [RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional Forwarding 280 Detection (BFD) for the Pseudowire Virtual Circuit 281 Connectivity Verification (VCCV)", RFC 5885, June 2010. 283 [RFC6426] Gray, E., Bahadur, N., Boutros, S., and R. Aggarwal, "MPLS 284 On-Demand Connectivity Verification and Route Tracing", 285 RFC 6426, November 2011. 287 [RFC6435] Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux, M., 288 and X. Dai, "MPLS Transport Profile Lock Instruct and 289 Loopback Functions", RFC 6435, November 2011. 291 [RFC6478] Martini, L., Swallow, G., Heron, G., and M. Bocci, 292 "Pseudowire Status for Static Pseudowires", RFC 6478, 293 May 2012. 295 [RFC6671] Betts, M., "Allocation of a Generic Associated Channel 296 Type for ITU-T MPLS Transport Profile Operation, 297 Maintenance, and Administration (MPLS-TP OAM)", RFC 6671, 298 November 2012. 300 Authors' Addresses 302 Loa Andersson 303 Huawei 305 Email: loa@mail01.huawei.com 306 Carlos Pignataro 307 Cisco Systems, Inc. 309 Email: cpignata@cisco.com