LSP Ping/Traceroute for Prefix SID in Presence of Multi-Algorithm/Multi-Topology Networks
draft-iqbal-spring-mpls-ping-algo-01

Document Type Active Internet-Draft (individual)
Last updated 2018-10-23
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                      F. Iqbal, Ed.
Internet-Draft                                                  N. Kumar
Updates: 8287 (if approved)                                       Z. Ali
Intended status: Standards Track                            C. Pignataro
Expires: April 26, 2019                                            Cisco
                                                        October 23, 2018

LSP Ping/Traceroute for Prefix SID in Presence of Multi-Algorithm/Multi-
                           Topology Networks
                  draft-iqbal-spring-mpls-ping-algo-01

Abstract

   [RFC8287] defines the extensions to MPLS LSP Ping and Traceroute for
   Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifier
   (SIDs) with an MPLS data plane.  The machinery defined in [RFC8287]
   works well in single topology, single algorithm deployments where
   each Prefix SID is only associated with a single IP prefix.  In
   multi-topology networks, or networks deploying multiple algorithms
   for the same IP Prefix, MPLS echo request needs to carry additional
   information in the Target FEC Stack sub-TLVs to properly validate IGP
   Prefix SID.

   This document updates [RFC8287] by modifying IPv4 and IPv6 IGP-Prefix
   Segment ID FEC sub-TLVs to also include algorithm identification
   while maintaining backwards compatibility.  This document also
   introduces new Target FEC Stack sub-TLVs for Prefix SID validation in
   multi-topology networks.

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 https://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 26, 2019.

Iqbal, et al.            Expires April 26, 2019                 [Page 1]
Internet-Draft     Detecting MPLS Data Plane Failures       October 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Algorithm Identification for IGP-Prefix SID Sub-TLVs  . . . .   5
     4.1.  IPv4 IGP-Prefix Segment ID Sub-TLV  . . . . . . . . . . .   5
     4.2.  IPv6 IGP-Prefix Segment ID Sub-TLV  . . . . . . . . . . .   5
   5.  Multi-topology Support for IGP Prefix SID . . . . . . . . . .   6
     5.1.  Multi-topology IPv4 IGP-Prefix Segment ID Sub-TLV . . . .   6
     5.2.  Multi-Topology IPv6 IGP-Prefix Segment ID Sub-TLV . . . .   6
   6.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Single-Topology Networks  . . . . . . . . . . . . . . . .   7
       6.1.1.  Initiator Node Procedures . . . . . . . . . . . . . .   7
       6.1.2.  Responder Node Procedures . . . . . . . . . . . . . .   8
     6.2.  Multi-Topology Networks . . . . . . . . . . . . . . . . .   8
       6.2.1.  Initiator Node Procedures . . . . . . . . . . . . . .   8
       6.2.2.  Responding Node Procedures  . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
Show full document text