Re: [i2rs] Results of WG Adoption Call: draft-keyupate-i2rs-bgp-usecases

"Russ White" <russw@riw.us> Fri, 16 August 2013 12:29 UTC

Return-Path: <russw@riw.us>
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 CA7A111E81A1 for <i2rs@ietfa.amsl.com>; Fri, 16 Aug 2013 05:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
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 kh2cYHvwfKf1 for <i2rs@ietfa.amsl.com>; Fri, 16 Aug 2013 05:29:08 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 1F66011E8102 for <i2rs@ietf.org>; Fri, 16 Aug 2013 05:29:08 -0700 (PDT)
Received: from cpe-174-106-045-093.ec.res.rr.com ([174.106.45.93] helo=RussPC) by da31.namelessnet.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <russw@riw.us>) id 1VAJ9O-0006Hi-Ka; Fri, 16 Aug 2013 05:29:06 -0700
From: Russ White <russw@riw.us>
To: "'Keyur Patel (keyupate)'" <keyupate@cisco.com>, 'Alia Atlas' <akatlas@gmail.com>, i2rs@ietf.org
References: <002c01ce9a10$5f25cc70$1d716550$@riw.us> <4931A85EED76CA48BD52F2D94E7FAB0E088B8EEB@xmb-aln-x09.cisco.com>
In-Reply-To:
Date: Fri, 16 Aug 2013 08:29:08 -0400
Message-ID: <01ef01ce9a7c$35570280$a0050780$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQG4ccFKqIbkfseLSde7M0hLhuHKegKAzhJ1AiSKoLiZnuh1YA==
Content-Language: en-us
X-Antivirus-Scanner: Seems clean. You should still use an Antivirus Scanner
Subject: Re: [i2rs] Results of WG Adoption Call: draft-keyupate-i2rs-bgp-usecases
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: Fri, 16 Aug 2013 12:29:13 -0000

 
> I'm a bit confused at this point about when those decisions were changed,
> and how we intend to proceed.

I have one possible suggestion, after looking at the structure of the drafts
again. What I think we might want to do is to pull the bgp use cases from
draft-white to bolster the bgp use cases draft, moving the bgp use cases
draft to an editor/contributor format (since it already has a lot of co's).
The remaining use cases can be put into a rib uses cases draft, where we can
collect all the various "routing protocol agnostic" use cases. Again, we
could move this to editor/contributor --I'll be happy to hold the editor
baton for this new draft.

There may be some question about what fits where (are all the bgp uses
really limited to bgp? Do we want a separate overlay use cases, or should
these fall into the protocol related draft they work with?), but I think
this is a workable model to get all the use cases organized into a
reasonable set of drafts that can be added to, etc., until the WG gets to
the point of having a 'first set' of use cases on the table. After this
initial batch is actually published, then it's going to be better to
continue with individual drafts for individual use cases, rather than
bis'ing this set, I think.

Thoughts?

Russ