LAN to wan multicast data

_______________________________________________
magma mailing list
magma <at> ietf.org
https://www1.ietf.org/mailman/listinfo/magma

Re: IGMP Snooping and IGMP proxy

Way back on Tue, 2004-12-28 at 12:40 -0500, Marshall Eubanks wrote:
>
> On Tue, 28 Dec 2004 19:46:54 +0530, Neeraj.Gupta <at> infineon.com
> <Neeraj.Gupta <at> infineon.com> wrote:
> > Hi,
> > 
> >   I have some doubt about IGMP snooping and IGMP proxy
> > 
> > 1 .In Latest draft of IGMP snooping "draft-ietf-magma-snoop-11.txt" they
> > have removed the reference of "draft-ietf-magma-proxy-06.txt" . So any
> > good reason for it ?
>
> I think that the reasons [for snooping and using proxy] are quite
> different...

That was the main reason for removing the references to the proxy draft:
it created a perception of a functional dependency (as the original
question illustrates) while all we meant to do was to use it as an
example.

> ..
> It may be because it has expired, as of Oct 2004. It is still on the site :
> http://www.ietf.org/internet-drafts/draft-ietf-magma-igmp-proxy-06.txt

A more mundane reason is that in November '03 the -10 version of the
snooping draft was held in the RFC Editor's queue because of its
dependencies on both the proxy and mrdisc drafts.  We took the proxy
dependencies out back in May '04.

I'll add here that a -12 version of the snooping draft should be out
shortly to update my contact address and document rev numbers.

> > 
> > 2. Can we Implement IGMP snooping and proxy simultaneously on same
> > switch ?

What he said.
				-- Frank

IGMP Snooping

Hi,
I have a question with respect to IGMP Snooping switches.

If Layer 2 switch builds an "Include" List as per the Reports it has
received from the Hosts, and if the switch receives data from a
particular source which is part of this "Include" list, will the switch
forward the data to all the Host which are part of the group or will it
send it to only those Hosts which are interested in the source? If it
has to send it to only those hosts which are interested how will this be
sent?
regards
Keerthi

RE: IGMP Snooping

Hi

This scenario of forwarding data based on both Group and Source information
is possible
only in case of IP address based IGMPv3 snooping.
Here the membership information is stored in format where the
Group IP address and Source IP addresses are the indices for the
forwarding table built.
So data should be forwarded to the hosts based on groups they are interested
and when the source of that data is from the list of intended sources for
this group.
i.e. the host is able to say the list of sources from which it wants data in
addition
to the interested group(in IGMP v3 snooping).

Regards
Bharani

***************************************

-----Original Message-----
From: magma-bounces <at> ietf.org [mailto:magma-bounces <at> ietf.org]On Behalf Of
keerthi.jayaram <at> wipro.com
Sent: Monday, 17 January 2005 7:05 PM
To: magma <at> ietf.org
Subject: [magma] IGMP Snooping

Hi,
I have a question with respect to IGMP Snooping switches.

If Layer 2 switch builds an "Include" List as per the Reports it has
received from the Hosts, and if the switch receives data from a
particular source which is part of this "Include" list, will the switch
forward the data to all the Host which are part of the group or will it
send it to only those Hosts which are interested in the source? If it
has to send it to only those hosts which are interested how will this be
sent?
regards
Keerthi

_______________________________________________
magma mailing list
magma <at> ietf.org
https://www1.ietf.org/mailman/listinfo/magma

***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************

Re: IGMP Snooping

Bharani wrote:

>Hi
>
>This scenario of forwarding data based on both Group and Source information
>is possible
>only in case of IP address based IGMPv3 snooping.
>Here the membership information is stored in format where the
>Group IP address and Source IP addresses are the indices for the
>forwarding table built.
>So data should be forwarded to the hosts based on groups they are interested
>and when the source of that data is from the list of intended sources for
>this group.
>i.e. the host is able to say the list of sources from which it wants data in
>addition
>to the interested group(in IGMP v3 snooping).
>  
>
HI,
note that all packets from  non local sources may have the same layer 2 
source address :
the address of the multicast router. Therefore source management for an 
IGMPv3 snooping
switch would imply to look at the IP header of all multicast data packets.

regards

Jean-Jacques

