RFC 2236:Internet Group Management Protocol, Versi...
RFC-Ref

router


Click on the red underlined text to get to the source

... report their multicast group memberships to any immediately- neighboring multicast routers. This memo describes only the use of IGMP between hosts ...
... IGMP between hosts and routers to determine group membership. Routers ...
... routers to determine group membership. Routers that are members of multicast groups are expected to behave as hosts ...
... multicast groups are expected to behave as hosts as well as routers, and may even respond to their own queries. IGMP ...
... queries. IGMP may also be used between routers, but such use is not specified here. ...
... of 2. All IGMP messages described in this document are sent with IP TTL 1, and contain the IP Router Alert option [RFC2113] in their IP header ...
... IGMP messages of concern to the host- router interaction: ...
... Varying this setting allows IGMPv2 routers to tune the "leave latency" (the time between the moment the last host ...


... primary interface on an attached network"; if a router has multiple physical interfaces on a single network ...
... Multicast routers use IGMP to learn which groups have members on each ...
... of their attached physical networks. A multicast router keeps a list of multicast group memberships for each attached network ...
... network, not a list of all of the members. With respect to each of its attached networks, a multicast router may assume one of two roles: Querier ...
... Querier per physical network. All multicast routers start up as a Querier ...
... Querier on each attached network. If a multicast router hears a Query message from a router ...
... multicast router hears a Query message from a router with a lower IP address, it MUST become a Non-Querier ...
... Non-Querier on that network. If a router has not heard a Query message from another router ...
... router has not heard a Query message from another router for [Other Querier Present Interval], it resumes the role ...
... resumes the role of Querier. Routers periodically [Query Interval] send a General Query ...
... send a General Query on each attached network for which this router is the Querier, to solicit membership information. On startup, a ...
... is the Querier, to solicit membership information. On startup, a router SHOULD send [Startup Query Count] General Queries spaced ...
... When a router receives a Report, it adds the group being reported to the list of multicast group ...
... group before this timer has expired, the router assumes that the group has no local members and that it need not forward remotely-originated multicasts ...
... group, it SHOULD send a Leave Group message to the all-routers multicast group (224.0.0.2). If it was not the last host ...
... send a Leave Group message when it leaves a group. Routers SHOULD accept a Leave Group message addressed to the group ...
... version of this standard. Leave Group messages are addressed to the all-routers group because other group members ...
... received after the response time of the last query expires, the routers assume that the group has no local members, as above. Any Querier ...
... Querier to non-Querier transition is ignored during this time; the same router keeps sending the Group-Specific Queries. ...


... Compatibility with IGMPv1 Routers ...
... host may be placed on a subnet where the Querier router has not yet been upgraded to IGMPv2. The following requirements ...
... The IGMPv1 router will send General Queries with the Max Response Time set to 0. This MUST be interpreted as a value of ...
... The IGMPv1 router expects Version 1 Membership Reports in response to its Queries ...
... query was heard in the last [Version 1 Router Present Timeout] seconds, and MUST NOT be based upon the type of the last Query heard. This state ...
... An IGMPv2 router may be placed on a subnet where at least one router ...
... IGMPv2 router may be placed on a subnet where at least one router on the subnet has not yet been upgraded to IGMPv2 ...
... If any IGMPv1 routers are present, the querier MUST use IGMPv1. ...
... is no reliable way of dynamically determining whether IGMPv1 routers are present on a network. Implementations MAY provide a way for system administrators ...
... system administrators to enable the use of IGMPv1 on their routers; in the absence of explicit configuration, the configuration MUST default to IGMPv2. When in IGMPv1 ...
... IGMPv2. When in IGMPv1 mode, routers MUST send Periodic Queries with a Max Response Time of 0, and MUST ignore Leave Group ...
... If a router is not explicitly configured to use IGMPv1 and hears an IGMPv1 ...


... An IGMPv2 router may be placed on a subnet where there are hosts that ...
... If a router receives a Version 1 Membership Report, it MUST set a timer ...
... hosts present for a particular group, a router MUST ignore any Leave Group messages that it receives for that group ...


... host to report is cleared, this action MAY be skipped. The Leave Message is sent to the ALL-ROUTERS group (224.0.0.2). ...
... "No IGMPv1 Router Present", when the host has not heard an IGMPv1 ...
... style query for the [Version 1 Router Present Timeout]. This is the initial state. ...
... "IGMPv1 Router Present", when the host has heard an IGMPv1 style ...
... query within the [Version 1 Router Present Timeout]. ...
... timer set to note the presence of an IGMPv1 router expires. ...
... timer to its maximum value [Version 1 Router Present Timeout] and (re)starting it. ...
... | No IGMPv1 | | Router | | Present | | | ...
... -----| IGMPv1 |<--- | Router | | Present | | | ...


... Router State Diagram ...
... Router behavior is more formally specified by the state transition diagrams below. ...
... A router may be in one of two possible states with respect to any single attached network: ...
... "Querier", when this router is designated to transmit IGMP Membership Queries ...
... "Non-Querier", when there is another router designated to transmit IGMP membership Queries ...
... The following three events can cause the router to change states: ...
... "query received from a router with a lower IP address" occurs when an IGMP ...
... an IGMP Membership Query is received from a router on the same network with a lower IP address ...
... query received from a | | other querier router with a lower | | present timer IP address ...
... | query received from a | | router with a lower IP | | address ...
... A router should start in the Initial state on all attached networks ...
... In addition, to keep track of which groups have members, a router may be in one of four possible states with respect to any single IP multicast group ...
... initial state for all groups on the router; it requires no storage in the router. ...
... groups on the router; it requires no storage in the router. ...
... "Checking Membership" state, when the router has received a Leave Group message but has not yet heard a Membership Report for ...
... There are six significant events that can cause router state transitions: ...
... "v2 report received" occurs when the router receives a Version 2 Membership Report for the group ...
... "v1 report received" occurs when the router receives a Version 1 Membership report for the group ...
... "leave received" occurs when the router receives an IGMP Group ...
... Query Interval] * [Last Member Query Count] if this router is a Querier, or the [Max Response Time] in the packet * [Last Member Query ...
... Response Time] in the packet * [Last Member Query Count] if this router is a non-Querier. ...
... The state diagram for a router in Querier state follows: ...
... The state diagram for a router in Non-Querier state is similar, ...


