idnits 2.17.00 (12 Aug 2021) /tmp/idnits8081/draft-chen-bier-te-ospfv3-01.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 (27 July 2021) is 297 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 105 -- Looks like a reference, but probably isn't: '65535' on line 105 == Unused Reference: 'RFC5120' is defined on line 213, but no explicit reference was found in the text == Unused Reference: 'RFC5226' is defined on line 219, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 228, but no explicit reference was found in the text == Unused Reference: 'RFC5250' is defined on line 241, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 245, but no explicit reference was found in the text == Unused Reference: 'RFC8444' is defined on line 256, but no explicit reference was found in the text == Unused Reference: 'RFC8556' is defined on line 262, but no explicit reference was found in the text == Outdated reference: A later version (-13) exists of draft-ietf-bier-te-arch-10 ** 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: 28 January 2022 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 27 July 2021 17 OSPFv3 Extensions for BIER-TE 18 draft-chen-bier-te-ospfv3-01 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 28 January 2022. 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 (https://trustee.ietf.org/ 57 license-info) in effect on the date of publication of this document. 58 Please review these documents carefully, as they describe your rights 59 and restrictions with respect to this document. Code Components 60 extracted from this document must include Simplified BSD License text 61 as described in Section 4.e of the Trust Legal Provisions and are 62 provided without warranty as described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 68 2. Extensions to OSPFv3 . . . . . . . . . . . . . . . . . . . . 3 69 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 70 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 71 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 72 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 73 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 74 6.2. Informative References . . . . . . . . . . . . . . . . . 5 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 77 1. Introduction 79 [I-D.ietf-bier-te-arch] introduces Bit Index Explicit Replication 80 (BIER) Traffic/Tree Engineering (BIER-TE). It is an architecture for 81 per-packet stateless explicit point to multipoint (P2MP) multicast 82 path/tree. A link in a BIER-TE domain has its BitPositions. For a 83 link between two nodes X and Y, there are two BitPositions for two 84 forward connected adjacencies. These two adjacency BitPositions 85 could be configured on nodes X and Y respectively. The BitPosition 86 configured on X is the forward connected adjacency of Y. The 87 BitPosition configured on Y is the forward connected adjacency of X. 89 This document proposes OSPFv3 extensions for distributing 90 BitPositions configured on the links in "Bit Index Explicit 91 Replication Traffic Engineering" (BIER-TE) domain. 93 1.1. Terminology 95 BIER: Bit Index Explicit Replication. 97 BIER-TE: BIER Traffic Engineering. 99 BFR: Bit-Forwarding Router. 101 BFIR: Bit-Forwarding Ingress Router. 103 BFER: Bit-Forwarding Egress Router. 105 BFR-id: BFR Identifier. It is a number in the range [1,65535]. 107 BFR-NBR: BFR Neighbor. 109 LSA: Link State Advertisement. 111 OSPF: Open Shortest Path First. 113 2. Extensions to OSPFv3 115 This section describes protocol extensions to OSPFv3 for distributing 116 BIER-TE information such as the BitPositions configured on the links 117 in a BIER-TE domain. 119 [RFC8362] defines OSPFv3 Extended Router LSA, which may include 120 multiple Router-Link TLVs. A Router-Link TLV defines a single router 121 link. A Router-Link TLV may include a BIER-TE Sub-TLV below for 122 distributing BIER-TE information. This Sub-TLV has the following 123 format. 125 0 1 2 3 126 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 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 | Type (TBD1) | Length | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | sub-domain-id | MT-ID | BAR | IPA | 131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | BitPosition | DrEndBitPosition | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 | Sub-TLVs (variable) | 135 ~ ~ 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 Figure 1: BIER-TE Sub-TLV in Router-Link TLV 140 Type: TBD1 is to be assigned by IANA. 142 Length: Variable, dependent on Sub-Sub-TLVs. 144 sub-domain-id: Unique value identifying a BIER-TE sub-domain. 146 MT-ID: Multi-Topology ID identifying the topology that is associated 147 with the BIER-TE sub-domain. 149 BAR: Single-octet BIER Algorithm used to calculate underlay paths to 150 reach other BFRs. Values are allocated from the "BIER 151 Algorithm" registry defined in [RFC8401]. 153 IPA: Single-octet IGP Algorithm used to either modify, enhance, or 154 replace the calculation of underlay paths to reach other BFRs 155 as defined by the BAR value. Values are defined in the "IGP 156 Algorithm Types" registry. 158 BitPosition: A 2-octet field encoding the BitPosition locally 159 configured on the link/interface when the Link Type of the link 160 in the Router-Link TLV containing this Sub-TLV is 1 (i.e., 161 Point-to-Point connection to another router) or 2 (i.e., 162 connection to Transit Network or say LAN). 164 DrEndBitPosition: A 2-octet field encoding the BitPosition of the 165 connection on the designated router (DR) end. This field is 166 valid when the Link Type in the Router-Link TLV containing this 167 Sub-TLV is 2 (i.e., Transit Network or LAN). For the other 168 value of the Link Type, this field MUST be ignored. The 169 DrEndBitPosition may be configured on the link/interface to a 170 transit network (i.e., broadcast link or say LAN). 172 No Sub-TLV is defined so far. Note that if each of BitPosition and 173 DrEndBitPosition uses more than 2 octets, we use 4 or more octets for 174 each of them. 176 3. Security Considerations 178 TBD. 180 4. IANA Considerations 182 Under "OSPFv3 Extended-LSA Sub-TLVs registry" as defined in 183 [RFC8362], IANA is requested to assign a new registry value for BIER- 184 TE Sub-TLV as follows: 186 +==============+===================+=====================+ 187 | Value | Description | reference | 188 +==============+===================+=====================+ 189 | TBD1 (30) | BIER-TE | This document | 190 +--------------+-------------------+---------------------+ 192 5. Acknowledgements 194 The authors would like to thank Acee Lindem and Tony Przygienda for 195 their comments on this work. 197 6. References 199 6.1. Normative References 201 [I-D.ietf-bier-te-arch] 202 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 203 for Bit Index Explicit Replication (BIER-TE)", Work in 204 Progress, Internet-Draft, draft-ietf-bier-te-arch-10, 9 205 July 2021, . 208 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 209 Requirement Levels", BCP 14, RFC 2119, 210 DOI 10.17487/RFC2119, March 1997, 211 . 213 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 214 Topology (MT) Routing in Intermediate System to 215 Intermediate Systems (IS-ISs)", RFC 5120, 216 DOI 10.17487/RFC5120, February 2008, 217 . 219 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 220 IANA Considerations Section in RFCs", RFC 5226, 221 DOI 10.17487/RFC5226, May 2008, 222 . 224 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 225 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 226 May 2017, . 228 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 229 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 230 Explicit Replication (BIER)", RFC 8279, 231 DOI 10.17487/RFC8279, November 2017, 232 . 234 [RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and 235 F. Baker, "OSPFv3 Link State Advertisement (LSA) 236 Extensibility", RFC 8362, DOI 10.17487/RFC8362, April 237 2018, . 239 6.2. Informative References 241 [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The 242 OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, 243 July 2008, . 245 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 246 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 247 for Bit Index Explicit Replication (BIER) in MPLS and Non- 248 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 249 2018, . 251 [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. 252 Zhang, "Bit Index Explicit Replication (BIER) Support via 253 IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, 254 . 256 [RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A., 257 Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2 258 Extensions for Bit Index Explicit Replication (BIER)", 259 RFC 8444, DOI 10.17487/RFC8444, November 2018, 260 . 262 [RFC8556] Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S., 263 and A. Dolganow, "Multicast VPN Using Bit Index Explicit 264 Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April 265 2019, . 267 Authors' Addresses 269 Huaimo Chen 270 Futurewei 271 Boston, MA, 272 United States of America 274 Email: Huaimo.chen@futurewei.com 276 Mike McBride 277 Futurewei 279 Email: michael.mcbride@futurewei.com 280 Aijun Wang 281 China Telecom 282 Beiqijia Town, Changping District 283 Beijing 284 102209 285 China 287 Email: wangaj3@chinatelecom.cn 289 Gyan S. Mishra 290 Verizon Inc. 291 13101 Columbia Pike 292 Silver Spring, MD 20904 293 United States of America 295 Phone: 301 502-1347 296 Email: gyan.s.mishra@verizon.com 298 Yanhe Fan 299 Casa Systems 300 United States of America 302 Email: yfan@casa-systems.com 304 Lei Liu 305 Fujitsu 306 United States of America 308 Email: liulei.kddi@gmail.com 310 Xufeng Liu 311 Volta Networks 312 McLean, VA 313 United States of America 315 Email: xufeng.liu.ietf@gmail.com