idnits 2.17.1 draft-yong-isis-ext-4-distribution-tree-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 : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 9 characters in excess of 72. ** The abstract seems to contain references ([IGP-MCAST]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 27, 2014) is 3462 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) -- No information found for draft-yong-rtgwg-igp-mutlicast-arch - is the name correct? Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group L. Yong 2 Internet Draft W. Hao 3 D. Eastlake 4 Category: Standard Track Huawei 5 A. Qu 6 MetiaTek 7 J. Hudson 8 Brocade 9 U. Chunduri 10 Ericsson 12 Expires: April 2015 October 27, 2014 14 IS-IS Protocol Extension For Building Distribution Trees 15 draft-yong-isis-ext-4-distribution-tree-03 17 Abstract 19 This document proposes an IS-IS protocol extension to support IGP 20 based multicast transport architecture and solution [IGP-MCAST]. 22 Status of this document 24 This Internet-Draft is submitted to IETF in full conformance with 25 the provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF), its areas, and its working groups. Note that 29 other groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six 33 months and may be updated, replaced, or obsoleted by other documents 34 at any time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt. 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 This Internet-Draft will expire on April 27, 2015. 45 Copyright Notice 47 Copyright (c) 2014 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with 55 respect to this document. 57 Table of Contents 59 1. Introduction...................................................3 60 1.1. Conventions used in this document.........................3 61 2. IS-IS Protocol Extension.......................................3 62 2.1. RTADDR sub-TLV............................................3 63 2.2. RTADDRV6 sub-TLV..........................................5 64 2.3. The Group Address Sub-TLV.................................6 65 3. Security Considerations........................................7 66 4. IANA Considerations............................................7 67 5. Acknowledgements...............................................7 68 6. References.....................................................7 69 6.1. Normative References......................................7 70 6.2. Informative References....................................7 72 1. Introduction 74 This document proposes an IS-IS protocol extension to support IGP 75 based multicast transport architecture and solution [IGP-MCAST]. 77 1.1. Conventions used in this document 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 81 document are to be interpreted as described in RFC-2119 [RFC2119]. 83 2. IS-IS Protocol Extension 85 2.1. RTADDR sub-TLV 87 This is a sub-TLV that is used in either a Router Capabilities TLV 88 or an MT Capabilities TLV. Each RTADDR sub-TLV contains a root IPv4 89 address and multicast group addresses that associate to the tree. A 90 router may use multiple RTADDR sub-TLVs to announce multiple root 91 addresses and associated multicast groups with each root. RTADDR 92 sub-TLV format is below. 94 +-+-+-+-+-+-+-+-+ 95 |subType=RTADDR | (1 byte) 96 +-+-+-+-+-+-+-+-+ 97 | Length | (1 byte) 98 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 99 | Root IPv4 Address | 100 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 101 |S|D|RESV | (1 byte) 102 +-+-+-+-+-+-+-+-+ 103 | Tree Priority | (1 byte) 104 +-+-+-+-+-+-+-+-+ 105 |Num of Groups | (1 byte) 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | Group Address (1) | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | Group Mask (1) | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 ~ ~ 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | GROUP Address (N) | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 115 | Group Mask (N) | 116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 118 Where: 120 subType: RTADDR (TBD) 122 Length: variable depending on the number of associated groups 124 Root IPv4 Address: IPv4 Address for a router that is a tree root 126 S bit: When set, the rooted tree for single area only. Otherwise, 127 the rooted tree crosses multiple areas. 129 D bit: When set, the tree root is as of default tree root. 130 Otherwise, the default tree is auto-calculated. [IGP-MCAST] When 131 clear, the tree root is another distribution tree beside the 132 default tree. 134 RESV: 6 reserved bits. MUST be sent as zero and ignored on receipt. 136 Tree Priority: An eight bit unsigned integer where larger 137 magnitude means higher priority. Zero means no priority. 139 Num of Groups: the number of group addresses. When D bit sets, the 140 number of group addresses is 0, which means that indicated tree root 141 is the default tree root (supersede the auto-calculate one). 143 Group Address: IPv4 Address for the group 145 Group Mask: Group Mask: multicast groups mask. If the mask bit is a one, the 146 Group Address bit must match that corresponding bit in the packet destination 147 address to be associated with the tree whose root is given. 149 One router may be the root for multiple trees. Each tree associates 150 to a set of multicast groups. In this case, a router encodes 151 multiple RTADDR sub-TLVs to announce root addresses, one for each 152 root, in either a Router Capabilities TLV or an MT Capabilities TLV. 153 The group address/mask in different sub-TLVs can overlap. See [IGP- 154 MCAST] for details. 156 2.2. RTADDRV6 sub-TLV 158 This sub-TLV is used in an IPv6 network. It has the same format and 159 usage except that the addresses are in IPv6. 161 +-+-+-+-+-+-+-+-+ 162 |subTyp=RTADDRV6| (1 byte) 163 +-+-+-+-+-+-+-+-+ 164 | Length | (1 byte) 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | | 167 + + 168 | | 169 + Root IPv6 Address + 170 | | 171 + + 172 | | 173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 |S|D|RESV | (1 byte) 175 +-+-+-+-+-+-+-+-+ 176 | Tree Priority | (1 byte) 177 +-+-+-+-+-+-+-+-+ 178 |Num of Groups | (1 byte) 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | | 181 + + 182 | | 183 + Group IPv6 Address (1) + 184 | | 185 + + 186 | | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 | | 189 + + 190 | | 191 + MASK(1) + 192 | | 193 + + 194 | | 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 ~ ~ 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 2.3. The Group Address Sub-TLV 201 The Group Address TLV and a set of Group Address sub-TLVs are 202 defined in RFC 7176 [RFC7176]. The GIP-ADDR and GIPV6-ADDR sub-TLVs 203 are used in this solution. An edge router uses the GIP-ADDR sub-TLV 204 or GIPV6-ADDR to announce its interested multicast groups. The GIP- 205 ADDR sub-TLV applies to an IPv4 network and GIPV6-ADDR sub-TLV for 206 IPv6 network. 208 When using a GIP-ADDR or GIPV6-ADDR sub-TLV for IGP multicast, the 209 field VLAN-ID MUST set to zero and be ignored. Other field usage 210 remains the same as [RFC7176] 212 3. Security Considerations 214 See Security Considerations in [IGP-MCAST]. 216 4. IANA Considerations 218 IANA is requested to assign two new sub-TLV numbers for RTADDR and 219 RTADDRV6 as specified in Sections 2.1 and 2.2. These sub-TLVs can be 220 used under both the Router Capability (#242) and MT Capability (#144) 221 TLVs. To avoid confusion, each sub-TLV should be assigned the same 222 sub-Type number under each of these two TLVs. 224 5. Acknowledgements 226 Authors like to thank Mike McBride and Linda Dunbar for their 227 valuable inputs. 229 [Editor note: the previous draft has been split into two drafts: 230 draft-yong-isis-ext-4-distribution-tree-03 and draft-yong-rtgwg-igp- 231 multicast-arch-00 based on AD and chair's suggestion.] 233 6. References 235 6.1. Normative References 237 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 238 Requirement Levels", BCP 14, RFC2119, March 1997. 240 [RFC7176] Eastlake 3rd, D., Senevirathne, T., Ghanwani, A., Dutt, 241 D., and A. Banerjee, "Transparent Interconnection of Lots 242 of Links (TRILL) Use of IS-IS", RFC 7176, May 2014. 244 6.2. Informative References 246 [IGP-MCAST] Yong, L., Hao, W., Eastlake, D., Qu A., Hudson, J., and 247 Chunduri, "IGP Multicast Architecture", draft-yong-rtgwg-igp- 248 mutlicast-arch-00, work in progress. 250 Authors' Addresses 252 Lucy Yong 253 Huawei USA 255 Phone: 918-808-1918 256 Email: lucy.yong@huawei.com 258 Weiguo Hao 259 Huawei Technologies 260 101 Software Avenue, 261 Nanjing 210012 262 China 264 Phone: +86-25-56623144 265 Email: haoweiguo@huawei.com 267 Donald Eastlake 268 Huawei 269 155 Beaver Street 270 Milford, MA 01757 USA 272 Phone: +1-508-333-2270 273 EMail: d3e3e3@gmail.com 275 Andrew Qu 276 MediaTek 277 San Jose, CA 95134 USA 279 Email: laodulaodu@gmail.com 281 Jon Hudson 282 Brocade 283 130 Holger Way 284 San Jose, CA 95134 USA 286 Phone: +1-408-333-4062 287 Email: jon.hudson@gmail.com 289 Uma Chunduri 290 Ericsson Inc. 291 300 Holger Way, 292 San Jose, California 95134 293 USA 295 Phone: 408 750-5678 296 Email: uma.chunduri@ericsson