From pim-bounces@ietf.org Thu Feb 01 05:16:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCYyy-0001Qy-1l; Thu, 01 Feb 2007 05:15:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCYo5-0002Qb-7C
	for pim@ietf.org; Thu, 01 Feb 2007 05:04:41 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCYo0-0005YT-MP
	for pim@ietf.org; Thu, 01 Feb 2007 05:04:41 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Feb 2007 11:04:33 +0100
Received: from [10.193.15.74] ([10.193.15.74]) by
	ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Feb 2007 11:04:32 +0100
Subject: Re: [pim] New PIM Charter and milestones
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
To: Mike McBride <mmcbride@cisco.com>
In-Reply-To: <Pine.GSO.4.63.0701261621230.11346@irp-view7.cisco.com>
References: <Pine.GSO.4.63.0701261621230.11346@irp-view7.cisco.com>
Content-Type: text/plain
Organization: France Telecom R&D - Orange
Date: Thu, 01 Feb 2007 11:04:32 +0100
Message-Id: <1170324272.5011.26.camel@wintermute>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.2.1 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Feb 2007 10:04:33.0074 (UTC)
	FILETIME=[5EEE1920:01C745E8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: pim@ietf.org
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>
Errors-To: pim-bounces@ietf.org

Hi Mike, 

Mike McBride :
> [...] These PIM extensions could involve multipoint label switching, 
reliability, [...]
> ...
> Jul    2006     Develop a reliable pim specification
> ...

I think "reliability"/"reliable" here is a bit vague, especially in the
'July 2006' milestone, and that it should be better explained what it
means (I guess the milestone doesn't mean to say that current PIM
specifications are unreliable...).

Cheers,

-Thomas

(btw, I guess it's 2007 and not 2006...)


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



From pim-bounces@ietf.org Fri Feb 02 01:14:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCrfE-0000Kd-KO; Fri, 02 Feb 2007 01:12:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCrfC-0000KI-EV
	for pim@ietf.org; Fri, 02 Feb 2007 01:12:46 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCrfA-0008LX-Td
	for pim@ietf.org; Fri, 02 Feb 2007 01:12:46 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-4.cisco.com with ESMTP; 01 Feb 2007 22:12:44 -0800
X-IronPort-AV: i="4.13,272,1167638400"; 
	d="scan'208"; a="36826935:sNHT54394047"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id l126Chx7011757
	for <pim@ietf.org>; Thu, 1 Feb 2007 22:12:43 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l126Chho000636
	for <pim@ietf.org>; Thu, 1 Feb 2007 22:12:43 -0800 (PST)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Feb 2007 22:12:43 -0800
Received: from irp-view7.cisco.com ([171.70.65.144]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Feb 2007 22:12:43 -0800
Date: Thu, 1 Feb 2007 22:12:43 -0800 (PST)
From: Mike McBride <mmcbride@cisco.com>
To: pim@ietf.org
Subject: [pim] New PIM Charter rev3
Message-ID: <Pine.GSO.4.63.0702012207090.2461@irp-view7.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-OriginalArrivalTime: 02 Feb 2007 06:12:43.0688 (UTC)
	FILETIME=[26B3FA80:01C74691]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2025; t=1170396763;
	x=1171260763; c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mmcbride@cisco.com;
	z=From:=20Mike=20McBride=20<mmcbride@cisco.com>
	|Subject:=20[pim]=20New=20PIM=20Charter=20rev3 |Sender:=20;
	bh=vMDe3dx0RZCJx/dyCDGSK4r3YfJUu2BKtNpOaEmyNEk=;
	b=A8Hl9icwwf5D8RElgG9KuMj9pwI7JFfAZj5lD89eVfciB432Ec+k88Eap5SsS0/ipfGif14h
	xERCxQJy79/lSo6kcnC2nnppwnrI5ZyN5XkCEbX/reemTzfK7D8WRKgD;
Authentication-Results: sj-dkim-7; header.From=mmcbride@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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>
Errors-To: pim-bounces@ietf.org

All comments, both on and off list, have been addressed in the following 
revised Charter/Milestones. Thank you for you feedback. Please review this 
latest revision:

Description of Working Group:

The Protocol Independent Multicast (PIM) Working Group has completed the 
standardization of PIM with RFC 4601. The WG has determined there is 
additional work to be accomplished and is chartered to standardize 
extensions to RFC 4601 - Protocol Independent Multicast Version 2 - Sparse 
Mode. These PIM extensions could involve reliability, resiliency, 
scalability, management, and security.

The PIM WG will also consider implications of VPN service on PIM when it's 
a component of that service or when PIM interfaces with that service at a 
VPN edge. If L2VPN or L3VPN WGs determine that support for multicast in 
L2VPNs and/or L3VPNs requires extensions to PIM, then such extensions 
could be developed within the PIM WG.

Additional work on PIM-BIDIR and BSR may also be necessary.

The working group will continue to specify the MIBs required for PIM and 
its enhancements.

The PIM WG will further enhance RFC4601 as an even more scalable, 
efficient and robust multicast routing protocol, which is capable of 
supporting thousands of groups, different types of multicast applications, 
and all major underlying layer-2 subnetwork technologies.

The working group will determine if a Version 3 of PIM is required.

Goals and Milestones:

Mar    2007     Ratify new WG charter and milestones
Jul    2007     Submit the BSR MIB as a Proposed Standard
Nov    2007     Propose a more reliable pim solution which includes 
refresh reduction
Nov    2007     Submit a generic TLV PIM Join Attribute Proposed Standard 
draft
Nov    2007     Submit RPF Vector (use of PIM Join Attribute) as a 
Proposed Standard
Nov    2007     Submit a mechanism to authenticate PIM link local messages 
as PS
Nov    2007     Submit an Informational PIM last hop threats document.

thanks,
mike

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



From pim-bounces@ietf.org Fri Feb 02 10:22:13 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HD0DD-0005HF-6Y; Fri, 02 Feb 2007 10:20:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HD0DC-0005H8-90
	for pim@ietf.org; Fri, 02 Feb 2007 10:20:26 -0500
Received: from colo-dns-ext1.juniper.net ([207.17.137.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HD0D9-0006Sd-1i
	for pim@ietf.org; Fri, 02 Feb 2007 10:20:25 -0500
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id l12FKMX86334; 
	Fri, 2 Feb 2007 07:20:22 -0800 (PST)
	(envelope-from lenny@juniper.net)
Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l12FKHB24971;
	Fri, 2 Feb 2007 07:20:17 -0800 (PST)
	(envelope-from lenny@juniper.net)
Received: from zircon.juniper.net (localhost [127.0.0.1])
	by zircon.juniper.net (8.12.11/8.12.3) with ESMTP id l12FKFU4028220;
	Fri, 2 Feb 2007 07:20:17 -0800 (PST)
	(envelope-from lenny@juniper.net)
Received: from localhost (lenny@localhost)
	by zircon.juniper.net (8.12.11/8.12.3/Submit) with ESMTP id
	l12FKFAL028217; Fri, 2 Feb 2007 07:20:15 -0800 (PST)
X-Authentication-Warning: zircon.juniper.net: lenny owned process doing -bs
Date: Fri, 2 Feb 2007 07:20:15 -0800 (PST)
From: Leonard Giuliano <lenny@juniper.net>
To: Mike McBride <mmcbride@cisco.com>
Subject: Re: [pim] New PIM Charter rev3
In-Reply-To: <Pine.GSO.4.63.0702012207090.2461@irp-view7.cisco.com>
Message-ID: <20070202065540.D24982@zircon.juniper.net>
References: <Pine.GSO.4.63.0702012207090.2461@irp-view7.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: pim@ietf.org
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>
Errors-To: pim-bounces@ietf.org


How about widening the scope a bit more?  With the deaths of such WGs as 
Magma and IDMR, there is no WG that handles mcast routing and group 
membership protocols outside of PIM anymore.  Currently, Mboned is used as 
the catch-all WG for these issues.  However, protocol development is 
explicitly out of scope for Mboned.  What about renaming the PIM WG the 
Mcast Routing Protocols WG, and it would then be responsible for all mcast 
routing and group membership protocol developments.  Specifically, it 
would include PIM, IGMP, MLD, MSDP, BGMP, etc.  The amount of IGMP, MLD, 
MSDP and BGMP development is quite minimal at this time, but it does 
occasionally occur, and it would be good for it to have an appropriate and 
welcome home.

Mboned would still handle deployment issues, addressing and transition, 
and the protocols that support each (AMT, MADCAP, etc).

In any event, I do think it would be worthwhile to formally bifurcate 
deployment and routing protocols into 2 separate WGs.

Any thoughts?

-Lenny

On Thu, 1 Feb 2007, Mike McBride wrote:

-) All comments, both on and off list, have been addressed in the following
-) revised Charter/Milestones. Thank you for you feedback. Please review this
-) latest revision:
-) 
-) Description of Working Group:
-) 
-) The Protocol Independent Multicast (PIM) Working Group has completed the
-) standardization of PIM with RFC 4601. The WG has determined there is
-) additional work to be accomplished and is chartered to standardize extensions
-) to RFC 4601 - Protocol Independent Multicast Version 2 - Sparse Mode. These
-) PIM extensions could involve reliability, resiliency, scalability,
-) management, and security.
-) 
-) The PIM WG will also consider implications of VPN service on PIM when it's a
-) component of that service or when PIM interfaces with that service at a VPN
-) edge. If L2VPN or L3VPN WGs determine that support for multicast in L2VPNs
-) and/or L3VPNs requires extensions to PIM, then such extensions could be
-) developed within the PIM WG.
-) 
-) Additional work on PIM-BIDIR and BSR may also be necessary.
-) 
-) The working group will continue to specify the MIBs required for PIM and its
-) enhancements.
-) 
-) The PIM WG will further enhance RFC4601 as an even more scalable, efficient
-) and robust multicast routing protocol, which is capable of supporting
-) thousands of groups, different types of multicast applications, and all major
-) underlying layer-2 subnetwork technologies.
-) 
-) The working group will determine if a Version 3 of PIM is required.
-) 
-) Goals and Milestones:
-) 
-) Mar    2007     Ratify new WG charter and milestones
-) Jul    2007     Submit the BSR MIB as a Proposed Standard
-) Nov    2007     Propose a more reliable pim solution which includes refresh
-) reduction
-) Nov    2007     Submit a generic TLV PIM Join Attribute Proposed Standard
-) draft
-) Nov    2007     Submit RPF Vector (use of PIM Join Attribute) as a Proposed
-) Standard
-) Nov    2007     Submit a mechanism to authenticate PIM link local messages as
-) PS
-) Nov    2007     Submit an Informational PIM last hop threats document.
-) 
-) thanks,
-) mike
-) 
-) _______________________________________________
-) 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



From pim-bounces@ietf.org Fri Feb 02 11:10:18 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HD0yN-0002xf-5A; Fri, 02 Feb 2007 11:09:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HD0yL-0002wa-Cd
	for pim@ietf.org; Fri, 02 Feb 2007 11:09:09 -0500
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HD0yJ-0006jX-24
	for pim@ietf.org; Fri, 02 Feb 2007 11:09:09 -0500
Received: from ([128.244.206.105])
	by pilot.jhuapl.edu with ESMTP  id 5502123.20296283;
	Fri, 02 Feb 2007 11:08:46 -0500
Message-ID: <45C36210.3080402@innovationslab.net>
Date: Fri, 02 Feb 2007 11:08:48 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>,  pim@ietf.org
Subject: Re: [pim] New PIM Charter rev3
References: <Pine.GSO.4.63.0702012207090.2461@irp-view7.cisco.com>
	<20070202065540.D24982@zircon.juniper.net>
In-Reply-To: <20070202065540.D24982@zircon.juniper.net>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: 
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>
Errors-To: pim-bounces@ietf.org

Hey!  I wouldn't call MAGMA dead, we are just resting. :)

Seriously, the group is still open since we have not published all of
our documents yet.  My intent is to keep the list open for the
discussion of group management related issues.

