[i2rs] Mirja Kühlewind's No Objection on draft-ietf-i2rs-protocol-security-requirements-06: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Wed, 17 August 2016 08:37 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: i2rs@ietf.org
Delivered-To: i2rs@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D81212D1E6; Wed, 17 Aug 2016 01:37:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147142304704.12189.4149817417200297360.idtracker@ietfa.amsl.com>
Date: Wed, 17 Aug 2016 01:37:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/8NUF6pJ3SFyRjT7TVj6E07WUS84>
Cc: jhaas@pfrc.org, i2rs@ietf.org, i2rs-chairs@ietf.org, draft-ietf-i2rs-protocol-security-requirements@ietf.org
Subject: [i2rs] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-i2rs-protocol-security-requirements-06=3A_=28with_COMMENT?= =?utf-8?q?=29?=
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 17 Aug 2016 08:37:27 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-i2rs-protocol-security-requirements-06: No Objection

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/



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

A few comments:

1) I don't think copy&paste from RFC4949 is necessary. I would recommend
to remove this part and just name the definitions that are needed.

2) The following sentence seems to indicate that the refernce to RFC4949
should be normative.
"The transfer of data via the I2RS protocol has the property of data
integrity described in [RFC4949]."
As I don't think this is needed, I would recommend to rather spell out
the properties here in this sentence. Also, to be honstest I not sure
what this sentence tells me at all. So maybe stating clearing what you
mean (instead of just having the reference) would help anyway.

3) To me it's not really clear why there are several requirments docs
(that also are connected and refer each other; see e.g. section 3.6 and
SEC-REQ-16). The actually context of this doc is only 4 pages (3.1-3.6).
Couldn't those docs be combined to one requiremnet doc?

4) Section 3.1 says:
"The I2RS architecture [I-D.ietf-i2rs-architecture] sets the following
requirements:"
Why is this needed is RFC7921 already sets these requirements?