Re: [secdir] [sidr] Review of draft-ietf-sidr-bgpsec-pki-profiles-19

Rob Austein <sra@hactrn.net> Sun, 01 January 2017 19:15 UTC

Return-Path: <sra@hactrn.net>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C422126B6D; Sun, 1 Jan 2017 11:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1, 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 CTB72VH1oXOQ; Sun, 1 Jan 2017 11:15:55 -0800 (PST)
Received: from khatovar.hactrn.net (khatovar.hactrn.net [IPv6:2001:418:8006::30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DD9312941E; Sun, 1 Jan 2017 11:15:55 -0800 (PST)
Received: from minas-ithil.hactrn.net (c-73-47-197-23.hsd1.ma.comcast.net [73.47.197.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nargothrond.hactrn.net", Issuer "Grunchweather Associates" (not verified)) by khatovar.hactrn.net (Postfix) with ESMTPS id 5223B1399E; Sun, 1 Jan 2017 19:15:53 +0000 (UTC)
Received: from minas-ithil.hactrn.net (localhost [IPv6:::1]) by minas-ithil.hactrn.net (Postfix) with ESMTP id ADABC4576F68; Sun, 1 Jan 2017 14:16:11 -0500 (EST)
Date: Sun, 01 Jan 2017 14:16:11 -0500
From: Rob Austein <sra@hactrn.net>
To: Yaron Sheffer <yaronf@gmx.com>
In-Reply-To: <148328799488.25220.17994465220699555250.idtracker@ietfa.amsl.com>
References: <148328799488.25220.17994465220699555250.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20170101191611.ADABC4576F68@minas-ithil.hactrn.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/g8F47BIffBPZPvIQ7zFFyp9LlMo>
Cc: sidr@ietf.org, draft-ietf-sidr-bgpsec-pki-profiles.all@ietf.org, secdir@ietf.org
Subject: Re: [secdir] [sidr] Review of draft-ietf-sidr-bgpsec-pki-profiles-19
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jan 2017 19:15:56 -0000

At Sun, 01 Jan 2017 08:26:34 -0800, Yaron Sheffer wrote:
> 
> Reviewer: Yaron Sheffer
> Review result: Has Nits
> 
> * 3.1.1: The serial number in RFC 6487 is still a real, unique serial
> number that uniquely identifies the certificate. Here it is used as
> something other than a serial number, which is explicitly NOT unique,
> and the CA is left to decide how to make it unique in the face of
> potentially repeating BGP IDs. If this is not a real issue (e.g.
> because duplicate IDs are rare and never within a RIR), please say
> so.

Er, I suspect you're confusing serial numbers with serial numbers.

3.1.1 of this draft is talking about the id-at-serialNumber attribute
in the Subject field (RFC 5280 4.1.2.6, naming attribute type
X520SerialNumber), a different thing entirely from the certificate
Serial Number (RFC 5280 4.1.2.2, type CertificateSerialNumber).  Just
to make things more interesting, both are called serialNumber in
different contexts.  Clear as mud, I know.

So, agreed that this probably does need clarification, but perhaps not
quite the clarification you thought it needed.