RFC8287 Sub-TLV Length Clarification
draft-ietf-mpls-rfc8287-len-clarification-00

Document Type Active Internet-Draft (mpls WG)
Last updated 2019-05-23 (latest revision 2019-03-25)
Replaces draft-nainar-mpls-rfc8287-len-clarification
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state Waiting for WG Chair Go-Ahead
Document shepherd Loa Andersson
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Loa Andersson <loa@pi.nu>
Network Work group                                             N. Nainar
Internet-Draft                                              C. Pignataro
Updates: 8287 (if approved)                          Cisco Systems, Inc.
Intended status: Standards Track                                F. Iqbal
Expires: September 26, 2019                                   Individual
                                                           A. Vainshtein
                                                             ECI Telecom
                                                          March 25, 2019

                  RFC8287 Sub-TLV Length Clarification
              draft-ietf-mpls-rfc8287-len-clarification-00

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.  RFC8287 proposes 3 Target FEC Stack
   Sub-TLVs.  While the standard defines the format and procedure to
   handle those Sub-TLVs, it does not sufficiently clarify how the
   length of the Segment ID Sub-TLVs should be computed to include in
   the Length field of the Sub-TLVs which may result in interoperability
   issues.

   This document updates RFC8287 by clarifying the length of each
   Segment ID Sub-TLVs defined in RFC8287.

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 September 26, 2019.

Nainar, et al.         Expires September 26, 2019               [Page 1]
Internet-Draft    RFC8287 Sub-TLV Length Clarification        March 2019

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Requirements notation . . . . . . . . . . . . . . . . . . . .   3
   4.  Length field clarification for Segment ID Sub-TLVs  . . . . .   3
     4.1.  IPv4 IGP-Prefix Segment ID Sub-TLV  . . . . . . . . . . .   3
     4.2.  IPv6 IGP-Prefix Segment ID Sub-TLV  . . . . . . . . . . .   3
     4.3.  IGP-Adjacency Segment ID Sub-TLV  . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [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.  [RFC8287] proposes 3 Target FEC
   Stack Sub-TLVs.  While the standard defines the format and procedure
   to handle those Sub-TLVs, it does not sufficiently clarify how the
   length of the Segment ID Sub-TLVs should be computed to include in
   the Length field of the Sub-TLVs which may result in interoperability
   issues.

   This document updates [RFC8287] by clarifying the length of each
   Segment ID Sub-TLVs defined in [RFC8287].

Nainar, et al.         Expires September 26, 2019               [Page 2]
Internet-Draft    RFC8287 Sub-TLV Length Clarification        March 2019

2.  Terminology

   This document uses the terminologies defined in [RFC8402], [RFC8029],
   [RFC8287] and so the readers are expected to be familiar with the
   same.

3.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Show full document text