Regards,
Brian


Leonard Giuliano wrote:
> How about widening the scope a bit more?  With the deaths of such WGs as 
> Magma and IDMR, there is no WG that handles mcast routing and group 
> membership protocols outside of PIM anymore.  Currently, Mboned is used as 
> the catch-all WG for these issues.  However, protocol development is 
> explicitly out of scope for Mboned.  What about renaming the PIM WG the 
> Mcast Routing Protocols WG, and it would then be responsible for all mcast 
> routing and group membership protocol developments.  Specifically, it 
> would include PIM, IGMP, MLD, MSDP, BGMP, etc.  The amount of IGMP, MLD, 
> MSDP and BGMP development is quite minimal at this time, but it does 
> occasionally occur, and it would be good for it to have an appropriate and 
> welcome home.
> 
> Mboned would still handle deployment issues, addressing and transition, 
> and the protocols that support each (AMT, MADCAP, etc).
> 
> In any event, I do think it would be worthwhile to formally bifurcate 
> deployment and routing protocols into 2 separate WGs.
> 
> Any thoughts?
> 
> -Lenny
> 
> On Thu, 1 Feb 2007, Mike McBride wrote:
> 
> -) All comments, both on and off list, have been addressed in the following
> -) revised Charter/Milestones. Thank you for you feedback. Please review this
> -) latest revision:
> -) 
> -) Description of Working Group:
> -) 
> -) The Protocol Independent Multicast (PIM) Working Group has completed the
> -) standardization of PIM with RFC 4601. The WG has determined there is
> -) additional work to be accomplished and is chartered to standardize extensions
> -) to RFC 4601 - Protocol Independent Multicast Version 2 - Sparse Mode. These
> -) PIM extensions could involve reliability, resiliency, scalability,
> -) management, and security.
> -) 
> -) The PIM WG will also consider implications of VPN service on PIM when it's a
> -) component of that service or when PIM interfaces with that service at a VPN
> -) edge. If L2VPN or L3VPN WGs determine that support for multicast in L2VPNs
> -) and/or L3VPNs requires extensions to PIM, then such extensions could be
> -) developed within the PIM WG.
> -) 
> -) Additional work on PIM-BIDIR and BSR may also be necessary.
> -) 
> -) The working group will continue to specify the MIBs required for PIM and its
> -) enhancements.
> -) 
> -) The PIM WG will further enhance RFC4601 as an even more scalable, efficient
> -) and robust multicast routing protocol, which is capable of supporting
> -) thousands of groups, different types of multicast applications, and all major
> -) underlying layer-2 subnetwork technologies.
> -) 
> -) The working group will determine if a Version 3 of PIM is required.
> -) 
> -) Goals and Milestones:
> -) 
> -) Mar    2007     Ratify new WG charter and milestones
> -) Jul    2007     Submit the BSR MIB as a Proposed Standard
> -) Nov    2007     Propose a more reliable pim solution which includes refresh
> -) reduction
> -) Nov    2007     Submit a generic TLV PIM Join Attribute Proposed Standard
> -) draft
> -) Nov    2007     Submit RPF Vector (use of PIM Join Attribute) as a Proposed
> -) Standard
> -) Nov    2007     Submit a mechanism to authenticate PIM link local messages as
> -) PS
> -) Nov    2007     Submit an Informational PIM last hop threats document.
> -) 
> -) thanks,
> -) mike
> -) 
> -) _______________________________________________
> -) 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

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



From pim-bounces@ietf.org Fri Feb 02 16:43:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HD6Ap-0002wd-FN; Fri, 02 Feb 2007 16:42:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HD6Ao-0002qj-OD
	for pim@ietf.org; Fri, 02 Feb 2007 16:42:22 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HD6An-0003vD-5a
	for pim@ietf.org; Fri, 02 Feb 2007 16:42:22 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 02 Feb 2007 13:42:16 -0800
X-IronPort-AV: i="4.13,274,1167638400"; 
	d="scan'208"; a="108441961:sNHT14586148440"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l12LgC9h032082; 
	Fri, 2 Feb 2007 13:42:12 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l12Lg6V4005701;
	Fri, 2 Feb 2007 13:42:15 -0800 (PST)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Feb 2007 13:41:43 -0800
Received: from irp-view7.cisco.com ([171.70.65.144]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 2 Feb 2007 13:41:43 -0800
Date: Fri, 2 Feb 2007 13:41:40 -0800 (PST)
From: Mike McBride <mmcbride@cisco.com>
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: [pim] New PIM Charter rev3
In-Reply-To: <45C36210.3080402@innovationslab.net>
Message-ID: <Pine.GSO.4.63.0702021307000.13915@irp-view7.cisco.com>
References: <Pine.GSO.4.63.0702012207090.2461@irp-view7.cisco.com>
	<20070202065540.D24982@zircon.juniper.net>
	<45C36210.3080402@innovationslab.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-OriginalArrivalTime: 02 Feb 2007 21:41:43.0026 (UTC)
	FILETIME=[EDEFFD20:01C74712]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4533; t=1170452532;
	x=1171316532; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mmcbride@cisco.com;
	z=From:=20Mike=20McBride=20<mmcbride@cisco.com>
	|Subject:=20Re=3A=20[pim]=20New=20PIM=20Charter=20rev3
	|Sender:=20; bh=bjI0F94faBZkgrxNnzleToiXTMCLweslVf1z38S9TP0=;
	b=NScy6F0/rrXZN4kLz7X13rb55A3o15RxEZkdPGVTnSBaTU3YuI35rkoU2V/ahUPkPU54vsJR
	5/6T8qNtpTJ2kSsSK+V5gEindQk/R0ZlWWa4tCN8HsDIV4PHTPPvxApz;
Authentication-Results: sj-dkim-4; header.From=mmcbride@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: Leonard Giuliano <lenny@juniper.net>, pim@ietf.org
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>
Errors-To: pim-bounces@ietf.org

Good to hear Brian. So the necessary wg's exist for multicast. For new 
multicast protocols we (MBONED particularly) need to ensure we are in sync 
about the requirements and then consider new wg to close out that work.

I recommend we continue with the pim wg rechartering effort and review 
rev3.

mike

On Fri, 2 Feb 2007, Brian Haberman wrote:

> Hey!  I wouldn't call MAGMA dead, we are just resting. :)
>
> Seriously, the group is still open since we have not published all of
> our documents yet.  My intent is to keep the list open for the
> discussion of group management related issues.
>
> Regards,
> Brian
>
>
> Leonard Giuliano wrote:
>> How about widening the scope a bit more?  With the deaths of such WGs as
>> Magma and IDMR, there is no WG that handles mcast routing and group
>> membership protocols outside of PIM anymore.  Currently, Mboned is used as
>> the catch-all WG for these issues.  However, protocol development is
>> explicitly out of scope for Mboned.  What about renaming the PIM WG the
>> Mcast Routing Protocols WG, and it would then be responsible for all mcast
>> routing and group membership protocol developments.  Specifically, it
>> would include PIM, IGMP, MLD, MSDP, BGMP, etc.  The amount of IGMP, MLD,
>> MSDP and BGMP development is quite minimal at this time, but it does
>> occasionally occur, and it would be good for it to have an appropriate and
>> welcome home.
>>
>> Mboned would still handle deployment issues, addressing and transition,
>> and the protocols that support each (AMT, MADCAP, etc).
>>
>> In any event, I do think it would be worthwhile to formally bifurcate
>> deployment and routing protocols into 2 separate WGs.
>>
>> Any thoughts?
>>
>> -Lenny
>>
>> On Thu, 1 Feb 2007, Mike McBride wrote:
>>
>> -) All comments, both on and off list, have been addressed in the following
>> -) revised Charter/Milestones. Thank you for you feedback. Please review this
>> -) latest revision:
>> -)
>> -) Description of Working Group:
>> -)
>> -) The Protocol Independent Multicast (PIM) Working Group has completed the
>> -) standardization of PIM with RFC 4601. The WG has determined there is
>> -) additional work to be accomplished and is chartered to standardize extensions
>> -) to RFC 4601 - Protocol Independent Multicast Version 2 - Sparse Mode. These
>> -) PIM extensions could involve reliability, resiliency, scalability,
>> -) management, and security.
>> -)
>> -) The PIM WG will also consider implications of VPN service on PIM when it's a
>> -) component of that service or when PIM interfaces with that service at a VPN
>> -) edge. If L2VPN or L3VPN WGs determine that support for multicast in L2VPNs
>> -) and/or L3VPNs requires extensions to PIM, then such extensions could be
>> -) developed within the PIM WG.
>> -)
>> -) Additional work on PIM-BIDIR and BSR may also be necessary.
>> -)
>> -) The working group will continue to specify the MIBs required for PIM and its
>> -) enhancements.
>> -)
>> -) The PIM WG will further enhance RFC4601 as an even more scalable, efficient
>> -) and robust multicast routing protocol, which is capable of supporting
>> -) thousands of groups, different types of multicast applications, and all major
>> -) underlying layer-2 subnetwork technologies.
>> -)
>> -) The working group will determine if a Version 3 of PIM is required.
>> -)
>> -) Goals and Milestones:
>> -)
>> -) Mar    2007     Ratify new WG charter and milestones
>> -) Jul    2007     Submit the BSR MIB as a Proposed Standard
>> -) Nov    2007     Propose a more reliable pim solution which includes refresh
>> -) reduction
>> -) Nov    2007     Submit a generic TLV PIM Join Attribute Proposed Standard
>> -) draft
>> -) Nov    2007     Submit RPF Vector (use of PIM Join Attribute) as a Proposed
>> -) Standard
>> -) Nov    2007     Submit a mechanism to authenticate PIM link local messages as
>> -) PS
>> -) Nov    2007     Submit an Informational PIM last hop threats document.
>> -)
>> -) thanks,
>> -) mike
>> -)
>> -) _______________________________________________
>> -) 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
>
> _______________________________________________
> 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



From pim-bounces@ietf.org Fri Feb 09 13:10:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFaAZ-0007mD-CK; Fri, 09 Feb 2007 13:08:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEkrR-0006l7-Mq; Wed, 07 Feb 2007 06:21:13 -0500
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HEkrP-0001P8-AJ; Wed, 07 Feb 2007 06:21:13 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l17BL3Lf005120; Wed, 7 Feb 2007 06:21:04 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Feb 2007 13:21:03 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C43FDCA@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-ietf-pim-bidir (Bi-directional Protocol
	Independent Multicast (BIDIR-PIM)) to Proposed Standard 
Thread-Index: Acc/ysbx8GIsNscLTFm6mj4rUmgFvQK21BSQ
References: <E1H9jpE-0003yt-E2@stiedprstage1.ietf.org>
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ietf@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
X-Mailman-Approved-At: Fri, 09 Feb 2007 13:08:22 -0500
Cc: pim@ietf.org
Subject: [pim] RE: Last Call: draft-ietf-pim-bidir (Bi-directional Protocol
	Independent Multicast (BIDIR-PIM)) to Proposed Standard 
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>
Errors-To: pim-bounces@ietf.org

1. The document should list 'Intended Status: Proposed Standard' in the
header

2. The document lacks an IANA consideration section. Moreover the
allocation of OptionType 22 in section 3.7.4 contradicts section 4.9.2
in RFC 4601 which states:

'OptionTypes 17 through 65000 are assigned by the IANA.'

3. Reference problems (according to the experimental tool):=20

 - Unused Reference: '1' is defined on line 1784, but not referenced
    '[1] S.E. Deering, "Host extensions for IP multicasting", RFC 1112,
Aug...'

  - Unused Reference: '6' is defined on line 1803, but not referenced
    '[6] T. Bates , R. Chandra , D. Katz , Y. Rekhter, "Multiprotocol
Exten...'

  - Possible downref: Non-RFC Normative Reference: ref. '4'
  * Obsolete Normative Reference: RFC 2401 (ref. '5')
  - Obsolete Informational Reference (is this intentional?): RFC 2283
