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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 05 May 2012 17:21 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 1A47621F85E3 for <wellknown-uri-review@ietfa.amsl.com>; Sat, 5 May 2012 10:21:56 -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=[AWL=0.000, 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 tXLQFpyur0CJ for <wellknown-uri-review@ietfa.amsl.com>; Sat, 5 May 2012 10:21:55 -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 4F25421F85D5 for <wellknown-uri-review@ietf.org>; Sat, 5 May 2012 10:21:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id B4000157B18; Sat, 5 May 2012 18:21:54 +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=1336238514; bh=5BrA2/C5Pvi4vY 45MH4m94RQVQTL9Lngs3SoQtel7P4=; b=qLbvCMHw0QGzgZnmxo+oH4MOJ4jGsu UHYM7d9ZLiYPsmGizgxq1cOAKbHu/yWXpvUOqf5BIw/Ga5nOLa1KmHeneoofF5RB e665apYD2GN74yq6dMxkFLyVchiu2nuIwjLXvqWfB1oDVjIlw1L8bt/kWRfVEqUd G8m4/2pghWKIlTB579VTrxOKhNZ8GlTnSaCkf38+9YVkECSXSPrXB9jcuBBLV4Pe McGvPwC+mo/CDWUWSgaCEmR68ePfEQu3Lb8JQgndw7Ksge/2Tqcmk6HhxLmq0m7P N7YUu8Sj3iQ81YYIBvPofJUU4rP8KaczdcIooNSf848OWVVPZu28JVnw==
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 YvvGqjzJluol; Sat, 5 May 2012 18:21:54 +0100 (IST)
Received: from [192.168.212.241] (unknown [209.117.47.251]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 2E17C157B17; Sat, 5 May 2012 18:21:51 +0100 (IST)
Message-ID: <4FA561AF.3050203@cs.tcd.ie>
Date: Sat, 05 May 2012 18:21:51 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Eran Hammer <eran@hueniverse.com>
References: <4FA03189.1030603@KingsMountain.com> <0CBAEB56DDB3A140BA8E8C124C04ECA20101572B@P3PWEX2MB008.ex2.secureserver.net>
In-Reply-To: <0CBAEB56DDB3A140BA8E8C124C04ECA20101572B@P3PWEX2MB008.ex2.secureserver.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>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>, Barry Leiba <barryleiba@computer.org>, "wellknown-uri-review@ietf.org" <wellknown-uri-review@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: Sat, 05 May 2012 17:21:56 -0000

Hi Eran,

Question for you: would it work for you if we left the
.well-known structure as-is, but said that if you
de-reference such a URL, then you SHOULD expect a 30x
and MUST be able to handle that?

I think that might be more flexible so that if someone
had some kind of sharding of the objects (e.g. all
the objects with hashes starting 0x00 on server0,
..., 0xFF on server#256 (or whatever) then they could
easily make that work, compared to if we don't include
the hash value in the URL.

Ta,
S.


On 05/01/2012 07:58 PM, Eran Hammer wrote:
> NP. We had some confusion about this registry in the past, with IANA adding records without DE review...
> 
> EH
> 
>> -----Original Message-----
>> From: wellknown-uri-review-bounces@ietf.org [mailto:wellknown-uri-
>> review-bounces@ietf.org] On Behalf Of =JeffH
>> Sent: Tuesday, May 01, 2012 11:55 AM
>> To: Stephen Farrell
>> Cc: Alexey Melnikov; Barry Leiba; wellknown-uri-review@ietf.org; draft-
>> farrell-decade-ni@tools.ietf.org
>> Subject: Re: [wellknown-uri-review] A .well-known registration for review
>>
>>  > On 05/01/2012 03:22 PM, =JeffH wrote:
>>  >> what's the timeframe for this review? (this is a pretty packed week)  >  >
>> IETF LC hasn't started yet and I don't see any problem with  > those being
>> done in parallel so next couple of weeks should  > be fine. Dunno what SLA
>> you signed up for though:-)
>>
>> thanks. I was asking generically, no toe-stepping of roles intended.
>>
>>
>> =JeffH
>>
>> _______________________________________________
>> wellknown-uri-review mailing list
>> wellknown-uri-review@ietf.org
>> https://www.ietf.org/mailman/listinfo/wellknown-uri-review