IETF Logo Mail Archive

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

Sandra Murphy <sandy@tislabs.com> Tue, 08 July 2014 19:02 UTC

Return-Path: <sandy@tislabs.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 521481A02D8 for <sidr@ietfa.amsl.com>; Tue, 8 Jul 2014 12:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level:
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 HQX7ZSLvr2yT for <sidr@ietfa.amsl.com>; Tue, 8 Jul 2014 12:02:03 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) by ietfa.amsl.com (Postfix) with ESMTP id EACFA1A0251 for <sidr@ietf.org>; Tue, 8 Jul 2014 12:02:02 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 842F628B003D; Tue, 8 Jul 2014 15:02:02 -0400 (EDT)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 7C4B61F8032; Tue, 8 Jul 2014 15:02:02 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_8A98BEC9-6D6C-4502-874E-08D9C4C0BD98"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <134C6F51-689E-4BB0-BEF0-8D7F16DA52F9@ieca.com>
Date: Tue, 08 Jul 2014 15:02:02 -0400
Message-Id: <25CFFE15-BA13-488D-92B1-47B53B82AD44@tislabs.com>
References: <20140702153455.10414.45146.idtracker@ietfa.amsl.com> <0CA71605-C46F-4BAE-9646-1AB287549CF8@ieca.com> <0AD801E2-D37B-432C-91FE-7983235468A4@apnic.net> <CANTg3aAga4JsD93yR5uxkWELDiZqQduLLyUtu-MzwkEKcRrPCA@mail.gmail.com> <A435E54D-5CCD-4204-9738-5BA5CE1EF7DE@apnic.net> <CANTg3aBHmHgYC8aabXdszWT5XLTZRpHxXS3GZ9sbCzs+BvroKg@mail.gmail.com> <586E1AFE-895F-40AB-A101-271F07774FA6@apnic.net> <FD21BCCD-5E5C-4CAE-9898-792706FD91BF@tislabs.com> <134C6F51-689E-4BB0-BEF0-8D7F16DA52F9@ieca.com>
To: Sean Turner <TurnerS@ieca.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/sidr/Z8dptjaWxQVZmUklAxW3JVY2HyM
Cc: sidr wg list <sidr@ietf.org>, Sandra Murphy <sandy@tislabs.com>
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-bgpsec-algs-07.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: Tue, 08 Jul 2014 19:02:04 -0000

On Jul 7, 2014, at 9:11 PM, Sean Turner <TurnerS@ieca.com> wrote:

> On Jul 07, 2014, at 19:42, Sandra Murphy <sandy@tislabs.com> wrote:
> 
>> 
>> On Jul 7, 2014, at 7:00 PM, Geoff Huston <gih@apnic.net> wrote:
>>> 
>>> Whats the relationship between this draft and draft-ietf-sidr-rfc6485bis?
>> 
>> So you want to know if bgpsec-algs is updating the original RFC6485 or updating rfc6485bis?
> 
> draft-ietf-sidr-bgpsec-algs adds support for EC public keys & signature formats to RFC 6485 for BGPsec.  If 6485bis is going to be updated to include these changes then draft-ietf-sidr-bgpsec-algs can go away but I didn’t think that was the plan.  Assuming EC algs aren’t incorporated in 6485bis then draft-ietf-sidr-bgpsec-algs needs to update RFC 6485 or any document that obsoletes it.  I’m happy to change the updates header info to “Updates: draft-ietf-sidr-rfc6485bis (once approved)" though if that makes things crystal clear.
> 

The rfc6485bis draft is intended to clean up errors in RFC6485.  That should progress.  Implementations already comply with the corrected text.

The bgpsec-algs draft is adding new algorithms to be used in new RPKI objects and in the bgpsec protocol.  The bgpsec-algs draft should be updating the rfc6485bis document.  As there's still work in progress here, there should be no problem with the order of publication.  I can see that there are several references to RFC6485 in bgpsec-algs that will have to take the final publication of rfc6485bis draft into account, in order to clear up the relationships.

--Sandy, speaking for the wg co-chairs

v2.23.0 | Report a Bug | By Email