idnits 2.17.1 draft-cui-mpls-tp-cc-cv-rdi-id-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 : ---------------------------------------------------------------------------- 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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (March 5, 2012) is 4434 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) == Outdated reference: A later version (-08) exists of draft-ietf-mpls-tp-itu-t-identifiers-02 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Z. Cui 3 Internet-Draft R. Winter 4 Intended status: Standards Track NEC 5 Expires: September 6, 2012 March 5, 2012 7 Using ITU-T-based IDs for MPLS-TP Proactive Connectivity Verification 8 draft-cui-mpls-tp-cc-cv-rdi-id-00 10 Abstract 12 This document defines how to use ICC-based Multiprotocol Label 13 Switching Transport Profil(MPLS-TP) identifiers for proactive 14 connectivity verification (CV) analogous to RFC 6428. New TLVs are 15 defined to support proactive CV based on identifiers following ITU-T 16 conventions. 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 September 6, 2012. 35 Copyright Notice 37 Copyright (c) 2012 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. Requirements notation . . . . . . . . . . . . . . . . . . . . . 3 54 3. ICC_Operator_ID-based Source MEP-ID TLV Definitions . . . . . . 3 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 56 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 57 6. Normative References . . . . . . . . . . . . . . . . . . . . . 4 58 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 60 1. Introduction 62 Proactive Connectivity Verification, Continuity Check, and Remote 63 Defect Indication (CV, CC and RDI) [RFC6428] is a proactive 64 Operations, Administration, and Maintenance (OAM) mechanism for the 65 MPLS Transport Profile (MPLS-TP). [RFC6428], defines CV message 66 which carry a Global_ID-based Source MEP-ID TLV to permit mis- 67 connectivity detection to be performed by sink MEPs. In transport 68 networks however, the ITU Carrier Code (ICC) is traditionally used to 69 identify a carrier/service provider. Instead of using the Global_ID, 70 which is derived from the AS number of the service provider, this 71 document defines a set of Source MEP-ID TLVs based on the 72 ICC_Operator_ID for sections, LSPs and PWs as specified in 73 [I-D.ietf-mpls-tp-itu-t-identifiers] for use in CV. 75 2. Requirements notation 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD","SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in [RFC2119]. 81 3. ICC_Operator_ID-based Source MEP-ID TLV Definitions 83 An MPLS-TP CV message [RFC6428] consists of a BFD control packet pre- 84 pended by the Associated Channel Header (ACH) and appended by a 85 Source MEP-ID TLV. This section defines an ICC_Operator_ID-based 86 Source MEP-ID TLV object. It is used as a replacement for the 87 Global_ID-based Source MEP-ID TLV as specified in [RFC6428]. 89 The format of ICC_Operator_ID-based Source MEP-ID TLV is shown below. 91 0 1 2 3 92 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 93 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 94 | Type = X | Length = 20 | 95 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 96 | | 97 + + 98 | ICC_Operator_ID-based MEG-ID | 99 + (15 Characters) + 100 | | 101 + +-+-+-+-+-+-+-+-+ 102 | | Must be Zero | 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | MEP_Index (2 Octets) | Must be Zero | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 Figure 1: ICC_Operator_ID-based Source MEP-ID TLV Format 109 An ICC_Operator_ID-based Source MEP-ID TLV is encoded as a 2-octet 110 field that specifies a type, followed by a 2-octet length field, 111 followed by a value field. 113 The value field is encoded by appending a 16-bit MEP index to the 15 114 character long MEG_ID as defined in 115 [I-D.ietf-mpls-tp-itu-t-identifiers]. Padding is used to align the 116 field with a 4 octet boundary. The length of the padding MUST be 117 included in the length field. The type will be 'X', with no 118 distinction between sections, LSPs and Pseudowires [type value to be 119 assigned by IANA]. 121 4. Security Considerations 123 The security concerns expressed in the security considerations 124 section of [RFC6428] apply. No additional concerns stem from the use 125 of the TLV defined in this document. 127 5. IANA Considerations 129 TBD 131 6. Normative References 133 [I-D.ietf-mpls-tp-itu-t-identifiers] 134 Gray, E., Helvoort, H., Betts, M., and R. Winter, "MPLS-TP 135 Identifiers Following ITU-T Conventions", 136 draft-ietf-mpls-tp-itu-t-identifiers-02 (work in 137 progress), October 2011. 139 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 140 Requirement Levels", BCP 14, RFC 2119, March 1997. 142 [RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive 143 Connectivity Verification, Continuity Check, and Remote 144 Defect Indication for the MPLS Transport Profile", 145 RFC 6428, November 2011. 147 Authors' Addresses 149 Zhenlong Cui 150 NEC 152 Email: c-sai@bx.jp.nec.com 154 Rolf Winter 155 NEC 157 Email: Rolf.Winter@neclab.eu