Using a Generic Associated Channel Label as a Virtual Circuit Connectivity Verification Channel Indicator
RFC 7708
Document | Type | RFC - Proposed Standard (November 2015; No errata) | |
---|---|---|---|
Authors | Thomas Nadeau , Luca Martini , Stewart Bryant | ||
Last updated | 2015-11-24 | ||
Replaces | draft-ietf-pwe3-vccv-for-gal | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Matthew Bocci | ||
Shepherd write-up | Show (last changed 2015-08-25) | ||
IESG | IESG state | RFC 7708 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Deborah Brungard | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) T. Nadeau Request for Comments: 7708 Brocade Category: Standards Track L. Martini ISSN: 2070-1721 S. Bryant Cisco Systems November 2015 Using a Generic Associated Channel Label as a Virtual Circuit Connectivity Verification Channel Indicator Abstract The Virtual Circuit Connectivity Verification (VCCV) protocol specified in RFC 5085 provides a control channel (CC) that is associated with a pseudowire (PW). This document specifies an additional VCCV control channel type to be used with pseudowires that do not use the PW Control Word and that are carried over an MPLS network. This new VCCV CC type uses the Generic Associated Channel Label defined in RFC 5586 to distinguish VCCV packets from packets carrying user data. This new VCCV CC type introduces compatibility with the method of MPLS Label Switched Path Operations, Administration, and Maintenance (OAM) identification, particularly in MPLS Transport Profile (MPLS-TP) networks (RFC 5921). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7708. Nadeau, et al. Standards Track [Page 1] RFC 7708 GAL as a VCCV Channel November 2015 Copyright Notice Copyright (c) 2015 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 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 3. Type 4 MPLS VCCV Control Channel Type . . . . . . . . . . . . 3 4. FAT PWs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Multi-Segment Pseudowires . . . . . . . . . . . . . . . . . . 5 6. VCCV Capability Advertisement . . . . . . . . . . . . . . . . 5 7. Manageability Considerations . . . . . . . . . . . . . . . . 6 8. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 9.1. MPLS VCCV Control Channel (CC) Type 4 . . . . . . . . . . 7 9.2. LDP Status Code . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . 8 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction The Virtual Circuit Connectivity Verification (VCCV) protocol is specified in RFC 5085 [RFC5085]. This document specifies a new VCCV control channel (VCCV CC) type to be used with pseudowires (PWs) carried over an MPLS network that do not use the PW Control Word (CW) [RFC4385]. This new VCCV CC type uses the Generic Associated Channel Label (GAL) [RFC5586] to distinguish VCCV packets from packets carrying user data. This new VCCV CC type provides compatibility with the method of MPLS Label Switched Path (LSP) Operations, Administration, and Maintenance (OAM) message identification, as used in MPLS Transport Profile (MPLS-TP) networks [RFC5921]. Nadeau, et al. Standards Track [Page 2] RFC 7708 GAL as a VCCV Channel November 2015 VCCV currently specifies three CC types. VCCV CC Type 1 uses the PW Control Word (CW) to distinguish VCCV packets from packets carrying user data. VCCV CC Types 2 and 3 require IP encapsulation for OAMShow full document text