(ref.
    '6')
  - Obsolete Informational Reference (is this intentional?): RFC 2362
(ref.
    '8')

In general the references sections are in need of a serious update.

4. In general it is good to check idnits with the latest version of the
tools. Other complaints from the tool are related to boilerplate format,
usage of keywords without an appropriate RFC 2119 section and many
instances of too long lines

5. Is Section 6 (change history) supposed to be taken out at
publication? If so an appropriate editor note should be included

6. Section 11 - Index seems to be mixed with the Intellectual Property
section.=20

Dan




=20
=20

> -----Original Message-----
> From: The IESG [mailto:iesg-secretary@ietf.org]=20
> Sent: Wednesday, January 24, 2007 5:14 PM
> To: IETF-Announce
> Cc: pim@ietf.org
> Subject: Last Call: draft-ietf-pim-bidir (Bi-directional=20
> Protocol Independent Multicast (BIDIR-PIM)) to Proposed Standard=20
>=20
> The IESG has received a request from the Protocol Independent=20
> Multicast WG (pim) to consider the following document:
>=20
> - 'Bi-directional Protocol Independent Multicast (BIDIR-PIM) '
>    <draft-ietf-pim-bidir-08.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and=20
> solicits final comments on this action.  Please send=20
> substantive comments to the ietf@ietf.org mailing lists by=20
> 2007-02-07. Exceptionally, comments may be sent to=20
> iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.
>=20
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-pim-bidir-08.txt
>=20
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dvie
> w_id&dTag=3D5178&rfc_flag=3D0
>=20
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>=20

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



From pim-bounces@ietf.org Fri Feb 09 18:51:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFfVO-0002Ht-S2; Fri, 09 Feb 2007 18:50:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFfVK-00021U-H8; Fri, 09 Feb 2007 18:50:10 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HFfVC-0002o2-QV; Fri, 09 Feb 2007 18:50:10 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 7462C26EC8;
	Fri,  9 Feb 2007 23:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HFfVC-0002fK-Bb; Fri, 09 Feb 2007 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HFfVC-0002fK-Bb@stiedprstage1.ietf.org>
Date: Fri, 09 Feb 2007 18:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pim@ietf.org
Subject: [pim] I-D ACTION:draft-ietf-pim-bsr-mib-02.txt 
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>
Errors-To: pim-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

	Title		: PIM Bootstrap Router MIB
	Author(s)	: B. Joshi, R. Bijlani
	Filename	: draft-ietf-pim-bsr-mib-02.txt
	Pages		: 23
	Date		: 2007-2-9
	
This document defines a portion of the Management Information Base
   (MIB) for use with network management protocols in the Internet
   community.  In particular, it describes managed objects used for
   managing the Bootstrap Router (BSR) mechanism for PIM.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-bsr-mib-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pim-bsr-mib-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pim-bsr-mib-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-2-9172105.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pim-bsr-mib-02.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pim-bsr-mib-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-2-9172105.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--





From pim-bounces@ietf.org Tue Feb 13 15:52:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4co-0001Qn-6p; Tue, 13 Feb 2007 15:51:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4bh-0008Nl-RX; Tue, 13 Feb 2007 15:50:33 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HH4bg-0003H4-Fc; Tue, 13 Feb 2007 15:50:33 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 6614B2AD1C;
	Tue, 13 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HH4bC-0002wC-5F; Tue, 13 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HH4bC-0002wC-5F@stiedprstage1.ietf.org>
Date: Tue, 13 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: pim@ietf.org
Subject: [pim] I-D ACTION:draft-ietf-pim-sm-bsr-10.txt 
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>
Errors-To: pim-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

	Title		: Bootstrap Router (BSR) Mechanism for PIM
	Author(s)	: N. Bhaskar, et al.
	Filename	: draft-ietf-pim-sm-bsr-10.txt,.ps
	Pages		: 43
	Date		: 2007-2-13
	
This document specifies the Bootstrap Router (BSR) mechanism
     for the class of multicast routing protocols in the PIM
     (Protocol Independent Multicast) family that use the concept
     of a Rendezvous Point as a means for receivers to discover the
     sources that send to a particular multicast group.  BSR is one
     way that a multicast router can learn the set of group-to-RP
     mappings required in order to function.  The mechanism is
     dynamic, largely self-configuring, and robust to router
     failure.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-bsr-10.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pim-sm-bsr-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pim-sm-bsr-10.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-2-13104145.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pim-sm-bsr-10.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pim-sm-bsr-10.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-2-13104145.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From pim-bounces@ietf.org Thu Feb 22 15:45:35 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKKnL-0007jF-Om; Thu, 22 Feb 2007 15:44:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJbnD-0006ns-7o; Tue, 20 Feb 2007 15:40:55 -0500
Received: from fw1.si-intl.com ([208.97.217.3] helo=US01EX01.si.siroot.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HJbnC-0007Ri-Ow; Tue, 20 Feb 2007 15:40:55 -0500
Received: from va03ex01.si.siroot.com ([10.3.0.80]) by US01EX01.si.siroot.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 15:40:52 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 20 Feb 2007 15:41:33 -0500
Message-ID: <2A89D6B6FFB96046BE70561B718593F602ED6C59@va03ex01.si.siroot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IPv6 Inter-domain Multicasting and Address Assignments
Thread-Index: AcdVL4Jrwt8h6AVFS3+02rhe4E/ODg==
From: "Gibbons, James" <James.Gibbons@si-intl.com>
To: <magma@ietf.org>,
	<pim@ietf.org>
X-OriginalArrivalTime: 20 Feb 2007 20:40:52.0334 (UTC)
	FILETIME=[696418E0:01C7552F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
X-Mailman-Approved-At: Thu, 22 Feb 2007 15:44:00 -0500
Cc: 
Subject: [pim] IPv6 Inter-domain Multicasting and Address Assignments
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>
Content-Type: multipart/mixed; boundary="===============0109720640=="
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0109720640==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7552F.81A8EA1D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7552F.81A8EA1D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

=20

SI International represents and contracts with DITO (DoD IPv6 Transition
Office) on a number of IPv6 issues.  In this case we are providing DITO
with a white paper on IPv6 Inter-domain multicast address assignments
and issues/problems (expected or realized) regarding IPv6 multicast
implementations.

=20

To begin, I have gone over a number of RFCs (including RFC 3306, 3956,
3307, 2375, 4607, ID draft-ietf-mboned-ipv6-multicast-issues-02.txt
among others) but they are vague as to actual working implementation of
inter-domain multicast address assignments and how they will or might
work proceed.

=20

I wrote to IANA and it was suggested I might contact the IEFT MAGMA and
PIM groups, so I am forwarding this letter; any advice is greatly
appreciated.

=20

=3D=3D=3D=3D=3Dmy questions or issues =3D=3D=3D=3D=3D

=20

In IPv4 GLOP was developed but not widely used, where an organizations
ASN is embedded in the 223.0.0.0 / 8 multicast range.  In IPv6 I have
seen V6UPBM (RFC 3306) and "Embedded RP" (RFC 3956) as similar proposals
for IPv6. =20

=20

However, I am still not clear of the "reality" of IPv6 multicast address
assignments especially with regards to globally unique (by organization,
domain, site, etc.) inter-domain multicast. =20

=20

That is, how far have actual address assignments proceeded? =20

=20

What is just proposed versus being implemented or to be implemented? =20

=20

Are there actual standards being followed? =20

=20

Are there any referential real-world implementations? =20

=20

Are there known/expected issues/problems with IPv6 inter-domain
multicast and address assignments?

=20

Maybe a quote from my actual assignment will further clarify what I am
looking for:

=20

"DITO is having some concerns with IPv6 multicast address space and how
it should or should not be provisioned.  You should start the study with
regards to how IPv4 multicast addressing worked in the past.  If you
ever worked with it you would know there was never official group
reservations made with regards to address blocks.  However, this was
never a real issue since its popularity died.  So except for what was
deemed to be the well-known addresses there was never any reservations,
unlike how unicast is reserved.  One thought might be the Army gets a
block of addresses, Navy, and so on."

=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=20

Again, any help is appreciated. =20

=20

Thanks,

=20

James Gibbons

=20

Senior Network Engineer

SI International

Tel: 703.234.6894

=20


------_=_NextPart_001_01C7552F.81A8EA1D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hello,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>SI International represents and contracts with DITO =
(DoD
IPv6 Transition Office) on a number of IPv6 issues.&nbsp; In this case =
we are
providing DITO with a white paper on IPv6 Inter-domain multicast address
assignments and issues/problems (expected or realized) regarding IPv6 =
multicast
implementations.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>To begin, I have gone over a number of RFCs =
(including RFC
3306, 3956, 3307, 2375, 4607, ID =
draft-ietf-mboned-ipv6-multicast-issues-02.txt
among others) but they are vague as to actual working implementation of
inter-domain multicast address assignments and how they will or might =
work proceed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I wrote to IANA and it was suggested I might contact =
the
IEFT MAGMA and PIM groups, so I am forwarding this letter; any advice is
greatly appreciated.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>=3D=3D=3D=3D=3Dmy questions or issues =
=3D=3D=3D=3D=3D<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>In IPv4 GLOP was developed but not widely used, where =
an
organizations ASN is embedded in the 223.0.0.0 / 8 multicast =
range.&nbsp; In
IPv6 I have seen V6UPBM (RFC 3306) and &#8220;Embedded RP&#8221; (RFC =
3956) as
similar proposals for IPv6.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>However, I am still not clear of the =
&#8220;reality&#8221;
of IPv6 multicast address assignments especially with regards to =
globally
unique (by organization, domain, site, etc.) inter-domain =
multicast.&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>That is, how far have actual address assignments
proceeded?&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>What is just proposed versus being implemented or to =
be
implemented?&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Are there actual standards being followed?&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Are there any referential real-world =
implementations?&nbsp; <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Are there known/expected issues/problems with IPv6
inter-domain multicast and address =
assignments?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Maybe a quote from my actual assignment will further =
clarify
what I am looking for:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&#8220;DITO is having some concerns with IPv6 =
multicast
address space and how it should or should not be provisioned.&nbsp; You =
should
start the study with regards to how IPv4 multicast addressing worked in =
the
past.&nbsp; If you ever worked with it you would know there was never =
official
group reservations made with regards to address blocks.&nbsp; However, =
this was
never a real issue since its popularity died.&nbsp; So except for what =
was
deemed to be the well-known addresses there was never any reservations, =
unlike
how unicast is reserved.&nbsp; One thought might be the Army gets a =
block of
addresses, Navy, and so on.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:=
p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Again, any help is appreciated.&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>James Gibbons<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><i><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-style:italic'>Senior Network =
Engineer<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal><i><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-style:italic'>SI =
International<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal><i><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-style:italic'>Tel: =
703.234.6894</span></font></i><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7552F.81A8EA1D--


--===============0109720640==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0109720640==--




From pim-bounces@ietf.org Thu Feb 22 19:24:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKODZ-0005W7-EA; Thu, 22 Feb 2007 19:23:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKODY-0005Vf-95; Thu, 22 Feb 2007 19:23:20 -0500
Received: from [2001:630:d0:f102:230:48ff:fe77:96e] (helo=owl.ecs.soton.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKO9x-0007DR-Hi; Thu, 22 Feb 2007 19:19:40 -0500
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131])
	by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l1N0IuRr018084;
	Fri, 23 Feb 2007 00:18:56 GMT
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk
	[IPv6:2001:630:d0:f102:230:48ff:fe23:58df])
	by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l1N0IZlj013442; 
	Fri, 23 Feb 2007 00:18:36 GMT
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.12.11.20060308/8.11.6) id l1N0IYkb005123;
	Fri, 23 Feb 2007 00:18:34 GMT
