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

Dino Farinacci <dino@cisco.com> Tue, 07 February 2006 18:39 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6XkO-0003vr-Tc; Tue, 07 Feb 2006 13:39:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6XkM-0003v7-La for pim@megatron.ietf.org; Tue, 07 Feb 2006 13:39:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19161 for <pim@ietf.org>; Tue, 7 Feb 2006 13:37:45 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6Xwn-0002Dh-6p for pim@ietf.org; Tue, 07 Feb 2006 13:52:18 -0500
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 07 Feb 2006 10:39:14 -0800
X-IronPort-AV: i="4.02,95,1139212800"; d="scan'208"; a="254061034:sNHT28634188"
Received: from cisco.com (dino-lnx.cisco.com [171.71.54.55]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k17IdCQJ021804; Tue, 7 Feb 2006 10:39:12 -0800 (PST)
Received: from dino-lnx.cisco.com (localhost.localdomain [127.0.0.1]) by cisco.com (8.12.11/8.12.11) with ESMTP id k17IdCfU011442; Tue, 7 Feb 2006 10:39:12 -0800
Received: (from dino@localhost) by dino-lnx.cisco.com (8.12.11/8.12.11/Submit) id k17IdCMN011437; Tue, 7 Feb 2006 10:39:12 -0800
Date: Tue, 07 Feb 2006 10:39:12 -0800
Message-Id: <200602071839.k17IdCMN011437@dino-lnx.cisco.com>
From: Dino Farinacci <dino@cisco.com>
To: dave.price@aber.ac.uk
In-reply-to: <29466.1139308884@aber.ac.uk> (message from Dave Price on Tue, 07 Feb 2006 10:41:24 +0000)
Subject: Re: [pim] Minor comment plus question on draft-ietf-pim-anycast-rp-06.txt
References: <29466.1139308884@aber.ac.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: pim@ietf.org, dap@aber.ac.uk
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

>> 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.

>> 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