Re: Request for well-known URI: public.pem

Mark Nottingham <mnot@mnot.net> Mon, 25 March 2013 09:25 UTC

Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Request for well-known URI: public.pem
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <BLU0-SMTP18993D3AEEA49C2A1CFFC94D2D40@phx.gbl>
Date: Mon, 25 Mar 2013 20:25:13 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6F78F87-EC2B-40A5-AB59-336C1510E22A@mnot.net>
References: <BLU0-SMTP18993D3AEEA49C2A1CFFC94D2D40@phx.gbl>
To: Julian Cain <julian@junglecat.org>
Cc: wellknown-uri-review@ietf.org
Precedence: list

Hi Julian,

To register a well-known URI, its specification needs to be published in a stable place. One way to do that is to submit it as an Internet-Draft, and then request that the RFC Editor publish it on the independent submission track as Informational; see <http://www.rfc-editor.org/indsubs.html>.

However, the specification you've supplied only mentions the public.pem resource tangentially; it needs to be specified more clearly (e.g., what format(s) it should return, as identified by media types, etc.).

Beyond that, there isn't any explanation in the specification you've supplied as to why a well-known URI is needed; please see RFC5785. 

Regards,

On 22/03/2013, at 5:43 PM, Julian Cain <julian@junglecat.org> wrote:

> Hi,
> My service requires a public certificate before performing an action. I am formally requesting /.well-known/public.pem.
> 
> Thanks in advance,
> Julian

--
Mark Nottingham   http://www.mnot.net/

Request for well-known URI: public.pem Julian Cain
Re: Request for well-known URI: public.pem Mark Nottingham