idnits 2.17.1 draft-zhang-bier-babel-extensions-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 : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** 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 109: '...TLV. The prefix MUST NOT be summarize...' RFC 2119 keyword, line 110: '... TLV MUST be treated as optional and...' RFC 2119 keyword, line 125: '... 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 (October 30, 2016) is 2733 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) == Unused Reference: 'I-D.pfister-bier-over-ipv6' is defined on line 218, but no explicit reference was found in the text == Outdated reference: A later version (-20) exists of draft-ietf-babel-rfc6126bis-00 == Outdated reference: A later version (-08) exists of draft-ietf-bier-architecture-05 == Outdated reference: A later version (-11) exists of draft-ietf-bier-isis-extensions-03 == Outdated reference: A later version (-12) exists of draft-ietf-bier-mpls-encapsulation-05 == Outdated reference: A later version (-18) exists of draft-ietf-bier-ospf-bier-extensions-04 == Outdated reference: A later version (-01) exists of draft-pfister-bier-over-ipv6-00 ** Obsolete normative reference: RFC 6126 (Obsoleted by RFC 8966) ** Obsolete normative reference: RFC 7557 (Obsoleted by RFC 8966) Summary: 4 errors (**), 0 flaws (~~), 8 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: May 3, 2017 Juniper Networks 6 October 30, 2016 8 BIER in BABEL 9 draft-zhang-bier-babel-extensions-00 11 Abstract 13 BIER introduces a novel architecture for multicast packet forwarding. 14 It does not require a signalling protocol to explicitly build 15 multicast distribution trees, nor does it require intermediate nodes 16 to maintain any per-flow state. 18 Babel defines a distance-vector routing protocol that operates in a 19 robust and efficient fashion both in ordinary wired as well as in 20 wireless mesh networks. This document defines a way to carry BIER 21 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 May 3, 2017. 40 Copyright Notice 42 Copyright (c) 2016 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 . . . . . . . . . . . . . . 3 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. Security Considerations . . . . . . . . . . . . . . . . . . . 4 65 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 66 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 69 1. Introduction 71 [I-D.ietf-bier-architecture] introduces a novel architecture for 72 multicast data packets forwarding. It does not require a signalling 73 protocol to explicitly build multicast distribution trees, nor does 74 it require intermediate nodes to maintain any per-flow state. All 75 the necessary extensions to perform this functionality are 76 abbreviated by the "BIER architecture" moniker. 78 BIER information can be carried in OSPF and ISIS routing protocol as 79 defined in [I-D.ietf-bier-isis-extensions] and 80 [I-D.ietf-bier-ospf-bier-extensions] respectively. The according 81 tables for BIER forwarding purposes are built when OSPF/ISIS performs 82 according calculations on the advertised information. 84 [RFC6126] and [I-D.ietf-babel-rfc6126bis] define a distance-vector 85 routing protocol under the name of "Babel". Babel operates in a 86 robust and efficient fashion both in ordinary wired as well as in 87 wireless mesh networks. 89 2. Terminology 91 The terminology of this documents follows 92 [I-D.ietf-bier-architecture], [RFC6126], [RFC7557] and 93 [I-D.ietf-babel-rfc6126bis]. 95 3. Advertisement of BIER information 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 [RFC6126]. Several new sub-TLVs and sub-sub-TLVs are defined to 101 convey further BIER information such as BFR-id, sub-domain-id and 102 BSL. 104 3.1.1. BIER sub-TLV 106 The BIER sub-TLV format aligns exactly with the definition and 107 restrictions in [I-D.ietf-bier-isis-extensions] and 108 [I-D.ietf-bier-ospf-bier-extensions]. It is a sub-TLV of Babel 109 update TLV. The prefix MUST NOT be summarized and the according sub- 110 TLV MUST be treated as optional and transitive. 112 0 1 2 3 113 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 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | sub-Type | Length | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | Reserved | subdomain-id | BFR-id | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 Figure 1: BIER sub-TLV 121 o Type: as indicated in IANA section. 123 o Length: 1 octet 125 o Reserved: MUST be 0 on transmission, ignored on reception. May be 126 used in future versions. 8 bits. 128 o subdomain-id: Unique value identifying the BIER sub-domain. 1 129 octet. 131 o BFR-id: A 2 octet field encoding the BFR-id, as documented in 132 [I-D.ietf-bier-architecture]. If no BFR-id has been assigned this 133 field is set to the invalid BFR-id. 135 3.2. BIER MPLS Encapsulation sub-sub-TLV 137 The BIER MPLS Encapsulation sub-sub-TLV can be carried by BIER sub- 138 TLV. The format and restrictions are aligned with 139 [I-D.ietf-bier-isis-extensions] and 140 [I-D.ietf-bier-ospf-bier-extensions]. This sub-sub-TLV carries the 141 information for the BIER MPLS encapsulation including the label range 142 for a specific BSL for a certain pair. 144 0 1 2 3 145 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 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | sub-sub-Type | Length | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | Lbl Range Size|BS Len | Label | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 Figure 3: MPLS Encapsulation sub-sub-TLV 153 o Type: value of 1 indicating MPLS encapsulation. 155 o Length: 1 octet 157 o Local BitString Length (BS Len): Encoded bitstring length as per 158 [I- D.draft-ietf-bier-mpls-encapsulation-05]. 4 bits. 160 o Label Range Size: Number of labels in the range used on 161 encapsulation for this BIER sub-domain for this bitstring length, 162 1 octet. 164 o Label: First label of the range, 20 bits. The labels are as 165 defined in [I-D.ietf-bier-mpls-encapsulation]. 167 3.3. Optional BIER sub-domain BSL conversion sub-sub-TLV 169 This sub-sub-TLV is used to carry the BSL information. Its 170 definition and restrictions are aligned with 171 [I-D.ietf-bier-isis-extensions]. 173 0 1 2 3 174 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 175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 176 | sub-sub-Type | Length | 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 Figure 4: BSL conversion sub-sub-TLV 180 4. Security Considerations 182 TBD 184 5. Acknowledgements 186 The draft is aligned with the [I-D.ietf-bier-isis-extensions] and 187 [I-D.ietf-bier-ospf-bier-extensions] as far as feasible. 189 6. Normative References 191 [I-D.ietf-babel-rfc6126bis] 192 Chroboczek, J., "The Babel Routing Protocol", draft-ietf- 193 babel-rfc6126bis-00 (work in progress), August 2016. 195 [I-D.ietf-bier-architecture] 196 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 197 S. Aldrin, "Multicast using Bit Index Explicit 198 Replication", draft-ietf-bier-architecture-05 (work in 199 progress), October 2016. 201 [I-D.ietf-bier-isis-extensions] 202 Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang, 203 "BIER support via ISIS", draft-ietf-bier-isis- 204 extensions-03 (work in progress), September 2016. 206 [I-D.ietf-bier-mpls-encapsulation] 207 Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., 208 Aldrin, S., and I. Meilik, "Encapsulation for Bit Index 209 Explicit Replication in MPLS Networks", draft-ietf-bier- 210 mpls-encapsulation-05 (work in progress), July 2016. 212 [I-D.ietf-bier-ospf-bier-extensions] 213 Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., 214 Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions 215 for BIER", draft-ietf-bier-ospf-bier-extensions-04 (work 216 in progress), September 2016. 218 [I-D.pfister-bier-over-ipv6] 219 Pfister, P. and I. Wijnands, "An IPv6 based BIER Routing 220 Underlay", draft-pfister-bier-over-ipv6-00 (work in 221 progress), September 2016. 223 [RFC6126] Chroboczek, J., "The Babel Routing Protocol", RFC 6126, 224 DOI 10.17487/RFC6126, April 2011, 225 . 227 [RFC7557] Chroboczek, J., "Extension Mechanism for the Babel Routing 228 Protocol", RFC 7557, DOI 10.17487/RFC7557, May 2015, 229 . 231 Authors' Addresses 232 Zheng(Sandy) Zhang 233 ZTE Corporation 234 No. 50 Software Ave, Yuhuatai Distinct 235 Nanjing 236 China 238 Email: zhang.zheng@zte.com.cn 240 Tony Przygienda 241 Juniper Networks 243 Email: prz@juniper.net