[i2rs] WG adoption - draft-hares-i2rs-auth-trans-04 (8/17 to 8/31)

"Susan Hares" <shares@ndzh.com> Mon, 17 August 2015 17:42 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 1D5CC1ACDDD for <i2rs@ietfa.amsl.com>; Mon, 17 Aug 2015 10:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.354
X-Spam-Level:
X-Spam-Status: No, score=-96.354 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 X1Br1EHXQAKN for <i2rs@ietfa.amsl.com>; Mon, 17 Aug 2015 10:42:55 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0338B1ACDEA for <i2rs@ietf.org>; Mon, 17 Aug 2015 10:42:54 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.199.108;
From: Susan Hares <shares@ndzh.com>
To: i2rs@ietf.org
Date: Mon, 17 Aug 2015 13:42:52 -0400
Message-ID: <019b01d0d914$24c02590$6e4070b0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_019C_01D0D8F2.9DB192D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdDZEzlbg/lhoVOJTZijTrMq3pCI4Q==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/vwfRrv9ewtzqtRqKvFxuBW07YkI>
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>
Subject: [i2rs] WG adoption - draft-hares-i2rs-auth-trans-04 (8/17 to 8/31)
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: <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: Mon, 17 Aug 2015 17:42:57 -0000

This is a 2 week WG adoption call for the draft-hares-i2rs-auth-trans-04.txt
which provides the security requirements for the I2RS protocol.  

 

To be adopted, this draft does not need to be perfect, but a good direction
for the I2RS protocol security. 

 

Please note that Juergen's review of this draft has the following feedback:

.       Requirements 1, 2, 5, 6, 7, 9, 11, 13, 14, 15, 16, 18, 19, 20 - were
ok, 

.       Editorial requirements 3 and 4 need clarifications on words, and
requirement 10 is ambiguous, and 

.       Requirements 8, 12, and the multiple message sequence (was req-17)
are not security protocols, 

.       Technical question: Why should we support an insecure protocol. 

 

A security directorate reviewer will review this draft starting on 8/20.  I
will post these reviews and the document changes.  Please suggest changes to
requirement 3, 4, and 10; and if I2RS should support an insecure protocol. 

 

Once we get the security reviewers feedback on 8, 12, and the multiple
messages - I will post the feedback and we'll discuss real time. 

 

Sue Hares