RFC 6658 on Packet Pseudowire Encapsulation over an MPLS PSN

rfc-editor@rfc-editor.org Thu, 19 July 2012 00:12 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D587811E81C7; Wed, 18 Jul 2012 17:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.93
X-Spam-Level:
X-Spam-Status: No, score=-101.93 tagged_above=-999 required=5 tests=[AWL=0.070, 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 6ZwA2J372REo; Wed, 18 Jul 2012 17:12:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBC611E80E8; Wed, 18 Jul 2012 17:12:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 477A472E002; Wed, 18 Jul 2012 17:13:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6658 on Packet Pseudowire Encapsulation over an MPLS PSN
From: rfc-editor@rfc-editor.org
Message-Id: <20120719001309.477A472E002@rfc-editor.org>
Date: Wed, 18 Jul 2012 17:13:09 -0700
Cc: pwe3@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Thu, 19 Jul 2012 00:12:56 -0000

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

        
        RFC 6658

        Title:      Packet Pseudowire Encapsulation over an 
                    MPLS PSN 
        Author:     S. Bryant, Ed.,
                    L. Martini,
                    G. Swallow,
                    A. Malis
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2012
        Mailbox:    stbryant@cisco.com, 
                    lmartini@cisco.com, 
                    swallow@cisco.com,
                    andrew.g.malis@verizon.com
        Pages:      15
        Characters: 32164
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-packet-pw-04.txt

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

This document describes a pseudowire mechanism that is used to
transport a packet service over an MPLS PSN in the case where the
client Label Switching Router (LSR) and the server Provider Edge
equipments are co-resident in the same equipment.  This pseudowire
mechanism may be used to carry all of the required layer 2 and layer
3 protocols between the pair of client LSRs.  [STANDARDS-TRACK]

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