idnits 2.17.1 draft-hu-bier-bfd-03.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 (March 1, 2019) is 1883 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: 'RFC6213' is defined on line 294, but no explicit reference was found in the text == Unused Reference: 'RFC6328' is defined on line 298, but no explicit reference was found in the text == Unused Reference: 'ISO9577' is defined on line 320, but no explicit reference was found in the text == Outdated reference: A later version (-13) exists of draft-ietf-bier-ping-04 == Outdated reference: A later version (-02) exists of draft-xiong-bier-resilience-01 ** Downref: Normative reference to an Informational draft: draft-xiong-bier-resilience (ref. 'I-D.xiong-bier-resilience') Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER WG Quan Xiong 3 Internet-Draft Greg Mirsky 4 Intended status: Standards Track Fangwei Hu 5 Expires: September 2, 2019 ZTE Corporation 6 Chang Liu 7 China Unicom 8 March 1, 2019 10 BIER BFD 11 draft-hu-bier-bfd-03.txt 13 Abstract 15 Point to multipoint (P2MP) BFD is designed to verify multipoint 16 connectivity. This document specifies the application of P2MP BFD in 17 BIER network. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on September 2, 2019. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Conventions used in this document . . . . . . . . . . . . . . 3 55 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 57 3. BIER BFD Encapsulation . . . . . . . . . . . . . . . . . . . 3 58 4. Bootstrapping BIER BFD . . . . . . . . . . . . . . . . . . . 3 59 4.1. BIER OAM Ping Bootstrap . . . . . . . . . . . . . . . . . 3 60 4.2. IGP protocol Bootstrap . . . . . . . . . . . . . . . . . 4 61 4.2.1. IS-IS extension for BIER BFD . . . . . . . . . . . . 4 62 4.2.2. OSPF extension for BIER BFD . . . . . . . . . . . . . 5 63 5. Discriminators and Packet Demultiplexing . . . . . . . . . . 5 64 6. Active Tail in BIER BFD . . . . . . . . . . . . . . . . . . . 5 65 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 66 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 67 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 68 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 10.1. Normative References . . . . . . . . . . . . . . . . . . 6 70 10.2. Informative References . . . . . . . . . . . . . . . . . 7 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 73 1. Introduction 75 Bit Index Explicit Replication (BIER) [RFC8279] provides optimal 76 forwarding of multicast data packets through a multicast domain. It 77 does so without requiring any explicit tree-building protocol and 78 without requiring intermediate nodes to maintain any per-flow state. 79 BIER resilience use cases are described in 80 [I-D.xiong-bier-resilience] including End-to-End 1+1 and 1:1 81 Protection and the failure detection mechanisms MAY use P2MP BFD and 82 P2MP active tail detection method respectively. 84 [I-D.ietf-bfd-multipoint] defines a method of using Bidirectional 85 Forwarding Detection(BFD) to monitor and detect unicast failures 86 between the sender (head) and one or more receivers (tails) in 87 multipoint or multicast networks. 88 [I-D.ietf-bfd-multipoint-active-tail] describes active tail 89 extensions to the BFD protocol for multipoint networks. 91 This document describes the procedures for using such mode of BFD 92 protocol to verify multipoint or multicast connectivity between a 93 multipoint sender (the "head", Bit-Forwarding Ingress Routers(BFIRs)) 94 and a set of one or more multipoint receivers (the"tails", Bit- 95 Forwarding Egress Routers(BFERs)). The BIER BFD only supports the 96 unidirectional multicast. This document defines the use of P2MP BFD 97 as per [I-D.ietf-bfd-multipoint], and active tail as per 98 [I-D.ietf-bfd-multipoint-active-tail] for BIER-specific domain. 100 2. Conventions used in this document 102 2.1. Terminology 104 This document uses the acronyms defined in [RFC8279] along with the 105 following: 107 BFD: Bidirectional Forwarding Detection. 109 OAM: Operations, Administration, and Maintenance. 111 P2MP: Point to Multi-Point. 113 2.2. Requirements Language 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 117 "OPTIONAL" in this document are to be interpreted as described in BCP 118 14 [RFC2119] [RFC8174] when, and only when, they appear in all 119 capitals, as shown here. 121 3. BIER BFD Encapsulation 123 BIER BFD encapsulation uses the BIER OAM packet format defined in 124 [I-D.ietf-bier-ping]. The value of the Msg Type field MUST be set to 125 BIER BFD (TBD1 by IANA ). BFD Control packet, defined in Section 4 126 [RFC5880] immediately follows the BIER OAM header. 128 4. Bootstrapping BIER BFD 130 4.1. BIER OAM Ping Bootstrap 132 The BIER OAM ping could be used for BIER BFD bootstrap. The BFIR 133 sends the BIER OAM ping Echo request messages carring a BFD 134 discriminator TLV which immediately follows the Target SI-Bitstring 135 TLV (section 3.3.2 [I-D.ietf-bier-ping]) which MUST be included to 136 carry the set of BFER information (Sub-domain-id, Set ID, BS Len, 137 Bitstring) for the purpose of session establishment. 139 The BFD discriminator TLV is a new TLV for BIER OAM TLV with the type 140 (TBD2 by IANA) and the length of 4. The value contains the 4-byte 141 local discriminator generated by BFIR for this session. 143 4.2. IGP protocol Bootstrap 145 An alternative option to bootstrap the BIER BFD is to advertise the 146 BFD information IGP protocol in control plane. This document defines 147 a new BIER BFD Sub-TLV carried in IS-IS and OSPF capaibility to 148 advertise My Discriminator for BFIR. 150 4.2.1. IS-IS extension for BIER BFD 152 The new BIER BFD Sub-TLV is carried in the ISIS router capaiblity 153 TLV. The format is as follows. 155 0 1 2 3 156 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 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | Type | Length | 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | My Discriminator | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | RESERVED | BIFT-id | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | BitString (first 32 bits) ~ 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 ~ ~ 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 ~ BitString (last 32 bits) | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 Figure 1: BIER BFD Sub-TLV for IS-IS extension 173 Type : TBD3 by IANA. 175 Length : Length of the BIER BFD Sub-TLV for IS-IS extension, in 176 bytes. 178 My Discriminator : A unique, nonzero discriminator value generated by 179 BFIR for each multipoint path. 181 The BitString field carries the set of BFR-IDs of BFER(s) that the 182 BFIR expects to establish BIER BFD session. 184 The BIFT-id represents a particular Bit Index Forwarding Table (BIFT) 185 as per [RFC8279]. 187 4.2.2. OSPF extension for BIER BFD 189 The new BIER BFD Sub-TLV is carried in the Router Information Link 190 State Advertisement (LSA). The format is as follows. 192 0 1 2 3 193 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 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Type | Length | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | My Discriminator | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | RESERVED | BIFT-id | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | BitString (first 32 bits) ~ 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 ~ ~ 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 ~ BitString (last 32 bits) | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 208 Figure 2: BIER BFD Sub-TLV for OSPF extension 210 Type : TBD4 by IANA. 212 Length : Length of the BIER BFD Sub-TLV for OSPF extension, in bytes. 214 Other fields in BIER BFD Sub-TLV is the same with section 4.2.1. 216 5. Discriminators and Packet Demultiplexing 218 The tail(BFER) demultiplexes incoming BFD packets based on a 219 combination of the source address and My discriminator as specified 220 in [I-D.ietf-bfd-multipoint]. The source address is BFIR-id and BIER 221 MPLS Label (MPLS network) or BFIR-id and BIFT-id (Non-MPLS network) 222 for BIER BFD. 224 6. Active Tail in BIER BFD 226 [I-D.ietf-bfd-multipoint-active-tail] defined an extension for 227 Multipoint BFD, which allows tails to notify the head of the lack of 228 multipoint connectivity. For BIER BFD in active tail mode, the BFIR 229 may learn the state and connectivity of the BFERs. As per 230 [I-D.ietf-bfd-multipoint-active-tail], the BFIR can send the Poll 231 sequence messages in combination with the unicast BFD over the 232 monitored BFERs. 234 7. Security Considerations 236 For BIER OAM packet procssing security considerations, see 237 [I-D.ietf-bier-ping]. 239 For general multipoint BFD security considerations, see 240 [I-D.ietf-bfd-multipoint]. 242 No additional security issues are raised in this document beyond 243 those that exist in the referenced BFD documents. 245 8. Acknowledgements 247 Authors would like to thank the comments and suggestions from Jeffrey 248 (Zhaohui) Zhang, Donald Eastlake 3rd. 250 9. IANA Considerations 252 IANA is requested to assign new type from the BIER OAM Message Type 253 registry as follows: 255 +--------+-----------------------------+------------------+ 256 | Value | Description | Reference | 257 +--------+-----------------------------+------------------+ 258 | TBD1 | BIER BFD | [this document] | 259 | TBD2 | BFD discriminator TLV | [this document] | 260 | TBD3 | BIER BFD Sub-TLV for IS-IS | [this document] | 261 | TBD4 | BIER BFD Sub-TLV for OSPF | [this document] | 262 +--------+-----------------------------+------------------+ 264 Table 1 266 10. References 268 10.1. Normative References 270 [I-D.ietf-bfd-multipoint] 271 Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD for 272 Multipoint Networks", draft-ietf-bfd-multipoint-19 (work 273 in progress), December 2018. 275 [I-D.ietf-bier-ping] 276 Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M., 277 and G. Mirsky, "BIER Ping and Trace", draft-ietf-bier- 278 ping-04 (work in progress), October 2018. 280 [I-D.xiong-bier-resilience] 281 Xiong, Q., hu, f., and G. Mirsky, "The Resilience for 282 BIER", draft-xiong-bier-resilience-01 (work in progress), 283 October 2018. 285 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 286 Requirement Levels", BCP 14, RFC 2119, 287 DOI 10.17487/RFC2119, March 1997, 288 . 290 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 291 (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, 292 . 294 [RFC6213] Hopps, C. and L. Ginsberg, "IS-IS BFD-Enabled TLV", 295 RFC 6213, DOI 10.17487/RFC6213, April 2011, 296 . 298 [RFC6328] Eastlake 3rd, D., "IANA Considerations for Network Layer 299 Protocol Identifiers", BCP 164, RFC 6328, 300 DOI 10.17487/RFC6328, July 2011, 301 . 303 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 304 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 305 May 2017, . 307 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 308 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 309 Explicit Replication (BIER)", RFC 8279, 310 DOI 10.17487/RFC8279, November 2017, 311 . 313 10.2. Informative References 315 [I-D.ietf-bfd-multipoint-active-tail] 316 Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD 317 Multipoint Active Tails.", draft-ietf-bfd-multipoint- 318 active-tail-10 (work in progress), November 2018. 320 [ISO9577] ISO/IEC TR 9577:1999,, "International Organization for 321 Standardization "Information technology - 322 Telecommunications and Information exchange between 323 systems - Protocol identification in the network layer"", 324 1999. 326 Authors' Addresses 328 Quan Xiong 329 ZTE Corporation 330 No.6 Huashi Park Rd 331 Wuhan, Hubei 430223 332 China 334 Phone: +86 27 83531060 335 Email: xiong.quan@zte.com.cn 337 Greg Mirsky 338 ZTE Corporation 339 USA 341 Email: gregimirsky@gmail.com 343 Fangwei Hu 344 ZTE Corporation 345 No.889 Bibo Rd 346 Shanghai 201203 347 China 349 Phone: +86 21 68896273 350 Email: hu.fangwei@zte.com.cn 352 Chang Liu 353 China Unicom 354 No.9 Shouti Nanlu 355 Beijing 100048 356 China 358 Phone: +86-010-68799999-7294 359 Email: liuc131@chinaunicom.cn