Re: [sidr] revising Section 7.2 of RFC 6487

Stephen Kent <kent@bbn.com> Tue, 28 June 2016 17:39 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 DFBD212B012 for <sidr@ietfa.amsl.com>; Tue, 28 Jun 2016 10:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.627
X-Spam-Level:
X-Spam-Status: No, score=-4.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FSL_HELO_HOME=1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 2U3i-3dmhXuY for <sidr@ietfa.amsl.com>; Tue, 28 Jun 2016 10:39:33 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 636C812D10D for <sidr@ietf.org>; Tue, 28 Jun 2016 10:39:33 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:42722 helo=COMSEC.fios-router.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1bHwym-000AcH-CK; Tue, 28 Jun 2016 13:39:20 -0400
From: Stephen Kent <kent@bbn.com>
To: Geoff Huston <gih@apnic.net>
References: <bc4f2d97-e858-c834-b8c1-241f1cb0ed3a@bbn.com> <F5A6EBD6-49A8-4FBB-8039-53B09F4E0B9E@apnic.net>
Message-ID: <f989d80e-2538-8b02-fc65-7a2cbf6a57ca@bbn.com>
Date: Tue, 28 Jun 2016 13:39:18 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <F5A6EBD6-49A8-4FBB-8039-53B09F4E0B9E@apnic.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/7wAcB2MgVTgyUyZWfUd6DGJ32Os>
Cc: sidr <sidr@ietf.org>
Subject: Re: [sidr] revising Section 7.2 of RFC 6487
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: Tue, 28 Jun 2016 17:39:37 -0000

Geoff,

Thanks for reviewing the text.

I modified the text to change "current VRS-IP" to be "... the value of 
the VRS-IP computed for certificate x-1" as per your suggestion. I also 
made this change for the corresponding VRS-AS text.

I don't think we need to add a note about validation being performed 
"top down" since bullet B already says: "certificate '1' is a trust anchor"

Steve
> FWIW, I like this formulation Steve.
>
> Possibly when you refer to "the current value of the VRS-IP” you may want to explicitly refer to the VRS-IP of certificate x-1 rather than “current”.
>
> I also wonder if it is worth noting that the enumerated steps outlined here are intended to be performed “top down” - i.e. from a trust anchor to the certificate to be validated.
>
> regards,
>
>    Geoff
>