idnits 2.17.1 draft-xie-bier-ipv6-isis-extension-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 (July 1, 2019) is 1761 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) == Missing Reference: 'RFC8401' is mentioned on line 178, but not defined == Outdated reference: A later version (-04) exists of draft-ietf-bier-lsr-ethernet-extensions-00 == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-00 == Outdated reference: A later version (-10) exists of draft-xie-bier-ipv6-encapsulation-01 Summary: 0 errors (**), 0 flaws (~~), 5 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: January 2, 2020 China Telecom 6 G. Yan 7 S. Dhanaraj 8 Huawei Technologies 9 July 1, 2019 11 BIER IPv6 Encapsulation (BIERv6) Support via IS-IS 12 draft-xie-bier-ipv6-isis-extension-00 14 Abstract 16 This document defines IS-IS extensions to support multicast 17 forwarding using the Bit Index Explicit Replication (BIER) with IPv6 18 encapsulation (BIERv6). 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in [RFC2119] and 25 [RFC8174]. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on January 2, 2020. 44 Copyright Notice 46 Copyright (c) 2019 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 3. Specification . . . . . . . . . . . . . . . . . . . . . . . . 3 64 3.1. Function sub-TLV for BIERv6 . . . . . . . . . . . . . . . 3 65 3.2. Encapsulation sub-sub-TLV for BIERv6 . . . . . . . . . . 4 66 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 68 5.1. Function sub-TLV Type Code . . . . . . . . . . . . . . . 4 69 5.2. 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 Familiarity with the concept of "BIER specific" IPv6 address 83 introduced in [I-D.xie-bier-ipv6-encapsulation] is necessary to 84 understand the extensions specified in this document. 86 The [I-D.ietf-spring-srv6-network-programming] describes how a 87 function can be bound to a special "IPv6 Address" within a special 88 "IPv6 Address Block". The function bound to a special "IPv6 Address" 89 can be used to indicate a special forwarding process in data-plane. 91 The BIER IPv6 encapsulation [I-D.xie-bier-ipv6-encapsulation] uses a 92 "BIER specific" IPv6 unicast address configured locally on a BIER 93 Forwarding Router (BFR) to indicate a "BIER specific handling" in 94 Forwarding Information Base (FIB). This BIER specific IPv6 address 95 is also required to use as the BFR prefix as defined in [RFC8279]. 97 The indication of BFR prefix is a BIER Sub-TLV within the extended IP 98 reachability TLV as specified by in [RFC8401]. 100 The indication of BIER specific function is a "Function Sub-TLV" 101 within the extended IP reachability as specified by in this document. 103 Note the extended IP reachability only includes the TLV 236 (IPv6 IP 104 Reach TLV) [RFC5308] and TLV 237 (MT IPv6 IP Reach TLVs) [RFC5120] in 105 this document. 107 The following restrictions defined for BIER Sub-TLV in section 4.2 of 108 [RFC8401] apply equally to Function Sub-TLV: 110 o Prefix length MUST be 128 for an IPv6 prefix. 112 o When the Prefix Attributes Flags sub-TLV [RFC7794] is present, the 113 N flag MUST be set and the R flag MUST NOT be set. 115 o BIER sub-TLVs and Function Sub-TLVs MUST be included when a prefix 116 reachability advertisement is leaked between levels. 118 2. Terminology 120 Readers of this document are assumed to be familiar with the 121 terminology and concepts of the documents listed as Normative 122 References. 124 3. Specification 126 3.1. Function sub-TLV for BIERv6 128 The Function sub-TLV is introduced to advertise a specified function 129 bound to an IPv6 prefix with 128 bit prefix length. This new sub-TLV 130 is advertised in the TLV 236 or TLV 237. The sub-TLV has the 131 following format: 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 | Length | 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Function | Flags | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 Type: 1 octet value indicating "Function Information" this IPv6 142 prefix bound to. To be assigned by IANA. 144 Length: 1 octet length in octets. Value 4 is set to this field. 146 Function: 2 octets value indicating function. A BIER function value 147 called End.BIER defined in [I-D.xie-bier-ipv6-encapsulation] is 148 expected to be the only function in the TLV. 150 Flags: 1 octet value indicating the Flags for the function preceding 151 this field. No flags are currently defined and 0 should be set for 152 this field. 154 3.2. Encapsulation sub-sub-TLV for BIERv6 156 The Encapsulation sub-sub-TLV carries the information for the BIER 157 IPv6 encapsulation of a specific BitString length. It is advertised 158 within the BIER Info sub-TLV defined in [RFC8401] which in-turn is 159 carried within the TLVs 236 or 237. This sub-sub-TLV MAY appear 160 multiple times within a single BIER Info sub-TLV. If the same 161 BitString length is repeated in multiple sub-sub-TLVs inside the same 162 BIER Info sub- TLV, the BIER Info sub-TLV MUST be ignored. 164 0 1 2 3 165 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 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | Type | Length | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 | Max SI |BS Len | BIFT-id | 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 The Type field is a 1 octet value indicating BIER IPv6 encapsulation. 173 To be assigned by IANA. 175 The Length field is a 1 octet length in octets. Value 4 is set to 176 this field. 178 Other fields can be referred to [RFC8401] for MPLS encapsulation, or 179 [I-D.ietf-bier-lsr-ethernet-extensions] for Ethernet encapsulation. 181 4. Security Considerations 183 The procedures of this document do not, in themselves, provide 184 privacy, integrity, or authentication for the control plane or the 185 data plane. 187 5. IANA Considerations 189 5.1. Function sub-TLV Type Code 191 Allocation is expected from IANA for a IS-IS Sub-TLV Type codepoint 192 from the "Sub-TLVs for TLVs 135, 235, 236, and 237" sub-registry. 194 Type: To be assigned by IANA. 196 Description: Function Info. 198 Reference: This document. 200 Type 135 235 236 237 Reference 201 32 y y y y RFC8401 202 TBD n n y y This document 204 5.2. Encapsulation sub-sub-TLV Type Code 206 Allocation is expected from IANA for a BIER IPv6 encapsulation sub- 207 sub-TLV codepoint from the "sub-sub-TLVs for BIER Info sub-TLV" sub- 208 registry. 210 Type: To be assigned by IANA. 212 Name: BIER IPv6 Encapsulation. 214 Reference: This document. 216 6. Acknowledgements 218 TBD. 220 7. References 222 7.1. Normative References 224 [I-D.ietf-bier-lsr-ethernet-extensions] 225 Dhanaraj, S., Wijnands, I., Psenak, P., Zhang, Z., Yan, 226 G., and J. Xie, "LSR Extensions for BIER over Ethernet", 227 draft-ietf-bier-lsr-ethernet-extensions-00 (work in 228 progress), May 2019. 230 [I-D.ietf-spring-srv6-network-programming] 231 Filsfils, C., Camarillo, P., Leddy, J., 232 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 233 Network Programming", draft-ietf-spring-srv6-network- 234 programming-00 (work in progress), April 2019. 236 [I-D.xie-bier-ipv6-encapsulation] 237 Xie, J., Geng, L., McBride, M., Dhanaraj, S., Yan, G., and 238 Y. Xia, "Encapsulation for BIER in Non-MPLS IPv6 239 Networks", draft-xie-bier-ipv6-encapsulation-01 (work in 240 progress), June 2019. 242 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 243 Topology (MT) Routing in Intermediate System to 244 Intermediate Systems (IS-ISs)", RFC 5120, 245 DOI 10.17487/RFC5120, February 2008, 246 . 248 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, 249 DOI 10.17487/RFC5308, October 2008, 250 . 252 [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and 253 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 254 and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, 255 March 2016, . 257 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 258 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 259 Explicit Replication (BIER)", RFC 8279, 260 DOI 10.17487/RFC8279, November 2017, 261 . 263 7.2. Informative References 265 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 266 Requirement Levels", BCP 14, RFC 2119, 267 DOI 10.17487/RFC2119, March 1997, 268 . 270 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 271 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 272 May 2017, . 274 Authors' Addresses 276 Jingrong Xie 277 Huawei Technologies 279 Email: xiejingrong@huawei.com 281 Aijun Wang 282 China Telecom 284 Email: wangaj.bri@chinatelecom.cn 285 Gang Yan 286 Huawei Technologies 288 Email: yangang@huawei.com 290 Senthil Dhanaraj 291 Huawei Technologies 293 Email: senthil.dhanaraj@huawei.com