[PWE3] RFC 6478 on Pseudowire Status for Static Pseudowires

rfc-editor@rfc-editor.org Mon, 07 May 2012 19:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AFC221F8663; Mon, 7 May 2012 12:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.097
X-Spam-Level:
X-Spam-Status: No, score=-102.097 tagged_above=-999 required=5 tests=[AWL=-0.097, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tR2z6mLjSCDU; Mon, 7 May 2012 12:03:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 146D821F865B; Mon, 7 May 2012 12:03:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 81917B1E008; Mon, 7 May 2012 12:01:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120507190144.81917B1E008@rfc-editor.org>
Date: Mon, 07 May 2012 12:01:41 -0700
Cc: pwe3@ietf.org, rfc-editor@rfc-editor.org
Subject: [PWE3] RFC 6478 on Pseudowire Status for Static Pseudowires
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires 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, 07 May 2012 19:03:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6478

        Title:      Pseudowire Status for Static Pseudowires 
        Author:     L. Martini, G. Swallow,
                    G. Heron, M. Bocci
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2012
        Mailbox:    lmartini@cisco.com, 
                    swallow@cisco.com, 
                    giheron@cisco.com,
                    matthew.bocci@alcatel-lucent.com
        Pages:      13
        Characters: 28285
        Updates:    RFC5885

        I-D Tag:    draft-ietf-pwe3-static-pw-status-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6478.txt

This document specifies a mechanism to signal Pseudowire (PW) status
messages using a PW associated channel (ACh).  Such a mechanism is
suitable for use where no PW dynamic control plane exits, known as
static PWs, or where a Terminating Provider Edge (T-PE) needs
to send a PW status message directly to a far-end T-PE.  The mechanism
allows PW Operations, Administration, and Maintenance (OAM) message
mapping and PW redundancy to operate on static PWs.  This document
also updates RFC 5885 in the case when Bi-directional Forwarding 
Detection (BFD) is used to convey PW status-signaling information.
[STANDARDS-TRACK]

This document is a product of the Pseudowire Emulation Edge to Edge Working Group of the IETF.

This is now a Proposed Standard Protocol.

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/rfcsearch.html.
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