Question about proxy implemenation in RFC 4605
Kunal Shah <[email protected]> Fri, 29 Oct 2010 20:46:35 -0400
| Newsgroups | gmane.ietf.magma |
|---|---|
| Message-ID | <4FD1E7CD248BF84F86BD4814EDDDBCC150E72D61AE@EUSAACMS0703.eamcs.ericsson.se> |
--===============0290809407==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_4FD1E7CD248BF84F86BD4814EDDDBCC150E72D61AEEUSAACMS0703e_"
--_000_4FD1E7CD248BF84F86BD4814EDDDBCC150E72D61AEEUSAACMS0703e_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi all,
According to RFC 4605, a router creates a membership database after merging=
the subscriptions on individual interfaces. Lets say that 3 IGMPv3 capable=
interfaces are as follows:
Interface 1 has host reporting Include S1 -> I(S1)
Interface 2 has host reporting Exclude S2 -> E(0,S2)
Interface 3 has host reporting Exclude nothing -> E(0,0)
For a device doing IGMPv3 proxy, the final membership record for group G is=
(G, EXCLUDE, NULL). Now lets say the host on interface 3 goes away, becaus=
e of which the subscription on interface 3 would expire and there wont be a=
ny IGMPv3 state on interface 3. How would the new membership record for PR=
OXY be calculated?? The RFC does not suggest any way to do this. Would IGMP=
process have to go through each interface again and then recompute the new=
membership record?? This would be very inefficient especially if there are=
multiple interfaces.
Is there a better way to recompute the new membership record??
Thanks
Kunal
--_000_4FD1E7CD248BF84F86BD4814EDDDBCC150E72D61AEEUSAACMS0703e_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
#800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"2">
<div>Hi all,</div>
<div> </div>
<div>According to RFC 4605, a router creates a membership database after me=
rging the subscriptions on individual interfaces. Lets say that 3 IGMPv3 ca=
pable interfaces are as follows:</div>
<div> </div>
<div>Interface 1 has host reporting Include S1 -> I(S1)</div>
<div>Interface 2 has host reporting Exclude S2 -> E(0,S2)</div>
<div>Interface 3 has host reporting Exclude nothing -> E(0,0)</div>
<div> </div>
<div>For a device doing IGMPv3 proxy, the final membership record for group=
G is (G, EXCLUDE, NULL). Now lets say the host on interface 3 goes away, b=
ecause of which the subscription on interface 3 would expire and there wont=
be any IGMPv3 state on interface
3. How would the new membership record for PROXY be calculated?? The =
RFC does not suggest any way to do this. Would IGMP process have to go thro=
ugh each interface again and then recompute the new membership record?? Thi=
s would be very inefficient especially
if there are multiple interfaces.</div>
<div>Is there a better way to recompute the new membership record??</div>
<div> </div>
<div> </div>
<div>Thanks</div>
<div>Kunal</div>
<div> </div>
<div> </div>
</font>
</body>
</html>
--_000_4FD1E7CD248BF84F86BD4814EDDDBCC150E72D61AEEUSAACMS0703e_--
--===============0290809407==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
magma mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/magma
--===============0290809407==--