| 1 |
<pre>Internet Engineering Task Force (IETF) K. Patel |
| 2 |
Request for Comments: 8538 Arrcus |
| 3 |
Updates: <a href="./rfc4724">4724</a> R. Fernando |
| 4 |
Category: Standards Track Cisco Systems |
| 5 |
ISSN: 2070-1721 J. Scudder |
| 6 |
J. Haas |
| 7 |
Juniper Networks |
| 8 |
March 2019 |
| 9 |
|
| 10 |
|
| 11 |
<span class="h1">Notification Message Support for BGP Graceful Restart</span> |
| 12 |
|
| 13 |
Abstract |
| 14 |
|
| 15 |
The BGP Graceful Restart mechanism defined in <a href="./rfc4724">RFC 4724</a> limits the |
| 16 |
usage of BGP Graceful Restart to BGP messages other than BGP |
| 17 |
NOTIFICATION messages. This document updates <a href="./rfc4724">RFC 4724</a> by defining an |
| 18 |
extension that permits the Graceful Restart procedures to be |
| 19 |
performed when the BGP speaker receives a BGP NOTIFICATION message or |
| 20 |
the Hold Time expires. This document also defines a new subcode for |
| 21 |
BGP Cease NOTIFICATION messages; this new subcode requests a full |
| 22 |
session restart instead of a Graceful Restart. |
| 23 |
|
| 24 |
Status of This Memo |
| 25 |
|
| 26 |
This is an Internet Standards Track document. |
| 27 |
|
| 28 |
This document is a product of the Internet Engineering Task Force |
| 29 |
(IETF). It represents the consensus of the IETF community. It has |
| 30 |
received public review and has been approved for publication by the |
| 31 |
Internet Engineering Steering Group (IESG). Further information on |
| 32 |
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 33 |
|
| 34 |
Information about the current status of this document, any errata, |
| 35 |
and how to provide feedback on it may be obtained at |
| 36 |
<a href="https://www.rfc-editor.org/info/rfc8538">https://www.rfc-editor.org/info/rfc8538</a>. |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Patel, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2019 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
Table of Contents |
| 73 |
|
| 74 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 75 |
<a href="#section-1.1">1.1</a>. Requirements Language . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 76 |
<a href="#section-2">2</a>. Modifications to BGP Graceful Restart Capability . . . . . . <a href="#page-3">3</a> |
| 77 |
<a href="#section-3">3</a>. BGP Hard Reset Subcode . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 78 |
<a href="#section-3.1">3.1</a>. Sending a Hard Reset . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 79 |
<a href="#section-3.2">3.2</a>. Receiving a Hard Reset . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 80 |
<a href="#section-4">4</a>. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a> |
| 81 |
<a href="#section-4.1">4.1</a>. Rules for the Receiving Speaker . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 82 |
<a href="#section-5">5</a>. Use of Hard Reset . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 83 |
<a href="#section-5.1">5.1</a>. When to Send a Hard Reset . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 84 |
<a href="#section-5.2">5.2</a>. Interaction with Other Specifications . . . . . . . . . . <a href="#page-7">7</a> |
| 85 |
<a href="#section-6">6</a>. Management Considerations . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 86 |
<a href="#section-7">7</a>. Operational Considerations . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 87 |
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 88 |
<a href="#section-9">9</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 89 |
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 90 |
<a href="#section-10.1">10.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 91 |
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 92 |
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 93 |
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a> |
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Patel, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
For many classes of errors, BGP must send a NOTIFICATION message and |
| 116 |
reset the peering session to handle the error condition. The BGP |
| 117 |
Graceful Restart mechanism defined in [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>] requires that normal |
| 118 |
BGP procedures defined in [<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>] be followed when a NOTIFICATION |
| 119 |
message is sent or received. This document defines an extension to |
| 120 |
BGP Graceful Restart that permits the Graceful Restart procedures to |
| 121 |
be performed when the BGP speaker receives a NOTIFICATION message or |
| 122 |
the Hold Time expires. This permits the BGP speaker to avoid |
| 123 |
flapping reachability and continue forwarding while the BGP speaker |
| 124 |
restarts the session to handle errors detected in BGP. |
| 125 |
|
| 126 |
At a high level, this document can be summed up as follows. When a |
| 127 |
BGP session is reset, both speakers operate as "Receiving Speakers" |
| 128 |
according to [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>], meaning they retain each other's routes. |
| 129 |
This is also true for HOLDTIME expiration. The functionality can be |
| 130 |
defeated by sending a BGP Cease NOTIFICATION message with the Hard |
| 131 |
Reset subcode. If a Hard Reset is used, a full session reset is |
| 132 |
performed. |
| 133 |
|
| 134 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span> |
| 135 |
|
| 136 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 137 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and |
| 138 |
"OPTIONAL" in this document are to be interpreted as described in |
| 139 |
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all |
| 140 |
capitals, as shown here. |
| 141 |
|
| 142 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Modifications to BGP Graceful Restart Capability</span> |
| 143 |
|
| 144 |
The BGP Graceful Restart Capability is augmented to signal the |
| 145 |
Graceful Restart support for BGP NOTIFICATION messages. The Restart |
| 146 |
Flags field is augmented as follows (following the diagram in |
| 147 |
<a href="./rfc4724#section-3">Section 3 of [RFC4724]</a>). |
| 148 |
|
| 149 |
Restart Flags: |
| 150 |
|
| 151 |
This field contains bit flags relating to restart. |
| 152 |
|
| 153 |
0 1 2 3 |
| 154 |
+-+-+-+-+ |
| 155 |
|R|N| | |
| 156 |
+-+-+-+-+ |
| 157 |
|
| 158 |
The most significant bit is defined in [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>] as the Restart State |
| 159 |
("R") bit. |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Patel, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 167 |
|
| 168 |
|
| 169 |
The second most significant bit is defined in this document as the |
| 170 |
Graceful Notification ("N") bit. It is used to indicate Graceful |
| 171 |
Restart support for BGP NOTIFICATION messages. A BGP speaker |
| 172 |
indicates support for the procedures in this document by advertising |
| 173 |
a Graceful Restart Capability with its "N" bit set (value 1). |
| 174 |
|
| 175 |
If a BGP speaker that previously advertised a given set of Graceful |
| 176 |
Restart parameters opens a new session with a different set of |
| 177 |
parameters, these new parameters apply once the session has |
| 178 |
transitioned into ESTABLISHED state. |
| 179 |
|
| 180 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. BGP Hard Reset Subcode</span> |
| 181 |
|
| 182 |
This document defines a new subcode for BGP Cease NOTIFICATION |
| 183 |
messages, called the Hard Reset subcode. The value of this subcode |
| 184 |
is discussed in <a href="#section-8">Section 8</a>. In this document, a BGP Cease |
| 185 |
NOTIFICATION message with the Hard Reset subcode is referred to as a |
| 186 |
"Hard Reset message" or simply as a "Hard Reset". |
| 187 |
|
| 188 |
When the "N" bit has been exchanged by two peers, NOTIFICATION |
| 189 |
messages other than Hard Reset messages are referred to as |
| 190 |
"Graceful", since such messages invoke Graceful Restart semantics. |
| 191 |
|
| 192 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Sending a Hard Reset</span> |
| 193 |
|
| 194 |
When the "N" bit has been exchanged, a Hard Reset message is used to |
| 195 |
indicate to the peer that the session is to be fully terminated. |
| 196 |
|
| 197 |
When sending a Hard Reset, the data portion of the NOTIFICATION |
| 198 |
message is encoded as follows: |
| 199 |
|
| 200 |
+--------+--------+-------- |
| 201 |
| ErrCode| Subcode| Data |
| 202 |
+--------+--------+-------- |
| 203 |
|
| 204 |
ErrCode is a BGP Error Code (as documented in the IANA "BGP Error |
| 205 |
(Notification) Codes" registry) that indicates the reason for the |
| 206 |
Hard Reset. Subcode is a BGP Error Subcode (as documented in the |
| 207 |
IANA "BGP Error Subcodes" registry) as appropriate for the ErrCode. |
| 208 |
Similarly, Data is as appropriate for the ErrCode and Subcode. In |
| 209 |
short, the Hard Reset encapsulates another NOTIFICATION message in |
| 210 |
its data portion. |
| 211 |
|
| 212 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Receiving a Hard Reset</span> |
| 213 |
|
| 214 |
Whenever a BGP speaker receives a Hard Reset, the speaker MUST |
| 215 |
terminate the BGP session following the standard procedures in |
| 216 |
[<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>]. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Patel, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Operation</span> |
| 226 |
|
| 227 |
A BGP speaker that is willing to receive and send BGP NOTIFICATION |
| 228 |
messages according to the procedures of this document MUST advertise |
| 229 |
the "N" bit using the Graceful Restart Capability as defined in |
| 230 |
[<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>]. |
| 231 |
|
| 232 |
When such a BGP speaker has received the "N" bit from its peer, and |
| 233 |
receives from that peer a BGP NOTIFICATION message other than a Hard |
| 234 |
Reset, it MUST follow the rules for the Receiving Speaker mentioned |
| 235 |
in <a href="#section-4.1">Section 4.1</a>. The BGP speaker generating the BGP NOTIFICATION |
| 236 |
message MUST also follow the rules for the Receiving Speaker. |
| 237 |
|
| 238 |
When a BGP speaker resets its session due to a HOLDTIME expiry, it |
| 239 |
should generate the relevant BGP NOTIFICATION message as mentioned in |
| 240 |
[<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>] but subsequently MUST follow the rules for the Receiving |
| 241 |
Speaker mentioned in <a href="#section-4.1">Section 4.1</a>. |
| 242 |
|
| 243 |
A BGP speaker SHOULD NOT send a Hard Reset to a peer from which it |
| 244 |
has not received the "N" bit. We note, however, that if it did so, |
| 245 |
the effect would be as desired in any case because, according to |
| 246 |
[<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>] and [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>], any NOTIFICATION message, whether recognized |
| 247 |
or not, results in a session reset. Thus, the only negative effect |
| 248 |
to be expected from sending the Hard Reset to a peer that hasn't |
| 249 |
advertised compliance to this specification would be that the peer |
| 250 |
would be unable to properly log the associated information. |
| 251 |
|
| 252 |
Once the session is re-established, both BGP speakers SHOULD set |
| 253 |
their Forwarding State bit to 1. If the Forwarding State bit is not |
| 254 |
set, then, according to the procedures in <a href="./rfc4724#section-4.2">Section 4.2 of [RFC4724]</a>, |
| 255 |
the relevant routes will be flushed, defeating the goals of this |
| 256 |
specification. |
| 257 |
|
| 258 |
|
| 259 |
|
| 260 |
|
| 261 |
|
| 262 |
|
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Patel, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Rules for the Receiving Speaker</span> |
| 282 |
|
| 283 |
<a href="./rfc4724#section-4.2">Section 4.2 of [RFC4724]</a> defines rules for the Receiving Speaker. |
| 284 |
This document modifies those rules as follows: |
| 285 |
|
| 286 |
The sentence "To deal with possible consecutive restarts, a route |
| 287 |
(from the peer) previously marked as stale MUST be deleted" only |
| 288 |
applies when the "N" bit has not been exchanged with the peer: |
| 289 |
|
| 290 |
OLD: When the Receiving Speaker detects termination of the TCP |
| 291 |
session for a BGP session with a peer that has advertised the |
| 292 |
Graceful Restart Capability, it MUST retain the routes received |
| 293 |
from the peer for all the address families that were previously |
| 294 |
received in the Graceful Restart Capability and MUST mark them |
| 295 |
as stale routing information. To deal with possible consecutive |
| 296 |
restarts, a route (from the peer) previously marked as stale |
| 297 |
MUST be deleted. The router MUST NOT differentiate between |
| 298 |
stale and other routing information during forwarding. |
| 299 |
|
| 300 |
NEW: When the Receiving Speaker detects termination of the TCP |
| 301 |
session for a BGP session with a peer that has advertised the |
| 302 |
Graceful Restart Capability, it MUST retain the routes received |
| 303 |
from the peer for all the address families that were previously |
| 304 |
received in the Graceful Restart Capability and MUST mark them |
| 305 |
as stale routing information. The router MUST NOT differentiate |
| 306 |
between stale and other routing information during forwarding. |
| 307 |
If the "N" bit has not been exchanged with the peer, then to |
| 308 |
deal with possible consecutive restarts, a route (from the peer) |
| 309 |
previously marked as stale MUST be deleted. |
| 310 |
|
| 311 |
The stale timer is given a formal name and made mandatory: |
| 312 |
|
| 313 |
OLD: To put an upper bound on the amount of time a router retains the |
| 314 |
stale routes, an implementation MAY support a (configurable) |
| 315 |
timer that imposes this upper bound. |
| 316 |
|
| 317 |
NEW: To put an upper bound on the amount of time a router retains the |
| 318 |
stale routes, an implementation MUST support a (configurable) |
| 319 |
timer, called the "stale timer", that imposes this upper bound. |
| 320 |
A suggested default value for the stale timer is 180 seconds. |
| 321 |
An implementation MAY provide the option to disable the timer |
| 322 |
(i.e., to provide an infinite retention time) but MUST NOT do so |
| 323 |
by default. |
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Patel, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Use of Hard Reset</span> |
| 338 |
|
| 339 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. When to Send a Hard Reset</span> |
| 340 |
|
| 341 |
Although when to send a Hard Reset is an implementation-specific |
| 342 |
decision, we offer some advice. Many Cease NOTIFICATION subcodes |
| 343 |
represent permanent or long-term, rather than transient, session |
| 344 |
termination. Because of this, it's appropriate to use Hard Reset |
| 345 |
with them. As of publication of this document, subcodes 1-9 have |
| 346 |
been defined for Cease. The following table lists each of these |
| 347 |
subcodes along with suggested behavior. |
| 348 |
|
| 349 |
+-------+------------------------------------+----------------------+ |
| 350 |
| Value | Name | Suggested Behavior | |
| 351 |
+-------+------------------------------------+----------------------+ |
| 352 |
| 1 | Maximum Number of Prefixes Reached | Hard Reset | |
| 353 |
| 2 | Administrative Shutdown | Hard Reset | |
| 354 |
| 3 | Peer De-configured | Hard Reset | |
| 355 |
| 4 | Administrative Reset | Provide user control | |
| 356 |
| 5 | Connection Rejected | Graceful Cease | |
| 357 |
| 6 | Other Configuration Change | Graceful Cease | |
| 358 |
| 7 | Connection Collision Resolution | Graceful Cease | |
| 359 |
| 8 | Out of Resources | Graceful Cease | |
| 360 |
| 9 | Hard Reset | Hard Reset | |
| 361 |
+-------+------------------------------------+----------------------+ |
| 362 |
|
| 363 |
These suggestions are only that -- suggestions, not requirements. |
| 364 |
It's the nature of BGP implementations that the mapping of internal |
| 365 |
states to BGP NOTIFICATION codes and subcodes is not always perfect. |
| 366 |
The guiding principle for the implementor should be that if there is |
| 367 |
no realistic hope that forwarding can continue or that the session |
| 368 |
will be re-established within the deadline, Hard Reset should be |
| 369 |
used. |
| 370 |
|
| 371 |
For all NOTIFICATION codes other than Cease, use of Hard Reset does |
| 372 |
not appear to be indicated. |
| 373 |
|
| 374 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Interaction with Other Specifications</span> |
| 375 |
|
| 376 |
"BGP Administrative Shutdown Communication" [<a href="./rfc8203" title=""BGP Administrative Shutdown Communication"">RFC8203</a>] specifies use |
| 377 |
of the data portion of the Administrative Shutdown or Administrative |
| 378 |
Reset subcodes to convey a short message. When [<a href="./rfc8203" title=""BGP Administrative Shutdown Communication"">RFC8203</a>] is used in |
| 379 |
conjunction with Hard Reset, the subcode of the outermost Cease MUST |
| 380 |
be Hard Reset, with the Administrative Shutdown or Administrative |
| 381 |
Reset subcodes encapsulated within. The encapsulated message MUST |
| 382 |
subsequently be processed according to [<a href="./rfc8203" title=""BGP Administrative Shutdown Communication"">RFC8203</a>]. |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Patel, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Management Considerations</span> |
| 394 |
|
| 395 |
When reporting a Hard Reset to network management, the error code and |
| 396 |
subcode reported MUST be Cease and Hard Reset, respectively. If the |
| 397 |
network management layer in use permits it, the information carried |
| 398 |
in the Data portion SHOULD be reported as well. |
| 399 |
|
| 400 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Operational Considerations</span> |
| 401 |
|
| 402 |
Note that long (or infinite) retention time may cause operational |
| 403 |
issues and should be enabled with care. |
| 404 |
|
| 405 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span> |
| 406 |
|
| 407 |
IANA has assigned subcode 9 ("Hard Reset") in the "BGP Cease |
| 408 |
NOTIFICATION message subcodes" registry. |
| 409 |
|
| 410 |
IANA has created a sub-registry called "BGP Graceful Restart Flags" |
| 411 |
under the "Border Gateway Protocol (BGP) Parameters" registry. The |
| 412 |
registration procedure is Standards Action [<a href="./rfc8126" title="">RFC8126</a>]; this document |
| 413 |
and [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>] are listed as references. The initial values are as |
| 414 |
follows: |
| 415 |
|
| 416 |
+--------------+---------------+------------+-----------+ |
| 417 |
| Bit Position | Name | Short Name | Reference | |
| 418 |
+--------------+---------------+------------+-----------+ |
| 419 |
| 0 | Restart State | R | <a href="./rfc4724">RFC 4724</a> | |
| 420 |
| 1 | Notification | N | <a href="./rfc8538">RFC 8538</a> | |
| 421 |
| 2-3 | Unassigned | | | |
| 422 |
+--------------+---------------+------------+-----------+ |
| 423 |
|
| 424 |
IANA has created a sub-registry called "BGP Graceful Restart Flags |
| 425 |
for Address Family" under the "Border Gateway Protocol (BGP) |
| 426 |
Parameters" registry. The registration procedure is Standards |
| 427 |
Action; this document and [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>] are listed as references. The |
| 428 |
initial values are as follows: |
| 429 |
|
| 430 |
+--------------+------------------+------------+-----------+ |
| 431 |
| Bit Position | Name | Short Name | Reference | |
| 432 |
+--------------+------------------+------------+-----------+ |
| 433 |
| 0 | Forwarding State | F | <a href="./rfc4724">RFC 4724</a> | |
| 434 |
| 1-7 | Unassigned | | | |
| 435 |
+--------------+------------------+------------+-----------+ |
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Patel, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span> |
| 450 |
|
| 451 |
This specification doesn't change the basic security model inherent |
| 452 |
in [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>], with the exception that the protection against repeated |
| 453 |
resets is relaxed. To mitigate the consequent risk that an attacker |
| 454 |
could use repeated session resets to prevent stale routes from ever |
| 455 |
being deleted, we make the stale timer mandatory (in practice, it is |
| 456 |
already ubiquitous). To the extent [<a href="./rfc4724" title=""Graceful Restart Mechanism for BGP"">RFC4724</a>] might be said to help |
| 457 |
defend against denials of service by making the control plane more |
| 458 |
resilient, this extension may modestly increase that resilience; |
| 459 |
however, there are enough confounding and deployment-specific factors |
| 460 |
that no general claims can be made. |
| 461 |
|
| 462 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span> |
| 463 |
|
| 464 |
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span> |
| 465 |
|
| 466 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 467 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, |
| 468 |
DOI 10.17487/RFC2119, March 1997, |
| 469 |
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>. |
| 470 |
|
| 471 |
[<a id="ref-RFC4271">RFC4271</a>] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A |
| 472 |
Border Gateway Protocol 4 (BGP-4)", <a href="./rfc4271">RFC 4271</a>, |
| 473 |
DOI 10.17487/RFC4271, January 2006, |
| 474 |
<<a href="https://www.rfc-editor.org/info/rfc4271">https://www.rfc-editor.org/info/rfc4271</a>>. |
| 475 |
|
| 476 |
[<a id="ref-RFC4724">RFC4724</a>] Sangli, S., Chen, E., Fernando, R., Scudder, J., and Y. |
| 477 |
Rekhter, "Graceful Restart Mechanism for BGP", <a href="./rfc4724">RFC 4724</a>, |
| 478 |
DOI 10.17487/RFC4724, January 2007, |
| 479 |
<<a href="https://www.rfc-editor.org/info/rfc4724">https://www.rfc-editor.org/info/rfc4724</a>>. |
| 480 |
|
| 481 |
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a> |
| 482 |
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174, |
| 483 |
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>. |
| 484 |
|
| 485 |
[<a id="ref-RFC8203">RFC8203</a>] Snijders, J., Heitz, J., and J. Scudder, "BGP |
| 486 |
Administrative Shutdown Communication", <a href="./rfc8203">RFC 8203</a>, |
| 487 |
DOI 10.17487/RFC8203, July 2017, |
| 488 |
<<a href="https://www.rfc-editor.org/info/rfc8203">https://www.rfc-editor.org/info/rfc8203</a>>. |
| 489 |
|
| 490 |
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span> |
| 491 |
|
| 492 |
[<a id="ref-RFC8126">RFC8126</a>] Cotton, M., Leiba, B., and T. Narten, "Guidelines for |
| 493 |
Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, |
| 494 |
<a href="./rfc8126">RFC 8126</a>, DOI 10.17487/RFC8126, June 2017, |
| 495 |
<<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>>. |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Patel, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc8538">RFC 8538</a> Notification Support for BGP GR March 2019</span> |
| 503 |
|
| 504 |
|
| 505 |
Acknowledgements |
| 506 |
|
| 507 |
The authors would like to thank Jim Uttaro for the suggestion. The |
| 508 |
authors would also like to thank Emmanuel Baccelli, Bruno Decraene, |
| 509 |
Chris Hall, Warren Kumari, Paul Mattes, Robert Raszuk, and Alvaro |
| 510 |
Retana for their reviews and comments. |
| 511 |
|
| 512 |
Authors' Addresses |
| 513 |
|
| 514 |
Keyur Patel |
| 515 |
Arrcus |
| 516 |
|
| 517 |
Email: [email protected] |
| 518 |
|
| 519 |
|
| 520 |
Rex Fernando |
| 521 |
Cisco Systems |
| 522 |
170 W. Tasman Drive |
| 523 |
San Jose, CA 95134 |
| 524 |
United States of America |
| 525 |
|
| 526 |
Email: [email protected] |
| 527 |
|
| 528 |
|
| 529 |
John Scudder |
| 530 |
Juniper Networks |
| 531 |
1194 N. Mathilda Ave |
| 532 |
Sunnyvale, CA 94089 |
| 533 |
United States of America |
| 534 |
|
| 535 |
Email: [email protected] |
| 536 |
|
| 537 |
|
| 538 |
Jeff Haas |
| 539 |
Juniper Networks |
| 540 |
1194 N. Mathilda Ave |
| 541 |
Sunnyvale, CA 94089 |
| 542 |
United States of America |
| 543 |
|
| 544 |
Email: [email protected] |
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
Patel, et al. Standards Track [Page 10] |
| 557 |
</pre> |