>
>Regards
>Bharani
>
>***************************************
>
>
>-----Original Message-----
>From: magma-bounces <at> ietf.org [mailto:magma-bounces <at> ietf.org]On Behalf Of
>keerthi.jayaram <at> wipro.com
>Sent: Monday, 17 January 2005 7:05 PM
>To: magma <at> ietf.org
>Subject: [magma] IGMP Snooping
>
>
>Hi,
>  
>

RE: IGMP Snooping

Hi

Pl go thru my mail clearly.
I have mentioned that the forwarding table built by snooping IGMPv3 reports
is
IP addreses based,    i.e the forwarding entry would be like
-----------------
-----------------

Group IPAddress     Source IPAddress     PortList
________________    ________________     ________

This information is built by snooping IGMPv3 reports.
The v3 reports give the following info :
Group IP address and the list of sources from which data is required for
this group.
In case of v3 reports the source IPs is obtained from the report itself and
not from
the source IP of the report.

So it is implied that the look up in the database for data forwarding is
based on
the Group destination address and Source address in the IP header of the IP
Multicast(Data).

Regards
Bharani

***************************************

-----Original Message-----
From: Jean-Jacques Pansiot [mailto:pansiot <at> crc.u-strasbg.fr]
Sent: Tuesday, 18 January 2005 3:43 PM
To: bharanii <at> future.futsoft.com
Cc: keerthi.jayaram <at> wipro.com; magma <at> ietf.org
Subject: Re: [magma] IGMP Snooping

Bharani wrote:

>Hi
>
>This scenario of forwarding data based on both Group and Source information
>is possible
>only in case of IP address based IGMPv3 snooping.
>Here the membership information is stored in format where the
>Group IP address and Source IP addresses are the indices for the
>forwarding table built.
>So data should be forwarded to the hosts based on groups they are
interested
>and when the source of that data is from the list of intended sources for
>this group.
>i.e. the host is able to say the list of sources from which it wants data
in
>addition
>to the interested group(in IGMP v3 snooping).
>
>
HI,
note that all packets from  non local sources may have the same layer 2
source address :
the address of the multicast router. Therefore source management for an
IGMPv3 snooping
switch would imply to look at the IP header of all multicast data packets.

regards

Jean-Jacques

>
>Regards
>Bharani
>
>***************************************
>
>
>-----Original Message-----
>From: magma-bounces <at> ietf.org [mailto:magma-bounces <at> ietf.org]On Behalf Of
>keerthi.jayaram <at> wipro.com
>Sent: Monday, 17 January 2005 7:05 PM
>To: magma <at> ietf.org
>Subject: [magma] IGMP Snooping
>
>
>Hi,
>
>

***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************

Should a snooping switch proxy or forward IGMP queries?

I'm coming back to some code I wrote a couple of months ago and it's not doing what I now think it should.  I've
looked at the "Considerations for IGMP and MLD Snooping Switches" and not found any thing that resolves
the conflict.  Thanks for any feedback.

Consider an IGMP snooping switch with static routers configured on ports 1 and 2 which receives a general
Query on port 5.  Should that query be forwarded (intact) or proxied (with a source address of 0.0.0.0) to
ports 3, 4, 6, etc.?  It seems intuitive that it should or the router out port 5 will never know about members
that may be out port 3, etc. but "Considerations" doesn't seem to say so.

                              Chris

Possibility multicast routing daemons coexistence

Hi,

In a Linux router box, can two multicast routing daemons coexist?
For example, can we run IGMP Proxy on LAN interfaces and PIM-DM/DVMRP 
daemon on WAN interfaces ?

In Linux kernel, only one user space process can add multicast routes in 
kernel Multicast Forwarding Cache (MFC). Is there any solution to make IGMP 
Proxy and a Multicast routing daemon run at the same time on the same machine?

regards,
Srilatha

IGMP Snooping

_______________________________________________
magma mailing list
magma <at> ietf.org
https://www1.ietf.org/mailman/listinfo/magma

Re: IGMP Snooping

Why would the MIB for IGMP snooping be different from that of an IGMP router?  They keep track of the same data
(which groups were seen on which ports, etc.).  I imagine one value to determine that the device was a
snooping switch vs. a router would be helpful but I'm not sure what other differences you anticipate.

_______________________________________________
magma mailing list
magma <at> ietf.org
https://www1.ietf.org/mailman/listinfo/magma

_______________________________________________
magma mailing list
magma <at> ietf.org
https://www1.ietf.org/mailman/listinfo/magma