RFC 7267 on Dynamic Placement of Multi-Segment Pseudowires

rfc-editor@rfc-editor.org Tue, 17 June 2014 23:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id A156E1A00A3; Tue, 17 Jun 2014 16:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 8xSjNTok9mC3; Tue, 17 Jun 2014 16:28:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 62D7C1A00C3; Tue, 17 Jun 2014 16:28:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4697B180479; Tue, 17 Jun 2014 16:26:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7267 on Dynamic Placement of Multi-Segment Pseudowires
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140617232647.4697B180479@rfc-editor.org>
Date: Tue, 17 Jun 2014 16:26:47 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/lLhsiUI4R47OV452WqX0CQliQZ8
Cc: drafts-update-ref@iana.org, pwe3@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 23:28:05 -0000

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

        RFC 7267

        Title:      Dynamic Placement of Multi-Segment Pseudowires 
        Author:     L. Martini, Ed.,
                    M. Bocci, Ed.,
                    F. Balus, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2014
        Mailbox:    lmartini@cisco.com, 
        Pages:      24
        Characters: 49414
        Updates:    RFC 6073

        I-D Tag:    draft-ietf-pwe3-dynamic-ms-pw-22.txt

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

RFC 5254 describes the service provider requirements for extending
the reach of pseudowires (PWs) across multiple Packet Switched
Network domains.  A multi-segment PW is defined as a set of two or
more contiguous PW segments that behave and function as a single
point-to-point PW.  This document describes extensions to the PW
control protocol to dynamically place the segments of the
multi-segment pseudowire among a set of Provider Edge (PE) routers.
This document also updates RFC 6073 by updating the value of the
Length field of the PW Switching Point PE Sub-TLV Type 0x06 to 14.

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

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