Date: Fri, 23 Feb 2007 00:18:34 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: "Gibbons, James" <James.Gibbons@si-intl.com>
Subject: Re: [pim] IPv6 Inter-domain Multicasting and Address Assignments
Message-ID: <20070223001834.GA32766@login.ecs.soton.ac.uk>
References: <2A89D6B6FFB96046BE70561B718593F602ED6C59@va03ex01.si.siroot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2A89D6B6FFB96046BE70561B718593F602ED6C59@va03ex01.si.siroot.com>
User-Agent: Mutt/1.4i
X-Null-Tag: b59c85c115bd3bae90c1f7b05e16eede
X-Null-Tag: 021cb8294c064562fa1f31c66bbef2be
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: -2.8 (--)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: magma@ietf.org, pim@ietf.org
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>
Errors-To: pim-bounces@ietf.org

On Tue, Feb 20, 2007 at 03:41:33PM -0500, Gibbons, James wrote:
> 
>    Hello,
> 
> 
>    SI   International  represents  and  contracts  with  DITO  (DoD  IPv6
>    Transition  Office)  on  a number of IPv6 issues.  In this case we are
>    providing  DITO  with  a  white  paper  on IPv6 Inter-domain multicast
>    address   assignments   and  issues/problems  (expected  or  realized)
>    regarding IPv6 multicast implementations.
> 
>    To begin, I have gone over a number of RFCs (including RFC 3306, 3956,
>    3307,  2375,  4607,  ID draft-ietf-mboned-ipv6-multicast-issues-02.txt
>    among  others)  but they are vague as to actual working implementation
>    of  inter-domain  multicast  address  assignments and how they will or
>    might work proceed.

RFC3306 lets you create for yourself a globally unique multicast group
address where your unicast prefix (which is unique by allocation) contributes
towards the first 96 bits of the group address.

The missing bit is how you manage the last 32 bits, but that could be 
application determined if for example you used a /64 per application.
Or you can choose your own manually.
 
>    In IPv4 GLOP was developed but not widely used, where an organizations
>    ASN  is embedded in the 223.0.0.0 / 8 multicast range.  In IPv6 I have
>    seen  V6UPBM  (RFC  3306)  and  "Embedded  RP"  (RFC  3956) as similar
>    proposals for IPv6.

Yep.

>    However,  I  am  still  not  clear  of the "reality" of IPv6 multicast
>    address  assignments  especially  with  regards to globally unique (by
>    organization, domain, site, etc.) inter-domain multicast.

We're using RFC3306 and Embedded-RP group addresses for international
IPv6 multicast applications.
 
>    That is, how far have actual address assignments proceeded?

For 3306 you don't need an authority to hand it out, it's just there for
you to use implicitly by the format.
 
>    What is just proposed versus being implemented or to be implemented?
> 
>    Are there actual standards being followed?

A growing base of routers support Embedded RP... we've run that between
the UK and US academic networks; all router son path (mainly Cisco and
Juniper) support it.   No RP required :)
 
>    Are   there  known/expected  issues/problems  with  IPv6  inter-domain
>    multicast and address assignments?
> 
>    Maybe a quote from my actual assignment will further clarify what I am
>    looking for:
> 
>    "DITO  is  having  some concerns with IPv6 multicast address space and
>    how  it  should  or  should  not be provisioned.  You should start the
>    study  with  regards  to  how  IPv4 multicast addressing worked in the
>    past.   If  you  ever  worked  with  it you would know there was never
>    official  group  reservations  made  with  regards  to address blocks.
>    However,  this  was  never a real issue since its popularity died.  So
>    except  for  what  was deemed to be the well-known addresses there was
>    never  any  reservations, unlike how unicast is reserved.  One thought
>    might be the Army gets a block of addresses, Navy, and so on."

A big win for v6 is that you dont need an ASN for GLOP like v4, you can
just form multicast groups from your unicast allocated prefix(es).

And with a lot of /64's in an IPv6 site, you can (as we have) assign an
RFC3306 group range per application if you chose to do so.

The other nice thing about v6 multicast is the explicit scoping bits, which
make it easier to control where your traffic flows.

-- 
Tim

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



From pim-bounces@ietf.org Fri Feb 23 18:52:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKkAz-00051F-1M; Fri, 23 Feb 2007 18:50:09 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKkAs-0004vr-VP; Fri, 23 Feb 2007 18:50:02 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HKkAs-0005Ga-Hn; Fri, 23 Feb 2007 18:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 7F7CC3293E;
	Fri, 23 Feb 2007 23:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HKkAs-00024S-Bf; Fri, 23 Feb 2007 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HKkAs-00024S-Bf@stiedprstage1.ietf.org>
Date: Fri, 23 Feb 2007 18:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: pim@ietf.org
Subject: [pim] I-D ACTION:draft-ietf-pim-bidir-09.txt 
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>
Errors-To: pim-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Protocol Independent Multicast Working Group of the IETF.

	Title		: Bi-directional Protocol Independent Multicast (BIDIR-PIM)
	Author(s)	: M. Handley, et al.
	Filename	: draft-ietf-pim-bidir-09.txt
	Pages		: 45
	Date		: 2007-2-23
	
This document discusses Bi-directional PIM, a variant of PIM
     Sparse-Mode that builds bi-directional shared trees connecting
     multicast sources and receivers. Bi-directional trees are built
     using a fail-safe Designated Forwarder (DF) election mechanism
     operating on each link of a multicast topology.  With the
     assistance of the DF, multicast data is natively forwarded from
     sources to the Rendezvous-Point and hence along the shared tree
     to receivers without requiring source-specific state.  The DF
     election takes place at RP discovery time and provides the route
     to the RP thus eliminating the requirement for data-driven
     protocol events.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pim-bidir-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pim-bidir-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pim-bidir-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-2-23163311.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pim-bidir-09.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-pim-bidir-09.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-2-23163311.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From pim-bounces@ietf.org Mon Feb 26 15:47:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmjk-0003xn-Om; Mon, 26 Feb 2007 15:46:20 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLmjg-0003wZ-NA; Mon, 26 Feb 2007 15:46:16 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HLmjf-0006zT-EV; Mon, 26 Feb 2007 15:46:16 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 640122ACB0;
	Mon, 26 Feb 2007 20:45:45 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HLmjB-0004Rm-5R; Mon, 26 Feb 2007 15:45:45 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1HLmjB-0004Rm-5R@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 15:45:45 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: pim@ietf.org
Subject: [pim] Last Call: draft-ietf-pim-sm-bsr (Bootstrap Router (BSR) 
 Mechanism for PIM) to Proposed Standard 
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
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>
Errors-To: pim-bounces@ietf.org

The IESG has received a request from the Protocol Independent Multicast 
WG (pim) to consider the following document:

- 'Bootstrap Router (BSR) Mechanism for PIM '
   <draft-ietf-pim-sm-bsr-10.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-03-12. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pim-sm-bsr-10.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=6802&rfc_flag=0


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



From pim-bounces@ietf.org Tue Feb 27 05:44:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLznz-0000Do-9R; Tue, 27 Feb 2007 05:43:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HLznx-0000D3-5l
	for pim@ietf.org; Tue, 27 Feb 2007 05:43:33 -0500
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HLznt-0000GK-Jf
	for pim@ietf.org; Tue, 27 Feb 2007 05:43:33 -0500
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0JE4001G0B36S5@szxga02-in.huawei.com> for
	pim@ietf.org; Tue, 27 Feb 2007 18:42:42 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JE400MZAB347V@szxga02-in.huawei.com> for
	pim@ietf.org; Tue, 27 Feb 2007 18:42:42 +0800 (CST)
Received: from s33630C ([10.111.68.36])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0JE4001HQB31J5@szxml04-in.huawei.com> for
	pim@ietf.org; Tue, 27 Feb 2007 18:42:40 +0800 (CST)
Date: Tue, 27 Feb 2007 18:42:37 +0800
From: Su Haiyang <suhaiyang@huawei.com>
To: suhaiyang@huawei.com
Message-id: <000301c75a5b$ff62b050$df010264@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Thread-index: AcdaW/6yA3v+mFGDRaqMdD3/KBTHkQ==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9ce0328cdf9c90e4680655d09dccace5
Cc: pim@ietf.org
Subject: [pim] Some doubts about draft-ietf-pim-mib-v2-09?
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>
Content-Type: multipart/mixed; boundary="===============1377052669=="
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1377052669==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_0mx+vBq6rxoXsdyshbZkRw)"

This is a multi-part message in MIME format.

--Boundary_(ID_0mx+vBq6rxoXsdyshbZkRw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

   I have some doubts about The PIM Group Mapping Table defined at draft
draft-ietf-pim-mib-v2-09

I will appreciate your help if someone can give answer about the following
doubts

   in page 66 of draft-ietf-pim-mib-v2-09, there are some words as bellow:

   

            Given the collection of rows in this table at any point in

            time, the PIM mode and RP address to use for a particular

            group is determined using the following algorithm.

 

            1. From the set of all rows, the subset whose group prefix

               contains the group in question are selected.

 

            2. If there are no such rows, the behavior is undefined.

 

            3. If there is at least one such row, from the selected

               subset of rows, the subset that have the lowest value

               of pimGroupMappingPrecedence are selected.

 

            4. From the selected subset of rows, the subset that have

               the greatest value of pimGroupMappingGrpPrefixLength are

               selected.

 

            5. If there are multiple selected rows, the subset that have

               the highest precedence (the lowest numerical value for

               pimGroupMappingPrecedence) are selected.

 

            6. If there are multiple selected rows, the row selected is

               implementation dependent; the implementation might or

               might not apply the PIM hash function to select the row.

 

            7. The group mode to use is given by the value of

               pimGroupMappingPimMode from the single selected row; the

               RP to use is given by the value of

               pimGroupMappingRPAddress, unless pimGroupMappingOrigin is

               'embedded', in which case the RP is extracted from the

               group address in question."

 

 I don't understand these words totally:

                1. What's the purpose of  pimGroupMappingPrecedence item? Is
it only used in mapping a group prefix to a static rp?

                2. If there are static RP (embedded RP added in IPv6
multicast), BSR-RP, or some other dynamic RP mechanism like CISCO's private
AutoRP, 

willing to sever a group/prefix, How to choose the unique RP?

                3. Why the pimGroupMappingPrecedence appear twice in the
above words(row3 and row5)? Is there

                   any diffrence between this two rows? 

Best Regards

Steven Su

 


--Boundary_(ID_0mx+vBq6rxoXsdyshbZkRw)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Dotum;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:\9ED1\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:DotumChe;
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:\6977\4F53_GB2312;
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@Dotum";
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@MS UI Gothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@DotumChe";
	panose-1:2 11 6 9 0 1 1 1 1 1;}
@font-face
	{font-family:"\@\6977\4F53_GB2312";
	panose-1:2 1 6 9 3 1 1 1 1 1;}
@font-face
	{font-family:"\@\9ED1\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";

	layout-grid-mode:line;}
h1
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:21.6pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-21.6pt;
	page-break-after:avoid;
	font-size:16.0pt;
	font-family:Arial;}
h2
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:28.8pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-28.8pt;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0cm;
	margin-bottom:13.0pt;
	margin-left:36.0pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-36.0pt;
	line-height:173%;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.a, li.a, div.a
	{margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:54.45pt;
	margin-bottom:.0001pt;
	text-align:center;
	text-indent:-18.45pt;
	font-size:9.0pt;
	font-family:Arial;}
p.a0, li.a0, div.a0
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.a1, li.a1, div.a1
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.a2, li.a2, div.a2
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:12.0pt;
	margin-left:54.45pt;
	text-align:center;
	text-indent:-18.45pt;
	font-size:9.0pt;
	font-family:Arial;}
