Re: WG summaries for Paris

Mike McBride <mmcbride@cisco.com> Wed, 31 August 2005 19:45 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAYWW-0005lf-Ss; Wed, 31 Aug 2005 15:45:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAYWV-0005kx-Fd for rtg-dir@megatron.ietf.org; Wed, 31 Aug 2005 15:45:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09301; Wed, 31 Aug 2005 15:45:25 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAYYH-0007kj-GJ; Wed, 31 Aug 2005 15:47:19 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-3.cisco.com with ESMTP; 31 Aug 2005 12:45:13 -0700
X-IronPort-AV: i="3.96,158,1122879600"; d="scan'208"; a="337669310:sNHT30372088"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j7VJiU0r015028; Wed, 31 Aug 2005 12:45:09 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 31 Aug 2005 12:45:05 -0700
Received: from irp-view6.cisco.com ([171.70.65.143]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 31 Aug 2005 12:45:04 -0700
Date: Wed, 31 Aug 2005 12:45:04 -0700
From: Mike McBride <mmcbride@cisco.com>
To: Alex Zinin <zinin@psg.com>
In-Reply-To: <1092702281.20050809142631@psg.com>
Message-ID: <Pine.GSO.4.63.0508311147170.22245@irp-view6.cisco.com>
References: <1092702281.20050809142631@psg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-OriginalArrivalTime: 31 Aug 2005 19:45:04.0772 (UTC) FILETIME=[7BD92C40:01C5AE64]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: rtg-dir@ietf.org, rtg-chairs@ietf.org
Subject: Re: WG summaries for Paris
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org

> If you haven't done so yet, please send a brief summary of the WG meeting
> in Paris (2-3 paras max). Please use "reply-all" when doing so.

PIM WG:

Alex is reviewing (has reviewed now) draft-ietf-pim-sm-v2-new-11 and soon 
entering IETF last call. For draft-ietf-pim-bidir-07, Tom and I just need 
to answer publication request questionnaire and Bill will move along. 
draft-ietf-pim-anycast-rp-04 needs some modifications (now done) before 
IETF last call. Good progress on draft-ietf-pim-sm-bsr-05 and Stig gave a 
report. Should just take one more rev before submittal for WG LC. Lingard 
gave an update on draft-ietf-pim-mib-v2-03 which has miraculously 
generated interested recently. A few objects need to be added/removed and 
then it should be ready. Arjen gave a brief update on 
draft-ietf-pim-proxy. He'll change the title and resubmit an -00.

We also reviewed the request from l3vpn for pim to provide a solution for 
reducing pim messaging particularly in the context of mvpn. We've asked 
l3vpn to provide more direction on scalability requirements. They are 
collecting responses to a Multicast VPN survey that they've distributed to 
gather info on scalability expectations. This will help the pimwg decide 
if there is further work we need to do in this area. Some feel that an 
extension (such as j/p ack) to pim is the answer, some feel pimv3 is the 
answer (using tcp for instance), and some feel there is no real problem to 
solve within pimwg. We previously created a design team for this and some 
solutions were provided, but we'll see if this is work we will adopt.

mike