MPLS Flow Identification
draft-bryant-mpls-flow-ident-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-10-24
Replaced by draft-ietf-mpls-flow-ident
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)
MPLS                                                           S. Bryant
Internet-Draft                                              C. Pignataro
Intended status: Informational                             Cisco Systems
Expires: April 27, 2015                                 October 24, 2014

                        MPLS Flow Identification
                    draft-bryant-mpls-flow-ident-00

Abstract

   This memo discusses the desired capabilities for MPLS flow
   identification.  The key application that needs this is in-band
   performance monitoring of user data packets.

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 27, 2015.

Copyright Notice

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

Bryant & Pignataro       Expires April 27, 2015                 [Page 1]
Internet-Draft                   MPLS FI                    October 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Loss Measurement Considerations . . . . . . . . . . . . . . .   3
   3.  Units of identification . . . . . . . . . . . . . . . . . . .   3
   4.  Types of LSP  . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Network Scope . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Backwards Compatibility . . . . . . . . . . . . . . . . . . .   6
   7.  Dataplane . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Control Plane . . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Manageability Considerations  . . . . . . . . . . . . . . . .   8
   10. Privacy Considerations  . . . . . . . . . . . . . . . . . . .   8
   11. Security Considerations . . . . . . . . . . . . . . . . . . .   8
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   13. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     14.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     14.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   This memo discusses the desired capabilities for MPLS flow
   identification.  The key application that needs this is in-band
   performance monitoring of user data packets.

   There is a need to identify flows in MPLS networks for applications
   such as packet loss and packet delay measurement.  A method of loss
   and delay measurement in MPLS networks was defined in [RFC6374].
   However this work needs to be extended to deal with different
   granularities of flow and to address a number of the multi-point
   cases in which a number of ingress LSRs could send to one or more
   destinations.

   Improvements in link and transmission technologies mean that it is
   difficult to assess a loss using synthetic traffic due to the very
   low loss rate in normal operation.  That together with more demanding
   service level requirements mean that network operators need to be
   able to measure the loss of the actual user data traffic.  Any
   technique deployed needs to be transparent to the end user, and it
   needs to be assumed that they will not take any active part in the
   measurement process.  Indeed it is important that any flow
   identification technique be invisible to them and that no remnant of
   the identification of measurement process leak into their network.

Bryant & Pignataro       Expires April 27, 2015                 [Page 2]
Internet-Draft                   MPLS FI                    October 2014

2.  Loss Measurement Considerations

   Modern networks normally drop very few packets, thus packet loss
   measurement are highly sensitive to counter errors.  Without some
Show full document text