IETF Logo Mail Archive

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

"Alvaro Retana (aretana)" <aretana@cisco.com> Thu, 18 August 2016 03:12 UTC

Return-Path: <aretana@cisco.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 6306A12D85C; Wed, 17 Aug 2016 20:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.768
X-Spam-Level:
X-Spam-Status: No, score=-15.768 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, 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 m9UcAPfrnZ59; Wed, 17 Aug 2016 20:12:55 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BE7012D857; Wed, 17 Aug 2016 20:12:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1191; q=dns/txt; s=iport; t=1471489975; x=1472699575; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=nUyAcejGRPLAGau6Tl5+qEJ/LnG/12ZQ/baAol96RtQ=; b=IM74hr4ndLuGu/xqQAUJbOQU8opBvlzD39Y9LR3yF1QYToCN1ln/0QUv FyaCn6gdS/k+pz7f8ThAn8Hfj+RDRbaV7JWkvc2HioF5KJf+ejnh0QGRA uWlwVesxh/5Y2gt8tpsCYepCpwdR5wALiLqhHlpiA6Jbm9ib34mGbRXBg U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CJAgAsJ7VX/5ldJa1eg0SBUge1RYIPgX2GHQKBZzgUAgEBAQEBAQFeJ4RfAQU6PxACAQgOKAULMiUCBAEJBAWIMb4dAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIYqhE2KGwEEk32FRwGPHYFriA6FUJAyAR42gkWBNW6GLn8BAQE
X-IronPort-AV: E=Sophos;i="5.28,537,1464652800"; d="scan'208";a="312254759"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Aug 2016 03:12:54 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u7I3CsHp001914 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 18 Aug 2016 03:12:54 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 17 Aug 2016 22:12:53 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Wed, 17 Aug 2016 22:12:53 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Susan Hares <shares@ndzh.com>, 'The IESG' <iesg@ietf.org>
Thread-Topic: Alvaro Retana's No Objection on draft-ietf-i2rs-protocol-security-requirements-07: (with COMMENT)
Thread-Index: AQHR+Plx0ThSsjCXkUiHItVMbeJWy6BOBWuAgABWnYD//67PgA==
Date: Thu, 18 Aug 2016 03:12:53 +0000
Message-ID: <D3DA9162.13A909%aretana@cisco.com>
References: <147148520752.23682.12743310118152055665.idtracker@ietfa.amsl.com> <000001d1f8f9$490933a0$db1b9ae0$@ndzh.com> <D3DA8AFF.13A8E7%aretana@cisco.com> <000a01d1f8fd$157d1bb0$40775310$@ndzh.com>
In-Reply-To: <000a01d1f8fd$157d1bb0$40775310$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.173.92]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E9FEA4FA474C5144873519136BB30EFF@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/W_YkphRnTaIiottisetnkHdKZoE>
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 03:12:56 -0000

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.

v2.23.0 | Report a Bug | By Email