The Use of MPLS Special Purpose Labels for the Computation of Load Balancing
draft-pignataro-mpls-reserved-labels-lb-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-01-25
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       C. Pignataro
Internet-Draft                                       Cisco Systems, Inc.
Updates:  4928, 6790 (if approved)                          L. Andersson
Intended status:  Standards Track                    Huawei Technologies
Expires:  July 29, 2013                                      K. Kompella
                                                        Juniper Networks
                                                        January 25, 2013

   The Use of MPLS Special Purpose Labels for the Computation of Load
                               Balancing
               draft-pignataro-mpls-reserved-labels-lb-00

Abstract

   In addition to being used for forwarding, an MPLS label stack may
   also be used as an entropy source to perform load balancing
   computation in various ways.  RFC 4928 and RFC 6790 describe this
   mechanism in great detail.  However, those two RFCs differ in the use
   of MPLS special purpose labels (previously referred to as "reserved
   labels") for computation of load balancing.  This document restricts
   the use of MPLS special purpose labels for computation of load
   balancing, clarifying the difference in specifications.

   This document updates RFC 4928 and RFC 6790.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 29, 2013.

Pignataro, et al.         Expires July 29, 2013                 [Page 1]
Internet-Draft         MPLS Reserved Labels and LB          January 2013

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  MPLS Reserved Labels and Load Balancing . . . . . . . . . . . . 3
     2.1.  Current Specifications  . . . . . . . . . . . . . . . . . . 3
     2.2.  Detail of Updates . . . . . . . . . . . . . . . . . . . . . 4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   5.  Normative References  . . . . . . . . . . . . . . . . . . . . . 4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 4

Pignataro, et al.         Expires July 29, 2013                 [Page 2]
Internet-Draft         MPLS Reserved Labels and LB          January 2013

1.  Introduction

   In addition to being used for forwarding, an MPLS label stack may
   also be used as an entropy source to perform load balancing
   computation in various ways.  RFC 4928 and RFC 6790 describe this
   mechanism in great detail.  However, those two RFCs defer in the use
   of MPLS special purpose labels (previously referred to as "reserved
   labels") for computation of load balancing.  This document restricts
   the use of MPLS special purpose labels for computation of load
   balancing, clarifying the difference in specifications.

   This document updates RFC 4928 and RFC 6790.

2.  MPLS Reserved Labels and Load Balancing

2.1.  Current Specifications

   This section highlights current specifications relating to the usage
   of MPLS special purpose labels for purposes of load balancing
   computation.

   [RFC4928] states that special purpose labels ("reserved labels") may
   be used for load balancing, and describes current ECMP practice as
   follows:

      It must also be noted that LSRs that correctly identify a payload
      as not being IP most often will load-share traffic across multiple
      equal-cost paths based on the label stack.  Any reserved label, no
Show full document text