Re: [core] feedback on resource-directory and mirror-proxy (and base) drafts

Jari Arkko <jari.arkko@piuha.net> Fri, 09 March 2012 16:59 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534FA21E8013 for <core@ietfa.amsl.com>; Fri, 9 Mar 2012 08:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level:
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, 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 o7r7FXr3GT1z for <core@ietfa.amsl.com>; Fri, 9 Mar 2012 08:59:56 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 94E3A21F872E for <core@ietf.org>; Fri, 9 Mar 2012 08:59:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E5E362DA06; Fri, 9 Mar 2012 18:59:54 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e3dIqfO4YJTd; Fri, 9 Mar 2012 18:59:54 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 59BE32CC3C; Fri, 9 Mar 2012 18:59:54 +0200 (EET)
Message-ID: <4F5A370A.7090308@piuha.net>
Date: Fri, 09 Mar 2012 18:59:54 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <4F59F906.4080906@piuha.net> <6144B86F-0CAF-47E9-BE60-16647BFF22DA@tzi.org>
In-Reply-To: <6144B86F-0CAF-47E9-BE60-16647BFF22DA@tzi.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: Heidi-Maria Rissanen <heidi-maria.rissanen@ericsson.com>, core <core@ietf.org>
Subject: Re: [core] feedback on resource-directory and mirror-proxy (and base) drafts
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/core>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 16:59:57 -0000

Carsten,

>
>
> When talking about the value of the sequence of options, it is a bit more intuitive to instead talk about the implied URI.  Notated in a HTTP header style:
>
> Location: /foo/bar
>
> is a short form of »two Location-Path options "foo" and "bar"«.
>
> Yes, we need to get consistent here -- either use that notation and explain it or use the actual option values.  I still like to talk about /.well-known/core etc. instead of saying [{"Location-Path": ".well-known"}, {"Location-Path": "core"}] (or, worse, "\x6B.well-known\x04core").
>

You can certainly still talk about paths such as /.well-known/core in the text, but if you actually write an example that has lines like Location: /.well-known/core that is always going to be confusing, no matter what explanations you might add to the text. The point of an example is to show the real messages and attributes, and shorthand notations there is misleading. IMO, of course.

Jari