Hi,

In particular this kind of messages can be useful for mld snooping
switches.

Konstantin 

_____________________________________________________

Konstantin K. KABASSANOV 
Research and Development Engineer

LIP6 Laboratory
Pierre and Marie Curie University

8, rue du Capitaine Scott,
75015 Paris, France

Phone: +33 (0) 1 44 27 71 26
Fax:   +33 (0) 1 44 27 74 95

E-mail: [EMAIL PROTECTED]
Web: http://www.kabassanov.com
______________________________________________________


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:owner-
> [EMAIL PROTECTED] On Behalf Of Siva Veerepalli
> Sent: jeudi 27 f�vrier 2003 20:23
> To: [EMAIL PROTECTED]
> Subject: Question on MLD
> 
> RFC2710 (MLD) states that when a General Membership Query is received,
a
> node listening to the query sends a membership report for all
multicast
> addresses it is listening to, excluding the all-nodes link-local
multicast
> address and any multicast addresses of scope 0 (reserved) and 1 (node-
> local).
> 
> My question is, is the node required to send the membership report for
> solicited-node multicast address as well? In general, since nodes do
not
> receive link-local scope multicast packets from out side the link, why
is
> it required for the nodes to report membership to the router for *any*
> link-local scope multicast addresses?
> 
> Thanks,
> Siva
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to [EMAIL PROTECTED]
> --------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to