Re: New work items

Eric Rosen <erosen@cisco.com> Wed, 16 September 2009 04:49 UTC

Return-Path: <erosen@cisco.com>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F6713A68D5 for <l3vpn@core3.amsl.com>; Tue, 15 Sep 2009 21:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level:
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RakiYcOTBYZg for <l3vpn@core3.amsl.com>; Tue, 15 Sep 2009 21:49:47 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id E4D0A3A683F for <l3vpn@ietf.org>; Tue, 15 Sep 2009 21:49:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,394,1249257600"; d="scan'208";a="58285712"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 16 Sep 2009 04:50:34 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n8G4oYdo014355; Wed, 16 Sep 2009 00:50:34 -0400
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n8G4oYIa013467; Wed, 16 Sep 2009 04:50:34 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id n8G4oYQH023765; Wed, 16 Sep 2009 00:50:34 -0400
To: Ross Callon <rcallon@juniper.net>
Subject: Re: New work items
In-reply-to: Your message of Tue, 15 Sep 2009 22:20:08 -0400. <DF7F294AF4153D498141CBEFADB177049A09C7E8A5@EMBX01-WF.jnpr.net>
Date: Wed, 16 Sep 2009 00:50:34 -0400
Message-ID: <23764.1253076634@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1266; t=1253076634; x=1253940634; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=erosen@cisco.com; z=From:=20Eric=20Rosen=20<erosen@cisco.com> |Subject:=20Re=3A=20New=20work=20items=20 |Sender:=20 |To:=20Ross=20Callon=20<rcallon@juniper.net>; bh=yavOOuzYLEn4cgfkBsaxNgvPzQAD7NgeSOiAd3Ll0AE=; b=hQJnSqsNa7dRymmpO2RT+iIsli1PVRL28wmmm5XIvieXrOxdfYHILJjVrk g/ixB1W+HIVZ4LmyPzD95IfgCjBJwnrRenXHO5n6OvFpNplCoGH//NL73GA9 D3nkGLtq6b;
Authentication-Results: rtp-dkim-1; header.From=erosen@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: Yakov Rekhter <yakov@juniper.net>, "l3vpn@ietf.org" <l3vpn@ietf.org>, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: erosen@cisco.com
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2009 04:49:48 -0000

> If the group can't get its currently chartered multicast work completed in
> more than five years then why should we charter additional multicast work?

Could you point to the particular sentences in the charter that distinguish
what you call the "currently chartered multicast work" from the "additional
chartered work"?

If you cannot do so, then one might conclude that the new work items that
have been suggested fall under the existing charter and no rechartering is
necessary.  One might also conclude that the WG is nowhere near completing
its chartered work.

> Clearly more than six months have passed since the Dublin IETF. However,
> very considerable work has been completed since then

This isn't really accurate.  The work that was recently submitted to the
IESG was substantially completed before that time.  Since then, there was
some review during WG LC, but that was substantially completed early in
2009.

> don't expect the IESG to approve these without some guidance regarding
> what subset of the many available options we expect in interoperable
> implementations.

My practical advice would be that you shouldn't base your expectations about
this too heavily on the guidance provided in any particular document.