Re: [sidr] Stephen Farrell's No Objection on draft-ietf-sidr-rpsl-sig-12: (with COMMENT)

Stephen Kent <kent@bbn.com> Fri, 20 May 2016 12:53 UTC

Return-Path: <kent@bbn.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99EF812D916 for <sidr@ietfa.amsl.com>; Fri, 20 May 2016 05:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.627
X-Spam-Level:
X-Spam-Status: No, score=-4.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FSL_HELO_HOME=1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham 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 42c3Lc81L0J9 for <sidr@ietfa.amsl.com>; Fri, 20 May 2016 05:53:21 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BEEC12B03D for <sidr@ietf.org>; Fri, 20 May 2016 05:53:21 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:36852 helo=COMSEC.fios-router.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1b3jvc-000Dj3-9I for sidr@ietf.org; Fri, 20 May 2016 08:53:20 -0400
From: Stephen Kent <kent@bbn.com>
To: sidr@ietf.org
References: <20160519123348.17368.83837.idtracker@ietfa.amsl.com>
Message-ID: <573F08C0.1020202@bbn.com>
Date: Fri, 20 May 2016 08:53:20 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160519123348.17368.83837.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/cBbBxhsk5PquL87Xsjov3Wyjbcc>
Subject: Re: [sidr] Stephen Farrell's No Objection on draft-ietf-sidr-rpsl-sig-12: (with COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 12:53:23 -0000

Stephen, et al.,

A couple of observations about the topic of certs used to verify RPSL sigs:

     - the title of the I-D says that it relies upon the RPKI, and, as 
currently
written, it mandates use of RPKI certs. So, using certs from a different PKI
would require a re-write. Also, the security of the system would be reduced
if other certs were employed, wrt verification of assertions about address
space and ASN holdings. So, I don't think it's appropriate to suggest 
alternative
PKIs. I also note that the text on page 3 that says "equivalent 
functionality can
be achieved" using an alternative PKI is questionable. Merely having 
3379 extensions
in a cert does not mean that all of the other security-relevant elements 
of the RPKI
accrue. (Also, there is a typo: certificate authority" -> "certification 
authority")

     - if one is using RPKI EE certs, as currently mandated, then the 
single use
requirement (which is imposed on CAs, but RPs are not required to 
verify) applies.
Deliberate re-use of a cert would mean that the CA violated the cert 
policy, and
thus the cert ought not contain the RPKI policy ID, etc. Also, the 
Security Considerations
section of the I-D refers to 6487, which is appropriate only if we're 
discussing RPKI certs.

     - The phrase "money-in-the-middle" is cute, but Randy's terminology 
is not widely
adopted. I suggest using the more conventional terminology that a wider 
range of
readers will recognize.

Steve