| 1 |
<pre>Internet Engineering Task Force (IETF) P. Psenak, Ed. |
| 2 |
Request for Comments: 8444 N. Kumar |
| 3 |
Category: Standards Track IJ. Wijnands |
| 4 |
ISSN: 2070-1721 Cisco |
| 5 |
A. Dolganow |
| 6 |
Nokia |
| 7 |
T. Przygienda |
| 8 |
J. Zhang |
| 9 |
Juniper Networks, Inc. |
| 10 |
S. Aldrin |
| 11 |
Google, Inc. |
| 12 |
November 2018 |
| 13 |
|
| 14 |
|
| 15 |
<span class="h1">OSPFv2 Extensions for Bit Index Explicit Replication (BIER)</span> |
| 16 |
|
| 17 |
Abstract |
| 18 |
|
| 19 |
Bit Index Explicit Replication (BIER) is an architecture that |
| 20 |
provides optimal multicast forwarding through a "BIER domain" without |
| 21 |
requiring intermediate routers to maintain multicast-related, per- |
| 22 |
flow state. BIER also does not require an explicit tree-building |
| 23 |
protocol for its operation. A multicast data packet enters a BIER |
| 24 |
domain at a Bit-Forwarding Ingress Router (BFIR) and leaves the BIER |
| 25 |
domain at one or more Bit-Forwarding Egress Routers (BFERs). The |
| 26 |
BFIR adds a BIER packet header to the packet. The BIER packet header |
| 27 |
contains a BitString in which each bit represents exactly one BFER to |
| 28 |
forward the packet to. The set of BFERs to which the multicast |
| 29 |
packet needs to be forwarded is expressed by the set of bits in the |
| 30 |
BIER packet header. |
| 31 |
|
| 32 |
This document describes the OSPF protocol extension (from <a href="./rfc2328">RFC 2328</a>) |
| 33 |
that is required for BIER with MPLS encapsulation (which is defined |
| 34 |
in <a href="./rfc8296">RFC 8296</a>). Support for other encapsulation types and the use of |
| 35 |
multiple encapsulation types are outside the scope of this document. |
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 55 |
|
| 56 |
|
| 57 |
Status of This Memo |
| 58 |
|
| 59 |
This is an Internet Standards Track document. |
| 60 |
|
| 61 |
This document is a product of the Internet Engineering Task Force |
| 62 |
(IETF). It represents the consensus of the IETF community. It has |
| 63 |
received public review and has been approved for publication by the |
| 64 |
Internet Engineering Steering Group (IESG). Further information on |
| 65 |
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 66 |
|
| 67 |
Information about the current status of this document, any errata, |
| 68 |
and how to provide feedback on it may be obtained at |
| 69 |
<a href="https://www.rfc-editor.org/info/rfc8444">https://www.rfc-editor.org/info/rfc8444</a>. |
| 70 |
|
| 71 |
Copyright Notice |
| 72 |
|
| 73 |
Copyright (c) 2018 IETF Trust and the persons identified as the |
| 74 |
document authors. All rights reserved. |
| 75 |
|
| 76 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 77 |
Provisions Relating to IETF Documents |
| 78 |
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of |
| 79 |
publication of this document. Please review these documents |
| 80 |
carefully, as they describe your rights and restrictions with respect |
| 81 |
to this document. Code Components extracted from this document must |
| 82 |
include Simplified BSD License text as described in Section 4.e of |
| 83 |
the Trust Legal Provisions and are provided without warranty as |
| 84 |
described in the Simplified BSD License. |
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 116 |
<a href="#section-2">2</a>. Flooding of the BIER Information in OSPF ........................<a href="#page-4">4</a> |
| 117 |
<a href="#section-2.1">2.1</a>. BIER Sub-TLV ...............................................<a href="#page-4">4</a> |
| 118 |
<a href="#section-2.2">2.2</a>. BIER MPLS Encapsulation Sub-TLV ............................<a href="#page-5">5</a> |
| 119 |
<a href="#section-2.3">2.3</a>. Flooding Scope of BIER Information .........................<a href="#page-7">7</a> |
| 120 |
<a href="#section-3">3</a>. Security Considerations .........................................<a href="#page-8">8</a> |
| 121 |
<a href="#section-4">4</a>. IANA Considerations .............................................<a href="#page-9">9</a> |
| 122 |
<a href="#section-5">5</a>. References ......................................................<a href="#page-9">9</a> |
| 123 |
<a href="#section-5.1">5.1</a>. Normative References .......................................<a href="#page-9">9</a> |
| 124 |
<a href="#section-5.2">5.2</a>. Informative References ....................................<a href="#page-10">10</a> |
| 125 |
Acknowledgments ...................................................<a href="#page-11">11</a> |
| 126 |
Authors' Addresses ................................................<a href="#page-11">11</a> |
| 127 |
|
| 128 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 129 |
|
| 130 |
Bit Index Explicit Replication (BIER) is an architecture that |
| 131 |
provides optimal multicast forwarding through a "BIER domain" without |
| 132 |
requiring intermediate routers to maintain any multicast-related, |
| 133 |
per-flow state. Neither does BIER explicitly require a tree-building |
| 134 |
protocol for its operation. A multicast data packet enters a BIER |
| 135 |
domain at a Bit-Forwarding Ingress Router (BFIR) and leaves the BIER |
| 136 |
domain at one or more Bit-Forwarding Egress Routers (BFERs). The |
| 137 |
BFIR router adds a BIER packet header to the packet. The BIER packet |
| 138 |
header contains a BitString in which each bit represents exactly one |
| 139 |
BFER to forward the packet to. The set of BFERs to which the |
| 140 |
multicast packet needs to be forwarded is expressed by the set of |
| 141 |
bits in the BIER packet header. |
| 142 |
|
| 143 |
The BIER architecture requires routers participating in BIER to |
| 144 |
exchange BIER-related information within a given domain and permits |
| 145 |
link-state routing protocols to perform distribution of such |
| 146 |
information. This document describes extensions to OSPF necessary to |
| 147 |
advertise BIER-specific information in the case where BIER uses MPLS |
| 148 |
encapsulation as described in [<a href="./rfc8296" title=""Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non- MPLS Networks"">RFC8296</a>]. |
| 149 |
|
| 150 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 151 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and |
| 152 |
"OPTIONAL" in this document are to be interpreted as described in |
| 153 |
<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 |
| 154 |
capitals, as shown here. |
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Flooding of the BIER Information in OSPF</span> |
| 170 |
|
| 171 |
All BIER-specific information that a Bit-Forwarding Router (BFR) |
| 172 |
needs to advertise to other BFRs is associated with a BFR-prefix. A |
| 173 |
BFR-prefix is a unique (within a given BIER domain) routable IP |
| 174 |
address that is assigned to each BFR as described in detail in |
| 175 |
<a href="./rfc8279#section-2">Section 2 of [RFC8279]</a>. |
| 176 |
|
| 177 |
Given that BIER information must be associated with a BFR-prefix, the |
| 178 |
OSPFv2 Extended Prefix Opaque LSA [<a href="./rfc7684" title=""OSPFv2 Prefix/Link Attribute Advertisement"">RFC7684</a>] has been chosen for |
| 179 |
advertisement. |
| 180 |
|
| 181 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. BIER Sub-TLV</span> |
| 182 |
|
| 183 |
A sub-TLV of the OSPFv2 Extended Prefix TLV (defined in [<a href="./rfc7684" title=""OSPFv2 Prefix/Link Attribute Advertisement"">RFC7684</a>]) is |
| 184 |
defined for distributing BIER information. The sub-TLV is called the |
| 185 |
BIER Sub-TLV. Multiple BIER Sub-TLVs may be included in the OSPFv2 |
| 186 |
Extended Prefix TLV. |
| 187 |
|
| 188 |
The BIER Sub-TLV has the following format: |
| 189 |
|
| 190 |
0 1 2 3 |
| 191 |
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 |
| 192 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 193 |
| Type | Length | |
| 194 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 195 |
| sub-domain-id | MT-ID | BFR-id | |
| 196 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 197 |
| BAR | IPA | Reserved | |
| 198 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 199 |
| Sub-TLVs (variable) | |
| 200 |
+- -+ |
| 201 |
| | |
| 202 |
|
| 203 |
Type: 9 |
| 204 |
|
| 205 |
Length: Variable, dependent on sub-TLVs. |
| 206 |
|
| 207 |
sub-domain-id: Unique value identifying the BIER sub-domain within |
| 208 |
the BIER domain, as described in <a href="./rfc8279#section-1">Section 1 of [RFC8279]</a>. |
| 209 |
|
| 210 |
MT-ID: Multi-Topology ID (as defined in [<a href="./rfc4915" title=""Multi-Topology (MT) Routing in OSPF"">RFC4915</a>]) that identifies |
| 211 |
the topology that is associated with the BIER sub-domain. |
| 212 |
|
| 213 |
BFR-id: A 2-octet field encoding the BFR-id, as documented in |
| 214 |
<a href="./rfc8279#section-2">Section 2 of [RFC8279]</a>. If the BFR is not locally configured with |
| 215 |
a valid BFR-id, the value of this field is set to 0, which is |
| 216 |
defined as illegal in [<a href="./rfc8279" title=""Multicast Using Bit Index Explicit Replication (BIER)"">RFC8279</a>]. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 223 |
|
| 224 |
|
| 225 |
BAR: Single-octet BIER Algorithm used to calculate underlay paths to |
| 226 |
reach other BFRs. Values are allocated from the "BIER Algorithm" |
| 227 |
registry defined in [<a href="./rfc8401" title=""Bit Index Explicit Replication (BIER) Support via IS-IS"">RFC8401</a>]. |
| 228 |
|
| 229 |
IPA: Single-octet IGP Algorithm used to either modify, enhance, or |
| 230 |
replace the calculation of underlay paths to reach other BFRs as |
| 231 |
defined by the BAR value. Values are defined in the "IGP |
| 232 |
Algorithm Types" registry [<a href="#ref-IANA-IGP" title=""IGP Algorithm Types"">IANA-IGP</a>]. |
| 233 |
|
| 234 |
Each BFR sub-domain MUST be associated with one and only one OSPF |
| 235 |
topology that is identified by the MT-ID. If the association between |
| 236 |
the BIER sub-domain and OSPF topology advertised in the BIER Sub-TLV |
| 237 |
by other BFRs is in conflict with the association locally configured |
| 238 |
on the receiving router, the BIER Sub-TLV for such conflicting sub- |
| 239 |
domains MUST be ignored. |
| 240 |
|
| 241 |
If the MT-ID contains an invalid value as specified in [<a href="./rfc4915" title=""Multi-Topology (MT) Routing in OSPF"">RFC4915</a>], the |
| 242 |
BIER Sub-TLV for such subdomains with conflict MUST be ignored. |
| 243 |
|
| 244 |
If a BFR advertises the same sub-domain-id in multiple BIER Sub-TLVs, |
| 245 |
the BFR MUST be treated as if it did not advertise a BIER Sub-TLV for |
| 246 |
such sub-domain. |
| 247 |
|
| 248 |
All BFRs MUST detect advertisement of duplicate valid BFR-ids for a |
| 249 |
given MT-ID and sub-domain-id. When such duplication is detected by |
| 250 |
the BFR, it MUST behave as described in <a href="./rfc8279#section-5">Section 5 of [RFC8279]</a>. |
| 251 |
|
| 252 |
The supported BAR and IPA algorithms MUST be consistent for all |
| 253 |
routers supporting a given BFR sub-domain. If a router receives a |
| 254 |
BIER Sub-TLV advertisement with a value in the BAR or IPA fields that |
| 255 |
does not match the locally configured value for a given BFR sub- |
| 256 |
domain, the router MUST report a misconfiguration for such BIER sub- |
| 257 |
domain and MUST ignore the BIER Sub-TLV containing the error. |
| 258 |
|
| 259 |
The use of non-zero values in either the BAR field or the IPA field |
| 260 |
is outside the scope of this document. |
| 261 |
|
| 262 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. BIER MPLS Encapsulation Sub-TLV</span> |
| 263 |
|
| 264 |
The BIER MPLS Encapsulation Sub-TLV is a sub-TLV of the BIER Sub-TLV. |
| 265 |
The BIER MPLS Encapsulation Sub-TLV is used in order to advertise |
| 266 |
MPLS-specific information used for BIER. It MAY appear multiple |
| 267 |
times in the BIER Sub-TLV. |
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 279 |
|
| 280 |
|
| 281 |
The BIER MPLS Encapsulation Sub-TLV has the following format: |
| 282 |
|
| 283 |
0 1 2 3 |
| 284 |
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 |
| 285 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 286 |
| Type | Length | |
| 287 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 288 |
| Max SI | Label | |
| 289 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 290 |
|BS Len | Reserved | |
| 291 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 292 |
|
| 293 |
Type: 10 |
| 294 |
|
| 295 |
Length: 8 octets |
| 296 |
|
| 297 |
Max SI: A 1-octet field encoding the maximum Set Identifier (SI) |
| 298 |
(see <a href="./rfc8279#section-1">Section 1 of [RFC8279]</a>) used in the encapsulation for this |
| 299 |
BIER sub-domain for this BitString length. |
| 300 |
|
| 301 |
Label: A 3-octet field, where the 20 rightmost bits represent the |
| 302 |
first label in the label range. The 4 leftmost bits MUST be |
| 303 |
ignored. |
| 304 |
|
| 305 |
BS Len (BitString Length): A 4-bit field encoding the supported |
| 306 |
BitString length associated with this BFR-prefix. The values |
| 307 |
allowed in this field are specified in <a href="./rfc8296#section-2">Section 2 of [RFC8296]</a>. |
| 308 |
|
| 309 |
Reserved: SHOULD be set to 0 on transmission and MUST be ignored on |
| 310 |
reception. |
| 311 |
|
| 312 |
The "label range" is the set of labels beginning with the Label and |
| 313 |
ending with (Label + (Max SI)). A unique label range is allocated |
| 314 |
for each BitString length and sub-domain-id. These labels are used |
| 315 |
for BIER forwarding as described in [<a href="./rfc8279" title=""Multicast Using Bit Index Explicit Replication (BIER)"">RFC8279</a>] and [<a href="./rfc8296" title=""Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non- MPLS Networks"">RFC8296</a>]. |
| 316 |
|
| 317 |
The size of the label range is determined by the number of SIs |
| 318 |
(<a href="./rfc8279#section-1">Section 1 of [RFC8279]</a>) that are used in the network. Each SI maps |
| 319 |
to a single label in the label range: the first label is for SI=0, |
| 320 |
the second label is for SI=1, etc. |
| 321 |
|
| 322 |
If the label associated with the Maximum Set Identifier exceeds the |
| 323 |
20-bit range, the BIER MPLS Encapsulation Sub-TLV containing the |
| 324 |
error MUST be ignored. |
| 325 |
|
| 326 |
If the BitString length is set to a value that does not match any of |
| 327 |
the allowed values specified in [<a href="./rfc8296" title=""Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non- MPLS Networks"">RFC8296</a>], the BIER MPLS |
| 328 |
Encapsulation Sub-TLV containing the error MUST be ignored. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 335 |
|
| 336 |
|
| 337 |
If the same BitString length is repeated in multiple BIER MPLS |
| 338 |
Encapsulation Sub-TLVs inside the same BIER Sub-TLV, the whole BIER |
| 339 |
Sub-TLV containing the conflicts MUST be ignored. |
| 340 |
|
| 341 |
Label ranges within all BIER MPLS Encapsulation Sub-TLVs advertised |
| 342 |
by the same BFR MUST NOT overlap. If an overlap is detected, all |
| 343 |
BIER sub-TLVs advertised by such a router MUST be ignored. |
| 344 |
|
| 345 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Flooding Scope of BIER Information</span> |
| 346 |
|
| 347 |
The flooding scope of the OSPFv2 Extended Prefix Opaque LSA [<a href="./rfc7684" title=""OSPFv2 Prefix/Link Attribute Advertisement"">RFC7684</a>] |
| 348 |
that is used for advertising the BIER Sub-TLV is set to area-local. |
| 349 |
To allow BIER deployment in a multi-area environment, OSPF must |
| 350 |
propagate BIER information between areas. |
| 351 |
|
| 352 |
( ) ( ) ( ) |
| 353 |
( ) ( ) ( ) |
| 354 |
R1 Area 1 R2 Area 0 R3 Area 2 R4 |
| 355 |
( ) ( ) ( ) |
| 356 |
( ) ( ) ( ) |
| 357 |
|
| 358 |
Figure 1: BIER Propagation between Areas |
| 359 |
|
| 360 |
The following procedure is used in order to propagate BIER-related |
| 361 |
information between areas: |
| 362 |
|
| 363 |
When an OSPF Area Border Router (ABR) advertises a Type-3 Summary |
| 364 |
LSA from an intra-area or inter-area prefix to all its attached |
| 365 |
areas, it will also originate an OSPFv2 Extended Prefix Opaque |
| 366 |
LSA, as described in [<a href="./rfc7684" title=""OSPFv2 Prefix/Link Attribute Advertisement"">RFC7684</a>]. The flooding scope of the OSPFv2 |
| 367 |
Extended Prefix Opaque LSA type will be set to area-local. The |
| 368 |
route-type in the OSPFv2 Extended Prefix TLV is set to inter-area. |
| 369 |
When determining whether a BIER Sub-TLV should be included in this |
| 370 |
LSA, an OSPF ABR will: |
| 371 |
|
| 372 |
* Examine its best path to the prefix in the source area and find |
| 373 |
the advertising router associated with the best path to that |
| 374 |
prefix. |
| 375 |
|
| 376 |
* Determine if the advertising router advertised a BIER Sub-TLV |
| 377 |
for the prefix. If yes, the ABR will copy the information from |
| 378 |
that BIER Sub-TLV when advertising the BIER Sub-TLV to each |
| 379 |
attached area. |
| 380 |
|
| 381 |
In Figure 1, R1 advertises a prefix 192.0.2.1/32 in Area 1. It |
| 382 |
also advertises an OSPFv2 Extended Prefix Opaque LSA for prefix |
| 383 |
192.0.2.1/32 and includes a BIER Sub-TLV in it. ABR R2 calculates |
| 384 |
the reachability for prefix 192.0.2.1/32 inside Area 1 and |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 391 |
|
| 392 |
|
| 393 |
propagates it to Area 0. When doing so, it copies the entire BIER |
| 394 |
Sub-TLV (including all of its Sub-TLVs) that it received from R1 |
| 395 |
in Area 1 and includes it in the OSPFv2 Extended Prefix Opaque LSA |
| 396 |
it generates for 192.0.2.1/32 in Area 0. ABR R3 calculates the |
| 397 |
reachability for prefix 192.0.2.1/32 inside Area 0 and propagates |
| 398 |
it to Area 2. When doing so, it copies the entire BIER Sub-TLV |
| 399 |
(including all of its sub-TLVs) that it received from R2 in Area 0 |
| 400 |
and includes it in the OSPFv2 Extended Prefix Opaque LSA it |
| 401 |
generates for 192.0.2.1/32 in Area 2. |
| 402 |
|
| 403 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span> |
| 404 |
|
| 405 |
This document introduces new sub-TLVs for the existing OSPFv2 |
| 406 |
Extended Prefix TLV. It does not introduce any new security risks to |
| 407 |
OSPF. Existing security extensions as described in [<a href="./rfc2328" title=""OSPF Version 2"">RFC2328</a>] and |
| 408 |
[<a href="./rfc7684" title=""OSPFv2 Prefix/Link Attribute Advertisement"">RFC7684</a>] apply. |
| 409 |
|
| 410 |
It is assumed that both the BIER and OSPF layers are under a single |
| 411 |
administrative domain. There can be deployments where potential |
| 412 |
attackers have access to one or more networks in the OSPF routing |
| 413 |
domain. In these deployments, stronger authentication mechanisms |
| 414 |
such as those specified in [<a href="./rfc7474" title=""Security Extension for OSPFv2 When Using Manual Key Management"">RFC7474</a>] SHOULD be used. |
| 415 |
|
| 416 |
The Security Considerations section of [<a href="./rfc8279" title=""Multicast Using Bit Index Explicit Replication (BIER)"">RFC8279</a>] discusses the |
| 417 |
possibility of performing a Denial-of-Service (DoS) attack by setting |
| 418 |
too many bits in the BitString of a BIER-encapsulated packet. |
| 419 |
However, this sort of DoS attack cannot be initiated by modifying the |
| 420 |
OSPF BIER advertisements specified in this document. A BFIR decides |
| 421 |
which systems are to receive a BIER-encapsulated packet. In making |
| 422 |
this decision, it is not influenced by the OSPF control messages. |
| 423 |
When creating the encapsulation, the BFIR sets one bit in the |
| 424 |
encapsulation for each destination system. The information in the |
| 425 |
OSPF BIER advertisements is used to construct the forwarding tables |
| 426 |
that map each bit in the encapsulation into a set of next hops for |
| 427 |
the host that is identified by that bit, but the information is not |
| 428 |
used by the BFIR to decide which bits to set. Hence, an attack on |
| 429 |
the OSPF control plane cannot be used to cause this sort of DoS |
| 430 |
attack. |
| 431 |
|
| 432 |
While a BIER-encapsulated packet is traversing the network, a BFR |
| 433 |
that receives a BIER-encapsulated packet with n bits set in its |
| 434 |
BitString may have to replicate the packet and forward multiple |
| 435 |
copies. However, a given bit will only be set in one copy of the |
| 436 |
packet. This means that each transmitted replica of a received |
| 437 |
packet has fewer bits set (i.e., is targeted to fewer destinations) |
| 438 |
than the received packet. This is an essential property of the BIER |
| 439 |
forwarding process as defined in [<a href="./rfc8279" title=""Multicast Using Bit Index Explicit Replication (BIER)"">RFC8279</a>]. While a failure of this |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 447 |
|
| 448 |
|
| 449 |
process might cause a DoS attack (as discussed in the Security |
| 450 |
Considerations section of [<a href="./rfc8279" title=""Multicast Using Bit Index Explicit Replication (BIER)"">RFC8279</a>]), such a failure cannot be caused |
| 451 |
by an attack on the OSPF control plane. |
| 452 |
|
| 453 |
Implementations MUST ensure that malformed BIER and BIER MPLS |
| 454 |
Encapsulation Sub-TLVs as defined in this document are detected and |
| 455 |
that they do not provide a vulnerability for attackers to crash the |
| 456 |
OSPF router or routing process. Reception of malformed TLVs or sub- |
| 457 |
TLVs SHOULD be counted and/or logged for further analysis. Logging |
| 458 |
of malformed TLVs and sub-TLVs SHOULD be rate-limited to prevent a |
| 459 |
DoS attack (distributed or otherwise) from overloading the OSPF |
| 460 |
control plane. |
| 461 |
|
| 462 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span> |
| 463 |
|
| 464 |
IANA has allocated the following from the "OSPFv2 Extended Prefix TLV |
| 465 |
Sub-TLVs" registry defined in [<a href="./rfc7684" title=""OSPFv2 Prefix/Link Attribute Advertisement"">RFC7684</a>]. |
| 466 |
|
| 467 |
BIER Sub-TLV: 9 |
| 468 |
|
| 469 |
BIER MPLS Encapsulation Sub-TLV: 10 |
| 470 |
|
| 471 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span> |
| 472 |
|
| 473 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span> |
| 474 |
|
| 475 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 476 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, |
| 477 |
DOI 10.17487/RFC2119, March 1997, |
| 478 |
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>. |
| 479 |
|
| 480 |
[<a id="ref-RFC2328">RFC2328</a>] Moy, J., "OSPF Version 2", STD 54, <a href="./rfc2328">RFC 2328</a>, |
| 481 |
DOI 10.17487/RFC2328, April 1998, |
| 482 |
<<a href="https://www.rfc-editor.org/info/rfc2328">https://www.rfc-editor.org/info/rfc2328</a>>. |
| 483 |
|
| 484 |
[<a id="ref-RFC4915">RFC4915</a>] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. |
| 485 |
Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", |
| 486 |
<a href="./rfc4915">RFC 4915</a>, DOI 10.17487/RFC4915, June 2007, |
| 487 |
<<a href="https://www.rfc-editor.org/info/rfc4915">https://www.rfc-editor.org/info/rfc4915</a>>. |
| 488 |
|
| 489 |
[<a id="ref-RFC7474">RFC7474</a>] Bhatia, M., Hartman, S., Zhang, D., and A. Lindem, Ed., |
| 490 |
"Security Extension for OSPFv2 When Using Manual Key |
| 491 |
Management", <a href="./rfc7474">RFC 7474</a>, DOI 10.17487/RFC7474, April 2015, |
| 492 |
<<a href="https://www.rfc-editor.org/info/rfc7474">https://www.rfc-editor.org/info/rfc7474</a>>. |
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Psenak, 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="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 503 |
|
| 504 |
|
| 505 |
[<a id="ref-RFC7684">RFC7684</a>] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., |
| 506 |
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute |
| 507 |
Advertisement", <a href="./rfc7684">RFC 7684</a>, DOI 10.17487/RFC7684, November |
| 508 |
2015, <<a href="https://www.rfc-editor.org/info/rfc7684">https://www.rfc-editor.org/info/rfc7684</a>>. |
| 509 |
|
| 510 |
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a> |
| 511 |
<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, |
| 512 |
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>. |
| 513 |
|
| 514 |
[<a id="ref-RFC8279">RFC8279</a>] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., |
| 515 |
Przygienda, T., and S. Aldrin, "Multicast Using Bit Index |
| 516 |
Explicit Replication (BIER)", <a href="./rfc8279">RFC 8279</a>, |
| 517 |
DOI 10.17487/RFC8279, November 2017, |
| 518 |
<<a href="https://www.rfc-editor.org/info/rfc8279">https://www.rfc-editor.org/info/rfc8279</a>>. |
| 519 |
|
| 520 |
[<a id="ref-RFC8296">RFC8296</a>] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., |
| 521 |
Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation |
| 522 |
for Bit Index Explicit Replication (BIER) in MPLS and Non- |
| 523 |
MPLS Networks", <a href="./rfc8296">RFC 8296</a>, DOI 10.17487/RFC8296, January |
| 524 |
2018, <<a href="https://www.rfc-editor.org/info/rfc8296">https://www.rfc-editor.org/info/rfc8296</a>>. |
| 525 |
|
| 526 |
[<a id="ref-RFC8401">RFC8401</a>] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. |
| 527 |
Zhang, "Bit Index Explicit Replication (BIER) Support via |
| 528 |
IS-IS", <a href="./rfc8401">RFC 8401</a>, DOI 10.17487/RFC8401, June 2018, |
| 529 |
<<a href="https://www.rfc-editor.org/info/rfc8401">https://www.rfc-editor.org/info/rfc8401</a>>. |
| 530 |
|
| 531 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span> |
| 532 |
|
| 533 |
[<a id="ref-IANA-IGP">IANA-IGP</a>] IANA, "IGP Algorithm Types", |
| 534 |
<<a href="https://www.iana.org/assignments/igp-parameters/">https://www.iana.org/assignments/igp-parameters/</a>>. |
| 535 |
|
| 536 |
|
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Psenak, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 559 |
|
| 560 |
|
| 561 |
Acknowledgments |
| 562 |
|
| 563 |
The authors would like to thank Rajiv Asati, Christian Martin, Greg |
| 564 |
Shepherd, and Eric Rosen for their contributions. |
| 565 |
|
| 566 |
Authors' Addresses |
| 567 |
|
| 568 |
Peter Psenak (editor) |
| 569 |
Cisco |
| 570 |
Apollo Business Center |
| 571 |
Mlynske nivy 43 |
| 572 |
Bratislava 821 09 |
| 573 |
Slovakia |
| 574 |
|
| 575 |
Email: [email protected] |
| 576 |
|
| 577 |
|
| 578 |
Nagendra Kumar |
| 579 |
Cisco |
| 580 |
7200 Kit Creek Road |
| 581 |
Research Triangle Park, NC 27709 |
| 582 |
United States of America |
| 583 |
|
| 584 |
Email: [email protected] |
| 585 |
|
| 586 |
|
| 587 |
IJsbrand Wijnands |
| 588 |
Cisco |
| 589 |
De Kleetlaan 6a |
| 590 |
Diegem 1831 |
| 591 |
Belgium |
| 592 |
|
| 593 |
Email: [email protected] |
| 594 |
|
| 595 |
|
| 596 |
Andrew Dolganow |
| 597 |
Nokia |
| 598 |
750 Chai Chee Rd |
| 599 |
06-06 Viva Business Park |
| 600 |
Singapore 469004 |
| 601 |
Singapore |
| 602 |
|
| 603 |
Email: [email protected] |
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Psenak, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc8444">RFC 8444</a> OSPFv2 Extensions for BIER November 2018</span> |
| 615 |
|
| 616 |
|
| 617 |
Tony Przygienda |
| 618 |
Juniper Networks, Inc. |
| 619 |
10 Technology Park Drive |
| 620 |
Westford, MA 01886 |
| 621 |
United States of America |
| 622 |
|
| 623 |
Email: [email protected] |
| 624 |
|
| 625 |
|
| 626 |
Jeffrey Zhang |
| 627 |
Juniper Networks, Inc. |
| 628 |
10 Technology Park Drive |
| 629 |
Westford, MA 01886 |
| 630 |
United States of America |
| 631 |
|
| 632 |
Email: [email protected] |
| 633 |
|
| 634 |
|
| 635 |
Sam Aldrin |
| 636 |
Google, Inc. |
| 637 |
1600 Amphitheatre Parkway |
| 638 |
Mountain View, CA |
| 639 |
United States of America |
| 640 |
|
| 641 |
Email: [email protected] |
| 642 |
|
| 643 |
|
| 644 |
|
| 645 |
|
| 646 |
|
| 647 |
|
| 648 |
|
| 649 |
|
| 650 |
|
| 651 |
|
| 652 |
|
| 653 |
|
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
Psenak, et al. Standards Track [Page 12] |
| 669 |
</pre> |