Re: [Idr] Revised proposed IDR charter

Eric Rosen <erosen@cisco.com> Wed, 03 February 2010 16:02 UTC

Return-Path: <erosen@cisco.com>
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5709B28C173 for <idr@core3.amsl.com>; Wed, 3 Feb 2010 08:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 eQdtjxn6Xbms for <idr@core3.amsl.com>; Wed, 3 Feb 2010 08:02:51 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 556DD28C15E for <idr@ietf.org>; Wed, 3 Feb 2010 08:02:51 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.49,399,1262563200"; d="scan'208";a="83810191"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 03 Feb 2010 16:03:33 +0000
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 o13G3XtJ019290; Wed, 3 Feb 2010 16:03:33 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 o13G3WdA029515; Wed, 3 Feb 2010 11:03:33 -0500
To: "John G. Scudder" <jgs@juniper.net>
In-reply-to: Your message of Thu, 28 Jan 2010 10:53:44 +0200. <52635EAD-5E0B-4975-BFA5-B315036F59C8@juniper.net>
Date: Wed, 03 Feb 2010 11:03:32 -0500
Message-ID: <29514.1265213012@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
Cc: idr List <idr@ietf.org>, idr-chairs@tools.ietf.org, idr-ads@tools.ietf.org
Subject: Re: [Idr] Revised proposed IDR charter
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: erosen@cisco.com
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 16:02:52 -0000

With regard to the paragraph:

        The IDR working group also has an oversight role for all extensions
        made to BGP for other uses that may be developed in other working
        groups. IDR will review extensions made to BGP in other working
        groups at least at WG document adoption and during working group
        last calls. The IDR working group will also provide advice and
        guidance on BGP to other working groups as requested. In some cases
        the IDR WG chairs may work with the chairs of other working groups
        and the IESG to move BGP work into the IDR WG instead of the another
        WG.

I'd suggest omitting the first and last sentences.  The first sentence adds
no content, it just provides something to fight about (what does "oversight"
mean, exactly?).  The last sentence doesn't seem to add anything either, as
WG chairs may negotiate at any time to move stuff from one WG to another.
Historically, however, IDR has been more likely to give stuff away than to
take stuff in.

On the issue of whether it is IDR's job to "protect the Internet" by
blocking other WGs from augmenting the use of BGP (or particular BGP
sessions), that fight has been fought and lost multiple times in the past
dozen years.