idnits 2.17.00 (12 Aug 2021) /tmp/idnits6685/draft-chen-bier-te-ospfv3-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 14, 2021) is 401 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '1' on line 106 -- Looks like a reference, but probably isn't: '65535' on line 106 == Unused Reference: 'RFC5120' is defined on line 212, but no explicit reference was found in the text == Unused Reference: 'RFC5226' is defined on line 218, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 227, but no explicit reference was found in the text == Unused Reference: 'RFC5250' is defined on line 240, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 244, but no explicit reference was found in the text == Unused Reference: 'RFC8444' is defined on line 255, but no explicit reference was found in the text == Unused Reference: 'RFC8556' is defined on line 261, but no explicit reference was found in the text == Outdated reference: A later version (-13) exists of draft-ietf-bier-te-arch-09 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group H. Chen 3 Internet-Draft M. McBride 4 Intended status: Standards Track Futurewei 5 Expires: October 16, 2021 A. Wang 6 China Telecom 7 G. Mishra 8 Verizon Inc. 9 Y. Fan 10 Casa Systems 11 L. Liu 12 Fujitsu 13 X. Liu 14 Volta Networks 15 April 14, 2021 17 OSPFv3 Extensions for BIER-TE 18 draft-chen-bier-te-ospfv3-00 20 Abstract 22 This document describes OSPFv3 extensions for distributing 23 BitPositions configured on the links in "Bit Index Explicit 24 Replication Traffic Engineering" (BIER-TE) domain. 26 Requirements Language 28 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 29 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 30 document are to be interpreted as described in [RFC2119] [RFC8174] 31 when, and only when, they appear in all capitals, as shown here. 33 Status of This Memo 35 This Internet-Draft is submitted in full conformance with the 36 provisions of BCP 78 and BCP 79. 38 Internet-Drafts are working documents of the Internet Engineering 39 Task Force (IETF). Note that other groups may also distribute 40 working documents as Internet-Drafts. The list of current Internet- 41 Drafts is at https://datatracker.ietf.org/drafts/current/. 43 Internet-Drafts are draft documents valid for a maximum of six months 44 and may be updated, replaced, or obsoleted by other documents at any 45 time. It is inappropriate to use Internet-Drafts as reference 46 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on October 16, 2021. 50 Copyright Notice 52 Copyright (c) 2021 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (https://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 68 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 69 2. Extensions to OSPFv3 . . . . . . . . . . . . . . . . . . . . 3 70 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 71 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 72 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 73 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 75 6.2. Informative References . . . . . . . . . . . . . . . . . 6 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 78 1. Introduction 80 [I-D.ietf-bier-te-arch] introduces Bit Index Explicit Replication 81 (BIER) Traffic/Tree Engineering (BIER-TE). It is an architecture for 82 per-packet stateless explicit point to multipoint (P2MP) multicast 83 path/tree. A link in a BIER-TE domain has its BitPositions. For a 84 link between two nodes X and Y, there are two BitPositions for two 85 forward connected adjacencies. These two adjacency BitPositions 86 could be configured on nodes X and Y respectively. The BitPosition 87 configured on X is the forward connected adjacency of Y. The 88 BitPosition configured on Y is the forward connected adjacency of X. 90 This document proposes OSPFv3 extensions for distributing 91 BitPositions configured on the links in "Bit Index Explicit 92 Replication Traffic Engineering" (BIER-TE) domain. 94 1.1. Terminology 96 BIER: Bit Index Explicit Replication. 98 BIER-TE: BIER Traffic Engineering. 100 BFR: Bit-Forwarding Router. 102 BFIR: Bit-Forwarding Ingress Router. 104 BFER: Bit-Forwarding Egress Router. 106 BFR-id: BFR Identifier. It is a number in the range [1,65535]. 108 BFR-NBR: BFR Neighbor. 110 LSA: Link State Advertisement. 112 OSPF: Open Shortest Path First. 114 2. Extensions to OSPFv3 116 This section describes protocol extensions to OSPFv3 for distributing 117 BIER-TE information such as the BitPositions configured on the links 118 in a BIER-TE domain. 120 [RFC8362] defines OSPFv3 Extended Router LSA, which may include 121 multiple Router-Link TLVs. A Router-Link TLV defines a single router 122 link. A Router-Link TLV may include a BIER-TE Sub-TLV below for 123 distributing BIER-TE information. This Sub-TLV has the following 124 format. 126 0 1 2 3 127 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 128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 129 | Type (TBD1) | Length | 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | sub-domain-id | MT-ID | BAR | IPA | 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | BitPosition | DrEndBitPosition | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | Sub-Sub-TLVs (variable) | 136 ~ ~ 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 Figure 1: BIER-TE Sub-TLV in Router-Link TLV 141 Type: TBD1 is to be assigned by IANA. 143 Length: Variable, dependent on Sub-Sub-TLVs. 145 sub-domain-id: Unique value identifying a BIER-TE sub-domain. 147 MT-ID: Multi-Topology ID identifying the topology that is associated 148 with the BIER-TE sub-domain. 150 BAR: Single-octet BIER Algorithm used to calculate underlay paths to 151 reach other BFRs. Values are allocated from the "BIER 152 Algorithm" registry defined in [RFC8401]. 154 IPA: Single-octet IGP Algorithm used to either modify, enhance, or 155 replace the calculation of underlay paths to reach other BFRs 156 as defined by the BAR value. Values are defined in the "IGP 157 Algorithm Types" registry. 159 BitPosition: A 2-octet field encoding the BitPosition locally 160 configured on the link/interface when the Link Type of the link 161 in the Router-Link TLV containing this Sub-TLV is 1 (i.e., 162 Point-to-Point connection to another router) or 2 (i.e., 163 connection to Transit Network or say LAN). 165 DrEndBitPosition: A 2-octet field encoding the BitPosition of the 166 connection on the designated router (DR) end. This field is 167 valid when the Link Type in the Router-Link TLV containing this 168 Sub-TLV is 2 (i.e., Transit Network or LAN). For the other 169 value of the Link Type, this field MUST be ignored. The 170 DrEndBitPosition may be configured on the link/interface to a 171 transit network (i.e., broadcast link or say LAN). 173 No Sub-Sub-TLV is defined so far. Note that if each of BitPosition 174 and DrEndBitPosition uses more than 2 octets, we use 4 or more octets 175 for each of them. 177 3. Security Considerations 179 TBD. 181 4. IANA Considerations 183 Under "OSPFv3 Extended-LSA sub-TLV registry" as defined in [RFC8362], 184 IANA is requested to assign a new registry type for BIER-TE Sub-TLV 185 as follows: 187 +==============+===================+=====================+ 188 | Sub-TLV Type | Sub-TLV Name | reference | 189 +==============+===================+=====================+ 190 | TBD1 | BIER-TE | This document | 191 +--------------+-------------------+---------------------+ 193 5. Acknowledgements 195 The authors would like to thank people for their comments to this 196 work. 198 6. References 200 6.1. Normative References 202 [I-D.ietf-bier-te-arch] 203 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 204 for Bit Index Explicit Replication (BIER-TE)", draft-ietf- 205 bier-te-arch-09 (work in progress), October 2020. 207 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 208 Requirement Levels", BCP 14, RFC 2119, 209 DOI 10.17487/RFC2119, March 1997, 210 . 212 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 213 Topology (MT) Routing in Intermediate System to 214 Intermediate Systems (IS-ISs)", RFC 5120, 215 DOI 10.17487/RFC5120, February 2008, 216 . 218 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 219 IANA Considerations Section in RFCs", RFC 5226, 220 DOI 10.17487/RFC5226, May 2008, 221 . 223 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 224 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 225 May 2017, . 227 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 228 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 229 Explicit Replication (BIER)", RFC 8279, 230 DOI 10.17487/RFC8279, November 2017, 231 . 233 [RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and 234 F. Baker, "OSPFv3 Link State Advertisement (LSA) 235 Extensibility", RFC 8362, DOI 10.17487/RFC8362, April 236 2018, . 238 6.2. Informative References 240 [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The 241 OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, 242 July 2008, . 244 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 245 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 246 for Bit Index Explicit Replication (BIER) in MPLS and Non- 247 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 248 2018, . 250 [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. 251 Zhang, "Bit Index Explicit Replication (BIER) Support via 252 IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, 253 . 255 [RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A., 256 Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2 257 Extensions for Bit Index Explicit Replication (BIER)", 258 RFC 8444, DOI 10.17487/RFC8444, November 2018, 259 . 261 [RFC8556] Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S., 262 and A. Dolganow, "Multicast VPN Using Bit Index Explicit 263 Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April 264 2019, . 266 Authors' Addresses 268 Huaimo Chen 269 Futurewei 270 Boston, MA 271 USA 273 Email: Huaimo.chen@futurewei.com 275 Mike McBride 276 Futurewei 278 Email: michael.mcbride@futurewei.com 279 Aijun Wang 280 China Telecom 281 Beiqijia Town, Changping District 282 Beijing, 102209 283 China 285 Email: wangaj3@chinatelecom.cn 287 Gyan S. Mishra 288 Verizon Inc. 289 13101 Columbia Pike 290 Silver Spring MD 20904 291 USA 293 Phone: 301 502-1347 294 Email: gyan.s.mishra@verizon.com 296 Yanhe Fan 297 Casa Systems 298 USA 300 Email: yfan@casa-systems.com 302 Lei Liu 303 Fujitsu 305 USA 307 Email: liulei.kddi@gmail.com 309 Xufeng Liu 310 Volta Networks 312 McLean, VA 313 USA 315 Email: xufeng.liu.ietf@gmail.com