Re: [sidr] I-D Action: draft-ietf-sidr-bgpsec-algs-01.txt

Sean Turner <turners@ieca.com> Wed, 28 March 2012 13:44 UTC

Return-Path: <turners@ieca.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 3B7A421F88A8 for <sidr@ietfa.amsl.com>; Wed, 28 Mar 2012 06:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.272
X-Spam-Level:
X-Spam-Status: No, score=-102.272 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIxjWbWdEdUh for <sidr@ietfa.amsl.com>; Wed, 28 Mar 2012 06:44:09 -0700 (PDT)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [67.18.22.93]) by ietfa.amsl.com (Postfix) with ESMTP id EE25621F889A for <sidr@ietf.org>; Wed, 28 Mar 2012 06:44:08 -0700 (PDT)
Received: by gateway05.websitewelcome.com (Postfix, from userid 5007) id 1F01B1F0E25C9; Wed, 28 Mar 2012 08:44:08 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway05.websitewelcome.com (Postfix) with ESMTP id 147121F0E2597 for <sidr@ietf.org>; Wed, 28 Mar 2012 08:44:08 -0500 (CDT)
Received: from [198.180.150.230] (port=58433 helo=dhcp-2594.meeting.ietf.org) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1SCtAV-0005H0-4I; Wed, 28 Mar 2012 08:44:07 -0500
Message-ID: <4F7315A4.5010507@ieca.com>
Date: Wed, 28 Mar 2012 15:44:04 +0200
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <20111205182117.8883.99030.idtracker@ietfa.amsl.com> <CAL9jLabvho9T6omP7Y0ZiU0OXR1J40E0Ar6+xE1_0+kApDD3NA@mail.gmail.com>
In-Reply-To: <CAL9jLabvho9T6omP7Y0ZiU0OXR1J40E0Ar6+xE1_0+kApDD3NA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.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:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: v230.vpn.iad.rg.net (dhcp-2594.meeting.ietf.org) [198.180.150.230]:58433
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: sidr-chairs@ietf.org, sidr@ietf.org
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-bgpsec-algs-01.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 28 Mar 2012 13:44:13 -0000

Chris,

I think this draft should probably go in a cluster.  There are normative 
references to draft-sidr-bgpsec-pki-profiles and 
draft-ietf-sidr-bgpsec-protocol.  However, you could WGLC this draft 
because unless you're planning on changing the alg (ECDSA) there's 
really no dependencies on the other drafts.  In other words, if you 
change bgpsec or the cert profile to add/remove fields them really 
doesn't affect this draft.  It could then just wait on the protocol to 
go forward in a sensible cluster.

There's two tweaks I'd do before a WGLC and barring any other changes:

1. s3: r/The RSA key pairs/The key pairs

I'd do this because RSA might not be the alg used in the RPKI later. 
It's helping to future proof this draft.

2. s11.1: Update references to [ID.sidr-res-cert-profile] and 
[ID.sidr-rpki-algs] to the appropriate RFC #s.

Why don't I go ahead and post a new version to fix these two points and 
then you & Sandy can decide whether to start the WGLC button.

spt

On 3/28/12 2:23 PM, Christopher Morrow wrote:
> Sean,
> This document seems settled, should we WGLC this in the near future?
>
> -chris
> <cochair>
>
> On Mon, Dec 5, 2011 at 1:21 PM,<internet-drafts@ietf.org>  wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing Working Group of the IETF.
>>
>>         Title           : BGP Algorithms, Key Formats,&  Signature Formats
>>         Author(s)       : Sean Turner
>>         Filename        : draft-ietf-sidr-bgpsec-algs-01.txt
>>         Pages           : 7
>>         Date            : 2011-12-05
>>
>>    This document specifies the algorithms, algorithms' parameters,
>>    asymmetric key formats, asymmetric key size and signature format used
>>    in BGPSEC (Border Gateway Protocol Security).  This document updates
>>    the Profile for Algorithms and Key Sizes for use in the Resource
>>    Public Key Infrastructure (draft-ietf-sidr-rpki-algs).
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-sidr-bgpsec-algs-01.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-sidr-bgpsec-algs-01.txt
>>
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>