idnits 2.17.1 draft-hu-bier-bfd-02.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 (Oct 11, 2018) is 2024 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 185, but no explicit reference was found in the text == Unused Reference: 'RFC6328' is defined on line 189, but no explicit reference was found in the text == Unused Reference: 'ISO9577' is defined on line 211, but no explicit reference was found in the text == Outdated reference: A later version (-19) exists of draft-ietf-bfd-multipoint-18 == Outdated reference: A later version (-13) exists of draft-ietf-bier-ping-03 == Outdated reference: A later version (-10) exists of draft-ietf-bfd-multipoint-active-tail-09 Summary: 0 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER WG Fangwei Hu 3 Internet-Draft Greg Mirsky 4 Intended status: Standards Track Quan Xiong 5 Expires: April 14, 2019 ZTE Corporation 6 Chang Liu 7 China Unicom 8 Oct 11, 2018 10 BIER BFD 11 draft-hu-bier-bfd-02.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 April 14, 2019. 36 Copyright Notice 38 Copyright (c) 2018 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 . . . . . . . . . . . . . . 2 55 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 57 3. BIER BFD Encapsulation . . . . . . . . . . . . . . . . . . . 3 58 4. Bootstrapping BIER BFD . . . . . . . . . . . . . . . . . . . 3 59 5. Discriminators and Packet Demultiplexing . . . . . . . . . . 3 60 6. Security Considerations . . . . . . . . . . . . . . . . . . . 3 61 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 62 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 9.1. Normative References . . . . . . . . . . . . . . . . . . 4 65 9.2. Informative References . . . . . . . . . . . . . . . . . 5 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 68 1. Introduction 70 Bit Index Explicit Replication(BIER)[RFC8279] provides optimal 71 forwarding of multicast data packets through a multicast domain. It 72 does so without requiring any explicit tree-building protocol and 73 without requiring intermediate nodes to maintain any per-flow state. 75 [I-D.ietf-bfd-multipoint] defines a method of using Bidirectional 76 Detection(BFD) to monitor and detect unicast failures between the 77 sender (head) and one or more receivers (tails) in multipoint or 78 multicast networks. 80 This document describes the procedures for using such mode of BFD 81 protocol to verify multipoint or multicast connectivity between a 82 multipoint sender (the "head", Bit-Forwarding Ingress Routers(BFIRs)) 83 and a set of one or more multipoint receivers (the"tails", Bit- 84 Forwarding Egress Routers(BFERs)). The BIER BFD only supports the 85 unidirectional multicast. This document defines the use of BFD, as 86 defined in [I-D.ietf-bfd-multipoint], for BIER domain. Use of BFD 87 for multipoint networks active tail 88 [I-D.ietf-bfd-multipoint-active-tail] is for further study. 90 2. Conventions used in this document 91 2.1. Terminology 93 This document uses the acronyms defined in [RFC8279] along with the 94 following: 96 BFD: Bidirectional Forwarding Detection. 98 OAM: Operations, Administration, and Maintenance. 100 P2MP: Point to Multi-Point. 102 2.2. Requirements Language 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 106 "OPTIONAL" in this document are to be interpreted as described in BCP 107 14 [RFC2119] [RFC8174] when, and only when, they appear in all 108 capitals, as shown here. 110 3. BIER BFD Encapsulation 112 BIER BFD encapsulation uses the BIER OAM packet format defined in 113 [I-D.ietf-bier-ping]. The value of the Msg Type field MUST be set to 114 BIER BFD (TBD by IANA ). BFD Control packet, defined in Section 4 115 [RFC5880] immediately follows the BIER OAM header. 117 4. Bootstrapping BIER BFD 119 The BIER OAM ping could be used for BIER BFD bootstrap. The 120 multipoint header sends the BIER OAM packet with Target SI-Bitstring 121 TLV (section 3.3.2 of [I-D.ietf-bier-ping]) carrying the set of BFER 122 information (Sub-domain-id, Set ID, BS Len, Bitstring) to the 123 multipoint tails to bootstrap the BIER BFD sessions. 125 5. Discriminators and Packet Demultiplexing 127 The tail(BFER) demultiplexes incoming BFD packets based on a 128 combination of the source address and My discriminator as specified 129 in [I-D.ietf-bfd-multipoint]. The source address is BFIR-id and BIER 130 MPLS Label(MPLS network) or BFIR-id and BIFT-id(Non-MPLS network)for 131 BIER BFD. 133 6. Security Considerations 135 For BIER OAM packet procssing security considerations, see 136 [I-D.ietf-bier-ping]. 138 For general multipoint BFD security considerations, see 139 [I-D.ietf-bfd-multipoint]. 141 No additional security issues are raised in this document beyond 142 those that exist in the referenced BFD documents. 144 7. Acknowledgements 146 Authors would like to thank the comments and suggestions from Jeffrey 147 (Zhaohui) Zhang, Donald Eastlake 3rd. 149 8. IANA Considerations 151 IANA is requested to assign new type from the BIER OAM Message Type 152 registry as follows: 154 +--------+--------------+------------------+ 155 | Value | Description | Reference | 156 +--------+--------------+------------------+ 157 | TBD | BIER BFD | [this document] | 158 +--------+--------------+------------------+ 160 Table 1 162 9. References 164 9.1. Normative References 166 [I-D.ietf-bfd-multipoint] 167 Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD for 168 Multipoint Networks", draft-ietf-bfd-multipoint-18 (work 169 in progress), June 2018. 171 [I-D.ietf-bier-ping] 172 Kumar, N., Pignataro, C., Akiya, N., Zheng, L., Chen, M., 173 and G. Mirsky, "BIER Ping and Trace", draft-ietf-bier- 174 ping-03 (work in progress), January 2018. 176 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 177 Requirement Levels", BCP 14, RFC 2119, 178 DOI 10.17487/RFC2119, March 1997, 179 . 181 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 182 (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, 183 . 185 [RFC6213] Hopps, C. and L. Ginsberg, "IS-IS BFD-Enabled TLV", 186 RFC 6213, DOI 10.17487/RFC6213, April 2011, 187 . 189 [RFC6328] Eastlake 3rd, D., "IANA Considerations for Network Layer 190 Protocol Identifiers", BCP 164, RFC 6328, 191 DOI 10.17487/RFC6328, July 2011, 192 . 194 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 195 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 196 May 2017, . 198 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 199 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 200 Explicit Replication (BIER)", RFC 8279, 201 DOI 10.17487/RFC8279, November 2017, 202 . 204 9.2. Informative References 206 [I-D.ietf-bfd-multipoint-active-tail] 207 Katz, D., Ward, D., Networks, J., and G. Mirsky, "BFD 208 Multipoint Active Tails.", draft-ietf-bfd-multipoint- 209 active-tail-09 (work in progress), June 2018. 211 [ISO9577] ISO/IEC TR 9577:1999,, "International Organization for 212 Standardization "Information technology - 213 Telecommunications and Information exchange between 214 systems - Protocol identification in the network layer"", 215 1999. 217 Authors' Addresses 219 Fangwei Hu 220 ZTE Corporation 221 No.889 Bibo Rd 222 Shanghai 201203 223 China 225 Phone: +86 21 68896273 226 Email: hu.fangwei@zte.com.cn 227 Greg Mirsky 228 ZTE Corporation 229 USA 231 Email: gregimirsky@gmail.com 233 Quan Xiong 234 ZTE Corporation 235 No.6 Huashi Park Rd 236 Wuhan, Hubei 430223 237 China 239 Phone: +86 27 83531060 240 Email: xiong.quan@zte.com.cn 242 Chang Liu 243 China Unicom 244 No.9 Shouti Nanlu 245 Beijing 100048 246 China 248 Phone: +86-010-68799999-7294 249 Email: liuc131@chinaunicom.cn