Re: [sidr] addendum

Eric Osterweil <eosterweil@verisign.com> Mon, 14 November 2011 06:06 UTC

Return-Path: <eosterweil@verisign.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 B35C611E820B for <sidr@ietfa.amsl.com>; Sun, 13 Nov 2011 22:06:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level:
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 58XKvOSNlpKk for <sidr@ietfa.amsl.com>; Sun, 13 Nov 2011 22:06:01 -0800 (PST)
Received: from exprod6og102.obsmtp.com (exprod6og102.obsmtp.com [64.18.1.183]) by ietfa.amsl.com (Postfix) with ESMTP id EAF3A11E8207 for <sidr@ietf.org>; Sun, 13 Nov 2011 22:06:00 -0800 (PST)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob102.postini.com ([64.18.5.12]) with SMTP ID DSNKTsCvxh8EYOubuQmyKSxP/XWQ5SqY1jZx@postini.com; Sun, 13 Nov 2011 22:06:01 PST
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id pAE65vnc028523; Mon, 14 Nov 2011 01:05:57 -0500
Received: from dul1eosterwe-m1.vcorp.ad.vrsn.com ([10.100.0.69]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Nov 2011 01:05:56 -0500
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Osterweil <eosterweil@verisign.com>
In-Reply-To: <p06240802cae65275fc1b@[130.129.18.170]>
Date: Mon, 14 Nov 2011 14:05:56 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <72FA123B-43C9-44D5-A3BC-7DF71984662E@verisign.com>
References: <p06240802cae65275fc1b@[130.129.18.170]>
To: Stephen Kent <kent@bbn.com>
X-Mailer: Apple Mail (2.1084)
X-OriginalArrivalTime: 14 Nov 2011 06:05:57.0251 (UTC) FILETIME=[79B21D30:01CCA293]
Cc: sidr@ietf.org
Subject: Re: [sidr] addendum
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: Mon, 14 Nov 2011 06:06:01 -0000

On Nov 14, 2011, at 1:21 PM, Stephen Kent wrote:

> Eric,
> 
> I forgot to address an issue that you mentioned in a previous message,
> and that relates to the alg agility doc.
> 
> The alg spec for the RPKI is separate from the CP, precisely so that we could change the algs without changing the CP. So, when the alg spec is replaced to introduce the next set of algs, we do not plan to re-issue the CP. As a result, the cert policy OID will not change as a side effect of the alg transition.
> 
> I discussed this assumption re OID stability with several PKI experts today, and they agreed that there is no need to change the policy OID.
> 
> i mention this because I recall that a previous message touched on this question, and I realize that the alg agility doc failed to mention this.  The next rev will make this explicit.

Ah, very kewl.  Thanks,

Eric