Provide for method to know accepted and rejected NLRI.
draft-mauch-bgp-accepted-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-18
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
Inter-Domain Routing                                            J. Mauch
Internet-Draft                                                    Akamai
Intended status: Informational                         November 18, 2019
Expires: May 21, 2020

         Provide for method to know accepted and rejected NLRI.
                      draft-mauch-bgp-accepted-00

Abstract

   This document defines a method to receive accepted and rejected NLRI
   over a BGP peering session.

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 May 21, 2020.

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.

Mauch                     Expires May 21, 2020                  [Page 1]
Internet-Draft             BGP-TRACE-ACCEPTED              November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     7.2.  Informational References  . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   BGP [RFC4271] operators face challenges when attempting to
   troubleshoot external BGP sessions.  Commonly operators debug BGP
   sessions with commands that display the results of advertised or
   received routes.

   When operating a network, you can easily verify you are sending
   routes to a BGP peer, but you have limited ability to understand the
   external partner device.  Common debugging tools such as a looking
   glass or contacting a remote operator via e-mail, telephone or other
   out of band methods is required.

   This proposal intends to provide an automated method to see the NLRI
   eligible for selection that pass any filtering methods provided by
   the peer software stack.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] when, and only when, they appear in all capitals, as
   shown here.

3.  Solution

   The requesting device will send a BGP message of type XXX to the
   partner device requesting the list of the NLRI. (excerpted from
   rfc2918)

Mauch                     Expires May 21, 2020                  [Page 2]
Internet-Draft             BGP-TRACE-ACCEPTED              November 2019

             Message Format: One AFI, SAFI encoded as

                     0       7      15      23      31
                     +-------+-------+-------+-------+
                     |      AFI      | Res.  | SAFI  |
                     +-------+-------+-------+-------+

   The meaning, use and encoding of this AFI, SAFI field is the same as
   defined in [BGP-MP, sect. 7].  More specifically,

   AFI - Address Family Identifier (16 bit).

   Res. - Reserved (8 bit) field.  Should be set to 0 by the sender and
   ignored by the receiver.

   SAFI - Subsequent Address Family Identifier (8 bit).

   Responses will include:

             Message Format: per

                     0       15      31      47      64
                     +---+---+---+---+---+---+---+---+
                     |   accepted    |    rejected   |
Show full document text