idnits 2.17.1 draft-betts-itu-oam-ach-code-point-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 (April 10, 2012) is 4391 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- 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. -------------------------------------------------------------------------------- 1 Network Working Group M. Betts 2 Internet Draft ZTE 3 Intended status: Informational April 10, 2012 4 Expires: October 10, 2012 6 Allocation of a Generic Associated Channel Type for ITU-T MPLS 7 Transport Profile Operation, Maintenance, and Administration 8 (MPLS-TP OAM) 9 draft-betts-itu-oam-ach-code-point-04.txt 11 Status of this Memo 13 This Internet-Draft is submitted in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 This Internet-Draft will expire on October 10, 2012. 34 Copyright Notice 36 Copyright (c) 2012 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with 44 respect to this document. 46 Abstract 48 This document assigns a Generic Associated Channel (G-ACh) Type for 49 carrying ITU-T MPLS Transport Profile Operations, Administration, and 50 Management (MPLS-TP OAM) messages in the MPLS Generic Associated 51 Channel. 53 1. Introduction 55 The Transport Profile of MPLS (MPLS-TP) defined in [RFC5654] is a 56 profile of MPLS technology for use in packet transport networks. The 57 MPLS-TP profile includes a set of Operations, Administration, and 58 Management (OAM) tools defined by the IETF 59 [I-D.ietf-mpls-tp-oam-analysis], that are used to meet the OAM 60 functional requirements defined in [RFC5860]. 62 ITU-T Recommendation [G.8113.1] documents MPLS-TP OAM. This 63 Recommendation builds upon Ethernet OAM as documented in [Y.1731]. 64 The messages in [G.8113.1] are defined to be carried in a new 65 Generic Associated Channel (G-ACh) Type in the MPLS Generic 66 Associated Channel. In order to carry these messages in an 67 interoperable fashion, a Generic Associated Channel Type from the 68 IANA maintained registry "Pseudowire Associated Channel Types'' is to 69 be used. 71 To fulfill the request from ITU-T SG15 in [LS370] and to allow 72 deployment of the [G.8113.1] OAM solution without using an 73 experimental G-ACh Type, this document requests IANA to assign a G- 74 ACh Type for use by the ITU-T for [G.8113.1]. This G-ACh type shall 75 be known as the G.8113.1 OAM G-ACh Type. 77 A number of experts in the IETF do not consider that the development 78 or deployment of a second protocol solution within the same 79 architectural problem space is necessary or advisable 80 [I-D.sprecher-mpls-tp-oam-considerations]. 82 2. Conventions used in this document 84 2.1. Requirements notation 86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 88 document are to be interpreted as described in [RFC2119]. 90 3. Scope of the G.8113.1 OAM G-ACh Type 92 The G-ACh Type assigned by this document MUST only be used for OAM 93 messages, defined in the ITU-T Recommendation [G.8113.1], carried in 94 the G-ACh. The OAM messages and procedures carried behind this G-ACh 95 type, are restricted to only those that address the OAM functional 96 requirements defined in [RFC5860]. Other message types MUST NOT be 97 carried behind this G-ACh type. 99 All ITU-T Recommendations are subject to updates by errata, 100 corrigenda, amendments or complete revisions. In any update of 101 [G.8113.1] the G-ACh Type assigned by this document MUST NOT be used 102 for any functions not identified as OAM functional requirements in 103 [RFC5860]. An update of [G.8113.1] may use the G-ACh Type assigned 104 by this document to support the OAM functions identified in 105 [RFC5860]. When an amendment or complete revision of G.8113.1 is 106 approved the reference to [G.8113.1], provided in this document, 107 should be updated to show the approval date of the new version. 109 The G-ACh Type assigned by this document may be used on any 110 transport construct that uses the G-ACh, e.g., MPLS-TP Sections, 111 MPLS-TP LSPs or PWs as described in [G.8113.1]. 113 4. Security Considerations 115 As noted in [RFC5586], when new G-ACh Types are defined, the 116 "security considerations MUST be described in the relevant 117 associated channel type specification." The IETF takes this 118 opportunity to remind the ITU-T of the need to describe security 119 considerations in [G.8113.1]. 121 5. IANA Considerations 123 IANA maintains a registry of Pseudowire Associated Channel Types as 124 a subregistry of the Pseudowire Name Spaces registry. 126 IANA is requested to allocate a new G-ACh Type as follows: 128 Value Description TLV Follows Reference 130 ----------- ----------------------- ----------- --------- 132 TBD G.8113.1 OAM No [This.I-D] 134 A value of 0x8902 is suggested. 136 6. References 138 6.1. Normative References 140 [RFC2119] Key words for use in RFCs to Indicate Requirement Levels, 141 BCP 14, RFC 2119, March 1997 143 [RFC5586] MPLS Generic Associated Channel, RFC 5586, June 2009 145 [RFC5654] Requirements of an MPLS Transport Profile, September 2009 147 [RFC5860] Requirements for Operations, Administration, and 148 Maintenance (OAM) in MPLS Transport Networks, RFC5860, May 149 2010 151 [G.8113.1] ITU-T Recommendation ''Operations, Administration and 152 Maintenance mechanism for MPLS-TP in Packet Transport 153 Network (PTN)'' 10/12, 154 http://www.itu.int/rec/T-REC-G.8113.1/en 155 (Note to RFC editor: This link will become valid after 156 G.8113.1 is approved) 158 [Y.1731] ITU-T Recommendation ''OAM functions and mechanisms for 159 Ethernet based networks'' 7/2007 as updated by Corrigendum 160 1, 10/2011, http://www.itu.int/rec/T-REC-Y.1731/en 162 6.2. Informative References 164 [LS370] Liaison statement from ITU-T SG 15, 165 https://datatracker.ietf.org/liaison/1125/ 167 [I-D.ietf-mpls-tp-oam-analysis] 168 Sprecher, N., and Fang, L., "An Overview of the OAM Tool 169 Set for MPLS based Transport Networks", draft-ietf-mpls- 170 tp-oam-analysis, work in progress. 172 [I-D.sprecher-mpls-tp-oam-considerations] 173 Sprecher, N. and Hong, KY., "The Reasons for Selecting a 174 Single Solution for MPLS-TP OAM", draft-sprecher-mpls-tp- 175 oam-considerations, work in progress. 177 7. Acknowledgments 179 This document was prepared using 2-Word-v2.0.template.dot. 181 Author's Address 183 Malcolm Betts 184 ZTE 186 Email: malcolm.betts@zte.com.cn