idnits 2.17.1 draft-xie-bier-ipv6-isis-extension-02.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 (October 27, 2020) is 1274 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) == Outdated reference: A later version (-04) exists of draft-ietf-bier-lsr-ethernet-extensions-01 == Outdated reference: A later version (-10) exists of draft-xie-bier-ipv6-encapsulation-08 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Xie 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track A. Wang 5 Expires: April 30, 2021 China Telecom 6 G. Yan 7 S. Dhanaraj 8 X. Geng 9 Huawei Technologies 10 October 27, 2020 12 BIER IPv6 Encapsulation (BIERv6) Support via IS-IS 13 draft-xie-bier-ipv6-isis-extension-02 15 Abstract 17 This document defines IS-IS extensions to support multicast 18 forwarding using the Bit Index Explicit Replication (BIER) with IPv6 19 encapsulation (BIERv6). 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in [RFC2119] and 26 [RFC8174]. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at https://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on April 30, 2021. 45 Copyright Notice 47 Copyright (c) 2020 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (https://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3. Specification . . . . . . . . . . . . . . . . . . . . . . . . 3 65 3.1. Encapsulation sub-sub-TLV of End.BIER address . . . . . . 3 66 3.2. Encapsulation sub-sub-TLV of BIFT-id for each BSL . . . . 4 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 68 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 69 5.1. Encapsulation sub-sub-TLV Type Code . . . . . . . . . . . 5 70 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 71 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 72 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 73 7.2. Informative References . . . . . . . . . . . . . . . . . 6 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 76 1. Introduction 78 This document defines IS-IS extensions to support multicast 79 forwarding using the Bit Index Explicit Replication (BIER) with IPv6 80 encapsulation (BIERv6). 82 The BIER IPv6 encapsulation [I-D.xie-bier-ipv6-encapsulation] uses a 83 "BIER specific" IPv6 unicast address, the "End.BIER" address, 84 configured locally on a BIER Forwarding Router (BFR) to indicate a 85 "BIER specific handling" in Forwarding Information Base (FIB). This 86 BIER specific IPv6 address, used as part of BIER IPv6 encapsulation, 87 is advertised as a type of Encapsulation sub-sub-TLV within the BIER 88 Info sub-TLV defined [RFC8401]. 90 The BIFT-id field for each BSL of each Sub-domain is another part of 91 BIER IPv6 encapsulation, and is advertised as a type of Encapsulation 92 sub-sub-TLV within the BIER Info sub-TLV defined [RFC8401]. 94 The BIER Sub-TLV is advertised within the extended IP reachability 95 TLV as specified by in [RFC8401]. 97 Note the extended IP reachability only includes the TLV 236 (IPv6 IP 98 Reach TLV) [RFC5308] and TLV 237 (MT IPv6 IP Reach TLVs) [RFC5120] in 99 this document. 101 The following restrictions defined for BIER Sub-TLV in section 4.2 of 102 [RFC8401] apply equally to this document: 104 o Prefix length MUST be 128 for an IPv6 prefix. 106 o When the Prefix Attributes Flags sub-TLV [RFC7794] is present, the 107 N flag MUST be set and the R flag MUST NOT be set. 109 o BIER sub-TLVs and Function Sub-TLVs MUST be included when a prefix 110 reachability advertisement is leaked between levels. 112 2. Terminology 114 Readers of this document are assumed to be familiar with the 115 terminology and concepts of the documents listed as Normative 116 References. 118 3. Specification 120 3.1. Encapsulation sub-sub-TLV of End.BIER address 122 The Encapsulation sub-sub-TLV carries the information for the 123 End.BIER address of a sub-domain for BIER IPv6 encapsulation. It is 124 advertised within the BIER Info sub-TLV defined in [RFC8401] which 125 in-turn is carried within the TLVs 236 or 237. This sub-sub-TLV MUST 126 appear no more than one time within a single BIER Info sub-TLV. If 127 the sub-sub-TLV appears more than one time, the BIER Info sub-TLV 128 MUST be ignored. 130 0 1 2 3 131 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 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | Type | Length | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | | 136 | End.BIER address | 137 | | 138 | | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 Type: 1 octet value indicating "Encapsulation of End.BIER" this IPv6 142 prefix bound to. TBD1 to be assigned by IANA. 144 Length: 1 octet length in octets. Value 16 is set to this field. 146 End.BIER address: 16 octets IPv6 address. 148 3.2. Encapsulation sub-sub-TLV of BIFT-id for each BSL 150 The Encapsulation sub-sub-TLV carries the information for the BIER 151 IPv6 encapsulation of a specific BitString length. It is advertised 152 within the BIER Info sub-TLV defined in [RFC8401] which in-turn is 153 carried within the TLVs 236 or 237. This sub-sub-TLV MAY appear 154 multiple times within a single BIER Info sub-TLV. If the same 155 BitString length is repeated in multiple sub-sub-TLVs inside the same 156 BIER Info sub- TLV, the BIER Info sub-TLV MUST be ignored. 158 When a BIER IPv6 encapsulation sub-sub-TLV of BIFT-id for any BSL 159 appears in a BIER Info sub-TLV, one End.BIER Encapsulation sub-sub- 160 TLV MUST appears in the BIER info sub-TLV, otherwise the BIER Info 161 sub-TLV MUST be ignored. 163 0 1 2 3 164 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 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | Type | Length | 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 | Max SI |BS Len | BIFT-id | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 Type: 1 octet value indicating BIER IPv6 encapsulation. TBD2 to be 172 assigned by IANA. 174 Length: 1 octet length in octets. Value 4 is set to this field. 176 Max SI: 1 octet value. Maximum Set Identifier (Section 1 of 177 [RFC8279]) used in the encapsulation for this BIER sub-domain for 178 this BitString length. Each SI maps to a single BIFT-id in the BIFT- 179 id range. The first BIFT-id is for SI=0, the second BIFT-id is for 180 SI=1, etc. If the BIFT-id associated with the Maximum Set Identifier 181 exceeds the 20-bit range, the sub-sub-TLV MUST be ignored. 183 BS Len: 4 bits value of Local BitString Length. Encoded BitString 184 length as per [RFC8296]. 186 BIFT-id: 20 bits value. First BIFT-id of the range. The BIFT-id(s) 187 are as defined in [RFC8296], or refer to 188 [I-D.ietf-bier-lsr-ethernet-extensions] for Non-MPLS encapsulation. 190 4. Security Considerations 192 The security considerations defined in [RFC8401] and 193 [I-D.xie-bier-ipv6-encapsulation] apply equally to this document. 195 5. IANA Considerations 197 5.1. Encapsulation sub-sub-TLV Type Code 199 Allocation is expected from IANA for two sub-sub-TLV codepoints from 200 the "sub-sub-TLVs for BIER Info sub-TLV" sub-registry. 202 Type: TBD1 to be assigned by IANA. 204 Name: BIER IPv6 encapsulation of End.BIER address. 206 Reference: This document. 208 Type: TBD2 to be assigned by IANA. 210 Name: BIER IPv6 Encapsulation of BIFT-id for each BSL. 212 Reference: This document 214 6. Acknowledgements 216 TBD. 218 7. References 220 7.1. Normative References 222 [I-D.ietf-bier-lsr-ethernet-extensions] 223 Dhanaraj, S., Wijnands, I., Psenak, P., Zhang, Z., Yan, 224 G., and J. Xie, "LSR Extensions for BIER over Ethernet", 225 draft-ietf-bier-lsr-ethernet-extensions-01 (work in 226 progress), July 2019. 228 [I-D.xie-bier-ipv6-encapsulation] 229 Xie, J., Geng, L., McBride, M., Asati, R., Dhanaraj, S., 230 Zhu, Y., Qin, Z., Shin, M., Mishra, G., and X. Geng, 231 "Encapsulation for BIER in Non-MPLS IPv6 Networks", draft- 232 xie-bier-ipv6-encapsulation-08 (work in progress), July 233 2020. 235 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 236 Topology (MT) Routing in Intermediate System to 237 Intermediate Systems (IS-ISs)", RFC 5120, 238 DOI 10.17487/RFC5120, February 2008, 239 . 241 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, 242 DOI 10.17487/RFC5308, October 2008, 243 . 245 [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and 246 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 247 and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, 248 March 2016, . 250 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 251 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 252 Explicit Replication (BIER)", RFC 8279, 253 DOI 10.17487/RFC8279, November 2017, 254 . 256 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 257 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 258 for Bit Index Explicit Replication (BIER) in MPLS and Non- 259 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 260 2018, . 262 [RFC8401] Ginsberg, L., Ed., Przygienda, T., Aldrin, S., and Z. 263 Zhang, "Bit Index Explicit Replication (BIER) Support via 264 IS-IS", RFC 8401, DOI 10.17487/RFC8401, June 2018, 265 . 267 7.2. Informative References 269 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 270 Requirement Levels", BCP 14, RFC 2119, 271 DOI 10.17487/RFC2119, March 1997, 272 . 274 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 275 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 276 May 2017, . 278 Authors' Addresses 279 Jingrong Xie 280 Huawei Technologies 282 Email: xiejingrong@huawei.com 284 Aijun Wang 285 China Telecom 287 Email: wangaj3@chinatelecom.cn 289 Gang Yan 290 Huawei Technologies 292 Email: yangang@huawei.com 294 Senthil Dhanaraj 295 Huawei Technologies 297 Email: senthil.dhanaraj@huawei.com 299 Xuesong Geng 300 Huawei Technologies 302 Email: gengxuesong@huawei.com