Re: [i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-protocol-security-requirements-07: (with COMMENT)

Susan Hares <shares@ndzh.com> Thu, 18 August 2016 12:53 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 CD25D12D0B4; Thu, 18 Aug 2016 05:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 b9oh4_0ddW7b; Thu, 18 Aug 2016 05:53:30 -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 043B312DD8F; Thu, 18 Aug 2016 05:52:35 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.167.170;
Date: Thu, 18 Aug 2016 08:51:26 -0400
Message-ID: <vv6q80nviaybxv36ou4d4hil.1471520231205@email.android.com>
Importance: normal
From: Susan Hares <shares@ndzh.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, 'The IESG' <iesg@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_1243475407913100"
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/jJEfEjB8HdLXIrhZGRslYU6qODY>
Cc: 'Jeffrey Haas' <jhaas@pfrc.org>, "i2rs@ietf.org" <i2rs@ietf.org>, "i2rs-chairs@ietf.org" <i2rs-chairs@ietf.org>, "draft-ietf-i2rs-protocol-security-requirements@ietf.org" <draft-ietf-i2rs-protocol-security-requirements@ietf.org>
Subject: Re: [i2rs] Alvaro Retana's No Objection on draft-ietf-i2rs-protocol-security-requirements-07: (with COMMENT)
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: Thu, 18 Aug 2016 12:53:32 -0000

Alvaro:
You are right.  I will remove it in the next revision.  
Sue


Sent via the Samsung Galaxy Note5, an AT&T 4G LTE smartphone
-------- Original message --------From: "Alvaro Retana (aretana)" <aretana@cisco.com> Date: 8/17/16  11:12 PM  (GMT-05:00) To: Susan Hares <shares@ndzh.com>om>, 'The IESG' <iesg@ietf.org> Cc: 'Jeffrey Haas' <jhaas@pfrc.org>rg>, i2rs@ietf.org, i2rs-chairs@ietf.org, draft-ietf-i2rs-protocol-security-requirements@ietf.org Subject: Re: Alvaro Retana's No Objection on
  draft-ietf-i2rs-protocol-security-requirements-07: (with COMMENT) 
On 8/17/16, 10:03 PM, "iesg on behalf of Susan Hares"
<iesg-bounces@ietf.org on behalf of shares@ndzh.com> wrote:

Hi!


>How about the following for the introduction to section 3:
>
>The security for the I2RS protocol requires mutually authenticated I2RS
>clients
>and I2RS agents. The I2RS client and I2RS agent using the I2RS protocol
>MUST
>be able to exchange
>data over a secure transport.  Optionally, the I2RS Client and I2RS agent
>MAY operate
>on a non-secure transport to transfer a specific set of non-confidential
>data 
>
>I think this matches SEC-REQ-08

It does. 

Now that the text is in sync, it makes me wonder why it needs to be
mentioned twice (and not just in the requirements section).

...
> 
>For SEC-REQ-05, I re-read it now and it is redundant.  I changed to:
>
>SEC-REQ-05: Identifier distribution and the loading of these identifiers
>into I2RS agent
> and I2RS Client SHOULD occur outside the I2RS protocol prior to the
> I2RS protocol establishing a connection between I2RS client and I2RS
>agent.
>
> (One mechanism such mechanism is AAA protocols.)
>
>What do you think?

Looks good to me.

Thanks!

Alvaro.