[appsdir] Fwd: Last Call: <draft-ietf-i2rs-protocol-security-requirements-06.txt> (I2RS Security Related Requirements) to Informational RFC
Eliot Lear <lear@cisco.com> Tue, 02 August 2016 10:15 UTC
Return-Path: <lear@cisco.com>
X-Original-To: appsdir@ietfa.amsl.com
Delivered-To: appsdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD9FC12D08C for <appsdir@ietfa.amsl.com>; Tue, 2 Aug 2016 03:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 1baCb1u04rh7 for <appsdir@ietfa.amsl.com>; Tue, 2 Aug 2016 03:15:43 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0426812B049 for <appsdir@ietf.org>; Tue, 2 Aug 2016 03:15:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10139; q=dns/txt; s=iport; t=1470132943; x=1471342543; h=references:subject:to:from:message-id:date:mime-version: in-reply-to; bh=c/UIWhsEHZ5UVcnzvmNICRhH6DvyeWeQtd8U2m6uHTg=; b=ZATeOxq8BRoizZVXAX6lF2Tin7Sp4B9dLOAvxy3bZBkXSl8cqj+t+/pL WTR32bii0Z9e82UOwyQeEMn6huWtVL35t6cFb/fXWxOwpkl0gnhFKkUwz LN/unC1UYVoaif/c3jyMpm7OiqFTHKa+bO5+IXutdKc6XKQSSQLIdYftU U=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CdCACJcaBX/xbLJq1chBsqUrslJoV3AoF/AQEBAQEBXhwLhF8GI0sbRgcCAkYHCgYKAwYCAQGILQ6xA5ADAQEBAQEBAQMBAQEBAQETCQWIIoJVh0GCWgWZM4M6gXBuiGeBa4Ragw4jhUmMMIN3VIJFgTc6MogXAQEB
X-IronPort-AV: E=Sophos;i="5.28,459,1464652800"; d="asc'?eml'208?scan'208,208";a="639048399"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Aug 2016 10:15:41 +0000
Received: from [10.61.168.28] ([10.61.168.28]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u72AFerA025091 for <appsdir@ietf.org>; Tue, 2 Aug 2016 10:15:40 GMT
References: <20160801144052.32557.44206.idtracker@ietfa.amsl.com>
To: "appsdir@ietf.org" <appsdir@ietf.org>
From: Eliot Lear <lear@cisco.com>
X-Forwarded-Message-Id: <20160801144052.32557.44206.idtracker@ietfa.amsl.com>
Message-ID: <0aab7300-9c3a-97a0-99c6-b6e60847df63@cisco.com>
Date: Tue, 02 Aug 2016 12:15:39 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160801144052.32557.44206.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="9cwKUAtDbOb6MALH0RoKxJjgAcCd3CbCV"
Archived-At: <https://mailarchive.ietf.org/arch/msg/appsdir/eU2YfpiT4Fq0biVtwC7V3bne204>
Subject: [appsdir] Fwd: Last Call: <draft-ietf-i2rs-protocol-security-requirements-06.txt> (I2RS Security Related Requirements) to Informational RFC
X-BeenThere: appsdir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Apps Area Review List <appsdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/appsdir>, <mailto:appsdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/appsdir/>
List-Post: <mailto:appsdir@ietf.org>
List-Help: <mailto:appsdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/appsdir>, <mailto:appsdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 10:15:45 -0000
Would anyone care to review draft-ietf-i2rs-protocol-security-requirements? I think the key thing here is to confirm that none of the requirements are impracticable in an application context. This is a pretty short read. Eliot
--- Begin Message ---The IESG has received a request from the Interface to the Routing System WG (i2rs) to consider the following document: - 'I2RS Security Related Requirements' <draft-ietf-i2rs-protocol-security-requirements-06.txt> as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2016-08-15. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This presents security-related requirements for the I2RS protocol for mutual authentication, transport protocols, data transfer and transactions. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/ballot/ No IPR declarations have been submitted directly on this I-D.--- End Message ---