[rfc-dist] BCP0128 RFC 4928 on Avoiding Equal Cost Multipath Treatment in MPLS Networks

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Jun 27 17:26:03 PDT 2007


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

        BCP 128        
        RFC 4928

        Title:      Avoiding Equal Cost Multipath Treatment 
                    in MPLS Networks 
        Author:     G. Swallow, S. Bryant,
                    L. Andersson
        Status:     Best Current Practice
        Date:       June 2007
        Mailbox:    stbryant at cisco.com, 
                    swallow at cisco.com, 
                    loa at pi.se
        Pages:      8
        Characters: 18376
        Updates:    
        See-Also:   BCP0128

        I-D Tag:    draft-ietf-mpls-ecmp-bcp-03.txt

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

This document describes the Equal Cost Multipath (ECMP) behavior of
currently deployed MPLS networks.  This document makes best practice
recommendations for anyone defining an application to run over an
MPLS network that wishes to avoid the reordering that can result from
transmission of different packets from the same flow over multiple
different equal cost paths.  These recommendations rely on inspection
of the IP version number field in packets.  Despite the heuristic
nature of the recommendations, they provide a relatively safe way
to operate MPLS networks, even if future allocations of IP version
numbers were made for some purpose.  This document specifies an Internet 
Best Current Practices for the Internet Community, and requests discussion 
and suggestions for improvements.

This document is a product of the Multiprotocol Label Switching
Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.


This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list