[Sidrops] Alissa Cooper's Discuss on draft-ietf-sidrops-rtr-keying-03: (with DISCUSS and COMMENT)

Alissa Cooper <alissa@cooperw.in> Wed, 23 January 2019 19:52 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C01512785F; Wed, 23 Jan 2019 11:52:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-sidrops-rtr-keying@ietf.org, Chris Morrow <morrowc@ops-netman.net>, sidrops-chairs@ietf.org, morrowc@ops-netman.net, sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.90.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154827316130.7453.12140820828793016275.idtracker@ietfa.amsl.com>
Date: Wed, 23 Jan 2019 11:52:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/znIXKfLCxK1Qk0i73_8jTLROlIg>
Subject: [Sidrops] Alissa Cooper's Discuss on draft-ietf-sidrops-rtr-keying-03: (with DISCUSS and COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2019 19:52:41 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-sidrops-rtr-keying-03: 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-sidrops-rtr-keying/



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

As this is a BCP, I don't understand why transport encryption of the private
key is not normatively required. Could you explain?


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

Given that this document is ostensibly specifying a "best" current practice, I
would have expected a clearer expression of preference for the router-driven
method over the operator-driven method, e.g., something like BGPsec-speaking
routers MUST implement the router-driven method and MAY implement the
operator-driven method. Or if there is some exception case that makes that MUST
problematic, it would at least be good to emphasize which one of these is
actually "best" from a security perspective, even though the other one is being
specified and we know will be used.

Nit in Section 1:

s/gritty details/details of the BGPsec protocol/