BGP Diagnostic Path Attribute
draft-heitz-idr-diagnostic-attr-01

Document Type Active Internet-Draft (individual)
Last updated 2019-03-25
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)
IDR                                                             J. Heitz
Internet-Draft                                              P. Narasimha
Intended status: Standards Track                            S. Gulrajani
Expires: September 26, 2019                                        Cisco
                                                          March 25, 2019

                     BGP Diagnostic Path Attribute
                   draft-heitz-idr-diagnostic-attr-01

Abstract

   A BGP path attribute for the purpose of network diagnostics is
   described.  It is non-transitive, such that BGP speakers will not
   forward it by default.  It is structured as a list of elements.  An
   element begins with the BGP identifier and AS number of the speaker
   that appends the element and includes a list of TLVs.  Any speaker
   can add or remove an element to/from the list.  TLVs for a timestamp
   and for a checksum are described.

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

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.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Heitz, et al.          Expires September 26, 2019               [Page 1]
Internet-Draft          BGP Diagnostic Attribute              March 2019

   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.  Data Formats  . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Checksum TLV  . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Timestamp TLV . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Operational Considerations  . . . . . . . . . . . . . . . . .   5
   5.  Error Handling  . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   A BGP path attribute for the purpose of network diagnostics is
   described.  It is non-transitive, such that BGP speakers that do not
   recognize the attribute will not propagate it by default.  Even
   speakers that do recognize the attribute MUST NOT propagate it by
   default.  A speaker MAY propagate the attribute if it is configured
   to do so and MAY add it's own information as it does so.  The
   attribute is structured as a list of elements.  An element begins
   with the BGP identifier and AS number of the speaker that appends the
   element and includes a list of TLVs.  Any speaker can append or
   remove an element to/from the list.  TLVs for a timestamp and for a
   checksum are described.  The diagnostic attribute may be sent in a
   withdraw message.

2.  Data Formats

   The BGP diagnostic consists of a series of elements, each of which is
   formatted as follows.

Heitz, et al.          Expires September 26, 2019               [Page 2]
Internet-Draft          BGP Diagnostic Attribute              March 2019

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              ASN                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Show full document text