Re: [sidr] I-D Action: draft-ietf-sidr-algorithm-agility-01.txt

Stephen Kent <kent@bbn.com> Mon, 11 July 2011 20:33 UTC

Return-Path: <kent@bbn.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 D131411E8201 for <sidr@ietfa.amsl.com>; Mon, 11 Jul 2011 13:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZ3-yMlAGZ5h for <sidr@ietfa.amsl.com>; Mon, 11 Jul 2011 13:33:25 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id DA26511E80AB for <sidr@ietf.org>; Mon, 11 Jul 2011 13:33:25 -0700 (PDT)
Received: from dhcp89-089-024.bbn.com ([128.89.89.24]:49221) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1QgNAR-0006wp-Uk; Mon, 11 Jul 2011 16:33:24 -0400
Mime-Version: 1.0
Message-Id: <p06240808ca40f463bf6d@[128.89.89.24]>
In-Reply-To: <Pine.WNT.4.64.1107111340180.3744@SMURPHY-LT.columbia.ads.sparta.com>
References: <20110708161252.27961.972.idtracker@ietfa.amsl.com> <42FAFCD2-C5F0-471C-8E90-A6AF0EC17DE6@cisco.com> <AAA28269-7DC5-4E19-A05B-6FAA4DF01388@cisco.com> <p06240800ca40dd314fe7@[192.168.1.10]> <Pine.WNT.4.64.1107111340180.3744@SMURPHY-LT.columbia.ads.sparta.com>
Date: Mon, 11 Jul 2011 14:46:53 -0400
To: Sandra Murphy <Sandra.Murphy@sparta.com>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: "sidr@ietf.org wg" <sidr@ietf.org>
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-algorithm-agility-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: Mon, 11 Jul 2011 20:33:26 -0000

At 1:44 PM -0400 7/11/11, Sandra Murphy wrote:
>>>...
>>
>>Agreed. The CP cites the alg spec (draft-ietf-sidr-rpki-algs). 
>>However, this doc say that the alg specs doc will be updated to 
>>reflect the new alg suite, and to include the timeline for the alg 
>>transition. Once that happens, a failure to comply with the alg 
>>transition procedure described here will imply noncompliance with 
>>the CP.
>
>S---T---R---E---T---C---H???
>
>If the non-compliance with this draft was to fail to update the algs 
>document, then the failure to comply with the procedure would not 
>imply non-compliance with the CP.
>
>--Sandy, speaking as wg chair

Sandy,

But stretching is the usual pre-exercise warm up, and the transition to a
new alg suite will be an exercise, so ... :-).

Stated less circuitously, the CP currently mandates support for the algs
in the Alg Spec. These algs used to be in the CP, but it was decided to
move them into a separate doc, to avoid the need ti change the CP when the
algs change. An early version of the alg transition doc called for updating
the CP to reflect alg transition. But, we moved the algs spec to a separate
doc, so the alg transition now cals for the alg spec to be replaced with
a new doc that calls out the new algs and provides the transition timeline.

We have gone down the path of document modularization and 
indirection, this is where we wound up!

Steve