RFC 6073 on Segmented Pseudowire

rfc-editor@rfc-editor.org Tue, 18 January 2011 20:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0941228C1A5; Tue, 18 Jan 2011 12:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level:
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ChP45bSKwZuW; Tue, 18 Jan 2011 12:30:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 1B2FE28C190; Tue, 18 Jan 2011 12:30:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 61547E0738; Tue, 18 Jan 2011 12:32:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6073 on Segmented Pseudowire
From: rfc-editor@rfc-editor.org
Message-Id: <20110118203244.61547E0738@rfc-editor.org>
Date: Tue, 18 Jan 2011 12:32:44 -0800
Cc: pwe3@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 18 Jan 2011 20:30:13 -0000

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

        
        RFC 6073

        Title:      Segmented Pseudowire 
        Author:     L. Martini, C. Metz,
                    T. Nadeau, M. Bocci,
                    M. Aissaoui
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    lmartini@cisco.com, 
                    chmetz@cisco.com, 
                    tnadeau@lucidvision.com,  
                    matthew.bocci@alcatel-lucent.co.uk, 
                    mustapha.aissaoui@alcatel-lucent.com
        Pages:      43
        Characters: 102428
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-segmented-pw-18.txt

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

This document describes how to connect pseudowires (PWs) between
different Packet Switched Network (PSN) domains or between two or
more distinct PW control plane domains, where a control plane domain
uses a common control plane protocol or instance of that protocol for
a given PW.  The different PW control plane domains may belong to
independent autonomous systems, or the PSN technology is
heterogeneous, or a PW might need to be aggregated at a specific PSN
point.  The PW packet data units are simply switched from one PW to
another without changing the PW payload.  [STANDARDS-TRACK]

This document is a product of the Pseudo Wire 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