Re: [pim] Minor comment plus question on draft-ietf-pim-anycast-rp-06.txt

>>> First, minor comment.  There is a typo in 3.0
>>> where half way down it says "Ancyast-RP" and not "Anycast-RP".
>
>    Fixed. But not sure this justifies another rev of the spec. I'll let the
>    working group chairs decide.

Probably not, but thanks for doing it anyway, will make the iesg process 
proceed that much more smoothly.

mike

>>> E.g. in section 3.0, perhaps RP1 is indeed itself the DR for S1.
>>> I think this all still works o.k. though, RP1 would
>>> presumably still send the PIM-register to the RPA and
>>> thus intercept it itself and behave as described
>>> as though it had arrived from another DR.
>
>    Right, but the main PIM spec presumes this. This isn't anything speific
>    to Anycast-PIM.
>
>>> I suppose the only potential problem is if it checked the source
>>> of the PIM-register and then acted as though it had arrived
>>> "from another RP" in the set...
>
>    Yes, most implementations, the DR will send the PIM register to the RP
>    address, which is itself. The packet is looped back into an input queue
>    and processed like it came from another system. The same goes for the
>    Register-Stop message that it returns to itself.
>
> Thanks,
> Dino
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www1.ietf.org/mailman/listinfo/pim
>

_______________________________________________
pim mailing list
pim@ietf.org
https://www1.ietf.org/mailman/listinfo/pim