idnits 2.17.1 draft-nadeau-pwe3-vccv2-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 date (July 4, 2012) is 4314 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) ** Downref: Normative reference to an Informational RFC: RFC 3985 ** Downref: Normative reference to an Informational RFC: RFC 5994 == Outdated reference: A later version (-02) exists of draft-ietf-pwe3-vccv-for-gal-01 == Outdated reference: A later version (-03) exists of draft-ietf-pwe3-vccv-impl-survey-results-00 Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PWE3 T. Nadeau 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track C. Pignataro 5 Expires: January 5, 2013 Cisco Systems, Inc. 6 YJ. Stein 7 RAD Data Communications 8 July 4, 2012 10 Virtual Circuit Connectivity Verification version 2 (VCCV2) 11 draft-nadeau-pwe3-vccv2-00.txt 13 Abstract 15 This document describes VCCV2, a new version of Virtual Circuit 16 Connectivity Verification (VCCV), the pseudowire OAM mechanism. This 17 new version is backwards compatible with VCCV for MPLS PWs for modes 18 that the versions share, although the Router Alert (RA) CV type is 19 not supported by VCCV2. Furthermore, this document collects the 20 complete description of VCCV2 into a single specification. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on January 5, 2013. 39 Copyright Notice 41 Copyright (c) 2012 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Overview of the PW OAM Channel . . . . . . . . . . . . . . . . 3 58 3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 4. The Protocol and its Options . . . . . . . . . . . . . . . . . 4 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 64 7.2. Informative References . . . . . . . . . . . . . . . . . . 5 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 67 1. Introduction 69 Virtual Circuit Connectivity Verification (VCCV), the pseudowire OAM 70 mechanism is described in [RFC5085], [RFC5885], and 71 [I-D.ietf-pwe3-vccv-for-gal]. This mechanism has been widely 72 implemented and deployed, but it has been reported 73 [I-D.ietf-pwe3-vccv-impl-survey-results] that the large number of 74 VCCV options has led to interoperability issues. 76 [RFC5085] together with [I-D.ietf-pwe3-vccv-for-gal] define four 77 Control Channel (CC) types for MPLS PWs: 78 Type 1 using the control word (CW), 79 Type 2 using the Router Alert label (label=1) above the PW label, 80 Type 3 using TTL expiry, 81 Type 4 using G-ACh Label (label=13) [RFC5586] below the PW label. 82 In order to simplify implementations and operations, we herein 83 obsolete Type 2, and provide guidance as to when to use the remaining 84 three types. 86 [RFC5085] together with [RFC5885] define four Connectivity 87 Verification (CV) types for MPLS PWs: 88 ICMP ping, 89 LSP ping, 90 BFD with UDP/IP encapsulation, 91 raw BFD (without IP encapsulation), 92 and BFD has several options of its own (see [RFC5880]). The 93 description of what and how to implement these is spread over several 94 documents, and we herein attempt to summarize the entire 95 functionality set in one place. 97 This document only describes OAM for PWs over MPLS. Functionality 98 for L2TPv2-based PWs remains as presently specified. 100 The present version of this document is a skeleton only, intended to 101 initiate discussion. Once the principles are agreed upon, the 102 authors will flesh out the rest. 104 2. Overview of the PW OAM Channel 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in [RFC2119]. 110 VCCV and VCCV2 are fault OAM mechanisms to verify liveliness and to 111 further diagnose the pseudowire forwarding path. This section will 112 provide an overview of the requirements and architecture of PW OAM. 114 3. Abbreviations 116 AC Attachment Circuit [RFC3985] 117 CC Control Channel (used as CC Type) 118 CE Customer Edge 119 CV Connectivity Verification (used as CV Type) 120 CW Control Word [RFC3985] 121 GACh Generic Associated Channel [RFC5586] 122 GAL GACh Channel Label [RFC5586] 123 MPLS-TP MPLS-Transport Profile 124 OAM Operations, Administration and Maintenance 125 PE Provider Edge 126 PSN Packet Switched Network [RFC3985] 127 PW Pseudowire [RFC3985] 128 PW-ACH PW Associated Channel Header [RFC4385] 129 VCCV Virtual Circuit Connectivity Verification 131 4. The Protocol and its Options 133 This section will detail all the CC and CV options, the signaling 134 needed to choose each of them, the bit-masks and codings. The 135 description will be concise, yet readable. 137 In particular, CC Type 2 is obsoleted. Subsections will discuss 138 Types 1, 3, and 4. 140 In addition, the text will provide guidance for selection of CC 141 types, as follows: When the PW employs a CW then CC Type 1 SHOULD be 142 used. TDM PWs always use the CW, and thus SHOULD always use Type 1. 143 Legacy (ATM, port mode frame relay, and HDLC PWs) without CWs SHOULD 144 use Type 3. [RFC5994] states that Ethernet PWs over MPLS-TP MUST use 145 the CW, and thus they SHOULD use Type 1, but MAY use Type 4. 147 Discussion is needed as to whether all CV types are required. 148 Subsections will detail the use of the different CV types. 150 5. Security Considerations 152 Are there significant threats on PWs based on VCCV? 154 6. IANA Considerations 156 It is not clear what needs to be put here. Will CC Type 2 be 157 removed? 159 7. References 161 7.1. Normative References 163 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 164 Requirement Levels", BCP 14, RFC 2119, March 1997. 166 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 167 Edge (PWE3) Architecture", RFC 3985, March 2005. 169 [RFC4385] Bryant, S., Swallow, G., Martini, L., and D. McPherson, 170 "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for 171 Use over an MPLS PSN", RFC 4385, February 2006. 173 [RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual Circuit 174 Connectivity Verification (VCCV): A Control Channel for 175 Pseudowires", RFC 5085, December 2007. 177 [RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic 178 Associated Channel", RFC 5586, June 2009. 180 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 181 (BFD)", RFC 5880, June 2010. 183 [RFC5885] Nadeau, T. and C. Pignataro, "Bidirectional Forwarding 184 Detection (BFD) for the Pseudowire Virtual Circuit 185 Connectivity Verification (VCCV)", RFC 5885, June 2010. 187 [RFC5994] Bryant, S., Morrow, M., Swallow, G., Cherukuri, R., 188 Nadeau, T., Harrison, N., and B. Niven-Jenkins, 189 "Application of Ethernet Pseudowires to MPLS Transport 190 Networks", RFC 5994, October 2010. 192 [I-D.ietf-pwe3-vccv-for-gal] 193 Nadeau, T. and L. Martini, "A Unified Control Channel for 194 Pseudowires", draft-ietf-pwe3-vccv-for-gal-01 (work in 195 progress), May 2012. 197 7.2. Informative References 199 [I-D.ietf-pwe3-vccv-impl-survey-results] 200 Regno, N., "The Pseudowire (PW) & Virtual Circuit 201 Connectivity Verification (VCCV) Implementation Survey 202 Results", draft-ietf-pwe3-vccv-impl-survey-results-00 203 (work in progress), April 2012. 205 Authors' Addresses 207 Thomas D. Nadeau 208 Juniper Networks 210 Email: tnadeau@juniper.net 212 Carlos Pignataro 213 Cisco Systems, Inc. 214 7200-12 Kit Creek Road 215 PO Box 14987 216 Research Triangle Park, NC 27709 217 USA 219 Email: cpignata@cisco.com 221 Yaakov (Jonathan) Stein 222 RAD Data Communications 223 24 Raoul Wallenberg St., Bldg C 224 Tel Aviv 69719 225 ISRAEL 227 Email: yaakov_s@rad.com