Re: [i2rs] Comments on draft-white-i2rs-use-case-02
"Susan Hares" <shares@ndzh.com> Wed, 19 February 2014 01:48 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C4461A042B for <i2rs@ietfa.amsl.com>; Tue, 18 Feb 2014 17:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4R0xxS9PKxws for <i2rs@ietfa.amsl.com>; Tue, 18 Feb 2014 17:48:05 -0800 (PST)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id E005E1A02D0 for <i2rs@ietf.org>; Tue, 18 Feb 2014 17:48:04 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=64.112.195.202;
From: Susan Hares <shares@ndzh.com>
To: 'Jeffrey Haas' <jhaas@pfrc.org>, i2rs@ietf.org
References: <20140217232512.GB445@pfrc>
In-Reply-To: <20140217232512.GB445@pfrc>
Date: Tue, 18 Feb 2014 20:47:55 -0500
Message-ID: <015701cf2d14$9c6a6d10$d53f4730$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLCr6nQqztkbSPqjFegOnK62eaq0JjUwKow
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: http://mailarchive.ietf.org/arch/msg/i2rs/ynDe9A7EQW_5cGrUVJYIkFYZoWk
Cc: draft-white-i2rs-use-case@tools.ietf.org
Subject: Re: [i2rs] Comments on draft-white-i2rs-use-case-02
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 19 Feb 2014 01:48:06 -0000
Jeff: Thanks for the suggestion on the distributed reaction to the network, and catching /IRS/I2RS/. Could you just give me a short example of what you mean by enumerate the capabilities? Thanks, Sue -----Original Message----- From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Jeffrey Haas Sent: Monday, February 17, 2014 6:25 PM To: i2rs@ietf.org Cc: draft-white-i2rs-use-case@tools.ietf.org Subject: [i2rs] Comments on draft-white-i2rs-use-case-02 A few quick comments on draft -02: In section 2 (Distributed Reaction to Network Based Attacks), there is an implicit knowledge that the router in question supports policy based routing. While an extremely common feature these days, it's not guaranteed to be there. I'd suggest that this capability needs to be reported to I2RS. The document still mentions IRS. :-) The summaries of capabilities and interactions are nice, but it'd be helpful, I think, to enumerate them. This would let common requirements be a bit more visible across the use cases. -- Jeff _______________________________________________ i2rs mailing list i2rs@ietf.org https://www.ietf.org/mailman/listinfo/i2rs
- [i2rs] Comments on draft-white-i2rs-use-case-02 Jeffrey Haas
- Re: [i2rs] Comments on draft-white-i2rs-use-case-… Susan Hares
- Re: [i2rs] Comments on draft-white-i2rs-use-case-… Jeffrey Haas
- Re: [i2rs] Comments on draft-white-i2rs-use-case-… Susan Hares