MPLS Forwarding Compliance and Performance Requirements
draft-villamizar-mpls-forwarding-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-10-08
Replaced by rfc7325, draft-ietf-mpls-forwarding
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
MPLS                                                  C. Villamizar, Ed.
Internet-Draft                                    Outer Cape Cod Network
Intended status: Informational                                Consulting
Expires: April 11, 2013                                      K. Kompella
                                                        Contrail Systems
                                                         October 8, 2012

        MPLS Forwarding Compliance and Performance Requirements
                  draft-villamizar-mpls-forwarding-00

Abstract

   This document provides guidelines for implementors regarding MPLS
   forwarding and a basis for evaluations of forwarding implementations.
   Guidelines cover basic MPLS forwarding, forwarding when a deep MPLS
   label stack is encountered, MPLS UHP operations which require one or
   more label POP plus a PUSH, guidelines for hashing an MPLS stack and
   payload for multipath, and conformance and performance requirements
   for recent pseudowire and MPLS standards.

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 April 11, 2013.

Copyright Notice

   Copyright (c) 2012 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

Villamizar & Kompella    Expires April 11, 2013                 [Page 1]
Internet-Draft               MPLS Forwarding                October 2012

   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
     1.1.  Apparent Misconceptions  . . . . . . . . . . . . . . . . .  3
     1.2.  Target Audience  . . . . . . . . . . . . . . . . . . . . .  4
   2.  Forwarding Issues  . . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  Forwarding Basics  . . . . . . . . . . . . . . . . . . . .  5
       2.1.1.  Early Uses of Multiple Label Stack Entries . . . . . .  5
       2.1.2.  MPLS Link Bundling . . . . . . . . . . . . . . . . . .  6
       2.1.3.  MPLS Hierarchy . . . . . . . . . . . . . . . . . . . .  6
     2.2.  Packet Rates . . . . . . . . . . . . . . . . . . . . . . .  6
     2.3.  MPLS Multipath Techniques  . . . . . . . . . . . . . . . .  7
       2.3.1.  Pseudowire Control Word  . . . . . . . . . . . . . . .  8
       2.3.2.  Pseudowire Flow Label  . . . . . . . . . . . . . . . .  8
       2.3.3.  MPLS Entropy Label . . . . . . . . . . . . . . . . . .  8
     2.4.  MPLS-TP and UHP  . . . . . . . . . . . . . . . . . . . . .  9
   3.  Questions for Suppliers  . . . . . . . . . . . . . . . . . . .  9
   4.  Forwarding Compliance and Performance Testing  . . . . . . . . 11
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 15
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 15
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 16
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17

Villamizar & Kompella    Expires April 11, 2013                 [Page 2]
Internet-Draft               MPLS Forwarding                October 2012

1.  Introduction

   The document addresses concerns raised on the MPLS WG mailing list
   about shortcomings in implementations of MPLS forwarding.

   Although this document is informational, the key words "MUST", "MUST
   NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
   "RECOMMENDED", "MAY", and "OPTIONAL" are used.  For those who wish to
   take the advice of this document, these keywords SHOULD be
   interpreted as described in RFC 2119 [RFC2119].  Similarly, the
   References section is split into Normative and Informative
   subsections.  In this case references which are normative for
Show full document text