idnits 2.17.1 draft-zhang-bier-babel-extensions-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 : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 94: '...d, such a router MAY use Babel protoco...' RFC 2119 keyword, line 105: '...-TLV, the router MUST ignore this unkn...' RFC 2119 keyword, line 113: '...TLV. The prefix MUST NOT be summarize...' RFC 2119 keyword, line 114: '... TLV MUST be treated as optional and...' RFC 2119 keyword, line 130: '... o Reserved: MUST be 0 on transmiss...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 27, 2017) is 2494 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 (-20) exists of draft-ietf-babel-rfc6126bis-02 == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-07 == Outdated reference: A later version (-11) exists of draft-ietf-bier-isis-extensions-04 == Outdated reference: A later version (-12) exists of draft-ietf-bier-mpls-encapsulation-07 == Outdated reference: A later version (-18) exists of draft-ietf-bier-ospf-bier-extensions-06 ** Obsolete normative reference: RFC 6126 (Obsoleted by RFC 8966) ** Obsolete normative reference: RFC 7557 (Obsoleted by RFC 8966) Summary: 3 errors (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER WG Z. Zhang 3 Internet-Draft ZTE Corporation 4 Intended status: Standards Track A. Przygienda 5 Expires: December 29, 2017 Juniper Networks 6 June 27, 2017 8 BIER in BABEL 9 draft-zhang-bier-babel-extensions-01 11 Abstract 13 BIER introduces a novel multicast architecture. It does not require 14 a signaling protocol to explicitly build multicast distribution 15 trees, nor does it require intermediate nodes to maintain any per- 16 flow state. 18 Babel defines a distance-vector routing protocol that operates in a 19 robust and efficient fashion both in wired as well as in wireless 20 mesh networks. This document defines a way to carry necessary BIER 21 signaling information in Babel. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on December 29, 2017. 40 Copyright Notice 42 Copyright (c) 2017 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 59 3. Advertisement of BIER information . . . . . . . . . . . . . . 2 60 3.1. BIER BFR-prefix and BIER sub-TLV . . . . . . . . . . . . 3 61 3.1.1. BIER sub-TLV . . . . . . . . . . . . . . . . . . . . 3 62 3.2. BIER MPLS Encapsulation sub-sub-TLV . . . . . . . . . . . 3 63 3.3. Optional BIER sub-domain BSL conversion sub-sub-TLV . . . 4 64 4. Tree types and tunneling . . . . . . . . . . . . . . . . . . 4 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 67 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 68 8. Normative References . . . . . . . . . . . . . . . . . . . . 5 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 71 1. Introduction 73 [I-D.ietf-bier-architecture] introduces a novel multicast 74 architecture. It does not require a signaling protocol to explicitly 75 build multicast distribution trees, nor does it require intermediate 76 nodes to maintain any per-flow state. All procedures necessary to 77 support BIER are abbreviated by the "BIER architecture" moniker in 78 this document. 80 [RFC6126] and [I-D.ietf-babel-rfc6126bis] define a distance-vector 81 routing protocol under the name of "Babel". Babel operates in a 82 robust and efficient fashion both in ordinary wired as well as in 83 wireless mesh networks. 85 2. Terminology 87 The terminology of this documents follows 88 [I-D.ietf-bier-architecture], [RFC6126], [RFC7557] and 89 [I-D.ietf-babel-rfc6126bis]. 91 3. Advertisement of BIER information 93 In case a router is configured with BIER information, and Babel is 94 the routing protocol used, such a router MAY use Babel protocol to 95 announce the BIER information using the BIER sub-TLV specified below. 97 3.1. BIER BFR-prefix and BIER sub-TLV 99 BFR-prefix and according information is carried in a Babel Update TLV 100 per [I-D.ietf-babel-rfc6126bis]. A new sub-TLV is defined to convey 101 further BIER information such as BFR-id, sub-domain-id and BSL. Two 102 sub-sub-TLVs are carried as payload of BIER sub-TLV. 104 The mandatory bit of BIER sub-TLV should be set to 0. If a router 105 cannot recognize a sub-TLV, the router MUST ignore this unknown sub- 106 TLV. 108 3.1.1. BIER sub-TLV 110 The BIER sub-TLV format aligns exactly with the definition and 111 restrictions in [I-D.ietf-bier-isis-extensions] and 112 [I-D.ietf-bier-ospf-bier-extensions]. It is a sub-TLV of Babel 113 update TLV. The prefix MUST NOT be summarized and the according sub- 114 TLV MUST be treated as optional and transitive. 116 0 1 2 3 117 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 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | sub-Type | Length | 120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 121 | Reserved | subdomain-id | BFR-id | 122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 123 Figure 1: BIER sub-TLV 125 o Type: as indicated in IANA section. 127 o Length: 1 octet. Include the length of BIER sub-TLV and potential 128 length of the two sub-sub-TLVs. 130 o Reserved: MUST be 0 on transmission, ignored on reception. May be 131 used in future versions. 8 bits. 133 o subdomain-id: Unique value identifying the BIER sub-domain. 1 134 octet. 136 o BFR-id: A 2 octet field encoding the BFR-id, as documented in 137 [I-D.ietf-bier-architecture]. If no BFR-id has been assigned this 138 field is set to the invalid BFR-id. 140 3.2. BIER MPLS Encapsulation sub-sub-TLV 142 The BIER MPLS Encapsulation sub-sub-TLV can be carried by BIER sub- 143 TLV. The format and restrictions are aligned with 144 [I-D.ietf-bier-isis-extensions] and 146 [I-D.ietf-bier-ospf-bier-extensions]. This sub-sub-TLV carries the 147 information for the BIER MPLS encapsulation including the label range 148 for a specific BSL for a certain pair. 150 0 1 2 3 151 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 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 153 | sub-sub-Type | Length | 154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 155 | Lbl Range Size|BS Len | Label | 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 Figure 3: MPLS Encapsulation sub-sub-TLV 159 o Type: value of 1 indicating MPLS encapsulation. 161 o Length: 1 octet 163 o Local BitString Length (BS Len): Encoded bitstring length as per 164 [I-D.ietf-bier-mpls-encapsulation]. 4 bits. 166 o Label Range Size: Number of labels in the range for this BIER sub- 167 domain and bitstring length combination, 1 octet. 169 o Label: First label of the range, 20 bits. The labels are as 170 defined in [I-D.ietf-bier-mpls-encapsulation]. 172 3.3. Optional BIER sub-domain BSL conversion sub-sub-TLV 174 This sub-sub-TLV is used to carry the BSL information. Its 175 definition and restrictions are aligned with 176 [I-D.ietf-bier-isis-extensions]. 178 0 1 2 3 179 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 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 | sub-sub-Type | Length | 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 Figure 4: BSL conversion sub-sub-TLV 185 4. Tree types and tunneling 187 Since Babel is performing a diffusion computation, support for 188 different tree types is not as natural as with link-state protocols. 189 Hence this specification is assuming that normal Babel reachability 190 computation is performed without further modifications. 192 BIER architecture does not rely on all routers in a domain performing 193 BFR procedures. How to support tunnels that will allow to tunnel 194 BIER across such routers in Babel is for further study. 196 5. Security Considerations 198 TBD 200 6. IANA Considerations 202 A new type of Babel update sub-TLV needs to be defined for BIER 203 information advertisement. 205 7. Acknowledgements 207 The draft is aligned with the [I-D.ietf-bier-isis-extensions] and 208 [I-D.ietf-bier-ospf-bier-extensions] as far as feasible. 210 8. Normative References 212 [I-D.ietf-babel-rfc6126bis] 213 Chroboczek, J., "The Babel Routing Protocol", draft-ietf- 214 babel-rfc6126bis-02 (work in progress), May 2017. 216 [I-D.ietf-bier-architecture] 217 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 218 S. Aldrin, "Multicast using Bit Index Explicit 219 Replication", draft-ietf-bier-architecture-07 (work in 220 progress), June 2017. 222 [I-D.ietf-bier-isis-extensions] 223 Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang, 224 "BIER support via ISIS", draft-ietf-bier-isis- 225 extensions-04 (work in progress), March 2017. 227 [I-D.ietf-bier-mpls-encapsulation] 228 Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., 229 Aldrin, S., and I. Meilik, "Encapsulation for Bit Index 230 Explicit Replication in MPLS and non-MPLS Networks", 231 draft-ietf-bier-mpls-encapsulation-07 (work in progress), 232 June 2017. 234 [I-D.ietf-bier-ospf-bier-extensions] 235 Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., 236 Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions 237 for BIER", draft-ietf-bier-ospf-bier-extensions-06 (work 238 in progress), June 2017. 240 [RFC6126] Chroboczek, J., "The Babel Routing Protocol", RFC 6126, 241 DOI 10.17487/RFC6126, April 2011, 242 . 244 [RFC7557] Chroboczek, J., "Extension Mechanism for the Babel Routing 245 Protocol", RFC 7557, DOI 10.17487/RFC7557, May 2015, 246 . 248 Authors' Addresses 250 Zheng(Sandy) Zhang 251 ZTE Corporation 252 No. 50 Software Ave, Yuhuatai Distinct 253 Nanjing 254 China 256 Email: zhang.zheng@zte.com.cn 258 Tony Przygienda 259 Juniper Networks 261 Email: prz@juniper.net