datatracker.ietf.org
Sign in
Version 5.9.0, 2014-12-18
Report a bug

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

Document type: Active Internet-Draft (pals WG)
Document stream: IETF
Last updated: 2014-11-16 (latest revision 2014-09-02)
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document Jun 2015
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

PWE3                                                           T. Nadeau
Internet-Draft                                               lucidvision
Updates: 5085 (if approved)                                   L. Martini
Intended status: Standards Track                               S. Bryant
Expires: March 6, 2015                                     Cisco Systems
                                                       September 2, 2014

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

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.  It describes new rules requiring this mode to be used as
   the default/mandatory mode of operation for VCCV.  The older VCCV
   types will remain optional.

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 March 6, 2015.

Copyright Notice

   Copyright (c) 2014 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

Nadeau, et al.            Expires March 6, 2015                 [Page 1]
Internet-Draft                   VCCV 2                   September 2014

   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.  Requirements Language and Terminology . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  VCCV Control Channel When The Control Word is Used  . . . . .   5
   4.  VCCV Control Channel When The Control Word is Not Used  . . .   6
   5.  VCCV Capability Advertisement . . . . . . . . . . . . . . . .   7
   6.  Manageability Considerations  . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  VCCV Interface Parameters Sub-TLV . . . . . . . . . . . .   7
     8.2.  MPLS VCCV Control Channel (CC) Type 4 . . . . . . . . . .   7
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Requirements Language and Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

   AC             Attachment Circuit [RFC3985].

   AVP            Attribute Value Pair [RFC3931].

   CC             Control Channel (used as CC Type).

   CE             Customer Edge.

   CV             Connectivity Verification (used as CV Type).

   CW             Control Word [RFC3985].

   L2SS           L2-Specific Sublayer [RFC3931].

   LCCE           L2TP Control Connection Endpoint [RFC3931].

Nadeau, et al.            Expires March 6, 2015                 [Page 2]
Internet-Draft                   VCCV 2                   September 2014

[include full document text]