RFC6374 UDP Return Path
draft-ietf-mpls-rfc6374-udp-return-path-04

The information below is for an old version of the document
Document Type Active Internet-Draft (mpls WG)
Last updated 2016-01-07 (latest revision 2015-08-26)
Replaces draft-ietf-mpls-pm-udp-return
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Loa Andersson
Shepherd write-up Show (last changed 2015-10-21)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Deborah Brungard
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
MPLS                                                           S. Bryant
Internet-Draft                                              S. Sivabalan
Intended status: Standards Track                                 S. Soni
Expires: February 27, 2016                                 Cisco Systems
                                                         August 26, 2015

                        RFC6374 UDP Return Path
               draft-ietf-mpls-rfc6374-udp-return-path-04

Abstract

   This document specifies the procedure 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 February 27, 2016.

Copyright Notice

   Copyright (c) 2015 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 February 27, 2016               [Page 1]
Internet-Draft           RFC6374 UDP Return Path             August 2015

1.  Introduction

   This document describes how Packet Loss and Delay Measurement for
   MPLS Networks protocol (MPLS-PLDM) [RFC6374] out-of-band responses
   can be delivered to the querier using UDP/IP.

   The use of UDP may be required to support data path management such
   as passage through firewalls, or to provide the necessary
   multiplexing needed in bistatic operation where the querier and the
   collector are not co-located and the collector is gathering the
   response information for a number of responders.  In a highly scaled
   system some MPLS-PLDM sessions may be off-loaded to a specific node
   within the distributed system that comprises the Label Switching
   Router (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
   querier 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, if a UDP
   Return Object (URO) is present in a MPLS-PLDM Query, the responder
   MUST use the IP address and UDP port in the URO to reply back to the
   querier.  Multiple UROs MAY be present in a MPLS-PLDM Query
   indicating that an identical responses SHOULD be sent to each
   address-port pair.  A responder MAY be designed or configured to only
   transmit a single response, in which case the response MUST be sent
   using the parameters specified in the first URO in the query packet.

   The procedures defined in this document may be applied to both
   unidirectional 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

Bryant, et al.          Expires February 27, 2016               [Page 2]
Internet-Draft           RFC6374 UDP Return Path             August 2015
Show full document text