idnits 2.17.1 draft-ietf-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 (24 January 2022) is 823 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 209, but no explicit reference was found in the text == Unused Reference: 'RFC5226' is defined on line 215, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 224, but no explicit reference was found in the text == Unused Reference: 'RFC5250' is defined on line 237, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 241, but no explicit reference was found in the text == Unused Reference: 'RFC8444' is defined on line 252, but no explicit reference was found in the text == Unused Reference: 'RFC8556' is defined on line 258, but no explicit reference was found in the text == Outdated reference: A later version (-13) exists of draft-ietf-bier-te-arch-11 ** 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 July 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 24 January 2022 17 OSPFv3 Extensions for BIER-TE 18 draft-ietf-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 28 July 2022. 50 Copyright Notice 52 Copyright (c) 2022 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 Revised BSD License text as 61 described in Section 4.e of the Trust Legal Provisions and are 62 provided without warranty as described in the Revised 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 . . . . . . . . . . . . . . . . . . . . . . 4 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 Figure 1: BIER-TE Sub-TLV in Router-Link TLV 137 Type: TBD1 is to be assigned by IANA. 139 Length: 8 (octets). 141 sub-domain-id: Unique value identifying a BIER-TE sub-domain. 143 MT-ID: Multi-Topology ID identifying the topology that is associated 144 with the BIER-TE sub-domain. 146 BAR: Single-octet BIER Algorithm used to calculate underlay paths to 147 reach other BFRs. Values are allocated from the "BIER 148 Algorithm" registry defined in [RFC8401]. 150 IPA: Single-octet IGP Algorithm used to either modify, enhance, or 151 replace the calculation of underlay paths to reach other BFRs 152 as defined by the BAR value. Values are defined in the "IGP 153 Algorithm Types" registry. 155 BitPosition: A 2-octet field encoding the BitPosition locally 156 configured on the link/interface when the Link Type of the link 157 in the Router-Link TLV containing this Sub-TLV is 1 (i.e., 158 Point-to-Point connection to another router) or 2 (i.e., 159 connection to Transit Network or say LAN). 161 DrEndBitPosition: A 2-octet field encoding the BitPosition of the 162 connection on the designated router (DR) end. This field is 163 valid when the Link Type in the Router-Link TLV containing this 164 Sub-TLV is 2 (i.e., Transit Network or LAN). For the other 165 value of the Link Type, this field MUST be ignored. The 166 DrEndBitPosition may be configured on the link/interface to a 167 transit network (i.e., broadcast link or say LAN). 169 Note that if each of BitPosition and DrEndBitPosition uses more than 170 2 octets, we use 4 or more octets for each of them. 172 3. Security Considerations 174 TBD. 176 4. IANA Considerations 178 Under "OSPFv3 Extended-LSA Sub-TLVs registry" as defined in 179 [RFC8362], IANA is requested to assign a new registry value for BIER- 180 TE Sub-TLV as follows: 182 +==============+===================+=====================+ 183 | Value | Description | reference | 184 +==============+===================+=====================+ 185 | TBD1 (30) | BIER-TE | This document | 186 +--------------+-------------------+---------------------+ 188 5. Acknowledgements 190 The authors would like to thank Acee Lindem and Tony Przygienda for 191 their comments on this work. 193 6. References 195 6.1. Normative References 197 [I-D.ietf-bier-te-arch] 198 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 199 for Bit Index Explicit Replication (BIER-TE)", Work in 200 Progress, Internet-Draft, draft-ietf-bier-te-arch-11, 15 201 November 2021, . 204 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 205 Requirement Levels", BCP 14, RFC 2119, 206 DOI 10.17487/RFC2119, March 1997, 207 . 209 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 210 Topology (MT) Routing in Intermediate System to 211 Intermediate Systems (IS-ISs)", RFC 5120, 212 DOI 10.17487/RFC5120, February 2008, 213 . 215 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 216 IANA Considerations Section in RFCs", RFC 5226, 217 DOI 10.17487/RFC5226, May 2008, 218 . 220 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 221 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 222 May 2017, . 224 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 225 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 226 Explicit Replication (BIER)", RFC 8279, 227 DOI 10.17487/RFC8279, November 2017, 228 . 230 [RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and 231 F. Baker, "OSPFv3 Link State Advertisement (LSA) 232 Extensibility", RFC 8362, DOI 10.17487/RFC8362, April 233 2018, . 235 6.2. Informative References 237 [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The 238 OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, 239 July 2008, . 241 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 242 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 243 for Bit Index Explicit Replication (BIER) in MPLS and Non- 244 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 245 2018, . 247 [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. 248 Zhang, "Bit Index Explicit Replication (BIER) Support via 249 IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, 250 . 252 [RFC8444] Psenak, P., Ed., Kumar, N., Wijnands, IJ., Dolganow, A., 253 Przygienda, T., Zhang, J., and S. Aldrin, "OSPFv2 254 Extensions for Bit Index Explicit Replication (BIER)", 255 RFC 8444, DOI 10.17487/RFC8444, November 2018, 256 . 258 [RFC8556] Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S., 259 and A. Dolganow, "Multicast VPN Using Bit Index Explicit 260 Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April 261 2019, . 263 Authors' Addresses 265 Huaimo Chen 266 Futurewei 267 Boston, MA, 268 United States of America 270 Email: Huaimo.chen@futurewei.com 272 Mike McBride 273 Futurewei 275 Email: michael.mcbride@futurewei.com 277 Aijun Wang 278 China Telecom 279 Beiqijia Town, Changping District 280 Beijing 281 102209 282 China 284 Email: wangaj3@chinatelecom.cn 285 Gyan S. Mishra 286 Verizon Inc. 287 13101 Columbia Pike 288 Silver Spring, MD 20904 289 United States of America 291 Phone: 301 502-1347 292 Email: gyan.s.mishra@verizon.com 294 Yanhe Fan 295 Casa Systems 296 United States of America 298 Email: yfan@casa-systems.com 300 Lei Liu 301 Fujitsu 302 United States of America 304 Email: liulei.kddi@gmail.com 306 Xufeng Liu 307 Volta Networks 308 McLean, VA 309 United States of America 311 Email: xufeng.liu.ietf@gmail.com