Re: [sidr] I-D Action: draft-ietf-sidr-bgpsec-pki-profiles-08.txt

Sean Turner <TurnerS@ieca.com> Thu, 30 October 2014 13:29 UTC

Return-Path: <TurnerS@ieca.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 457651AD1FE for <sidr@ietfa.amsl.com>; Thu, 30 Oct 2014 06:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.557
X-Spam-Level:
X-Spam-Status: No, score=-1.557 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FSL_HELO_BARE_IP_2=0.01] autolearn=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 9a5kdQM62RtH for <sidr@ietfa.amsl.com>; Thu, 30 Oct 2014 06:29:54 -0700 (PDT)
Received: from gateway07.websitewelcome.com (gateway07.websitewelcome.com [69.41.242.21]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73A441AD190 for <sidr@ietf.org>; Thu, 30 Oct 2014 06:29:53 -0700 (PDT)
Received: by gateway07.websitewelcome.com (Postfix, from userid 5007) id C0D1216ED4532; Thu, 30 Oct 2014 08:29:52 -0500 (CDT)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway07.websitewelcome.com (Postfix) with ESMTP id AFA9016ED450A for <sidr@ietf.org>; Thu, 30 Oct 2014 08:29:52 -0500 (CDT)
Received: from [173.73.121.234] (port=52726 helo=192.168.1.7) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <TurnerS@ieca.com>) id 1XjpnT-0005CK-Ax for sidr@ietf.org; Thu, 30 Oct 2014 08:29:51 -0500
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Sean Turner <TurnerS@ieca.com>
In-Reply-To: <m2r3yjhxav.wl%randy@psg.com>
Date: Thu, 30 Oct 2014 09:29:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE881FCB-CCB4-4947-A1DE-4E0DFBE89727@ieca.com>
References: <20140813004442.10560.45299.idtracker@ietfa.amsl.com> <B97A6E28-4EDB-4EC5-B8DA-9803C7B21900@ieca.com> <4556FA63-A6FD-471B-93FD-51D748C94EE8@tislabs.com> <8BFAD7DD-7CEA-4720-86BB-09407C6C543D@ieca.com> <m2r3yjhxav.wl%randy@psg.com>
To: sidr wg list <sidr@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 173.73.121.234
X-Exim-ID: 1XjpnT-0005CK-Ax
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (192.168.1.7) [173.73.121.234]:52726
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 3
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/1_TeX7HaAbG5YPJplJOVR_iUfV0
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-bgpsec-pki-profiles-08.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 30 Oct 2014 13:29:56 -0000

On Oct 08, 2014, at 02:48, Randy Bush <randy@psg.com> wrote:

>> Yep the issuer always gets to determine the subject name as per RFC
>> 6487 s4.5 so how about we just leave that bit out and make that
>> sentence a note:
>> 
>>  Note that more than one certificate can be issued to
>>  an AS (i.e., more than one router can get a certificate
>>  for the AS and hence the private key is shared among
>>  more than one router).
>> 
>> I guess the follow on question is whether we also point out that a
>> router could support more than one AS but having key pairs for each
>> AS:
>> 
>>  Also note that routers can support multiple ASs with
>>  separate keys pairs one for each AS.
>> 
>> or something like that?
> 
> i think i understand it and it makes sense.  though i would tersify it
> to
> 
>   Rrouters can support multiple ASs with
>   separate keys pairs, one for each AS
> 
> :)
> 
> randy

I let this one sit for a while and hearing no objections I went ahead and made the changes in the version on github:
https://github.com/seanturner/draft-ietf-sidr-bgpsec-pki-profiles/blob/master/draft-ietf-sidr-bgpsec-pki-profiles-09.txt

I’ll submit it to the IETF once the submission window reopens.

To the best of my knowledge this resolves the last remaining technical issue.

spt