Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

The Pseudowire (PW) and Virtual Circuit Connectivity Verification (VCCV) Implementation Survey Results (RFC7079)

IP.com Disclosure Number: IPCOM000233174D
Original Publication Date: 2013-Nov-01
Included in the Prior Art Database: 2013-Nov-28
Document File: 82 page(s) / 69K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Del Regno: AUTHOR [+4]

Abstract

Most Pseudowire Emulation Edge-to-Edge (PWE3) encapsulations mandate the use of the Control Word (CW) to carry information essential to the emulation, to inhibit Equal-Cost Multipath (ECMP) behavior, and to discriminate Operations, Administration, and Maintenance (OAM) from Pseudowire (PW) packets. However, some encapsulations treat the Control Word as optional. As a result, implementations of the CW, for encapsulations for which it is optional, vary by equipment manufacturer, equipment model, and service provider network. Similarly, Virtual Circuit Connectivity Verification (VCCV) supports three Control Channel (CC) types and multiple Connectivity Verification (CV) types. This flexibility has led to reports of interoperability issues within deployed networks and associated documents to attempt to remedy the situation.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                 N. Del Regno, Ed. Request for Comments: 7079                  Verizon Communications, Inc. Category: Informational                                    A. Malis, Ed. ISSN: 2070-1721                                               Consultant                                                            November 2013

 The Pseudowire (PW) and Virtual Circuit Connectivity Verification (VCCV)                      Implementation Survey Results

Abstract

   The IETF Pseudowire Emulation Edge-to-Edge (PWE3) working group has    defined many encapsulations of various layer 1 and layer 2 service-    specific PDUs and circuit data.  In most of these encapsulations, use    of the Pseudowire (PW) Control Word is required.  However, there are    several encapsulations for which the Control Word is optional, and    this optionality has been seen in practice to possibly introduce    interoperability concerns between multiple implementations of those    encapsulations.  This survey of the Pseudowire / Virtual Circuit    Connectivity Verification (VCCV) user community was conducted to    determine implementation trends and the possibility of always    mandating the Control Word.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   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).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see 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/rfc7079.

 Del Regno & Malis             Informational                     [Page 1]
 RFC 7079          PW/VCCV Implementation Survey Results    November 2013

 Copyright Notice

   Copyright (c) 2013 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 L...