A Unified Control Channel for Pseudowires
draft-ietf-pwe3-vccv-for-gal-00

The information below is for an old version of the document
Document Type Active Internet-Draft (pwe3 WG)
Last updated 2012-01-27
Replaced by draft-ietf-pals-vccv-for-gal
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document Jun 2015
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          T. Nadeau
Internet-Draft                                           CA Technologies
Intended status: Standards Track                                
Expires: July 27, 2012                                        L. Martini
                                                     Cisco Systems, Inc.

                                                        January 27, 2012

              A Unified Control Channel for Pseudowires
                 draft-ietf-pwe3-vccv-for-gal-00.txt

Abstract

   This document describes a unified mode of operation for Virtual 
   Circuit Connectivity Verification (VCCV), which provides a control 
   channel that is associated with a pseudowire (PW). VCCV applies to 
   all supported access circuit and transport types currently defined 
   for PWs, as well as those being transported by The MPLS Transport 
   Profile. This new mode is intended to augment those described in 
   RFC5085, but this document describes new rules requiring this mode
   to be used as the default/mandatory mode of operation for
   VCCV. The older types will remain optional.

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 July 27, 2012.

Copyright Notice

    

Nadeau & Martini              Expires July 2011              [Page 1]
                        VCCV 2                       January 27, 2011

   Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   1.2.  Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  VCCV Control Channel When The Control Word is Used . . . . . .  6
   3.  VCCV Control Channel When The Control Word is Not Used . . . .  6
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 19
     4.1.  VCCV Interface Parameters Sub-TLV  . . . . . . . . . . . . 19
       4.1.1.  MPLS VCCV Control Channel (CC) Type 4  . . . . . . . . 19
   5. Security Considerations   . . . . . . . . . . . . . . . . . . . 24
   6. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 25
   7. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 26
     7.1. Normative References  . . . . . . . . . . . . . . . . . . . 26
     7.2. Informative References  . . . . . . . . . . . . . . . . . . 26

1.  Introduction

   There is a need for fault detection and diagnostic mechanisms that
   can be used for end-to-end fault detection and diagnostics for a
   Pseudowire, as a means of determining the PW's true operational
   state.  Operators have indicated in [RFC4377], [RFC3916].
   that such a tool is required for PW operation and maintenance. To
   this end, the IETF's PWE3 Working Group defined The Virtual 
   Circuit Connectivity Verification Protocol (VCCV) in [RFC5085]. 
   Since then a number of interoperability issues have arisen with the 
   protocol as it is defined. 

   Over time, a variety of VCCV options or "modes" have been created to 
   support legacy hardware, the use of the control word in some cases, 
   while in others not. The difficulty of operating these 
   different combinations of "modes" have been detailed in an 
Show full document text