Re: [wellknown-uri-review] A .well-known registration for review

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 02 May 2012 08:38 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 294E621F88F5 for <wellknown-uri-review@ietfa.amsl.com>; Wed, 2 May 2012 01:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.39
X-Spam-Level:
X-Spam-Status: No, score=-102.39 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599, 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 9Oi5Vbwvsc6H for <wellknown-uri-review@ietfa.amsl.com>; Wed, 2 May 2012 01:38:49 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 5319421F88F4 for <wellknown-uri-review@ietf.org>; Wed, 2 May 2012 01:38:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id ED011172008; Wed, 2 May 2012 09:38:47 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1335947927; bh=VM1AzwYz4ksJOr eWrdO1lb8algnbxrNRw7fX+yn9NDE=; b=nPSK+jcv2++6rojkDov5yi7W5Pk3Lf IQ8psO9wWvIDtBIPBVMXOxDtDRqD4lusUhyQsqlbd3zqxfWJvSJUmVcOMQJH3teP 9WGFoZ8WhqPJHHHvRmqKP9+lqgwo3qaOCvNiNvPFnY0FmOG4Lb7hYoXJRt57W7M7 8Z1gR/8TLu/qXNU9u8/kf8NOKyK8uJpdX888pwmdVVAigStkDllZQsYqNtI6FTAB Vgpf2DXVoEWg4Ojimc7IUJ4OT6Zrnyq+hiTw3EXz249j0mcphLEy4eyPzETi+nHr bAKdNLa+Ucbkgi4tAQkm5U1zkn2JVevleH+DYLlLSxbjp3DaknQskpGw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id btQBCIoEKDsm; Wed, 2 May 2012 09:38:47 +0100 (IST)
Received: from [109.79.28.98] (unknown [109.79.28.98]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id D9C54171477; Wed, 2 May 2012 09:38:43 +0100 (IST)
Message-ID: <4FA0F290.6000002@cs.tcd.ie>
Date: Wed, 02 May 2012 09:38:40 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120424 Thunderbird/12.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <4F9EB6E8.4060405@cs.tcd.ie> <213E3399-C3A5-4947-B252-B0E913518AD4@mnot.net>
In-Reply-To: <213E3399-C3A5-4947-B252-B0E913518AD4@mnot.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, wellknown-uri-review@ietf.org, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>
Subject: Re: [wellknown-uri-review] A .well-known registration for review
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: Wed, 02 May 2012 08:38:55 -0000

On 05/02/2012 12:41 AM, Mark Nottingham wrote:
> My .02 - 
> 
> I suspect there are several better ways to do this, that don't do such bad things to the Web architecture. Well-known URIs are an escape valve, not permission :)
> 
> OTOH the role of a registry is to register, not to be a gatekeeper for quality. 
> 
> Regarding Eran's concern, I tend to agree, EXCEPT that 5785 also says:
> 
>>    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).
> 
> So, strictly speaking, there's an argument for both sides here.

Crap, so now I need to go re-read 5785 properly;-)

> 
> Anyway, I'd rather see these issues debated on the apps-discuss list than here. Although, apps-discuss is getting mighty busy these days...

We've asked for review of this on apps-discuss already so there's
a thread on which you can respond, e.g. [1] relates to comments
from James Manger. More comments are welcome!

S.

[1] http://www.ietf.org/mail-archive/web/apps-discuss/current/msg05483.html



> 
> 
> On 01/05/2012, at 1:59 AM, Stephen Farrell wrote:
> 
>>
>> Hi,
>>
>> We have a draft [1] that requests a registration of
>> a .well-known URI.
>>
>> The core WG are likely to want to use these we think
>> and possibly decade, but they're intended to be generally
>> useful as well.
>>
>> Barry Leiba is planning to AD sponsor this and Alexey
>> Melnikov will be shepherding so if you can cc them as
>> well as the authors on any questions or comments that'd
>> be good.
>>
>> I hope the plan is to IETF LC this soon, once this
>> review and the uri registrations review are done.
>>
>> Thanks,
>> Stephen.
>>
>> [1] http://tools.ietf.org/html/draft-farrell-decade-ni-05
>> _______________________________________________
>> wellknown-uri-review mailing list
>> wellknown-uri-review@ietf.org
>> https://www.ietf.org/mailman/listinfo/wellknown-uri-review
> 
> --
> Mark Nottingham
> http://www.mnot.net/
> 
> 
> 
>