Re: mboned: draft-liu-magma-igmpv3-mldv2-lite-00.txt
Dino Farinacci <[email protected]>
| Newsgroups | gmane.ietf.magma,gmane.ietf.mboned |
|---|---|
| Message-ID | <[email protected]> |
>> I would prefer to see, at least once in the beginning, that joining
>> (*,G) is equivalent to ASM. This makes it clear that IGMPv3/MLDv2 are
>> also usable for ASM, to potentially replace all previous versions of
>> IGMP and MLD.
It depends how you use the term ASM. We want an IGMPv3 host to join
a (*,G) entry where the network has that group configured to run in
Bidir-PIM mode. And in many circles the term ASM is different mode than
Bidir-PIM mode.
But I agree with your point in principle. It's just jargon I'm raising.
>> Also, maybe I've missed something obvious, but clearly EXCLUDE(null)
>> means joining (*,G) like ASM. What does INCLUDE(null) mean? Below:
Prune (*,G). But again for clarity why use the double-negative when
Include-All and Exclude-All can do the same thing.
>> implies it means the same thing as EXCLUDE(null). But logically, I don't
>> see that.
Right, but at the same time I fixed the double-negative situation and
having two ways to join (*,G) and leave (*,G). Less options are good
for implementors and encourage interoperability sooner. ;-)
Dino