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

Jon Mitchell <jrmitche@puck.nether.net> Tue, 30 July 2013 11:49 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 4A0AF21F93F3 for <i2rs@ietfa.amsl.com>; Tue, 30 Jul 2013 04:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level:
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=0.401, 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 lB1tbNzae6n7 for <i2rs@ietfa.amsl.com>; Tue, 30 Jul 2013 04:49:44 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 621CD21F8EFE for <i2rs@ietf.org>; Tue, 30 Jul 2013 04:49:44 -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 r6UBng4F029552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Jul 2013 07:49:42 -0400
Received: (from jrmitche@localhost) by puck.nether.net (8.14.7/8.14.7/Submit) id r6UBngla029551; Tue, 30 Jul 2013 07:49:42 -0400
Date: Tue, 30 Jul 2013 07:49:42 -0400
From: Jon Mitchell <jrmitche@puck.nether.net>
To: Thomas Nadeau <tnadeau@lucidvision.com>
Message-ID: <20130730114942.GA29393@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> <20130729130229.GA20218@puck.nether.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20130729130229.GA20218@puck.nether.net>
X-IMAPbase: 1365870647 0000000001
X-UID: 1
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]); Tue, 30 Jul 2013 07:49:43 -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: Tue, 30 Jul 2013 11:49:45 -0000

On 29/07/13 09:02 -0400, Jon Mitchell wrote:
> 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.

Based on my discussion with Keyur in person - I'm satisfied he will
work with the the other authors to integrate WG relevant use cases
from draft-white-i2rs-use-case-00 draft into the document if adopted,
so I now support it's adoption.  Here is my view on the differences
between the drafts:

I'd like to see Sections 3,5,6 from the white draft integrated.
Section 3 overlaps some with content in keyupdate but does not specify
using FlowSpec routes for DDoS diversion; presumably you could divert
traffic directly through i2rs messaging (if such a thing will exist).
Sections 2/7 are basically covered by the keyupdate doc, although
certainly useful text could be merged.  Use case in section 4 is not
on my list, maybe others feel strongly for it. 

Thanks,

-Jon