idnits 2.17.1 draft-ietf-pim-igmp-mld-extension-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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 8, 2020) is 1479 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) -- Looks like a reference, but probably isn't: '1' on line 223 -- Looks like a reference, but probably isn't: '2' on line 229 == Missing Reference: 'N' is mentioned on line 203, but not defined == Missing Reference: 'M' is mentioned on line 239, but not defined == Outdated reference: A later version (-08) exists of draft-ietf-bier-mld-04 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Sivakumar 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track S. Venaas 5 Expires: October 10, 2020 Cisco Systems, Inc. 6 Z. Zhang 7 ZTE Corporation 8 April 8, 2020 10 IGMPv3/MLDv2 Message Extension 11 draft-ietf-pim-igmp-mld-extension-00 13 Abstract 15 IGMP and MLD protocols are extensible, but no extensions have been 16 defined so far. This document provides a well-defined way of 17 extending IGMP and MLD, including a new extension type to distinguish 18 between different extensions. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on October 10, 2020. 37 Copyright Notice 39 Copyright (c) 2020 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Conventions used in this document . . . . . . . . . . . . . . 2 56 3. Multicast Listener Query Extension . . . . . . . . . . . . . 2 57 4. Version 2 Multicast Listener Report Extension . . . . . . . . 4 58 5. IGMP Membership Query Extension . . . . . . . . . . . . . . . 4 59 6. IGMP Version 3 Membership Report Extension . . . . . . . . . 5 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 61 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 62 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 63 9.1. Normative References . . . . . . . . . . . . . . . . . . 7 64 9.2. Informative References . . . . . . . . . . . . . . . . . 7 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 67 1. Introduction 69 In this document, we describe a generic method to extend IGMPv3 70 [RFC3376] and MLDv2 [RFC3810] messages to accommodate information 71 other than what is contained in the current message formats. This is 72 done by introducing an extension-type field in the message formats to 73 indicate the application for which the extension is done. This will 74 be followed by the actual value of the extension. 76 The extension will be part of additional data as mentioned in 77 [RFC3810] Section 5.1.12 (resp. [RFC3376] Section 4.1.10) for query 78 messages and [RFC3810] Section 5.2.12 (resp. [RFC3376] 79 Section 4.2.11) for report messages. 81 One such extension is being defined in [I-D.ietf-bier-mld] 83 2. Conventions used in this document 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 87 "OPTIONAL" in this document are to be interpreted as described in BCP 88 14 [RFC2119] [RFC8174] when, and only when, they appear in all 89 capitals, as shown here. 91 3. Multicast Listener Query Extension 93 The MLD query format with extension is shown below 95 0 1 2 3 96 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 97 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 98 | Type = 130 | Code | Checksum | 99 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 100 | Maximum Response Code | Reserved | 101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 102 | | 103 * * 104 | | 105 * Multicast Address * 106 | | 107 * * 108 | | 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | Resv |S| QRV | QQIC | Number of Sources (N) | 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 | | 113 * * 114 | | 115 * Source Address [1] * 116 | | 117 * * 118 | | 119 +- -+ 120 | | 121 * * 122 | | 123 * Source Address [2] * 124 | | 125 * * 126 | | 127 +- . -+ 128 . . . 129 . . . 130 +- -+ 131 | | 132 * * 133 | | 134 * Source Address [N] * 135 | | 136 * * 137 | | 138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 139 |Extension Type | Extension Value | 140 ~ ~ 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 143 Figure 2: MLD Query Extension 145 4. Version 2 Multicast Listener Report Extension 147 The MLD report format with extension is shown below 149 0 1 2 3 150 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 151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 152 | Type = 143 | Reserved | Checksum | 153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 | Reserved |Nr of Mcast Address Records (M)| 155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 156 | | 157 . . 158 . Multicast Address Record [1] . 159 . . 160 | | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | | 163 . . 164 . Multicast Address Record [2] . 165 . . 166 | | 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 | . | 169 . . . 170 | . | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 | | 173 . . 174 . Multicast Address Record [M] . 175 . . 176 | | 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 |Extension Type | Extension Value | 179 ~ ~ 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 Figure 3: MLD Report Extension 184 5. IGMP Membership Query Extension 186 The IGMP query format with the extension is shown below 187 0 1 2 3 188 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 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 | Type = 0x11 | Max Resp Code | Checksum | 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 192 | Group Address | 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 | Resv |S| QRV | QQIC | Number of Sources (N) | 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 | Source Address [1] | 197 +- -+ 198 | Source Address [2] | 199 +- . -+ 200 . . . 201 . . . 202 +- -+ 203 | Source Address [N] | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 |Extension Type | Extension Value | 206 ~ ~ 207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 Figure 4: IGMP Query Extension 211 6. IGMP Version 3 Membership Report Extension 213 The IGMP report format with the extension is shown below 214 0 1 2 3 215 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 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | Type = 0x22 | Reserved | Checksum | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 | Reserved | Number of Group Records (M) | 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | | 222 . . 223 . Group Record [1] . 224 . . 225 | | 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 | | 228 . . 229 . Group Record [2] . 230 . . 231 | | 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | . | 234 . . . 235 | . | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | | 238 . . 239 . Group Record [M] . 240 . . 241 | | 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 243 |Extension Type | Extension Value | 244 ~ ~ 245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 247 Figure 5: IGMP Report Extension 249 7. Security Considerations 251 This document extends MLD (resp. IGMP) message formats. As such, 252 there is no impact on security or changes to the considerations in 253 [RFC3810] and [RFC3376]. 255 8. IANA Considerations 257 This document requests that IANA creates a new registry for IGMP/MLD 258 extension-types. 260 9. References 262 9.1. Normative References 264 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 265 Requirement Levels", BCP 14, RFC 2119, 266 DOI 10.17487/RFC2119, March 1997, 267 . 269 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 270 Thyagarajan, "Internet Group Management Protocol, Version 271 3", RFC 3376, DOI 10.17487/RFC3376, October 2002, 272 . 274 [RFC3810] Vida, R., Ed. and L. Costa, Ed., "Multicast Listener 275 Discovery Version 2 (MLDv2) for IPv6", RFC 3810, 276 DOI 10.17487/RFC3810, June 2004, 277 . 279 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 280 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 281 May 2017, . 283 9.2. Informative References 285 [I-D.ietf-bier-mld] 286 Pfister, P., Wijnands, I., Venaas, S., Wang, C., Zhang, 287 Z., and M. Stenberg, "BIER Ingress Multicast Flow Overlay 288 using Multicast Listener Discovery Protocols", draft-ietf- 289 bier-mld-04 (work in progress), March 2020. 291 Authors' Addresses 293 Mahesh Sivakumar 294 Juniper Networks 295 64 Butler St 296 Milpitas CA 95035 297 USA 299 Email: sivakumar.mahesh@gmail.com 300 Stig Venaas 301 Cisco Systems, Inc. 302 Tasman Drive 303 San Jose CA 95134 304 USA 306 Email: stig@cisco.com 308 Zheng(Sandy) Zhang 309 ZTE Corporation 310 No. 50 Software Ave, Yuhuatai Distinct 311 Nanjing 210000 312 China 314 Email: zhang.zheng@zte.com.cn