IGMPv3/MLDv2 Message Extension
Juniper Networks64 Butler StMilpitasCA 95035USAsivakumar.mahesh@gmail.comCisco Systems, Inc.Tasman DriveSan JoseCA 95134USAstig@cisco.comZTE CorporationNo. 50 Software Ave, Yuhuatai DistinctNanjing210000Chinazhang.zheng@zte.com.cn
Routing
MulticastIGMP and MLD protocols are extensible, but no extensions
have been defined so far. This document provides a
well-defined way of extending IGMP and MLD, including a new
extension type to distinguish between different extensions.
In this document, we describe a generic method to extend
IGMPv3 and MLDv2
messages to accommodate information other than
what is contained in the current message formats. This is done by
introducing an extension-type field in the message formats to indicate
the application for which the extension is done. This will be followed by
the actual value of the extension.
The extension will be part of additional data as mentioned in
Section 5.1.12 (resp.
Section 4.1.10) for query messages and
Section 5.2.12 (resp.
Section 4.2.11) for report messages.
One such extension is being defined in The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP 14
when, and only when,
they appear in all capitals, as shown here.
The MLD query format with extension is shown belowThe MLD report format with extension is shown below The IGMP query format with the extension is shown below The IGMP report format with the extension is shown belowThis document extends MLD (resp. IGMP) message formats.
As such, there is no impact on security or changes to the
considerations in and .
This document requests that IANA creates a new registry for IGMP/MLD
extension-types.