-
Notifications
You must be signed in to change notification settings - Fork 0
/
draft-mauch-idr-accepted-prefixes-00.raw.txt
167 lines (113 loc) · 5.29 KB
/
draft-mauch-idr-accepted-prefixes-00.raw.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
Inter-Domain Routing J. Mauch
Internet-Draft Akamai
Intended status: Standards Track J. Snijders
Expires: February 1, 2020 NTT
July 31, 2019
Provide for method to know accepted and rejected NLRI.
draft-mauch-idr-accepted-prefixes-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 February 1, 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. Normative References
Authors' Addresses
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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 |
+-------+-------+-------+-------+
Figure 1: Version Negotiation Packet
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).
o Responses will include:
o Count of NLRI accepted (unsigned 32-bits)
o Count of NLRI rejected (unsigned 32-bits)
o List of NLRI accepted (NLRI list in same format as UPDATE)
o 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. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>.
Authors' Addresses
Jared Mauch
Akamai Technologies Inc.
8285 Reese Lane
Ann Arbor Michigan 48103
US
Email: [email protected]
Job Snijders
NTT Ltd
Theodorus Majofskistraat 100
Amsterdam 1065 SZ
The Netherlands
Email: [email protected]