RFC 6391 on Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network

rfc-editor@rfc-editor.org Tue, 01 November 2011 23:17 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 9E4C61F0C41; Tue, 1 Nov 2011 16:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.758
X-Spam-Status: No, score=-101.758 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id JO5qhA7aAx-y; Tue, 1 Nov 2011 16:17:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 41B5421F8CB7; Tue, 1 Nov 2011 16:17:17 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 005C562189; Tue, 1 Nov 2011 16:12:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6391 on Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network
From: rfc-editor@rfc-editor.org
Message-Id: <20111101231255.005C562189@rfc-editor.org>
Date: Tue, 01 Nov 2011 16:12:54 -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: Tue, 01 Nov 2011 23:17:17 -0000

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

        RFC 6391

        Title:      Flow-Aware Transport of Pseudowires over 
                    an MPLS Packet Switched Network 
        Author:     S. Bryant, Ed.,
                    C. Filsfils, U. Drafz,
                    V. Kompella, J. Regan,
                    S. Amante
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    stbryant@cisco.com, 
        Pages:      19
        Characters: 43848
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-fat-pw-07.txt

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

Where the payload of a pseudowire comprises a number of distinct
flows, it can be desirable to carry those flows over the Equal Cost
Multiple Paths (ECMPs) that exist in the packet switched network.
Most forwarding engines are able to generate a hash of the MPLS label
stack and use this mechanism to balance MPLS flows over ECMPs.

This document describes a method of identifying the flows, or flow
groups, within pseudowires such that Label Switching Routers can
balance flows at a finer granularity than individual pseudowires.
The mechanism uses an additional label in the MPLS label stack. 

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

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