idnits 2.17.1 draft-chen-idr-bgp-ls-bier-ext-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 (October 30, 2015) is 3101 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 (-08) exists of draft-ietf-bier-architecture-02 ** Downref: Normative reference to an Informational RFC: RFC 6952 Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Networking Working Group Ran. Chen 3 Internet-Draft Zheng. Zhang 4 Intended status: Standards Track ZTE Corporation 5 Expires: May 2, 2016 October 30, 2015 7 BGP Link-State extensions for BIER 8 draft-chen-idr-bgp-ls-bier-ext-00 10 Abstract 12 Bit Index Explicit Replication (BIER) is an architecture that 13 provides optimal multicast forwarding through a "BIER domain" without 14 requiring intermediate routers to maintain any multicast related per- 15 flow state. BIER forwards and replicates packets based on a 16 BitString in the packet header. 18 This document specifies extensions to the BGP Link-state address- 19 family in order to advertising BIER information. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on May 2, 2016. 38 Copyright Notice 40 Copyright (c) 2015 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Conventions used in this document . . . . . . . . . . . . . . 2 57 3. BGP-LS Extensions for BIER . . . . . . . . . . . . . . . . . 3 58 3.1. The Link-State NLRI . . . . . . . . . . . . . . . . . . . 3 59 3.1.1. Node NLRI TLV . . . . . . . . . . . . . . . . . . . . 3 60 3.1.2. Link NLRI TLV . . . . . . . . . . . . . . . . . . . . 4 61 3.2. The new BGP-LS Attribute . . . . . . . . . . . . . . . . 5 62 3.2.1. BIER information sub-TLV . . . . . . . . . . . . . . 5 63 3.2.2. BIER-TE sub-TLV . . . . . . . . . . . . . . . . . . . 6 64 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 65 4.1. BGP-LS node NLRI-Type . . . . . . . . . . . . . . . . . . 7 66 4.2. BGP-LS link NLRI-Type . . . . . . . . . . . . . . . . . . 7 67 4.3. BGP-LS Attribute TLV . . . . . . . . . . . . . . . . . . 7 68 4.3.1. BGP-LS node Attribute TLV . . . . . . . . . . . . . . 7 69 4.3.2. BGP-LS link Attribute TLV . . . . . . . . . . . . . . 8 70 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 71 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 72 7. Normative references . . . . . . . . . . . . . . . . . . . . 8 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 75 1. Introduction 77 Bit Index Explicit Replication (BIER) is an architecture that 78 provides optimal multicast forwarding through a "BIER domain" without 79 requiring intermediate routers to maintain any multicast related per- 80 flow state. BIER forwards and replicates packets based on a 81 BitString in the packet header. 83 This document specifies extensions to the BGP Link-state address- 84 family in order to advertising BIER-specific. An external component 85 (e.g., a controller) then can collect BIER information in the 86 "northbound" direction across IGP areas or ASes and construct the 87 end-to-end path. 89 2. Conventions used in this document 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in RFC2119. 95 3. BGP-LS Extensions for BIER 97 BGP-LS [I-D.ietf-idr-ls-distribution] defines the BGP-LS NLRI that 98 can be a Node NLRI, a Link NLRI or a Prefix NLRI. The corresponding 99 BGP-LS attribute is a Node Attribute, a Link Attribute or a Prefix 100 Attribute. 102 In this document, we define two new "Node NLRI type" and a "link NLRI 103 type". The corresponding new BGP-LS attributes are also defined. 105 3.1. The Link-State NLRI 107 3.1.1. Node NLRI TLV 109 The following new "Node NLRI types" are defined for node Identifier 110 Information as following: 112 o IPV4 BFR-Prefix NLRI. 114 o IPV6 BFR-Prefix NLRI. 116 The following IPv4 BFR-Prefix NLRI is defined: 118 0 1 2 3 119 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 120 +-+-+-+-+-+-+-+-+ 121 | Protocol-ID | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 | IPV4 BFR-Prefix | 124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 126 Figure 1 128 The IPv6 BFR-Prefix NLRI is shown in the following figure: 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 | Protocol-ID | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | | 136 | IPV6 BFR-Prefix | 137 | | 138 | | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 141 Figure 2 143 3.1.2. Link NLRI TLV 145 The following new "link NLRI types" are defined for TE LSP Identifier 146 Information as following: 148 o IPV4 BIER-TE NLRI. 150 o IPV6 BIER-TE NLRI. 152 The IPV4 BIER-TE NLRI is shown in the following figure: 154 0 1 2 3 155 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 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | Protocol-ID | Subdomain-id | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 | Local Node Descriptors | 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | Remote Node Descriptors | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 Figure 3 166 Protocol-ID: TBD. 168 Subdomain-id: Unique value identifying the BIER sub-domain. 1 octet. 170 Local Node descriptors: The IPV4 BFR-Prefix of local node.4 octets. 172 Remote Node descriptors: The IPV4 BFR-Prefix of Remote node. 4 173 octets. 175 The IPV6 BIER-TE NLRI is shown in the following figure: 177 0 1 2 3 178 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 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | Protocol-ID | Subdomain-id | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | | 183 | Local Node Descriptors | 184 | | 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | | 187 | Remote Node Descriptors | 188 | | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 Figure 4 193 Protocol-ID: TBD. 195 Subdomain-id: Unique value identifying the BIER sub-domain. 1 octet. 197 Local Node descriptors: The IPV6 BFR-Prefix of local node.16 octets. 199 Remote Node descriptors: The IPV6 BFR-Prefix of Remote node. 16 200 octets. 202 3.2. The new BGP-LS Attribute 204 3.2.1. BIER information sub-TLV 206 This sub-TLV SHOULD only be encoded in the BGP-LS node attributes 207 with a BFR Prefix NLRI that originates the corresponding BIER 208 information. 210 The following BIER info TLV is defined: 212 0 1 2 3 213 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 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | Type | Length | subdomain-id | BSL | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Reserved | BFR-id | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 Figure 5 222 Type: TBD. 224 Length: 1 octet. 226 Subdomain-id: Unique value identifying the BIER sub-domain, 1 octet. 228 BitString Length (BS Len): the number of bits in the BitString, 2 229 octets. 231 Reserved: reserved, must be 0 on transmission, ignored on reception. 232 May be used in future versions. 8 bits. 234 BFR-id: A 2 octets field encoding the BFR-id, as documented in 235 [I-D.ietf-bier-architecture]. 237 3.2.2. BIER-TE sub-TLV 239 This TLV SHOULD only be encoded in the BGP-LS link attributes with a 240 BIER-TE NLRI that originates the corresponding BIER-TE information. 242 The following new Link Attribute TLV is defined: 244 0 1 2 3 245 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 246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 | Type | Length | 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | sub-TLVs | 250 | | 251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 Figure 6 255 Type: TBD. 257 Length: variable. 259 Sub-TLVs:the following sub-sub-TLVs of the BIER-TE sub-TLV are 260 defined, the sub-sub-TLVs details as defined in [RFC3630]: 262 5- Traffic engineering metric(4 octets, as defined RFC3630 section 263 2.5.5). 265 6- Maximum bandwidth(4 octets, as defined RFC3630 section 2.5.6). 267 7- Maximum reservable bandwidth(4 octets, as defined RFC3630 268 section 2.5.7). 270 8- Unreserved bandwidth(32 octets, as defined RFC3036 section 271 2.5.8). 273 4. IANA Considerations 275 This document requests assigning code-points from the registry for 276 BGP-LS NLRI-Types and BGP-LS attribute TLVs. 278 4.1. BGP-LS node NLRI-Type 280 IANA is requested to assign two new Node NLRI-Types: 282 +------+---------------------------+---------------+ 283 | Type | NLRI Type | Reference | 284 +------+---------------------------+---------------+ 285 | TBD | IPv4 BFR-Prefix NLRI | this document | 286 | TBD | IPv6 BFR-Prefix NLRI | this document | 287 +------+---------------------------+---------------+ 289 4.2. BGP-LS link NLRI-Type 291 IANA is requested to assign two new link NLRI-Types: 293 +------+---------------------------+---------------+ 294 | Type | NLRI Type | Reference | 295 +------+---------------------------+---------------+ 296 | TBD | IPv4 BIER-TE NLRI | this document | 297 | TBD | IPv6 BIER-TE NLRI | this document | 298 +------+---------------------------+---------------+ 300 4.3. BGP-LS Attribute TLV 302 4.3.1. BGP-LS node Attribute TLV 304 IANA is requested to assign new node Attribute TLV: 306 +-----------+---------------------+-----------------+ 307 | TLV Code | Description | Value defined | 308 | Point | | in: | 309 +-----------+---------------------+-----------------+ 310 | TBD | BIER Info | this document | 311 +-----------+---------------------+-----------------+ 313 4.3.2. BGP-LS link Attribute TLV 315 IANA is requested to assign new link Attribute TLV 317 +-----------+---------------------+-----------------+ 318 | TLV Code | Description | Value defined | 319 | Point | | in: | 320 +-----------+---------------------+-----------------+ 321 | TBD | BIER-TE TLV | this document | 322 +-----------+---------------------+-----------------+ 324 5. Security Considerations 326 Procedures and protocol extensions defined in this document do not 327 affect the BGP security model. See [RFC6952] for details. 329 6. Acknowledgements 331 TBD. 333 7. Normative references 335 [I-D.ietf-bier-architecture] 336 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 337 S. Aldrin, "Multicast using Bit Index Explicit 338 Replication", draft-ietf-bier-architecture-02 (work in 339 progress), July 2015. 341 [I-D.ietf-idr-ls-distribution] 342 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 343 Ray, "North-Bound Distribution of Link-State and TE 344 Information using BGP", draft-ietf-idr-ls-distribution-13 345 (work in progress), October 2015. 347 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 348 (TE) Extensions to OSPF Version 2", RFC 3630, 349 DOI 10.17487/RFC3630, September 2003, 350 . 352 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of 353 BGP, LDP, PCEP, and MSDP Issues According to the Keying 354 and Authentication for Routing Protocols (KARP) Design 355 Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, 356 . 358 Authors' Addresses 360 Ran Chen 361 ZTE Corporation 362 No.50 Software Avenue,Yuhuatai District 363 Nanjing, Jiangsu Province 210012 364 China 366 Phone: +86 025 88014636 367 Email: chen.ran@zte.com.cn 369 Zheng Zhang 370 ZTE Corporation 371 No.50 Software Avenue,Yuhuatai District 372 Nanjing, Jiangsu Province 210012 373 China 375 Email: zhang.zheng@zte.com.cn