Re: [i2rs] Kathleen Moriarty's Discuss on draft-ietf-i2rs-protocol-security-requirements-07: (with DISCUSS and COMMENT)

"Susan Hares" <shares@ndzh.com> Thu, 18 August 2016 01:17 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 97F5312D0BC; Wed, 17 Aug 2016 18:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.738
X-Spam-Level: *
X-Spam-Status: No, score=1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 c5JUAgf1eNah; Wed, 17 Aug 2016 18:17:51 -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 8A82E12B04B; Wed, 17 Aug 2016 18:17:51 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.169.225;
From: "Susan Hares" <shares@ndzh.com>
To: "'Kathleen Moriarty'" <Kathleen.Moriarty.ietf@gmail.com>, "'The IESG'" <iesg@ietf.org>
References: <147146974235.23784.4389421535496134619.idtracker@ietfa.amsl.com>
In-Reply-To: <147146974235.23784.4389421535496134619.idtracker@ietfa.amsl.com>
Date: Wed, 17 Aug 2016 21:16:48 -0400
Message-ID: <013b01d1f8ee$31fa09b0$95ee1d10$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIa7Lz6VgZw6h2A0uGNzOgAA2Ic8Z+7/Lyg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/vzaKA5LPgyaFUWIZv7rOBUqONuA>
Cc: jhaas@pfrc.org, i2rs@ietf.org, i2rs-chairs@ietf.org, draft-ietf-i2rs-protocol-security-requirements@ietf.org
Subject: Re: [i2rs] Kathleen Moriarty's Discuss on draft-ietf-i2rs-protocol-security-requirements-07: (with DISCUSS and 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 01:17:53 -0000

Kathleen: 

Thank you for your comments.  Please see the inline comments below.  I will be uploading a version -08.txt that will resolve some of these comments. 

Sue 

-----Original Message-----
From: Kathleen Moriarty [mailto:Kathleen.Moriarty.ietf@gmail.com] 
Sent: Wednesday, August 17, 2016 5:36 PM
To: The IESG
Cc: draft-ietf-i2rs-protocol-security-requirements@ietf.org; Jeffrey Haas; i2rs-chairs@ietf.org; jhaas@pfrc.org; i2rs@ietf.org
Subject: Kathleen Moriarty's Discuss on draft-ietf-i2rs-protocol-security-requirements-07: (with DISCUSS and COMMENT)

Kathleen Moriarty has entered the following ballot position for
draft-ietf-i2rs-protocol-security-requirements-07: Discuss

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-i2rs-protocol-security-requirements/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks for your work on this draft.  There may be some overlap in points, I tried to minimize them...
----
>Section 3.1:
>
>I don't see any actual requirements for mutual authentication in this section, just requirements for identifiers.  Did I miss something?  

No, there are no additional requirements.  We only have requirements for identifiers.   Do you have a suggestion for improved language. 

> Are all mutual auth schemes in scope?  Are there any considerations for mutual authentication (passwords, keys, etc.)?

All mutual identification schemes are in scope.  Is there a reason we should restrict the mutual authentication schemes to a subset. 

----
>I share the same concern as others for secure transport, but since there are already discusses on that, I have one comment to add to the existing discusses below.

You have a concern regarding the secure transport?  My understanding is that other people had a concern regarding the insecure transport.   I have provide an example of the BGP data feed utilized by http://www.routeviews.org/ project.  


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

> Section 3: 
> Can you clarify the second to last sentence?  Do you mean there are sections that indicate an insecure transport should be used?
>   I2RS allows the use of an
>  insecure transport for portions of data models that clearly indicate
>  insecure transport.

>  Perhaps:
>  I2RS allows the use of an
>  insecure transport for portions of data models that clearly indicate the use of an
>  insecure transport.

Changed to :

I2RS allows the use of an insecure transport for portions of data models that clearly indicate
the use of an insecure transport. Operators deploying I2RS must determine if they want to populate and 
deploy the portions of the data model which use insecure transports.


----
> Section 3.2
> I agree with Alissa's discuss point on the following sentence (that could also be reworded a bit):
>  A non-secure transport can be can be used for publishing telemetry
>  data or other operational state that was specifically indicated to
>  non-confidential in the data model in the Yang syntax.

I would appreciate a recommended set of text or additional explanation on what you would like to see in rewording. 

----
>Section 3.4: In the following text:
>   SEC-REQ-15: The integrity that the message data is not repeated means
>   that I2RS client to I2RS agent transport SHOULD protect against
>   replay attack

>I'm not sure why this just doesn't say:
> SEC-REQ-15: I2RS client to I2RS agent transport SHOULD protect against
 > replay attack
>The additional text doesn't add anything and sounds a bit confusing.

Sue: Is this ok.  It will be changed 
 
----
Nit:

I'm not sure these definitions add any value as they seem to restate the term defined:

>   I2RS protocol data integrity
>
>    The transfer of data via the I2RS protocol has the property of
>    data integrity described in [RFC4949].

Deleted 


>   I2RS component protocols
>
>    Protocols which are combined to create the I2RS protocol.

Please suggest alternative text for this section. 

-----

> I also agree that the definitions from 4949 should be removed.
> Thank you in advance.

These definition have been removed.  I will provide feedback if this removal cause problems in the creation of the protocol.