[PWE3] RFC 7189 on Virtual Circuit Connectivity Verification (VCCV) Capability Advertisement for MPLS Transport Profile (MPLS-TP)
rfc-editor@rfc-editor.org Mon, 31 March 2014 19:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com
(Postfix) with ESMTP id 3B16C1A6FE9; Mon, 31 Mar 2014 12:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No,
score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hGdWuucp_u0a;
Mon, 31 Mar 2014 12:47:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3])
by ietfa.amsl.com (Postfix) with ESMTP id BC2601A6FED;
Mon, 31 Mar 2014 12:47:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 88A547FC3B3;
Mon, 31 Mar 2014 12:47:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20140331194709.88A547FC3B3@rfc-editor.org>
Date: Mon, 31 Mar 2014 12:47:09 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/Sg2dlJKTDQMc7M6z2CtcVvHXgx8
Cc: drafts-update-ref@iana.org, pwe3@ietf.org, rfc-editor@rfc-editor.org
Subject: [PWE3] RFC 7189 on Virtual Circuit Connectivity Verification (VCCV)
Capability Advertisement for MPLS Transport Profile (MPLS-TP)
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>,
<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3/>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>,
<mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Mar 2014 19:47:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7189
Title: Virtual Circuit Connectivity Verification (VCCV)
Capability Advertisement for MPLS Transport Profile
(MPLS-TP)
Author: G. Mirsky
Status: Standards Track
Stream: IETF
Date: March 2014
Mailbox: gregory.mirsky@ericsson.com
Pages: 7
Characters: 14254
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pwe3-mpls-tp-cv-adv-06.txt
URL: http://www.rfc-editor.org/rfc/rfc7189.txt
This document specifies how signaling and selection processes for
Pseudowire (PW) Virtual Circuit Connectivity Verification (VCCV) are
modified to ensure backward compatibility and allow use of proactive
Connectivity Verification (CV), Continuity Check (CC), and Remote
Defect Indication (RDI) over MPLS Transport Profile (MPLS-TP) PWs.
This document introduces four new CV types and, to accommodate them,
a new VCCV Extended CV parameter for PW Interface Parameters Sub-TLV
is defined.
This document is a product of the Pseudowire Emulation Edge to Edge Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC