[i2rs] feedback on I2RS use case requirements document
"Susan Hares" <shares@ndzh.com> Tue, 15 March 2016 19:33 UTC
Return-Path: <shares@ndzh.com>
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 EE02212DD31 for <i2rs@ietfa.amsl.com>; Tue, 15 Mar 2016 12:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.638
X-Spam-Level: ***
X-Spam-Status: No, score=3.638 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, RDNS_NONE=0.793] autolearn=no autolearn_force=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 dAMnKHTeYhpy for <i2rs@ietfa.amsl.com>; Tue, 15 Mar 2016 12:33:24 -0700 (PDT)
Received: from hickoryhill-consulting.com (unknown [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48C6B12DD2F for <i2rs@ietf.org>; Tue, 15 Mar 2016 12:33:24 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=74.43.47.30;
From: Susan Hares <shares@ndzh.com>
To: i2rs@ietf.org
Date: Tue, 15 Mar 2016 15:32:45 -0400
Message-ID: <007301d17ef1$740e3000$5c2a9000$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0074_01D17ECF.ECFFC450"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdF+8W4F07/E796IS7Wq+BxpmHkQ3g==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/2A-J6RMDJB4OtLpHQyJta0Nxvao>
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, "'jmh.direct'" <jmh.direct@joelhalpern.com>, 'Alia Atlas' <akatlas@gmail.com>
Subject: [i2rs] feedback on I2RS use case requirements document
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 15 Mar 2016 19:33:26 -0000
The draft-ietf-i2rs-use-case-reqs-summary has not received many reviews the last year. This is a living document that indicates what are valid use cases. As we work on the I2RS protocol, it is important to consider the requirements. Please note that (OC) means out of charter, and (IC) means in-Charter. The chairs are looking for feedback on this document: draft-ietf-i2rs-usecase-reqs-summary/ <https://datatracker.ietf.org/doc/draft-ietf-i2rs-usecase-reqs-summary/> on whether: a) IC requirements are need for phase 1 of the protocol? Other options are to put the requirements in a later phase or dropping the requirement. b) OC-requirements should be "In-charter" in a later phase? Or dropped? c) We are missing any urgent requirements for phase 1 protocol. Jeff and I would appreciate your feedback as we consider the I2rs protocol strawman. Sue Hares