IETF Logo Mail Archive

Re: [apps-discuss] draft-farrell-decade-ni-02 - we think this is done...

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 05 April 2012 21:25 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFA2621F860E for <apps-discuss@ietfa.amsl.com>; Thu, 5 Apr 2012 14:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 qOyKRzLLo1pw for <apps-discuss@ietfa.amsl.com>; Thu, 5 Apr 2012 14:25:31 -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 9BFF421F8694 for <apps-discuss@ietf.org>; Thu, 5 Apr 2012 14:25:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 49B4A171C02; Thu, 5 Apr 2012 22:25:30 +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=1333661130; bh=0fFQFLOrDdkfGL Rcsjag7wSNnmZW1uFfYkV32YRJBK4=; b=pwOuPmBnS7lbyWA4Ch5IwKoohgHYeP 6pE8da7t2bqd0W2uhVTUZvkCPj6++msmSInGNqbUYRvhYwucNRVWZji/he+l+5ak 9LhlK0OS7x5jF623yz0O3LzSpYxUrOuA9A84XfaTPprHvyx2/gEiP9KhvxblQ7fj vxyHh8iD3B08PmnR8dPEb7trtTlviSHSS7Ffs5DOjIW+2UxG9anx4iYD9TDSQTP/ DEa4xuibWTR6zLi+FHWz0wkRiEUF9F1aId1bvMr1gR+ZT6mvI7dL1WV+ChyWHBrO A0EE1Zoier5T1Ub9gNUeCDUc6j5eXvbIQNpsFl9iMdAH8CznPmGVbv5w==
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 Ub0XW18+EcWe; Thu, 5 Apr 2012 22:25:30 +0100 (IST)
Received: from [10.87.48.4] (unknown [86.46.29.158]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 3FD83171BFD; Thu, 5 Apr 2012 22:25:29 +0100 (IST)
Message-ID: <4F7E0DC8.8030707@cs.tcd.ie>
Date: Thu, 05 Apr 2012 22:25:28 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <4F7DFC47.2020604@cs.tcd.ie> <CABkgnnVECurSCCsVC6aCqEvdsY_dvKogSNLLM9dvTMoSx6Py2Q@mail.gmail.com>
In-Reply-To: <CABkgnnVECurSCCsVC6aCqEvdsY_dvKogSNLLM9dvTMoSx6Py2Q@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] draft-farrell-decade-ni-02 - we think this is done...
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2012 21:25:33 -0000

On 04/05/2012 10:22 PM, Martin Thomson wrote:
> On 5 April 2012 13:10, Stephen Farrell<stephen.farrell@cs.tcd.ie>  wrote:
>> So, please take a read if you're interested in naming things
>> with hashes and send your comments.
>
> This is my remaining concern.  The draft uses /.well-known/ as the
> base "locator".  That severely limits its use.  Access to
> /.well-known/ is necessarily constrained.
>
> I might want to identify a resource outside of /.well-known/.  I might
> also want to identify a resource that is served elsewhere.  I can't do
> either with this scheme.
>
> I'd prefer something that allowed for the embedding of a complete HTTP
> URI.  Bonus credit for embedding a any URI.

Sure. We added that though in section 5. (For URLs anyway.)
Be glad to add more text that makes that clear, and happy
to say its usable with other schemes if you can offer good
words for that.

Cheers,
S.

>

v2.23.0 | Report a Bug | By Email