idnits 2.17.1 draft-chen-bier-te-isis-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 1108 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: 'RFC5226' is defined on line 219, but no explicit reference was found in the text == Unused Reference: 'RFC8279' is defined on line 232, but no explicit reference was found in the text == Unused Reference: 'RFC8296' is defined on line 240, but no explicit reference was found in the text == Unused Reference: 'RFC8556' is defined on line 251, 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 (~~), 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: 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 IS-IS Extensions for BIER-TE 18 draft-chen-bier-te-isis-00 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 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 IS-IS . . . . . . . . . . . . . . . . . . . . . 3 70 3. Security Considerations . . . . . . . . . . . . . . . . . . . 5 71 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 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 IS-IS extensions for distributing BitPositions 91 configured on the links in "Bit Index Explicit Replication Traffic 92 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 IS-IS: Intermediate System to Intermediate System. 112 2. Extensions to IS-IS 114 This section describes protocol extensions to IS-IS for distributing 115 BIER-TE information such as the BitPositions configured on the links 116 in a BIER-TE domain. 118 An Extended IS Reachability TLV (Type 22) defined in [RFC5305] may 119 contain Sub-TLVs (such as those for TE) that apply to a link/ 120 interface to a neighbor. To encode multiple links or interfaces to 121 neighbors, the structure inside TLV is repeated. 123 MT Intermediate Systems TLV (Type 222) defined in [RFC5120] may 124 contain Sub-TLVs (such as those for TE) that apply to a link/ 125 interface. It is aligned with Extended IS Reachability TLV (Type 22) 126 beside an additional two bytes in front at the beginning of the TLV 127 for MT-ID. 129 BIER-TE Info Sub-TLV of the following format is defined and used in 130 Extended IS Reachability TLV (Type 22) and/or MT Intermediate Systems 131 TLV (Type 222) to advertise the BIER-TE information about a link or 132 interface. 134 0 1 2 3 135 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 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 137 | Type (TBD1) | Length | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 | sub-domain-id | BAR | IPA | 140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 | BitPosition | DisEndBitPosition | 142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 | Sub-Sub-TLVs (variable) | 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 146 Figure 1: BIER-TE Info Sub-TLV 148 Type: TBD1 is to be assigned by IANA. 150 Length: Variable, dependent on Sub-Sub-TLVs. 152 sub-domain-id: Unique value identifying a BIER-TE sub-domain. 154 BAR: Single-octet BIER Algorithm used to calculate underlay paths to 155 reach other BFRs. Values are allocated from the "BIER 156 Algorithm" registry defined in [RFC8401]. 158 IPA: Single-octet IGP Algorithm used to either modify, enhance, or 159 replace the calculation of underlay paths to reach other BFRs 160 as defined by the BAR value. Values are defined in the "IGP 161 Algorithm Types" registry. 163 BitPosition: A 2-octet field encoding the BitPosition locally 164 configured on the link/interface to an Intermediate System 165 neighbor. 167 DisEndBitPosition: A 2-octet field encoding the BitPosition of the 168 connection on the designated Intermediate Systems (Dis) end. 169 This field is valid when the neighbor is a pseudonode. If the 170 neighbor is not a pseudonode, this field MUST be ignored. The 171 DisEndBitPosition may be configured on the link/interface to a 172 transit network (i.e., broadcast link or say LAN). 174 No Sub-Sub-TLV is defined so far. Note that if each of BitPosition 175 and DrEndBitPosition uses more than 2 octets, we use 4 or more octets 176 for each of them. 178 3. Security Considerations 180 TBD. 182 4. IANA Considerations 184 Under "Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223" for IS-IS TLV 185 Codepoints, IANA is requested to assign a new codepoint for BIER-TE 186 Info Sub-TLV as follows: 188 +============+=============+==+==+==+===+===+===+=============+ 189 |Sub-TLV Type|Sub-TLV Name |22|23|25|141|222|223|reference | 190 +============+=============+==+==+==+===+===+===+=============+ 191 | TBD1 |BIER-TE Info |y |n |n | n | y | n |This document| 192 +------------+-------------+--+--+--+---+---+---+-------------+ 194 5. Acknowledgements 196 The authors would like to thank people for their comments to this 197 work. 199 6. References 201 6.1. Normative References 203 [I-D.ietf-bier-te-arch] 204 Eckert, T., Cauchie, G., and M. Menth, "Tree Engineering 205 for Bit Index Explicit Replication (BIER-TE)", draft-ietf- 206 bier-te-arch-09 (work in progress), October 2020. 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 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 225 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 226 2008, . 228 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 229 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 230 May 2017, . 232 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 233 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 234 Explicit Replication (BIER)", RFC 8279, 235 DOI 10.17487/RFC8279, November 2017, 236 . 238 6.2. Informative References 240 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 241 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 242 for Bit Index Explicit Replication (BIER) in MPLS and Non- 243 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 244 2018, . 246 [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. 247 Zhang, "Bit Index Explicit Replication (BIER) Support via 248 IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, 249 . 251 [RFC8556] Rosen, E., Ed., Sivakumar, M., Przygienda, T., Aldrin, S., 252 and A. Dolganow, "Multicast VPN Using Bit Index Explicit 253 Replication (BIER)", RFC 8556, DOI 10.17487/RFC8556, April 254 2019, . 256 Authors' Addresses 258 Huaimo Chen 259 Futurewei 260 Boston, MA 261 USA 263 Email: Huaimo.chen@futurewei.com 265 Mike McBride 266 Futurewei 268 Email: michael.mcbride@futurewei.com 269 Aijun Wang 270 China Telecom 271 Beiqijia Town, Changping District 272 Beijing, 102209 273 China 275 Email: wangaj3@chinatelecom.cn 277 Gyan S. Mishra 278 Verizon Inc. 279 13101 Columbia Pike 280 Silver Spring MD 20904 281 USA 283 Phone: 301 502-1347 284 Email: gyan.s.mishra@verizon.com 286 Yanhe Fan 287 Casa Systems 288 USA 290 Email: yfan@casa-systems.com 292 Lei Liu 293 Fujitsu 295 USA 297 Email: liulei.kddi@gmail.com 299 Xufeng Liu 300 Volta Networks 302 McLean, VA 303 USA 305 Email: xufeng.liu.ietf@gmail.com