MPLS Performance Measurement UDP Return Path
draft-bryant-mpls-oam-udp-return-01

The information below is for an old version of the document
Document Type Active Internet-Draft (candidate for mpls WG)
Last updated 2014-06-16 (latest revision 2014-05-21)
Replaced by draft-ietf-mpls-pm-udp-return
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS                                                           S. Bryant
Internet-Draft                                              S. Sivabalan
Intended status: Standards Track                                 S. Soni
Expires: November 22, 2014                                 Cisco Systems
                                                            May 21, 2014

              MPLS Performance Measurement UDP Return Path
                  draft-bryant-mpls-oam-udp-return-01

Abstract

   This document specifies the proceedure to be used by the Packet Loss
   and Delay Measurement for MPLS Networks protocol defined in RFC6374
   when sending and processing MPLS performance management out-of-band
   responses for delay and loss measurements over an IP/UDP return path.

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 November 22, 2014.

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, et al.          Expires November 22, 2014               [Page 1]
Internet-Draft             MPLS PM UDP Return                   May 2014

1.  Introduction

   The Packet Loss and Delay Measurement for MPLS Networks protocol
   (MPLS-PLDM) defined in[RFC6374] does not define how an MPLS-PLDM out-
   of-band response delivered over IP will be transmitted to the
   Querier.

   In a highly scaled system some MPLS-PLDM sessions may be off-loaded
   to a specific node within a the distributed system that comprises the
   LSR as a whole.  In such systems the response may arrive via any
   interface in the LSR and need to internally forwarded to the
   processor tasked with handling the particular MPLS-PLDM measurement.
   Currently the MPLS-PLDM protocol does not have any mechanism to
   deliver the PLDM Response message to particular node within a multi-
   CPU LSR.

   The procedure described in this specification describes how the
   queryer requests delivery of the MPLS-PLDM response over IP to a
   dynamic UDP port.  It makes no other changes to the protocol and thus
   does not affect the case where the reponse is delivered over a MPLS
   Associated Channel [RFC5586].

2.  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].

3.  Solution Overview

   This document specifies that, unless configured otherwise, the
   Addressing Object defined in [RFC6374] SHALL be sent in MPLS-PLDM
   query messages to tell the responder the IP return address to be
   used.  This document also defines Return UDP Port object which,
   unless configured otherwise SHALL be used to the return UDP port.
   The Addressing Object and the Return UDP PORT object carried in the
   MPLS-PLDM query message are used to specify to the Responder how to
   return the response message.

   The procedures defined in this document may be applied to both
   unidirectional tunnels and Bidirectional LSPs.  In this document, the
   term bidirectional LSP includes the co-routed Bidirectional LSP
   defined in [RFC3945] and the associated bidirectional LSP that is
   constructed from a pair of unidirectional LSPs (one for each
   direction) that are associated with one another at the LSP's ingress/
   egress points [RFC5654].  The mechanisms defined in this document can

Bryant, et al.          Expires November 22, 2014               [Page 2]
Internet-Draft             MPLS PM UDP Return                   May 2014

   apply to both IP/MPLS and the MPLS Transport Profile (MPLS-TP).

3.1.  Return UDP Port Object

   The format of the Return UDP Port Object is as follows:

       0                   1                   2                   3
Show full document text