Re: [i2rs] Call for WG Adoption: draft-keyupdate-irs-bgp-usecases-02

Jon Mitchell <jrmitche@puck.nether.net> Mon, 29 July 2013 13:02 UTC

Return-Path: <jrmitche@puck.nether.net>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3FE21F9E2B for <i2rs@ietfa.amsl.com>; Mon, 29 Jul 2013 06:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QB3KxL64ZoZs for <i2rs@ietfa.amsl.com>; Mon, 29 Jul 2013 06:02:45 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 2511A21F9E9C for <i2rs@ietf.org>; Mon, 29 Jul 2013 06:02:31 -0700 (PDT)
Received: from puck.nether.net (localhost [127.0.0.1]) by puck.nether.net (8.14.7/8.14.5) with ESMTP id r6TD2TB6022302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 Jul 2013 09:02:29 -0400
Received: (from jrmitche@localhost) by puck.nether.net (8.14.7/8.14.7/Submit) id r6TD2T27022301; Mon, 29 Jul 2013 09:02:29 -0400
Date: Mon, 29 Jul 2013 09:02:29 -0400
From: Jon Mitchell <jrmitche@puck.nether.net>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Message-ID: <20130729130229.GA20218@puck.nether.net>
References: <CAG4d1rdOrA4P6tZXqRmReRetusDLX3cjFvtxYw0OD9oE2ASZQA@mail.gmail.com> <039801ce8bf0$c7caed60$5760c820$@riw.us> <20130729104056.GA7087@puck.nether.net> <CAG4d1rcoDiwD821Yo5n5NFd4uZjTT-X2K51JWgqUUAkidrBcdQ@mail.gmail.com> <40409CD7-451E-41C1-9D77-BC39927CED88@lucidvision.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <40409CD7-451E-41C1-9D77-BC39927CED88@lucidvision.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.1 (puck.nether.net [127.0.0.1]); Mon, 29 Jul 2013 09:02:29 -0400 (EDT)
Cc: Russ White <russw@riw.us>, "i2rs@ietf.org" <i2rs@ietf.org>, Alia Atlas <akatlas@gmail.com>
Subject: Re: [i2rs] Call for WG Adoption: draft-keyupdate-irs-bgp-usecases-02
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i2rs>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2013 13:02:46 -0000

On 29/07/13 13:40 +0200, Thomas Nadeau wrote:
> 
> On Jul 29, 2013:1:27 PM, at 1:27 PM, Alia Atlas <akatlas@gmail.com> wrote:
> 
> > From the comments so far, it is clear that there is work to be done on this draft before adoption.  I am quite eager to see the set of reasonable use-cases get discussed and put in. 
> > 
> > A single draft of BGP use-cases would be good.  Once one is adopted, the WG can direct the editors to add cases - if and when there is consensus to do so.
> > 
> > I don't think that a single draft of all I2RS use-cases is at all practical.  
> 
> 	I agree. You also need to consider the fact that things will evolve over time, and as a result that could hold up the progress of the early use cases in the IETF process as other use cases are discovered and added.   As you also know, we could gut the entire document and start from scratch just using the draft as a shell that targets that charter item. The point is that the WG has such a charter item, and this document at a minimum, is a good start to satisfy that. As you mention, once its a WG draft, the WG is in control of its content and can alter it as needed.


Ed/Alia/Tom - thanks for clarifying that we will have potentially
multiple use case drafts but likely only one BGP use case draft in the
WG.  undertsood that the WG can direct the authors to include the
white use cases once WG adopted but I personally would like to know
their receptiveness to the use cases in the white draft, and it
appears others have posed the same question previously.

-Jon