Re: Request for well-known URI: est

[Sean Turner <[e-mail]>]

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
>