Multicast Router Discovery
Note: This ballot was opened for revision 07 and is now closed.
(Thomas Narten) Discuss
Discuss (2005-02-25 for -)
> 1. For IPv4 it is the 16-bit one's complement of the one's > complement sum of the IGMP message, starting with the Type field. > For computing the checksum, the checksum field is set to 0. > Checksum does not include any IPv4 header fields. This seems like a bad design choice. Note that in the IPv6 case, the checksum does include a pseudo-header. Why not be consistent? > 1. The expiration of the periodic advertisement interval timer. > Note that it this timer is not strictly periodic since it is a > random number between MaxAdvertisementInterval and > MinAdvertisementInterval. this doesn't seem good. The spread between these values can be pretty wide, I think. What you want is an average value with some randomness to prevent syncrhonization. You don't want the value to be completely random between (say) 3 and 180 seconds.
(Margaret Cullen) Yes
(Bill Fenner) Yes
(Harald Alvestrand) No Objection
Comment (2004-12-01 for -)
Reviewed by Mary Barnes, Gen-ART Her review: Draft is ready for publication as Proposed Standard.
(Sam Hartman) No Objection
(Scott Hollenbeck) No Objection
(Russ Housley) (was Discuss) No Objection
(Allison Mankin) No Objection
(Jon Peterson) No Objection
(Bert Wijnen) No Objection
Comment (2004-12-02 for -)
!! Missing citation for Informative reference: P016 L030:  Bradner, S., "Intellectual Property Rights in IETF Technology", !! Missing citation for Informative reference: P016 L034:  Daigle, L. and Internet Architecture Board, "IETF ISOC Board of QUestion: is there a MIB doc (in development) for the management variables listed in the subsections of sect 3? Section "9 Authors" may be a bit confusing with the other heading "Authors' Addresses" further down ----------- Comment from OPSDIR (Pekka) review: Nit: Although MRD messages could be sent as ICMP messages, the group management protocols were chosen since this functionality is multicast specific.