IETF Logo Mail Archive

[sidr] comments on draft-ymbk-sidr-transfer-01???

Sandra Murphy <sandy@tislabs.com> Thu, 08 October 2015 18:56 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 3429F1A9235 for <sidr@ietfa.amsl.com>; Thu, 8 Oct 2015 11:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yFXwCB-ea6ww for <sidr@ietfa.amsl.com>; Thu, 8 Oct 2015 11:56:43 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB3791A916E for <sidr@ietf.org>; Thu, 8 Oct 2015 11:56:43 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 2B84F28B0041 for <sidr@ietf.org>; Thu, 8 Oct 2015 14:56:43 -0400 (EDT)
Received: from [IPv6:::1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id CA5A11F8035; Thu, 8 Oct 2015 14:56:42 -0400 (EDT)
From: Sandra Murphy <sandy@tislabs.com>
X-Pgp-Agent: GPGMail 2.5.1
Content-Type: multipart/signed; boundary="Apple-Mail=_5F0B96F1-2C53-41FC-B440-604F4562B07E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Date: Thu, 08 Oct 2015 14:56:33 -0400
Message-Id: <C881A1D8-ADD9-4FE9-90D3-3C6DAA57C5EB@tislabs.com>
To: sidr wg list <sidr@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/t5XCXHskPPbEUxgIRW-nDnRVfnI>
Cc: Sandra Murphy <sandy@tislabs.com>
Subject: [sidr] comments on draft-ymbk-sidr-transfer-01???
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: <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: Thu, 08 Oct 2015 18:56:45 -0000

The draft draft-ietf-sidr-rpki-validation-reconsidered speaks forcefully of the potential for damage if a certificate over claims, i.e., claims more resources than its parent.  The draft discusses how that could result from a failure of timing in a transfer of resources.

In a presentation in the November 2014 IETF session on this topic, it was suggested that discussion of "a standard procedure for certificate management during resource transfer” and "current CA operational procedures for managing transfers” would help in the reconsideration of the validation algorithm.

A draft was submitted and discussed at the last meeting.  https://tools.ietf.org/html/draft-ymbk-sidr-transfer  But no comments have been received.

This is an important topic, folks, and deserves our attention.

Please do read the draft and comment.

—Sandy

v2.23.0 | Report a Bug | By Email