Re: Request for well-known URI: est

Sean Turner <turners@ieca.com> Mon, 19 August 2013 22:26 UTC

Return-Path: <turners@ieca.com>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3B521F8C3E for <wellknown-uri-review@ietfa.amsl.com>; Mon, 19 Aug 2013 15:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.574
X-Spam-Level:
X-Spam-Status: No, score=-101.574 tagged_above=-999 required=5 tests=[AWL=0.691, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gP1ibT5thnKL for <wellknown-uri-review@ietfa.amsl.com>; Mon, 19 Aug 2013 15:26:22 -0700 (PDT)
Received: from gateway02.websitewelcome.com (gateway02.websitewelcome.com [67.18.66.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5A9D011E8189 for <wellknown-uri-review@ietf.org>; Mon, 19 Aug 2013 15:26:01 -0700 (PDT)
Received: by gateway02.websitewelcome.com (Postfix, from userid 5007) id DB390146AA0A6; Mon, 19 Aug 2013 17:25:43 -0500 (CDT)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway02.websitewelcome.com (Postfix) with ESMTP id BEA53146AA038 for <wellknown-uri-review@ietf.org>; Mon, 19 Aug 2013 17:25:43 -0500 (CDT)
Received: from [96.231.225.44] (port=63819 helo=thunderfish.local) by gator3286.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1VBXtZ-00031p-0g; Mon, 19 Aug 2013 17:25:53 -0500
Message-ID: <52129B6F.4050607@ieca.com>
Date: Mon, 19 Aug 2013 18:25:51 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Request for well-known URI: est
References: <CE32E9BA.1F636%dharkins@arubanetworks.com> <520EAF60.2010509@stpeter.im> <CALaySJKxr1bxqo554zLQN2ttv=KdBoV4qnOnBaCWVXbX1NrRog@mail.gmail.com> <520EE13B.4020909@stpeter.im> <CALaySJJ6XWH8JNok26C5pv7JM-_6hqBHG1aGxDvKZGdh=erkGw@mail.gmail.com> <520EE500.3080103@stpeter.im> <6.2.5.6.2.20130816200334.0d5a38b0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130816200334.0d5a38b0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (thunderfish.local) [96.231.225.44]:63819
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 8
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Cc: Dan Harkins <dharkins@arubanetworks.com>, draft-ietf-pkix-est@tools.ietf.org, "Max Pritikin \(pritikin\)" <pritikin@cisco.com>, app-ads@tools.ietf.org, wellknown-uri-review@ietf.org
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wellknown-uri-review>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 22:26:31 -0000

Yep - I can make sure they do that.

spt

On 8/16/13 11:13 PM, SM wrote:
> Hi Sean,
> At 19:50 16-08-2013, Peter Saint-Andre wrote:
>> The IANA Considerations section of the EST spec says:
>>
>>    IANA is to update the well-known URI registry with the following
>>    filled-in template from [RFC5785].
>>
>>       URI suffix: est
>>
>>       Change controller: IETF
>>
>> That doesn't cover what it needs to cover, i.e., the kind of information
>> mentioned in RFC 5785:
>>
>>    Typically, a registration will reference a specification that defines
>>    the format and associated media type to be obtained by dereferencing
>>    the well-known URI.
>>
>>    It MAY also contain additional information, such as the syntax of
>>    additional path components, query strings and/or fragment identifiers
>>    to be appended to the well-known URI, or protocol-specific details
>>    (e.g., HTTP [RFC2616] method handling).
>>
>> None of that "additional information" is in the registration request, so
>> it's not clear to me that IANA will have the information it needs to
>> properly process this registration.
>
> IANA, in its review of the draft, mentioned that it needs the following
> information:
>
>    URI suffix: est
>    Change controller: IETF
>    Reference: [ RFC-to-be ]
>    Related Information:
>    Date Registered: [ TBD-at-registration ]
>    Date Modified:
>
> Could you please suggest to the authors of draft-ietf-pkix-est to add:
>
>    Reference: [this document]
>
> to the request for the well-known URI in Section 6?
>
> Regards,
> -sm
>