p.a3, li.a3, div.a3
	{margin-top:4.0pt;
	margin-right:0cm;
	margin-bottom:4.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a4, li.a4, div.a4
	{margin-top:15.0pt;
	margin-right:0cm;
	margin-bottom:15.0pt;
	margin-left:0cm;
	text-align:center;
	line-height:150%;
	text-autospace:none;
	font-size:18.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a5, li.a5, div.a5
	{margin:0cm;
	margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";
	layout-grid-mode:line;}
p.a6, li.a6, div.a6
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a7, li.a7, div.a7
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:18.0pt;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0cm;
	font-size:9.0pt;
	font-family:Arial;
	layout-grid-mode:line;}
p.a8, li.a8, div.a8
	{margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:Arial;
	color:blue;
	layout-grid-mode:line;
	font-style:italic;}
span.a9
	{font-family:&#23435;&#20307;;
	color:black;
	font-weight:bold;}
span.aa
	{font-family:&#23435;&#20307;;
	color:black;
	font-weight:bold;}
span.EmailStyle33
	{font-family:Arial;
	color:windowtext;}
 /* Page Definitions */
 @page Section1
	{size:595.3pt 841.9pt;
	margin:65.6pt 90.0pt 72.0pt 90.0pt;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>

</head>

<body lang=ZH-CN link=blue vlink=purple style='text-justify-trim:punctuation'>

<div class=Section1 style='layout-grid:15.6pt'>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>Hi,</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp; I have some doubts about <b><span
style='font-weight:bold'>The PIM Group Mapping Table </span></b>defined at
draft <b><span style='font-weight:bold'>draft-ietf-pim-mib-v2-09</span></b></span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>I will appreciate your help if someone
can give answer about the following doubts</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp; in <b><span
style='font-weight:bold'>page 66</span></b> of <b><span style='font-weight:
bold'>draft-ietf-pim-mib-v2-09</span></b>, there are some words as bellow:</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp; </span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp; <b><span style='font-weight:
bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Given the collection
of rows in this table at any point in</span></b></span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
time, the PIM mode and RP address to use for a particular</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
group is determined using the following algorithm.</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1. From the set of all rows, the subset whose group prefix</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
contains the group in question are selected.</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2. If there are no such rows, the behavior is undefined.</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3. If there is at least one such row, from the selected</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;subset
of rows, the subset that have the lowest value</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
of pimGroupMappingPrecedence are selected.</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
4. From the selected subset of rows, the subset that have</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the greatest value of pimGroupMappingGrpPrefixLength are</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
selected.</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
5. If there are multiple selected rows, the subset that have</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
the highest precedence (the lowest numerical value for</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
pimGroupMappingPrecedence) are selected.</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
6. If there are multiple selected rows, the row selected is</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementation dependent; the implementation might or</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
might not apply the PIM hash function to select the row.</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
7. The group mode to use is given by the value of</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
pimGroupMappingPimMode from the single selected row; the</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
RP to use is given by the value of</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
pimGroupMappingRPAddress, unless pimGroupMappingOrigin is</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
'embedded', in which case the RP is extracted from the</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
group address in question.&quot;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><b><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both;font-weight:bold'>&nbsp;</span></font></b></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;I don</span></font><font size=1
color=black><span lang=EN-US style='font-size:9.0pt;color:black;layout-grid-mode:
both'>&#8217;</span></font><font size=1 color=black face=&#23435;&#20307;><span lang=EN-US
style='font-size:9.0pt;font-family:&#23435;&#20307;;color:black;layout-grid-mode:both'>t
understand these words totally:</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1. What's the purpose of &nbsp;<b><span style='font-weight:bold'>pimGroupMappingPrecedence
item</span></b>? Is it only used in mapping a group prefix to a static rp?</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2. If there are
static RP (embedded RP added in IPv6 multicast), BSR-RP, or some other dynamic
RP mechanism like CISCO</span></font><font size=1 color=black><span lang=EN-US
style='font-size:9.0pt;color:black;layout-grid-mode:both'>&#8217;</span></font><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>s private AutoRP, </span></font></p>

<p class=MsoNormal style='text-indent:85.5pt;line-height:12.0pt;layout-grid-mode:
char'><font size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;
font-family:&#23435;&#20307;;color:black;layout-grid-mode:both'>willing to sever a
group/prefix, How to choose the unique RP?</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3. Why the <b><span style='font-weight:bold'>pimGroupMappingPrecedence</span></b>
appear twice in the above words(row3 and row5)? Is there</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;any
diffrence between this two rows? </span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>Best Regards</span></font></p>

<p class=MsoNormal style='line-height:12.0pt;layout-grid-mode:char'><font
size=1 color=black face=&#23435;&#20307;><span lang=EN-US style='font-size:9.0pt;font-family:
&#23435;&#20307;;color:black;layout-grid-mode:both'>Steven Su</span></font></p>

<p class=MsoNormal><font size=1 face=Arial><span lang=EN-US style='font-size:
9.0pt;line-height:150%;font-family:Arial'>&nbsp;</span></font></p>

</div>

</body>

</html>

--Boundary_(ID_0mx+vBq6rxoXsdyshbZkRw)--


--===============1377052669==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1377052669==--




From pim-bounces@ietf.org Tue Feb 27 05:59:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HM02h-0004C1-Jv; Tue, 27 Feb 2007 05:58:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HM02g-0004Bw-Oq
	for pim@ietf.org; Tue, 27 Feb 2007 05:58:46 -0500
Received: from smtp.dataconnection.com ([192.91.191.4]
	helo=enfismtp1.datcon.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HM02f-0002e8-P5
	for pim@ietf.org; Tue, 27 Feb 2007 05:58:46 -0500
Received: from enfimail2.datcon.co.uk ([172.19.14.250]) by
	enfismtp1.datcon.co.uk with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Feb 2007 10:58:40 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [pim] Some doubts about draft-ietf-pim-mib-v2-09?
Date: Tue, 27 Feb 2007 10:58:39 -0000
Message-ID: <8AC1AD08D396174DBC4E6D44EFACCFB102BC7995@enfimail2.datcon.co.uk>
In-Reply-To: <000301c75a5b$ff62b050$df010264@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [pim] Some doubts about draft-ietf-pim-mib-v2-09?
Thread-Index: AcdaW/6yA3v+mFGDRaqMdD3/KBTHkQAASQNw
From: "David McWalter" <DMcW@dataconnection.com>
To: "Su Haiyang" <suhaiyang@huawei.com>
X-OriginalArrivalTime: 27 Feb 2007 10:58:40.0698 (UTC)
	FILETIME=[3D67B1A0:01C75A5E]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d465bee15753def7c258f355435bdf03
Cc: pim@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============1857725271=="
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1857725271==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75A5E.3CF61368"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C75A5E.3CF61368
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Su.
=20
                1. What's the purpose of  pimGroupMappingPrecedence =
item? Is it only used in mapping a group prefix to a static rp?
[DMcW] If more than one RP could be used for a group, the =
pimGroupMappingPrecedence chooses between them.

                2. If there are static RP (embedded RP added in IPv6 =
multicast), BSR-RP, or some other dynamic RP mechanism like CISCO's =
private AutoRP,=20

willing to sever a group/prefix, How to choose the unique RP?

[DMcW] Each willing RP has a pimGroupMappingEntry row.  The one with the =
lowest numerical pimGroupMappingPrecedence is chosen.

                3. Why the pimGroupMappingPrecedence appear twice in the =
above words(row3 and row5)? Is there

                   any diffrence between this two rows?=20

[DMcW] You're right, 3 and 5 say the same thing.  I think 5 has no =
effect, and should be deleted.
=20
Hope that helps,
David McWalter.
=20
-----Original Message-----
From: Su Haiyang [mailto:suhaiyang@huawei.com]
Sent: 27 February 2007 10:43
To: suhaiyang@huawei.com
Cc: pim@ietf.org
Subject: [pim] Some doubts about draft-ietf-pim-mib-v2-09?



Hi,

   I have some doubts about The PIM Group Mapping Table defined at draft =
draft-ietf-pim-mib-v2-09

I will appreciate your help if someone can give answer about the =
following doubts

   in page 66 of draft-ietf-pim-mib-v2-09, there are some words as =
bellow:

  =20

            Given the collection of rows in this table at any point in

            time, the PIM mode and RP address to use for a particular

            group is determined using the following algorithm.

=20

            1. From the set of all rows, the subset whose group prefix

               contains the group in question are selected.

=20

            2. If there are no such rows, the behavior is undefined.

=20

            3. If there is at least one such row, from the selected

               subset of rows, the subset that have the lowest value

               of pimGroupMappingPrecedence are selected.

=20

            4. From the selected subset of rows, the subset that have

               the greatest value of pimGroupMappingGrpPrefixLength are

               selected.

=20

            5. If there are multiple selected rows, the subset that have

               the highest precedence (the lowest numerical value for

               pimGroupMappingPrecedence) are selected.

=20

            6. If there are multiple selected rows, the row selected is

               implementation dependent; the implementation might or

               might not apply the PIM hash function to select the row.

=20

            7. The group mode to use is given by the value of

               pimGroupMappingPimMode from the single selected row; the

               RP to use is given by the value of

               pimGroupMappingRPAddress, unless pimGroupMappingOrigin is

               'embedded', in which case the RP is extracted from the

               group address in question."

=20

 I don't understand these words totally:

                1. What's the purpose of  pimGroupMappingPrecedence =
item? Is it only used in mapping a group prefix to a static rp?

                2. If there are static RP (embedded RP added in IPv6 =
multicast), BSR-RP, or some other dynamic RP mechanism like CISCO's =
private AutoRP,=20

willing to sever a group/prefix, How to choose the unique RP?

                3. Why the pimGroupMappingPrecedence appear twice in the =
above words(row3 and row5)? Is there

                   any diffrence between this two rows?=20

Best Regards

Steven Su

=20


------_=_NextPart_001_01C75A5E.3CF61368
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 6.00.2800.1586" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: &#23435;&#20307;;
}
@font-face {
	font-family: Dotum;
}
@font-face {
	font-family: &#40657;&#20307;;
}
@font-face {
	font-family: MS UI Gothic;
}
@font-face {
	font-family: DotumChe;
}
@font-face {
	font-family: &#26999;&#20307;_GB2312;
}
@font-face {
	font-family: @&#23435;&#20307;;
}
@font-face {
	font-family: @Dotum;
}
@font-face {
	font-family: @MS UI Gothic;
}
@font-face {
	font-family: @DotumChe;
}
@font-face {
	font-family: @&#26999;&#20307;_GB2312;
}
@font-face {
	font-family: @&#40657;&#20307;;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 65.6pt 90.0pt 72.0pt =
90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"
}
H1 {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 16pt; MARGIN: 12pt 0cm 12pt =
21.6pt; TEXT-INDENT: -21.6pt; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
H2 {
	FONT-WEIGHT: normal; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 12pt; =
MARGIN: 12pt 0cm 12pt 28.8pt; TEXT-INDENT: -28.8pt; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
H3 {
	FONT-WEIGHT: normal; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 12pt; =
MARGIN: 13pt 0cm 13pt 36pt; LAYOUT-GRID-MODE: line; TEXT-INDENT: -36pt; =
LINE-HEIGHT: 173%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
P.MsoHeader {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; =
LAYOUT-GRID-MODE: char; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
LI.MsoHeader {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; =
LAYOUT-GRID-MODE: char; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
DIV.MsoHeader {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; =
LAYOUT-GRID-MODE: char; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
P.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
LI.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
DIV.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.a {
	FONT-SIZE: 9pt; MARGIN: 12pt 0cm 0pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
LI.a {
	FONT-SIZE: 9pt; MARGIN: 12pt 0cm 0pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
DIV.a {
	FONT-SIZE: 9pt; MARGIN: 12pt 0cm 0pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
P.a0 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
LI.a0 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
DIV.a0 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
P.a1 {
	FONT-WEIGHT: bold; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
LI.a1 {
	FONT-WEIGHT: bold; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
DIV.a1 {
	FONT-WEIGHT: bold; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
P.a2 {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 12pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
LI.a2 {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 12pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
DIV.a2 {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 12pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
P.a3 {
	FONT-SIZE: 10.5pt; MARGIN: 4pt 0cm; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: center
}
LI.a3 {
	FONT-SIZE: 10.5pt; MARGIN: 4pt 0cm; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: center
}
DIV.a3 {
	FONT-SIZE: 10.5pt; MARGIN: 4pt 0cm; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: center
}
P.a4 {
	FONT-SIZE: 18pt; MARGIN: 15pt 0cm; LAYOUT-GRID-MODE: line; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial; TEXT-ALIGN: center
}
LI.a4 {
	FONT-SIZE: 18pt; MARGIN: 15pt 0cm; LAYOUT-GRID-MODE: line; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial; TEXT-ALIGN: center
}
DIV.a4 {
	FONT-SIZE: 18pt; MARGIN: 15pt 0cm; LAYOUT-GRID-MODE: line; LINE-HEIGHT: =
150%; FONT-FAMILY: Arial; TEXT-ALIGN: center
}
P.a5 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"
}
LI.a5 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"
}
DIV.a5 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"
}
P.a6 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
LAYOUT-GRID-MODE: line; LINE-HEIGHT: 150%; PADDING-TOP: 0cm; =
BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
LI.a6 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
LAYOUT-GRID-MODE: line; LINE-HEIGHT: 150%; PADDING-TOP: 0cm; =
BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
DIV.a6 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
LAYOUT-GRID-MODE: line; LINE-HEIGHT: 150%; PADDING-TOP: 0cm; =
BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
P.a7 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
LAYOUT-GRID-MODE: line; TEXT-INDENT: 18pt; LINE-HEIGHT: 150%; =
PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
LI.a7 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
LAYOUT-GRID-MODE: line; TEXT-INDENT: 18pt; LINE-HEIGHT: 150%; =
PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
DIV.a7 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
LAYOUT-GRID-MODE: line; TEXT-INDENT: 18pt; LINE-HEIGHT: 150%; =
PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
P.a8 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; COLOR: =
blue; TEXT-INDENT: 21pt; LINE-HEIGHT: 150%; FONT-STYLE: italic; =
FONT-FAMILY: Arial
}
LI.a8 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; COLOR: =
blue; TEXT-INDENT: 21pt; LINE-HEIGHT: 150%; FONT-STYLE: italic; =
FONT-FAMILY: Arial
}
DIV.a8 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; LAYOUT-GRID-MODE: line; COLOR: =
blue; TEXT-INDENT: 21pt; LINE-HEIGHT: 150%; FONT-STYLE: italic; =
FONT-FAMILY: Arial
}
SPAN.a9 {
	FONT-WEIGHT: bold; COLOR: black; FONT-FAMILY: &#23435; 20307:=20
}
SPAN.aa {
	FONT-WEIGHT: bold; COLOR: black; FONT-FAMILY: &#23435; 20307:=20
}
SPAN.EmailStyle33 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</STYLE>
</HEAD>
<BODY lang=3DZH-CN style=3D"TEXT-JUSTIFY-TRIM: punctuation" =
vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>Hi=20
Su.</FONT></SPAN></DIV>
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D490465010-27022007><FONT face=3D&#23435;&#20307; =
color=3Dblack size=3D1><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1. What's the purpose of &nbsp;<B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence item</SPAN></B>? =
Is it only=20
used in mapping a group prefix to a static =
rp?</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D490465010-27022007><FONT face=3D&#23435;&#20307; =
color=3Dblack size=3D1><SPAN=20
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>[DMcW]=20
If more than one RP could be used for a group, the =
pimGroupMappingPrecedence=20
chooses between them.</FONT></SPAN></DIV></SPAN></FONT></SPAN><SPAN=20
class=3D490465010-27022007><FONT face=3D&#23435;&#20307; color=3Dblack =
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;"></SPAN></FONT></DIV>
<DIV>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2. If there =
are=20
static RP (embedded RP added in IPv6 multicast), BSR-RP, or some other =
dynamic=20
RP mechanism like CISCO</SPAN></FONT><FONT color=3Dblack size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: =
black">&#8217;</SPAN></FONT><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">s=20
private AutoRP, </SPAN></FONT></P>
<P class=3DMsoNormal=20
style=3D"LAYOUT-GRID-MODE: char; TEXT-INDENT: 85.5pt; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">willing=20
to sever a group/prefix, How to choose the unique =
RP?</SPAN></FONT></P><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2><SPAN=20
class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>[DMcW]=20
</FONT></SPAN>Each willing RP has a pimGroupMappingEntry row.&nbsp; The =
one with=20
the lowest numerical pimGroupMappingPrecedence is =
chosen.</FONT></SPAN></DIV>
<P class=3DMsoNormal=20
style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
3. Why the <B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence</SPAN></B> appear =
twice in=20
the above words(row3 and row5)? Is there</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;any=20
diffrence between this two rows? </SPAN></FONT></P></SPAN></DIV>
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2><SPAN=20
class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>[DMcW]=20
</FONT></SPAN>You're right,&nbsp;3 and 5 say the same thing.&nbsp; I =
think 5 has=20
no effect, and should be =
deleted.</FONT></SPAN></DIV></FONT></SPAN></DIV>
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>Hope=20
that helps,</FONT></SPAN></DIV>
<DIV><SPAN class=3D490465010-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>David=20
McWalter.</FONT></SPAN></DIV>
<DIV><SPAN class=3D490465010-27022007></SPAN><SPAN =
class=3D490465010-27022007><FONT=20
face=3DArial color=3D#800080 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Su Haiyang=20
[mailto:suhaiyang@huawei.com]<BR><B>Sent:</B> 27 February 2007=20
10:43<BR><B>To:</B> suhaiyang@huawei.com<BR><B>Cc:</B>=20
pim@ietf.org<BR><B>Subject:</B> [pim] Some doubts about=20
draft-ietf-pim-mib-v2-09?<BR><BR></FONT></DIV>
<DIV class=3DSection1 style=3D"LAYOUT-GRID:  15.6pt none">
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">Hi,</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;=20
I have some doubts about <B><SPAN style=3D"FONT-WEIGHT: bold">The PIM =
Group=20
Mapping Table </SPAN></B>defined at draft <B><SPAN=20
style=3D"FONT-WEIGHT: =
bold">draft-ietf-pim-mib-v2-09</SPAN></B></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">I=20
will appreciate your help if someone can give answer about the following =

doubts</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;=20
in <B><SPAN style=3D"FONT-WEIGHT: bold">page 66</SPAN></B> of <B><SPAN=20
style=3D"FONT-WEIGHT: bold">draft-ietf-pim-mib-v2-09</SPAN></B>, there =
are some=20
words as bellow:</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;=20
</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;=20
<B><SPAN=20
style=3D"FONT-WEIGHT: =
bold">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Given=20
the collection of rows in this table at any point=20
in</SPAN></B></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
time, the PIM mode and RP address to use for a =
particular</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
group is determined using the following algorithm.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
1. From the set of all rows, the subset whose group =
prefix</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
contains the group in question are selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
2. If there are no such rows, the behavior is =
undefined.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
3. If there is at least one such row, from the =
selected</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;s=
ubset=20
of rows, the subset that have the lowest value</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
of pimGroupMappingPrecedence are selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
4. From the selected subset of rows, the subset that =
have</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the greatest value of pimGroupMappingGrpPrefixLength =
are</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
5. If there are multiple selected rows, the subset that=20
have</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the highest precedence (the lowest numerical value =
for</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
pimGroupMappingPrecedence) are selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
6. If there are multiple selected rows, the row selected=20
is</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
implementation dependent; the implementation might =
or</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
might not apply the PIM hash function to select the =
row.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
7. The group mode to use is given by the value of</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
pimGroupMappingPimMode from the single selected row; =
the</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
RP to use is given by the value of</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
pimGroupMappingRPAddress, unless pimGroupMappingOrigin =
is</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
'embedded', in which case the RP is extracted from =
the</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
group address in question."</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; =
COLOR: black; FONT-FAMILY: =
&#23435;&#20307;"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;I=20
don</SPAN></FONT><FONT color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: =
black">&#8217;</SPAN></FONT><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">t=20
understand these words totally:</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1. What's the purpose of &nbsp;<B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence item</SPAN></B>? =
Is it only=20
used in mapping a group prefix to a static rp?</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2. If there =
are=20
static RP (embedded RP added in IPv6 multicast), BSR-RP, or some other =
dynamic=20
RP mechanism like CISCO</SPAN></FONT><FONT color=3Dblack size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: =
black">&#8217;</SPAN></FONT><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">s=20
private AutoRP, </SPAN></FONT></P>
<P class=3DMsoNormal=20
style=3D"LAYOUT-GRID-MODE: char; TEXT-INDENT: 85.5pt; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">willing=20
to sever a group/prefix, How to choose the unique RP?</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: =
&#23435;&#20307;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3. Why the <B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence</SPAN></B> appear =
twice in=20
the above words(row3 and row5)? Is there</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;any=20
diffrence between this two rows? </SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">Best=20
Regards</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D&#23435;&#20307; color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LAYOUT-GRID-MODE: both; COLOR: black; =
FONT-FAMILY: &#23435;&#20307;">Steven=20
Su</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; LINE-HEIGHT: 150%; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></BODY></HTML>

------_=_NextPart_001_01C75A5E.3CF61368--


--===============1857725271==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1857725271==--




From pim-bounces@ietf.org Tue Feb 27 14:48:41 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HM8J6-0007oM-3Z; Tue, 27 Feb 2007 14:48:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HM28Z-0003no-Qm
	for pim@ietf.org; Tue, 27 Feb 2007 08:12:59 -0500
Received: from smtp.dataconnection.com ([192.91.191.4]
	helo=enfismtp1.datcon.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HM28Y-0004OM-EJ
	for pim@ietf.org; Tue, 27 Feb 2007 08:12:59 -0500
Received: from enfimail2.datcon.co.uk ([172.19.14.250]) by
	enfismtp1.datcon.co.uk with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Feb 2007 13:11:00 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [pim] Some doubts about draft-ietf-pim-mib-v2-09?
Date: Tue, 27 Feb 2007 13:10:59 -0000
Message-ID: <8AC1AD08D396174DBC4E6D44EFACCFB102BC7997@enfimail2.datcon.co.uk>
In-Reply-To: <000e01c75a6d$300864a0$df010264@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [pim] Some doubts about draft-ietf-pim-mib-v2-09?
Thread-Index: AcdaW/6yA3v+mFGDRaqMdD3/KBTHkQAASQNwAAMoUVAAASqA4A==
From: "David McWalter" <DMcW@dataconnection.com>
To: "Su Haiyang" <suhaiyang@huawei.com>
X-OriginalArrivalTime: 27 Feb 2007 13:11:00.0108 (UTC)
	FILETIME=[B9A984C0:01C75A70]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: b67b344d961e46e8a65ebdf2f18911e8
X-Mailman-Approved-At: Tue, 27 Feb 2007 14:48:14 -0500
Cc: pim@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============1076334927=="
Errors-To: pim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1076334927==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C75A70.B93A4B3B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C75A70.B93A4B3B
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hi Su.
=20
You're right, we should usually consider prefix length before =
precendence, so it is better to delete rule 3, not rule 5.  I'll make =
that change when I next update the MIB.
=20
Yes, pimStaticRPOverrideDynamic does override the decision procedure =
described by pimGroupMappingTable.  You're right that it I should =
mention it there.
=20
However, note that these rules are a gray area where we are providing an =
outline of implementation-specific algorithms so that the MIB operator =
can understand what is happening.  We do not want to provide a =
completely firm specification, because that is up to the implementation. =
 See rule 6 for example.
=20
Finally about pimRPMappingChange, note that the origin and group prefix =
are present in that notification, even though they are not explicitly =
listed.  They are not-accessible index fields, which are present =
whenever objects indexed by them are present.  So all the fields from a =
pimGroupMappingEntry are available in a pimRPMappingChange notification.
=20
Thanks for your comments,
David McW.
=20
-----Original Message-----
From: Su Haiyang [mailto:suhaiyang@huawei.com]
Sent: 27 February 2007 12:46
To: David McWalter
Subject: RE: [pim] Some doubts about draft-ietf-pim-mib-v2-09?



Hi, DmcW,

 Thank you for your reply. There are still other doubts in my mind, =
please refer to the following comments with blue fonts:

  _____ =20

From: David McWalter [mailto:DMcW@dataconnection.com]=20
Sent: Tuesday, February 27, 2007 6:59 PM
To: Su Haiyang
Cc: pim@ietf.org
Subject: RE: [pim] Some doubts about draft-ietf-pim-mib-v2-09?

=20

Hi Su.

=20

                1. What's the purpose of  pimGroupMappingPrecedence =
item? Is it only used in mapping a group prefix to a static rp?

[DMcW] If more than one RP could be used for a group, the =
pimGroupMappingPrecedence chooses between them.

=20

                2. If there are static RP (embedded RP added in IPv6 =
multicast), BSR-RP, or some other dynamic RP mechanism like CISCO=A1=AFs =
private AutoRP,=20

willing to sever a group/prefix, How to choose the unique RP?

[DMcW] Each willing RP has a pimGroupMappingEntry row.  The one with the =
lowest numerical pimGroupMappingPrecedence is chosen.

=20

=20

[Su] Shouldn=A1=AFt the pimGroupMappingEntry row with greatest value of =
pimGroupMappingGrpPrefixLength be chosed first=A3=ACand then the row =
with lowest numberical pimGroupMappingPrecedence=A3=BFSo the following =
rule 4 should be considered before rule 3 if rule 5 has no effect.

=20

Another doubt, there is a pimStaticRPOverrideDynamic item defined at =
PimStaticRPEntry of pimStaticRPTable, and the following is commented at =
pimStaticRPPrecedence=A1=AFs description,=20

=A1=B0If pimStaticRPOverrideDynamic is set to TRUE, all dynamic RP

            configuration is overridden by this static configuration,

            whatever the value of this object.=A1=B1

My doubt is, why RP mapping rules defined at pimGroupMappingEntry =
dosen=A1=AFt consider whether static RP is preferred to dynamic RP =
mechanism?

=20

Another doubt about Page 70 of draft-ietf-pim-mib-v2-09, =
pimRPMappingChange trap is defined as bellow

      =20

       pimRPMappingChange NOTIFICATION-TYPE

    OBJECTS { pimGroupMappingPimMode,

              pimGroupMappingPrecedence

            }

    STATUS      current

    DESCRIPTION

            "A pimRPMappingChange trap signifies a change to the active

            RP mapping on this device.

=20

            This notification is generated whenever the counter

            pimRPMappingChangeCount is incremented, subject to the

            rate limit specified by pimRPMappingChangeTrapPeriod."

    ::=3D { pimTraps 4 }=20

      =20

        Shouldn=A1=AFt origin and group prefix be added into above trap =
so as to know which mapped group prefix changes?

=20

                3. Why the pimGroupMappingPrecedence appear twice in the =
above words(row3 and row5)? Is there

                   any diffrence between this two rows?=20

[DMcW] You're right, 3 and 5 say the same thing.  I think 5 has no =
effect, and should be deleted.

=20

Hope that helps,

David McWalter.

=20

-----Original Message-----
From: Su Haiyang [mailto:suhaiyang@huawei.com]
Sent: 27 February 2007 10:43
To: suhaiyang@huawei.com
Cc: pim@ietf.org
Subject: [pim] Some doubts about draft-ietf-pim-mib-v2-09?

Hi,

   I have some doubts about The PIM Group Mapping Table defined at draft =
draft-ietf-pim-mib-v2-09

I will appreciate your help if someone can give answer about the =
following doubts

   in page 66 of draft-ietf-pim-mib-v2-09, there are some words as =
bellow:

  =20

            Given the collection of rows in this table at any point in

            time, the PIM mode and RP address to use for a particular

            group is determined using the following algorithm.

=20

            1. From the set of all rows, the subset whose group prefix

               contains the group in question are selected.

=20

            2. If there are no such rows, the behavior is undefined.

=20

            3. If there is at least one such row, from the selected

               subset of rows, the subset that have the lowest value

               of pimGroupMappingPrecedence are selected.

=20

            4. From the selected subset of rows, the subset that have

               the greatest value of pimGroupMappingGrpPrefixLength are

               selected.

=20

            5. If there are multiple selected rows, the subset that have

               the highest precedence (the lowest numerical value for

               pimGroupMappingPrecedence) are selected.

=20

            6. If there are multiple selected rows, the row selected is

               implementation dependent; the implementation might or

               might not apply the PIM hash function to select the row.

=20

            7. The group mode to use is given by the value of

               pimGroupMappingPimMode from the single selected row; the

               RP to use is given by the value of

               pimGroupMappingRPAddress, unless pimGroupMappingOrigin is

               'embedded', in which case the RP is extracted from the

               group address in question."

=20

 I don=A1=AFt understand these words totally:

                1. What's the purpose of  pimGroupMappingPrecedence =
item? Is it only used in mapping a group prefix to a static rp?

                2. If there are static RP (embedded RP added in IPv6 =
multicast), BSR-RP, or some other dynamic RP mechanism like CISCO=A1=AFs =
private AutoRP,=20

willing to sever a group/prefix, How to choose the unique RP?

                3. Why the pimGroupMappingPrecedence appear twice in the =
above words(row3 and row5)? Is there

                   any diffrence between this two rows?=20

Best Regards

Steven Su

=20


------_=_NextPart_001_01C75A70.B93A4B3B
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dgb2312">


<META content=3D"MSHTML 6.00.2800.1586" name=3DGENERATOR>
<STYLE>@font-face {
	font-family: ;
}
@font-face {
	font-family: ;
}
@font-face {
	font-family: ;
}
@font-face {
	font-family: ;
}
@font-face {
	font-family: ;
}
@font-face {
	font-family: =CB=CE=CC=E5;
}
@font-face {
	font-family: Dotum;
}
@font-face {
	font-family: =BA=DA=CC=E5;
}
@font-face {
	font-family: MS UI Gothic;
}
@font-face {
	font-family: DotumChe;
}
@font-face {
	font-family: =BF=AC=CC=E5_GB2312;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: @=CB=CE=CC=E5;
}
@font-face {
	font-family: @Dotum;
}
@font-face {
	font-family: @MS UI Gothic;
}
@font-face {
	font-family: @DotumChe;
}
@font-face {
	font-family: @=BF=AC=CC=E5_GB2312;
}
@font-face {
	font-family: @=BA=DA=CC=E5;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 65.6pt 90.0pt 72.0pt =
90.0pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
H1 {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 16pt; MARGIN: 12pt 0cm 12pt =
21.6pt; TEXT-INDENT: -21.6pt; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
H2 {
	FONT-WEIGHT: normal; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 12pt; =
MARGIN: 12pt 0cm 12pt 28.8pt; TEXT-INDENT: -28.8pt; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
H3 {
	FONT-WEIGHT: normal; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 12pt; =
MARGIN: 13pt 0cm 13pt 36pt; LAYOUT-GRID-MODE: line; TEXT-INDENT: -36pt; =
LINE-HEIGHT: 173%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: justify
}
P.MsoHeader {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; =
LAYOUT-GRID-MODE: char; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
LI.MsoHeader {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; =
LAYOUT-GRID-MODE: char; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
DIV.MsoHeader {
	TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; =
LAYOUT-GRID-MODE: char; FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
P.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
LI.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
DIV.MsoFooter {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.a {
	FONT-SIZE: 9pt; MARGIN: 12pt 0cm 0pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
LI.a {
	FONT-SIZE: 9pt; MARGIN: 12pt 0cm 0pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
DIV.a {
	FONT-SIZE: 9pt; MARGIN: 12pt 0cm 0pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
P.a0 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
LI.a0 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
DIV.a0 {
	FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: Arial
}
P.a1 {
	FONT-WEIGHT: bold; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
LI.a1 {
	FONT-WEIGHT: bold; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
DIV.a1 {
	FONT-WEIGHT: bold; FONT-SIZE: 10.5pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: =
Arial; TEXT-ALIGN: center
}
P.a2 {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 12pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
LI.a2 {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 12pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
DIV.a2 {
	FONT-SIZE: 9pt; MARGIN: 0cm 0cm 12pt 54.45pt; TEXT-INDENT: -18.45pt; =
FONT-FAMILY: Arial; TEXT-ALIGN: center
}
P.a3 {
	FONT-SIZE: 10.5pt; MARGIN: 4pt 0cm; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: center
}
LI.a3 {
	FONT-SIZE: 10.5pt; MARGIN: 4pt 0cm; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: center
}
DIV.a3 {
	FONT-SIZE: 10.5pt; MARGIN: 4pt 0cm; LAYOUT-GRID-MODE: line; =
LINE-HEIGHT: 150%; FONT-FAMILY: "Times New Roman"; TEXT-ALIGN: center
}
P.a4 {
	FONT-SIZE: 18pt; MARGIN: 15pt 0cm; FONT-FAMILY: Arial; TEXT-ALIGN: =
center
}
LI.a4 {
	FONT-SIZE: 18pt; MARGIN: 15pt 0cm; FONT-FAMILY: Arial; TEXT-ALIGN: =
center
}
DIV.a4 {
	FONT-SIZE: 18pt; MARGIN: 15pt 0cm; FONT-FAMILY: Arial; TEXT-ALIGN: =
center
}
P.a5 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.a5 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.a5 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
P.a6 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
LI.a6 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
DIV.a6 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; FONT-FAMILY: Arial; =
TEXT-ALIGN: justify
}
P.a7 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
TEXT-INDENT: 18pt; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; =
FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
LI.a7 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
TEXT-INDENT: 18pt; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; =
FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
DIV.a7 {
	BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; =
PADDING-LEFT: 0cm; TEXT-JUSTIFY: inter-ideograph; FONT-SIZE: 9pt; =
PADDING-BOTTOM: 0cm; MARGIN: 0cm 0cm 0pt; BORDER-LEFT: medium none; =
TEXT-INDENT: 18pt; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none; =
FONT-FAMILY: Arial; TEXT-ALIGN: justify
}
P.a8 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; COLOR: blue; TEXT-INDENT: 21pt; =
FONT-STYLE: italic; FONT-FAMILY: Arial
}
LI.a8 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; COLOR: blue; TEXT-INDENT: 21pt; =
FONT-STYLE: italic; FONT-FAMILY: Arial
}
DIV.a8 {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; COLOR: blue; TEXT-INDENT: 21pt; =
FONT-STYLE: italic; FONT-FAMILY: Arial
}
SPAN.a9 {
	FONT-WEIGHT: bold; COLOR: black; FONT-FAMILY: =CB=CE=CC=E5
}
SPAN.aa {
	FONT-WEIGHT: bold; COLOR: black; FONT-FAMILY: =CB=CE=CC=E5
}
SPAN.EmailStyle33 {
	COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</STYLE>
</HEAD>
<BODY lang=3DZH-CN style=3D"TEXT-JUSTIFY-TRIM: punctuation" =
vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>Hi=20
Su.</FONT></SPAN></DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>You're=20
right, we should usually consider prefix length before precendence, so =
it is=20
better to delete rule 3,&nbsp;not rule 5.&nbsp; I'll make that change =
when I=20
next update the MIB.</FONT></SPAN></DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>Yes,=20
pimStaticRPOverrideDynamic does override the decision procedure =
described by=20
pimGroupMappingTable.&nbsp; You're right that it I should mention it=20
there.</FONT></SPAN></DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =

size=3D2>However, note that these rules are a gray area where we are =
providing an=20
outline&nbsp;of implementation-specific algorithms so that the MIB =
operator can=20
understand what is happening.&nbsp; We do not want to provide a =
completely firm=20
specification, because that is up to the implementation.&nbsp; See rule =
6 for=20
example.</FONT></SPAN></DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =

size=3D2>Finally about pimRPMappingChange, note that the origin and =
group prefix=20
are present in that notification, even though they are not explicitly=20
listed.&nbsp; They are not-accessible index fields, which are present =
whenever=20
objects indexed by them are present.&nbsp; So all the fields from a=20
pimGroupMappingEntry are available in a pimRPMappingChange=20
notification.</FONT></SPAN></DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>Thanks=20
for your comments,</FONT></SPAN></DIV>
<DIV><SPAN class=3D892345412-27022007><FONT face=3DArial color=3D#800080 =
size=3D2>David=20
McW.</FONT></SPAN></DIV>
<DIV><SPAN class=3D892345412-27022007></SPAN><SPAN =
class=3D892345412-27022007><FONT=20
face=3DArial color=3D#800080 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Su Haiyang=20
[mailto:suhaiyang@huawei.com]<BR><B>Sent:</B> 27 February 2007=20
12:46<BR><B>To:</B> David McWalter<BR><B>Subject:</B> RE: [pim] Some =
doubts=20
about draft-ietf-pim-mib-v2-09?<BR><BR></FONT></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">Hi,=20
DmcW,</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;Thank =
you for your=20
reply. There are still other doubts in my mind, please refer to the =
following=20
comments with blue fonts:</SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US style=3D"FONT-SIZE: =
12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D3>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> David McWalter=20
[mailto:DMcW@dataconnection.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, February 27, 2007 =
6:59=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Su =
Haiyang<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> pim@ietf.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [pim] Some doubts =
about=20
draft-ietf-pim-mib-v2-09?</SPAN></FONT></P></DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3D#800080 size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dpurple size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: Arial">Hi=20
Su.</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3D#800080 size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D=CB=CE=CC=E5 color=3Dblack =
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1. What's the purpose of &nbsp;<B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence item</SPAN></B>? =
Is it only=20
used in mapping a group prefix to a static rp?</SPAN></FONT></P></DIV>
<DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dpurple size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: Arial">[DMcW] If =
more than=20
one RP could be used for a group, the pimGroupMappingPrecedence chooses =
between=20
them.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV></DIV>
<DIV>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2. If there =
are=20
static RP (embedded RP added in IPv6 multicast), BSR-RP, or some other =
dynamic=20
RP mechanism like CISCO</SPAN></FONT><FONT color=3Dblack size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black">=A1=AF</SPAN></FONT><FONT =
face=3D=CB=CE=CC=E5 color=3Dblack=20
size=3D1><SPAN lang=3DEN-US style=3D"FONT-SIZE: 9pt; COLOR: black; =
FONT-FAMILY: =CB=CE=CC=E5">s=20
private AutoRP, </SPAN></FONT></P>
<P class=3DMsoNormal=20
style=3D"LAYOUT-GRID-MODE: char; TEXT-INDENT: 85.5pt; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">willing to sever a=20
group/prefix, How to choose the unique RP?</SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dpurple size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: Arial">[DMcW] Each =
willing=20
RP has a pimGroupMappingEntry row.&nbsp; The one with the lowest =
numerical=20
pimGroupMappingPrecedence is chosen.</SPAN></FONT></P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial">[Su]=20
Shouldn=A1=AFt </SPAN></FONT></B><B><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial">the</SPAN></FONT></B><B><FONT=20
color=3Dblue><SPAN lang=3DEN-US style=3D"FONT-WEIGHT: bold; COLOR: =
blue">=20
</SPAN></FONT></B><B><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial">pimGroupMappingEntry=20
row with greatest value of pimGroupMappingGrpPrefixLength be chosed=20
first</SPAN></FONT></B><B><FONT face=3D=CB=CE=CC=E5 color=3Dblue =
size=3D1><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">=A3=AC</SPAN></FONT></B><B><FONT=20
face=3DArial color=3Dblue size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial">and=20
then the row with lowest numberical=20
pimGroupMappingPrecedence</SPAN></FONT></B><B><FONT face=3D=CB=CE=CC=E5 =
color=3Dblue=20
size=3D1><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">=A3=BF</SPAN></FONT></B><B><FONT=20
face=3DArial color=3Dblue size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial">So=20
the following rule 4 should be considered before rule 3 if rule 5 has no =

effect.</SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial">Another=20
doubt, there is a </SPAN></FONT></B><B><FONT face=3D"Courier New" =
color=3Dblue=20
size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'">pimStaticRPOverrideDynamic=20
item defined at PimStaticRPEntry of pimStaticRPTable, and the following =
is=20
commented at pimStaticRPPrecedence=A1=AFs description, =
</SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3D"Courier New" color=3Dblue =
size=3D2><SPAN=20
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'">=A1=B0If=20
pimStaticRPOverrideDynamic is set to TRUE, all dynamic =
RP</SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3D"Courier New" color=3Dblue =
size=3D2><SPAN=20
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

configuration is overridden by this static =
configuration,</SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3D"Courier New" color=3Dblue =
size=3D2><SPAN=20
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

whatever the value of this object.=A1=B1</SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3D"Courier New" color=3Dblue =
size=3D2><SPAN=20
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'">My=20
doubt is, why RP mapping rules defined at </SPAN></FONT></B><B><FONT =
face=3DArial=20
color=3Dblue size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">pimGroupMappingEntry=20
dosen=A1=AFt consider</SPAN></FONT></B><B><FONT face=3D"Courier New" =
color=3Dblue=20
size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'">=20
whether static RP is preferred to dynamic RP =
mechanism?</SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3D"Courier New" color=3Dblue =
size=3D2><SPAN=20
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'"></SPAN></FONT></B>&nbsp;</P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><B><FONT =
face=3D"Courier New"=20
color=3Dblue size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'">Another=20
doubt about Page 70 of draft-ietf-pim-mib-v2-09, pimRPMappingChange trap =
is=20
defined as bellow</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
pimRPMappingChange NOTIFICATION-TYPE</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp; OBJECTS=20
{ pimGroupMappingPimMode,</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
pimGroupMappingPrecedence</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
}</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; current</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;=20
DESCRIPTION</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
"A pimRPMappingChange trap signifies a change to the =
active</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
RP mapping on this device.</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
This notification is generated whenever the counter</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
pimRPMappingChangeCount is incremented, subject to the</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
rate limit specified by pimRPMappingChangeTrapPeriod."</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp; ::=3D {=20
pimTraps 4 } </SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LINE-HEIGHT: 12pt"><FONT =
face=3D=CB=CE=CC=E5 color=3Dblue=20
size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></FONT><B><FONT face=3D"Courier New" color=3Dblue size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'">Shouldn=A1=AFt=20
origin and group prefix be added into above trap so as to know which =
mapped=20
group prefix changes?</SPAN></FONT></B></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: blue; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P></DIV>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D"Times New Roman" color=3Dblack size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt; COLOR: =
black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
3. Why the <B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence</SPAN></B> appear =
twice in=20
the above words(row3 and row5)? Is there</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;any=20
diffrence between this two rows? </SPAN></FONT></P></DIV>
<DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dpurple size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: Arial">[DMcW] =
You're=20
right,&nbsp;3 and 5 say the same thing.&nbsp; I think 5 has no effect, =
and=20
should be deleted.</SPAN></FONT></P></DIV></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3D#800080 size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dpurple size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: Arial">Hope that=20
helps,</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dpurple size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 10pt; COLOR: purple; FONT-FAMILY: Arial">David=20
McWalter.</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3D#800080 size=3D2><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3DTahoma =
size=3D2><SPAN=20
lang=3DEN-US style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN></B> Su =
Haiyang=20
[mailto:suhaiyang@huawei.com]<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 27 February 2007 =
10:43<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
suhaiyang@huawei.com<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> pim@ietf.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [pim] Some doubts about=20
draft-ietf-pim-mib-v2-09?</SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">Hi,</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp; I have some=20
doubts about <B><SPAN style=3D"FONT-WEIGHT: bold">The PIM Group Mapping =
Table=20
</SPAN></B>defined at draft <B><SPAN=20
style=3D"FONT-WEIGHT: =
bold">draft-ietf-pim-mib-v2-09</SPAN></B></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =CB=CE=CC=E5">I will =
appreciate your=20
help if someone can give answer about the following =
doubts</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp; in <B><SPAN=20
style=3D"FONT-WEIGHT: bold">page 66</SPAN></B> of <B><SPAN=20
style=3D"FONT-WEIGHT: bold">draft-ietf-pim-mib-v2-09</SPAN></B>, there =
are some=20
words as bellow:</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;=20
</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp; <B><SPAN=20
style=3D"FONT-WEIGHT: =
bold">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Given=20
the collection of rows in this table at any point=20
in</SPAN></B></SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
time, the PIM mode and RP address to use for a =
particular</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
group is determined using the following algorithm.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3DArial color=3D#800080 size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
1. From the set of all rows, the subset whose group =
prefix</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
contains the group in question are selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3DArial color=3D#800080 size=3D2><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
2. If there are no such rows, the behavior is =
undefined.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
3. If there is at least one such row, from the =
selected</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;s=
ubset=20
of rows, the subset that have the lowest value</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
of pimGroupMappingPrecedence are selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
4. From the selected subset of rows, the subset that =
have</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
the greatest value of pimGroupMappingGrpPrefixLength =
are</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
5. If there are multiple selected rows, the subset that=20
have</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
the highest precedence (the lowest numerical value =
for</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
pimGroupMappingPrecedence) are selected.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
6. If there are multiple selected rows, the row selected=20
is</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
implementation dependent; the implementation might =
or</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
might not apply the PIM hash function to select the =
row.</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
7. The group mode to use is given by the value of</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
pimGroupMappingPimMode from the single selected row; =
the</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
RP to use is given by the value of</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
pimGroupMappingRPAddress, unless pimGroupMappingOrigin =
is</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
'embedded', in which case the RP is extracted from =
the</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><B><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
group address in question."</SPAN></FONT></B></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;I=20
don</SPAN></FONT><FONT color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black">=A1=AF</SPAN></FONT><FONT =
face=3D=CB=CE=CC=E5 color=3Dblack=20
size=3D1><SPAN lang=3DEN-US style=3D"FONT-SIZE: 9pt; COLOR: black; =
FONT-FAMILY: =CB=CE=CC=E5">t=20
understand these words totally:</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
1. What's the purpose of &nbsp;<B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence item</SPAN></B>? =
Is it only=20
used in mapping a group prefix to a static rp?</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2. If there =
are=20
static RP (embedded RP added in IPv6 multicast), BSR-RP, or some other =
dynamic=20
RP mechanism like CISCO</SPAN></FONT><FONT color=3Dblack size=3D1><SPAN =
lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black">=A1=AF</SPAN></FONT><FONT =
face=3D=CB=CE=CC=E5 color=3Dblack=20
size=3D1><SPAN lang=3DEN-US style=3D"FONT-SIZE: 9pt; COLOR: black; =
FONT-FAMILY: =CB=CE=CC=E5">s=20
private AutoRP, </SPAN></FONT></P>
<P class=3DMsoNormal=20
style=3D"LAYOUT-GRID-MODE: char; TEXT-INDENT: 85.5pt; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">willing to sever a=20
group/prefix, How to choose the unique RP?</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
3. Why the <B><SPAN=20
style=3D"FONT-WEIGHT: bold">pimGroupMappingPrecedence</SPAN></B> appear =
twice in=20
the above words(row3 and row5)? Is there</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =
=CB=CE=CC=E5">&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;any=20
diffrence between this two rows? </SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =CB=CE=CC=E5">Best=20
Regards</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char; LINE-HEIGHT: =
12pt"><FONT=20
face=3D=CB=CE=CC=E5 color=3Dblack size=3D1><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: =CB=CE=CC=E5">Steven =

Su</SPAN></FONT></P>
<P class=3DMsoNormal style=3D"LAYOUT-GRID-MODE: char"><FONT =
face=3D"Times New Roman"=20
size=3D3><SPAN lang=3DEN-US=20
style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C75A70.B93A4B3B--


--===============1076334927==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1076334927==--




