idnits 2.17.1 draft-hu-bier-multicast-group-information-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 (November 4, 2015) is 3089 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 == Outdated reference: A later version (-12) exists of draft-ietf-bier-mpls-encapsulation-02 Summary: 0 errors (**), 0 flaws (~~), 3 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 Ran. Chen 4 Intended status: Standards Track ZTE Corporation 5 Expires: May 7, 2016 November 4, 2015 7 BIER Multicast Group Information 8 draft-hu-bier-multicast-group-information-00.txt 10 Abstract 12 This draft proposes to solve the multicast group address 13 announcement. The multicast group address information is 14 encapsulated as the BIER data payload. A new TLV is defined in this 15 document to carry the multicast group address information. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on May 7, 2016. 34 Copyright Notice 36 Copyright (c) 2015 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Multicast Group Address Announcement Mechanism . . . . . . . 2 53 3. BIER-GROUP-ADDRESS LV . . . . . . . . . . . . . . . . . . . . 3 54 4. ISIS Extension . . . . . . . . . . . . . . . . . . . . . . . 4 55 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 56 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 57 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 58 8. Normative References . . . . . . . . . . . . . . . . . . . . 5 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 61 1. Introduction 63 Bit Index Explicit Replication (BIER)[I-D.ietf-bier-architecture] 64 proposes an architecture that provides optimal multicast forwarding 65 through a "BIER domain" without requiring intermediate routers to 66 maintain any multicast related per-flow state. BIER also does not 67 require any explicit tree-building protocol for its operation. BIER 68 accomplishes this by addressing each of the targeted egress router in 69 a bit mask in the BIER header. A multicast data packet enters a BIER 70 domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the 71 BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs) . 72 The BIER header is encapsulated in the BFIR and decapsulated in the 73 BFER. Each BIER Forwarding Router (BFR) is assigned and uniquely 74 identified by a BFR-prefix which is a routable ipv4 or ipv6 address. 75 Each BIER egress (BFER) router needs a BFR-Identifier (1..65535) in 76 addition to BFR-prefix. To accomplish forwarding in a BIER network, 77 ingress router needs to know the list of egress routers to which the 78 flow is supposed be multicasted. 80 This document proposes a method to solve the issue. The ISIS or OSPF 81 protocol is extended for a BFER to announce its supported multicast 82 group address. A new TLV (BIER-GROUP-ADDRESS TLV) is defined to 83 carry the multicast group address for a BFER and encapsulated as the 84 BIER data payload. When BFER receives a new multicast group through 85 IGMP/MLD protocol, it sends the BIER data payload with the new 86 multicast group address information to all the other edge BFRs to 87 announce this new multicast group information in the BIER domain. 89 2. Multicast Group Address Announcement Mechanism 91 In order to improve the IGP (ISIS or OSPF protocol) stability, the 92 multicast group address information is encapsulated and carried as 93 the BIER data payload rather than IGP protocol directly. The 94 protocol field in in the MPLS BIER header 95 encapsulation[I-D.ietf-bier-mpls-encapsulation] is coded (7, to be 96 assigned by IANA) to indicated that the payload is the multicast 97 group address information. The structure is as following (take the 98 MPLS encapsulation as the example): 100 +-----------+-----------+-----------------------------------+ 101 |MPLS header|BIER header|Multicast group address information| 102 +-----------+-----------+-----------------------------------+ 103 Figure 1 Mutlicast Group Address Information Encapsulation 105 The multicast group address information is formatted as TLV (section 106 3) and filled in LSP or LSA in the BFER. The BFER sends the BIER 107 data payload with the multicast group address information to all the 108 other edge BFRs in the BIER domain. When the BFIR receives the 109 multicast group address information, it keeps and maintains the 110 multicast group and BFR-prefix entries in the local, which is to 111 guide the multicast flow forwarding. 113 3. BIER-GROUP-ADDRESS LV 115 The format of BIER-GROUP-ADDRESS TLV is specified in figure 2. 117 +--------------+ 118 | Type | 119 +--------------+--------------+ 120 | Length | 121 +-----------------------------+-------------------------------------+ 122 |Res|mutlicast group address type|Number of multicast Group address | 123 +-------------------------------------------------------------------+ 124 | Multicast Group address (1) | 125 +-------------------------------------------------------------------+ 126 | ... | 127 +-------------------------------------------------------------------+ 128 | Multicast Group address (i) | 129 +-------------------------------------------------------------------+ 130 | Multicast Group address (n) | 131 +-------------------------------------------------------------------+ 132 Figure 2 BIER-GROUP-ADDRESS TLV 134 The description for each field is as following: 136 Type: 8 bits. 138 Length: 16 bits, the whole length for this tlv. 140 Res: 8 bits, it is reserved for future use. 142 Multicast Group address type: 8 bits, it indicates the type for 143 the multicast group address. If it is 1, the multicast group 144 address is IPv4 address, while if 2, the multicast group address 145 is IPv6 address. 147 Number of multicast group address: 16 bits, the number for the 148 multicast group address. 150 Multicast Group address[i]: the multicast group addresses for the 151 BFER to be announced. 153 4. ISIS Extension 155 If the IGP is ISIS protocol in the BIER domain, the detailed format 156 of Mutlicast Group Address Information is as figure 3. 158 The label is MPLS-BIER label, and the S filed is 1(the end of the 159 MPLS stack) in the MPLS header. 161 All the Bitstring fields in the BEIR header is All-Edge-BFRs 162 (0xFFFF). The protocol fields is 7(to be assigned by IANA) to 163 indicate that that the payload of BIER is the multicast group 164 information payload. The multicast group information payload is 165 formatted as ISIS protocol. The multicast group information TLV is 166 filled in the ISIS LSP. We named this ISIS LSP as MGAA-LSP 167 (Multicast Group Address Announcement) to difference with the common 168 ISIS LSP. While the flooding and synchronization mechanism is 169 similar with the common ISIS LSP. 171 MPLS header 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | Label | Cos |S| TTL | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 176 BIER header 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 |0 1 0 1| Ver | Len | Entropy | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | BitString (first 32 bits) ~ 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 ~ ~ 185 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 ~ BitString (last 32 bits) | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 |OAM| Reserved |Proto=7| BFIR-id | 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 191 Multicast Group address payload(Formated as ISIS) 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | IS-IS Common Header, IS-IS PDU Specific Fields, IS-IS TLVs | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 Figure 3 Multicast Group Address Format 197 All the transit BFR forward MGAA packet as if they were ordinary BIER 198 data packet. All the edge BFRs (BFERs and BFIRs) supporting 199 multicast group address announcement are full mesh logically. 201 5. Security Considerations 203 TBD. 205 6. Acknowledgements 207 TBD. 209 7. IANA Considerations 211 TBD. 213 8. Normative References 215 [I-D.ietf-bier-architecture] 216 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 217 S. Aldrin, "Multicast using Bit Index Explicit 218 Replication", draft-ietf-bier-architecture-02 (work in 219 progress), July 2015. 221 [I-D.ietf-bier-mpls-encapsulation] 222 Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., and 223 S. Aldrin, "Encapsulation for Bit Index Explicit 224 Replication in MPLS Networks", draft-ietf-bier-mpls- 225 encapsulation-02 (work in progress), August 2015. 227 Authors' Addresses 229 Fangwei Hu 230 ZTE Corporation 231 No.889 Bibo Rd 232 Shanghai 201203 233 China 235 Phone: +86 21 68896273 236 Email: hu.fangwei@zte.com.cn 238 Ran Chen 239 ZTE Corporation 240 No.50 Software Avenue,Yuhuatai District 241 Nanjing, Jiangsu Province 210012 242 China 244 Phone: +86 025 88014636 245 Email: chen.ran@zte.com.cn