[mpls] RFC 6790 on The Use of Entropy Labels in MPLS Forwarding

rfc-editor@rfc-editor.org Mon, 19 November 2012 20:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 209BA21F8754; Mon, 19 Nov 2012 12:36:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tKTwzwf3As-H; Mon, 19 Nov 2012 12:36:27 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 7192A21F8752; Mon, 19 Nov 2012 12:36:27 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 25504B1E003; Mon, 19 Nov 2012 12:29:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121119202905.25504B1E003@rfc-editor.org>
Date: Mon, 19 Nov 2012 12:29:05 -0800
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6790 on The Use of Entropy Labels in MPLS Forwarding
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 20:36:28 -0000

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

        
        RFC 6790

        Title:      The Use of Entropy Labels 
                    in MPLS Forwarding 
        Author:     K. Kompella, J. Drake,
                    S. Amante, W. Henderickx, L. Yong
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2012
        Mailbox:    kireeti.kompella@gmail.com, 
                    jdrake@juniper.net, 
                    shane@level3.net,
                    wim.henderickx@alcatel-lucent.com, 
                    lucy.yong@huawei.com
        Pages:      25
        Characters: 53837
        Updates:    3031, 3107, 3209, 5036

        I-D Tag:    draft-ietf-mpls-entropy-label-06.txt

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

Load balancing is a powerful tool for engineering traffic across a
network.  This memo suggests ways of improving load balancing across
MPLS networks using the concept of "entropy labels".  It defines the
concept, describes why entropy labels are useful, enumerates
properties of entropy labels that allow maximal benefit, and shows
how they can be signaled and used for various applications.  This
document updates RFCs 3031, 3107, 3209, and 5036.  [STANDARDS-TRACK]

This document is a product of the Multiprotocol Label Switching 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