[sidr] Time frame for changing RPSTIR to the new validation algorithm

Declan Ma <madi@zdns.cn> Mon, 08 August 2016 14:59 UTC

Return-Path: <madi@zdns.cn>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ABDDB12D639 for <sidr@ietfa.amsl.com>; Mon, 8 Aug 2016 07:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id cwxTTULAecUm for <sidr@ietfa.amsl.com>; Mon, 8 Aug 2016 07:59:14 -0700 (PDT)
Received: from gw1.turbomail.org (gw1.turbomail.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B1BB12D0CB for <sidr@ietf.org>; Mon, 8 Aug 2016 07:59:14 -0700 (PDT)
X-TM-DID: 8d50bd7334eaca99b237bbf63fe25e00
From: Declan Ma <madi@zdns.cn>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Message-Id: <58E87CF4-2694-474F-BD48-DAB6E2BA78E4@zdns.cn>
Date: Mon, 08 Aug 2016 22:54:55 +0800
To: sidr <sidr@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/Sw52v86B_BUl_-BxMMEbICVRHh8>
Subject: [sidr] Time frame for changing RPSTIR to the new validation algorithm
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 08 Aug 2016 14:59:18 -0000


I recall Tim has suggested a schedule for transition to the new validation algorithm during Berlin meeting. His proposal is to mandate RP support for the new all 6 months after the doc is published as an RFC.

My team is now responsible for RPSTIR update. 

I am afraid that the proposal is sorta aggressive. IMHO, six-months after publication of the RFC may be too soon. Although this WG has been through discussions of the validation-reconsidered, but the conclusion was just reached. 

This is really a fundamental change to both RP and CA, I anticipate we need more time to have RP software code changed and thoroughly tested, to accommodate the new validation procedures. 

Anyway, we are evaluating the time frame,trying to give absolute dates as soon as possible.

BTW, OID issue has not been yet with IANA feedbacks. We can’t be sure how long it will take to go through the IESG approval process, incurring uncertainty. I am not reassured whether it is prudent to get started with RPSTIR update right away.   

I am therefore looking forwards to seeing more discussions and comments in this thread, especially from other RPKI implementers.