IETF Logo Mail Archive

Re: [Anima] Adam Roach's Discuss on draft-ietf-anima-bootstrapping-keyinfra-22: (with DISCUSS and COMMENT)

Adam Roach <adam@nostrum.com> Tue, 16 July 2019 21:28 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B5E120136; Tue, 16 Jul 2019 14:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level:
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 gkFBHhfibM6q; Tue, 16 Jul 2019 14:28:34 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B63A112007C; Tue, 16 Jul 2019 14:28:34 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x6GLSNZm012043 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 16 Jul 2019 16:28:25 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1563312506; bh=wzucsBLUiYZjmhcXbLsOxcTTDXIJEvpyiTpJ6VLciBs=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=IdhfuiQinpajBsm5EuPLmD3iwGAMySGIOFE69pxrbq72imyakSZpXQ9TO7fq4zLgJ s+O5K0vZYxX3W4ubjbZ7nFXh8i6bG9pbecbq/ZNKBaaxPq9PC7C9ggtzRBALAoO9Q8 bxm6YfGDPNiNFjFdCyUoiNGuiNsmUwbf1wwGVUKk=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Michael Richardson <mcr+ietf@sandelman.ca>, Ted Hardie <ted.ietf@gmail.com>
Cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, Toerless Eckert <tte+ietf@cs.fau.de>, anima@ietf.org, The IESG <iesg@ietf.org>, anima-chairs@ietf.org
References: <156282703648.15280.17739830959261983790.idtracker@ietfa.amsl.com> <19180.1562875321@localhost> <CA+9kkMA0U5rKi_1NBg-0riK2Xsty2bc=itfqSD91zz1bcB6g_g@mail.gmail.com> <26415.1563303923@localhost>
From: Adam Roach <adam@nostrum.com>
Message-ID: <0e096bdf-fd85-c13f-ac4b-58ff91d9b9d4@nostrum.com>
Date: Tue, 16 Jul 2019 16:28:17 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <26415.1563303923@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ZF_qQTUAXNuWtcfRMtHke6vWNYU>
Subject: Re: [Anima] Adam Roach's Discuss on draft-ietf-anima-bootstrapping-keyinfra-22: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2019 21:28:36 -0000

On 7/16/19 2:05 PM, Michael Richardson wrote:
> Ted Hardie <ted.ietf@gmail.com> wrote:
>      > Howdy,
>
>      > I would personally not suggest using IRIs here, given that the scheme
>      > (https) is expected to retrieve a resource at a well-known location and
>      > thus will always have to be mapped to a URI to do the retrieval (rather
>      > than used in a string comparison or something similar) .  RFC 5280,
>      > which this cites, actually goes through the steps pretty well, and I
>      > think the complexity there demonstrates the advantage for constrained
>      > devices of always using the URI form.
>
> I have changed the references from IRI to URL, and the components from
> iauthority to 'authority'.
>

I'm happy with this solution if you are.

/a

v2.23.0 | Report a Bug | By Email