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

"Russ White" <russw@riw.us> Fri, 16 August 2013 01:20 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 1747011E8213 for <i2rs@ietfa.amsl.com>; Thu, 15 Aug 2013 18:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Ldyf-0vwkJ06 for <i2rs@ietfa.amsl.com>; Thu, 15 Aug 2013 18:20:27 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id 6CBF521F9A57 for <i2rs@ietf.org>; Thu, 15 Aug 2013 18:20:23 -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 1VA8iD-0007cg-L2; Thu, 15 Aug 2013 18:20:22 -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: <4931A85EED76CA48BD52F2D94E7FAB0E088B8EEB@xmb-aln-x09.cisco.com>
Date: Thu, 15 Aug 2013 21:20:21 -0400
Message-ID: <007401ce9a1e$c8aed340$5a0c79c0$@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: AQKAzhJ12mrO6x8SKcYNuKCIa2z885gyoHgQ
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 01:20:33 -0000

> IMHO it would be best to keep BGP specific use cases into a separate
draft.

Okay --so... That leaves us with the next question --the use cases that
aren't BGP centric --do we try and continue a draft with just those one or
two, or... ?? 

I don't really understand what the situation is at this point. My
understanding of the discussion on list and in person from way back were
that the draft I was editing and the BGP use cases draft were going to be
merged, not that one was going to subsume the other completely, leaving the
remainder out of the picture entirely... In fact, the WG originally decided
to only use one use cases draft as it's basis for work until the use cases
in that first draft were covered by requirements/etc. It now sounds like
we've changed that direction completely, and we're back to boiling the
ocean.

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

:-)

Russ