idnits 2.17.1 draft-chen-bier-te-isis-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 997 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: 'RFC5226' is defined on line 223, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 236, 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: 'RFC8556' is defined on line 255, 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 (~~), 6 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 IS-IS Extensions for BIER-TE 18 draft-chen-bier-te-isis-01 20 Abstract 22 This document describes IS-IS 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 IS-IS . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . 6 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 IS-IS extensions for distributing BitPositions 90 configured on the links in "Bit Index Explicit Replication Traffic 91 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 IS-IS: Intermediate System to Intermediate System. 111 2. Extensions to IS-IS 113 This section describes protocol extensions to IS-IS for distributing 114 BIER-TE information such as the BitPositions configured on the links 115 in a BIER-TE domain. 117 An Extended IS Reachability TLV (Type 22) defined in [RFC5305] may 118 contain Sub-TLVs (such as those for TE) that apply to a link/ 119 interface to a neighbor. To encode multiple links or interfaces to 120 neighbors, the structure inside TLV is repeated. 122 MT Intermediate Systems TLV (Type 222) defined in [RFC5120] may 123 contain Sub-TLVs (such as those for TE) that apply to a link/ 124 interface. It is aligned with Extended IS Reachability TLV (Type 22) 125 beside an additional two bytes in front at the beginning of the TLV 126 for MT-ID. 128 BIER-TE Info Sub-TLV of the following format is defined and used in 129 Extended IS Reachability TLV (Type 22) and/or MT Intermediate Systems 130 TLV (Type 222) to advertise the BIER-TE information about a link or 131 interface. 133 0 1 2 3 134 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 135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 136 | Type (TBD1) | Length | sub-domain-id | BAR | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Reserved | IPA | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | BitPosition | DisEndBitPosition | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 | Sub-Sub-TLVs (variable) | 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 Figure 1: BIER-TE Info Sub-TLV 147 Type: TBD1 is to be assigned by IANA. 149 Length: Variable, dependent on Sub-Sub-TLVs. 151 sub-domain-id: Unique value identifying a BIER-TE sub-domain. 153 BAR: Single-octet BIER Algorithm used to calculate underlay paths to 154 reach other BFRs. Values are allocated from the "BIER 155 Algorithm" registry defined in [RFC8401]. 157 Reserved: SHOULD be set to zero on transmission and MUST be ignored 158 on receipt. 160 IPA: Single-octet IGP Algorithm used to either modify, enhance, or 161 replace the calculation of underlay paths to reach other BFRs 162 as defined by the BAR value. Values are defined in the "IGP 163 Algorithm Types" registry. 165 BitPosition: A 2-octet field encoding the BitPosition locally 166 configured on the link/interface to an Intermediate System 167 neighbor. 169 DisEndBitPosition: A 2-octet field encoding the BitPosition of the 170 connection on the designated Intermediate Systems (Dis) end. 171 This field is valid when the neighbor is a pseudonode. If the 172 neighbor is not a pseudonode, this field MUST be ignored. The 173 DisEndBitPosition may be configured on the link/interface to a 174 transit network (i.e., broadcast link or say LAN). 176 No Sub-Sub-TLV is defined so far. Note that if each of BitPosition 177 and DrEndBitPosition uses more than 2 octets, we use 4 or more octets 178 for each of them. 180 3. Security Considerations 182 TBD. 184 4. IANA Considerations 186 Under "Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223" for IS-IS TLV 187 Codepoints, IANA is requested to assign a new codepoint for BIER-TE 188 Info Sub-TLV as follows: 190 +============+=============+==+==+==+===+===+===+=============+ 191 |Sub-TLV Type|Sub-TLV Name |22|23|25|141|222|223|reference | 192 +============+=============+==+==+==+===+===+===+=============+ 193 | TBD1 |BIER-TE Info |y |n |n | n | y | n |This document| 194 +------------+-------------+--+--+--+---+---+---+-------------+ 196 5. Acknowledgements 198 The authors would like to thank Tony Przygienda and Acee Lindem for 199 their comments on this work. 201 6. References 203 6.1. Normative References 205 [I-D.ietf-bier-te-arch] 206 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 207 for Bit Index Explicit Replication (BIER-TE)", Work in 208 Progress, Internet-Draft, draft-ietf-bier-te-arch-10, 9 209 July 2021, . 212 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 213 Requirement Levels", BCP 14, RFC 2119, 214 DOI 10.17487/RFC2119, March 1997, 215 . 217 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 218 Topology (MT) Routing in Intermediate System to 219 Intermediate Systems (IS-ISs)", RFC 5120, 220 DOI 10.17487/RFC5120, February 2008, 221 . 223 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 224 IANA Considerations Section in RFCs", RFC 5226, 225 DOI 10.17487/RFC5226, May 2008, 226 . 228 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 229 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 230 2008, . 232 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 233 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 234 May 2017, . 236 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 237 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 238 Explicit Replication (BIER)", RFC 8279, 239 DOI 10.17487/RFC8279, November 2017, 240 . 242 6.2. Informative References 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 [RFC8556] Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S., 256 and A. Dolganow, "Multicast VPN Using Bit Index Explicit 257 Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April 258 2019, . 260 Authors' Addresses 262 Huaimo Chen 263 Futurewei 264 Boston, MA, 265 United States of America 267 Email: Huaimo.chen@futurewei.com 269 Mike McBride 270 Futurewei 272 Email: michael.mcbride@futurewei.com 274 Aijun Wang 275 China Telecom 276 Beiqijia Town, Changping District 277 Beijing 278 102209 279 China 281 Email: wangaj3@chinatelecom.cn 282 Gyan S. Mishra 283 Verizon Inc. 284 13101 Columbia Pike 285 Silver Spring, MD 20904 286 United States of America 288 Phone: 301 502-1347 289 Email: gyan.s.mishra@verizon.com 291 Yanhe Fan 292 Casa Systems 293 United States of America 295 Email: yfan@casa-systems.com 297 Lei Liu 298 Fujitsu 299 United States of America 301 Email: liulei.kddi@gmail.com 303 Xufeng Liu 304 Volta Networks 305 McLean, VA 306 United States of America 308 Email: xufeng.liu.ietf@gmail.com