Re: IGMPv3 EXCLUDE filter Source problem

mighty <[email protected]>
Newsgroups gmane.ietf.magma
Message-ID <[email protected]>
you asked "how you would translate an EXCLUDE to a PIM join/prune message"
with the non-binding caveat "IGMPv3 deployment is for SSM"... according to
the contents of the table in section 6.3 of RFC 3376, an EXCLUDE'd source is
translated by the IGMP module as a suggestion to the multicast router to
"not forward traffic from the source". i wasn't commenting on any other
suggestion(s).\

On 6/5/07, John Zwiebel <[email protected]> wrote:
>
>
> On Jun 5, 2007, at 2:28 PM, mighty wrote:
>
> section 6.3 of RFC 3376, "IGMPv3 Source-Specific Forwarding Rules",
> outlines the forwarding suggestions the IGMP module should make to the
> multicast router. in the case of EXCLUDE group record with source records,
> the table reads:
>
>
> So???
>
> That has nothing to do with the questions I asked nor with
> the suggestion that tech engineer might want to talk to someone
> other than the folks on this list.
>
> You can prove whatever you like on this list, but that isn't going to get
> anything changed
> nor is it going to make "tech engr"'s testing results change.
>

_______________________________________________
magma mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/magma
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.