Network Working Group M. Chen Internet-Draft Huawei Technologies Co., Ltd Intended status: Standards Track July 04, 2011 Expires: January 5, 2012 IPv6 Pseudowire Virtual Circuit Connectivity Verification (VCCV) draft-chen-pwe3-ipv6-lsp-ping-vccv-00.txt Abstract The current LSP Ping based VCCV can only work in IPv4 scenario, this document extends the VCCV application to IPv6 network where IPv6 LDP is used to signal Pseudowire and the Sender and Receiver's IP addresses are IPv6 adresses. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 5, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents Chen Expires January 5, 2012 [Page 1] Internet-Draft IPv6 LSP Ping VCCV July 2011 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. IPv6 FEC 128 Pseudowire Sub-TLV . . . . . . . . . . . . . . . . 3 3. IPv6 FEC 129 Pseudowire Sub-TLV . . . . . . . . . . . . . . . . 4 4. Application . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Chen Expires January 5, 2012 [Page 2] Internet-Draft IPv6 LSP Ping VCCV July 2011 1. Introduction Virtual Circuit Connection Verification (VCCV) [RFC5085] is designed to verify and diagnose the forwarding path of Pseudowires (PWs). VCCV defines two Connectivity Verification (CV) types, one is Label Switched Path (LSP) Ping that is for Multi-Protocol Label Switching (MPLS) PWs, the other is ICMP Ping that is for both for MPLS and L2TPv3 PWs. MPLS LSP Ping [RFC4379] is designed for detecting data path failures in all MPLS LSPs and PWs. It defines three sub-TLVs (FEC 128/129 sub TLVs) that are used for VCCV, which is known as LSP Ping based CV. IPv6 Label Distribution Protocol (LDP) is defined in [RFC5036] , which can be used in pure IPv6 network or dual-stack scenario where IPv6 transport addresses are used. But the existing PW FEC sub-TLVs (Section 3.2.8-10 of [RFC5036]) only consider IPv4 scenarios. This document focuses on LSP Ping based CV and defines two new IPv6 PW FEC sub-TLVs of Target FEC TLV to extend the VCCV application to IPv6. 2. IPv6 FEC 128 Pseudowire Sub-TLV IPv6 FEC 128 Pseudowire has the consistent structure with FEC 128 Pseudowire as decribed in Section 3.2.9 of [RFC4379]. The encoding of IPv6 FEC 128 Pseudowire is as follows: 0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IPv6 FEC 128 PW | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Sender's PE IPv6 Address ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Remote PE IPv6 Address ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PW ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PW Type | Must Be Zero | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1. IPv6 FEC 128 Pseudowire Sender's PE IPv6 Adress: The source IP address of the target IPv6 LDP session. Remote PE IPv6 Adress: The destination IP address of the target IPv6 Chen Expires January 5, 2012 [Page 3] Internet-Draft IPv6 LSP Ping VCCV July 2011 LDP session. PW ID: Same as FEC 128 Pseudowire [RFC4379]. PW Type: Same as FEC 128 Pseudowire [RFC4379]. 3. IPv6 FEC 129 Pseudowire Sub-TLV IPv6 FEC 129 Pseudowire has the consistent structure with FEC 128 Pseudowire as decribed in Section 3.2.10 of [RFC4379]. The encoding of IPv6 FEC 129 Pseudowire is as follows: 0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | IPv6 FEC 129 PW | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Sender's PE IPv6 Address ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Remote PE IPv6 Address ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PW Type | AGI Type | AGI Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ AGI Value ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AII Type | SAII Length | SAII Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ SAII Value (continued) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | AII Type | TAII Length | TAII Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ TAII Value (continued) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | TAII (cont.) | 0-3 octets of zero padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2. IPv6 FEC 129 Pseudowire Sender's PE IPv6 Adress: The source IP address of the target IPv6 LDP session. Remote PE IPv6 Adress: The destination IP address of the target IPv6 LDP session. The other fields are same as FEC 129 Pseudowire [RFC4379]. Chen Expires January 5, 2012 [Page 4] Internet-Draft IPv6 LSP Ping VCCV July 2011 4. Application This document only focuses on LSP Ping based CV, when IPv6 LDP session is deployed to signal PWs, the above defined sub-TLVs MUST be used. 5. IANA Considerations IANA is requested to create two new registry for the Sub-Type field of Target FEC TLV IPv6 FEC 128 Pseudowire: TBD IPv6 FEC 129 Pseudowire: TBD 6. Security Considerations This draft does not intrduce any new security issues, the security mechanisms defined in [RFC4379] and [RFC5085] apply here. 7. Acknowledgements 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures", RFC 4379, February 2006. [RFC5085] Nadeau, T. and C. Pignataro, "Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires", RFC 5085, December 2007. 8.2. Informative References [RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP Specification", RFC 5036, October 2007. Chen Expires January 5, 2012 [Page 5] Internet-Draft IPv6 LSP Ping VCCV July 2011 Author's Address Mach(Guoyi) Chen Huawei Technologies Co., Ltd No. 3 Xinxi Road, Shang-di, Hai-dian District Beijing 100085 China Email: mach@huawei.com Chen Expires January 5, 2012 [Page 6]