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.

Table of Contents

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

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)

          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   |
                  +---+---+---+---+---+---+---+---+

Count of NLRI accepted (unsigned 32-bits)

Count of NLRI rejected (unsigned 32-bits)

List of NLRI accepted (NLRI list in same format as UPDATE)

List of NLRI rejected (NLRI list in same format as UPDATE - infeasible)

4. Acknowledgements

The authors would like to thank the following people for their comments and support: XXX.

5. Security Considerations

This message MAY be subject to rate-limits by a partner device to protect itself from CPU or other resource exhaustion. A suggested interval is to not permit more than one request per 60 seconds.

6. IANA Considerations

This document has unknown IANA Considerations

7. References

7.1. Normative References

7.2. Informational References

Author's Address