IETF Logo Mail Archive

Re: [pim] I-D ACTION:draft-ietf-pim-group-rp-mapping-01.txt

"Andy Kessler (kessler)" <kessler@cisco.com> Tue, 21 July 2009 08:19 UTC

Return-Path: <kessler@cisco.com>
X-Original-To: pim@core3.amsl.com
Delivered-To: pim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D7F528C229 for <pim@core3.amsl.com>; Tue, 21 Jul 2009 01:19:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.469
X-Spam-Level:
X-Spam-Status: No, score=-5.469 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hAQPf3E+iZ9P for <pim@core3.amsl.com>; Tue, 21 Jul 2009 01:19:53 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 2B2B23A69CC for <pim@ietf.org>; Tue, 21 Jul 2009 01:19:53 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAA8XZUqrR7MV/2dsb2JhbAC4f4gjjycFhAw
X-IronPort-AV: E=Sophos;i="4.43,239,1246838400"; d="scan'208";a="188010118"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 21 Jul 2009 08:19:49 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6L8JnlP017967; Tue, 21 Jul 2009 01:19:49 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n6L8Jqog010879; Tue, 21 Jul 2009 08:19:52 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 21 Jul 2009 01:19:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 21 Jul 2009 01:19:48 -0700
Message-ID: <65B900A32A86DB4EBF57C0D07F9B2A9E0188E545@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <4A6578BF.1010806@venaas.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [pim] I-D ACTION:draft-ietf-pim-group-rp-mapping-01.txt
Thread-Index: AcoJ20tlrMfl7eWsRkSjVGUjfUDG+gAAGTbA
References: <20090625174502.0FEDC3A6DE0@core3.amsl.com><001729A7-308F-4F87-A98D-D42B87D84478@cisco.com><4A629A13.9050806@venaas.com> <4F52AD33-C3C3-4D00-945C-E1816C68EE81@cisco.com> <65B900A32A86DB4EBF57C0D07F9B2A9E0188E541@xmb-sjc-215.amer.cisco.com> <4A6578BF.1010806@venaas.com>
From: "Andy Kessler (kessler)" <kessler@cisco.com>
To: Stig Venaas <stig@venaas.com>
X-OriginalArrivalTime: 21 Jul 2009 08:19:49.0317 (UTC) FILETIME=[03B59F50:01CA09DC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1752; t=1248164389; x=1249028389; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kessler@cisco.com; z=From:=20=22Andy=20Kessler=20(kessler)=22=20<kessler@cisco. com> |Subject:=20RE=3A=20[pim]=20I-D=20ACTION=3Adraft-ietf-pim-g roup-rp-mapping-01.txt |Sender:=20; bh=Our3T2a9HRUFxzS4cBQD89HPeOdali6DFeEA0TU1Zqo=; b=YzDDyJxow3M4dj+vprvpcpm7D1qCxnJ7hhpmNMIAKXq5dbAD8KP7ubaX92 wJS07nduRC6hDS01Lntjj4LdDcIRiDsQrJVYobHSb0+Os+sngsunXYnDIR+b gTGojLBDrv3DC3tA4aT73oYYt+fr0FWJbzhcAZGowSslmD9rjYSq0=;
Authentication-Results: sj-dkim-1; header.From=kessler@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: pim@ietf.org
Subject: Re: [pim] I-D ACTION:draft-ietf-pim-group-rp-mapping-01.txt
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2009 08:19:54 -0000

Comments below...

----Original Message-----
From: Stig Venaas [mailto:stig@venaas.com] 
Sent: Tuesday, July 21, 2009 1:14 AM
To: Andy Kessler (kessler)
Cc: John Zwiebel (jzwiebel); pim@ietf.org
Subject: Re: [pim] I-D ACTION:draft-ietf-pim-group-rp-mapping-01.txt

Andy Kessler (kessler) wrote:
> Ok, we didn't intend to restrict or clarify how people should deploy 
> autorp, bsr,
> 
> static or embedded rp - but if you think that is relevant we can add
some
> 
> language in a new section like this:
> 
>  
> 
>   Use of dynamic group-to-rp mapping protocols
> 
>  
> 
>   Generally it is not necessary or recommended to run multiple dynamic

> group-to-rp
> 
>   mapping protocols in one administrative domain. Specifically, there
is 
> no interoperation of BSR
> 
>   and AutoRP implied or recommended by this draft. However, if a
router 
> was to receive two
>   sets of group-to-rp mappings from AutoRP and BSR, such as may be the

> case on a border
> 
>   router between two domains or perhaps through a misconfiguration
this 
> draft creates a
> 
>   deterministic way to resolve the conflict and select one group-to-rp

> mapping. This is
> 
>   necessary for consistency and stability of the network across the
PIM 
> domain.
> 

I think you could make a more general statement saying that the draft
does not imply implementation of any of the mapping mechanisms, but that
it provides a deterministic way to resolve...

Stig

Andy> John is not directly concerned about the implementation of the
mapping
Andy> mechanisms but rather that they are required to run together. We
are 
Andy> saying that it is not required or recommended.

v2.23.0 | Report a Bug | By Email