... Most of these timers are configurable. If non-default settings are used, they MUST be consistent among all routers on a single link. Note that parentheses are used to group ...
... The Group Membership Interval is the amount of time that must pass before a multicast router decides there are no more members of a group on a network ...
... The Other Querier Present Interval is the length of time that must pass before a multicast router decides that there is no longer another multicast router which should be the querier ...
... pass before a multicast router decides that there is no longer another multicast router which should be the querier. This value MUST be ((the Robustness Variable ...
... Group-Specific Queries sent before the router assumes there are no local members. Default: the Robustness Variable. ...
... Version 1 Router Present Timeout ...
... The Version 1 Router Present Timeout is how long a host must wait after hearing a Version 1 ...


... Membership Report The group being reported Leave Message ALL-ROUTERS (224.0.0.2) Note: in older (i.e., non-standard and now obsolete) versions ...
... hosts send Leave Messages to the group being left. A router SHOULD accept Leave Messages addressed to the group being left in the interests of backwards compatibility ...
... hosts. In all cases, however, hosts MUST send to the ALL-ROUTERS address to be compliant with this specification. ...


... forger. If the forger then sends no more Query messages, other routers' Other Querier Present timer will time out and one will ...
... Report messages: A forged Report message may cause multicast routers to think there are members of a group on a subnet ...
... subnet will be ignored. - Ignore Report messages without Router Alert options [RFC2113], and require that routers ...
... Router Alert options [RFC2113], and require that routers not forward Report messages. (The requirement is not a requirement ...
... requirement of generalized filtering in the forwarding path, since the packets already have Router Alert options in them). This solution breaks backwards compatibility with implementations of earlier versions ...
... with implementations of earlier versions of this specification which did not require Router Alert. A forged Version 1 ...
... A forged Version 1 Report Message may put a router into "version 1 members present" state ...
... state for a particular group, meaning that the router will ignore Leave messages. This can cause traffic to flow ...
... ignored. - Provide routers with a configuration switch to ignore Version 1 ...
... Queries for the group in question. This causes extra processing on each router and on each member of the group, but can not cause loss of desired traffic ...
... subnet will be ignored. - Ignore Leave messages without Router Alert options [RFC2113], and require that routers ...
... Router Alert options [RFC2113], and require that routers not forward Leave messages. (The requirement is not a requirement ...
... requirement of generalized filtering in the forwarding path, since the packets already have Router Alert options in them). This solution breaks backwards compatibility with implementations of earlier versions ...
... with implementations of earlier versions of this specification which did not require Router Alert. ...


... Katz, D., "IP Router Alert Option," RFC 2113prop, February 1997. ...


... IGMP Type is assigned to Version 2 Membership Report messages, so a router may tell the difference between an IGMPv1 and IGMPv2 host ...
... IGMPv2. However, this means that care must be taken when an IGMPv2 router is trying to coexist with an IGMPv1 router ...
... router is trying to coexist with an IGMPv1 router that uses a different querier election mechanism. In particular, it means that an IGMPv2 ...
... querier election mechanism. In particular, it means that an IGMPv2 router must be able to act as an IGMPv1 router ...
... router must be able to act as an IGMPv1 router on a particular network if configured to do so. The actions required include: ...
... The IGMPv2 spec requires the presence of the IP Router Alert option [RFC2113 ...



Google
Web
RFC-Ref