Re: FYI: new draft of site-meta; now well-known

Peter Koch <pk@DENIC.DE> Mon, 13 July 2009 07:24 UTC

Return-Path: <peter@denic.de>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E506E3A6CC3 for <apps-discuss@core3.amsl.com>; Mon, 13 Jul 2009 00:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.819
X-Spam-Level:
X-Spam-Status: No, score=-5.819 tagged_above=-999 required=5 tests=[AWL=0.430, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8utbSmwFJCzW for <apps-discuss@core3.amsl.com>; Mon, 13 Jul 2009 00:24:29 -0700 (PDT)
Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id CD3853A6A8B for <discuss@apps.ietf.org>; Mon, 13 Jul 2009 00:24:28 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1MQFuC-0000Hi-Q7; Mon, 13 Jul 2009 09:24:56 +0200
Received: from localhost by x27.adm.denic.de with local id 1MQFuC-00040n-MQ; Mon, 13 Jul 2009 09:24:56 +0200
Date: Mon, 13 Jul 2009 09:24:56 +0200
From: Peter Koch <pk@DENIC.DE>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: FYI: new draft of site-meta; now well-known
Message-ID: <20090713072456.GA12378@x27.adm.denic.de>
Mail-Followup-To: Mark Nottingham <mnot@mnot.net>, Apps Discuss <discuss@apps.ietf.org>
References: <A89DB2C2-1A29-4680-AE41-CCC749132631@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A89DB2C2-1A29-4680-AE41-CCC749132631@mnot.net>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Cc: Apps Discuss <discuss@apps.ietf.org>
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 13 Jul 2009 07:24:30 -0000

On Sun, Jul 12, 2009 at 01:38:32PM +1000, Mark Nottingham wrote:
> See:
>   http://bit.ly/48bdmV

                        Defining Well-Known URIs
                     draft-nottingham-site-meta-02

The IANA registration policy could benefit from a disambiguation.  Section
5.1 says "Designated Expert" with "Specification Required", but then says
"typically published in an RFC or Open Standard".  The threshold for
"Specification Required" is lower, so it's unclear to me whether the
additional clause is intended to provide guidance only or is meant to
be normative.  Later, 5.1.1 seems to imply that change control with all
specifications backed by an RFC lies with the IETF, which isn't
necessarily the case.

On the choice of the name:

   It's short, descriptive and according to search indices, not widely
   used.

It's descriptive in a certain language environment but at the same time
it's a protocol element that is likely exposed to end users. There's an
odd chance that helpful implementations will provide localizations (like
some do today for email header fields).  A tag like "/.---.-" (W and K
in Morse code) looks less nice, but might reduce the temptaion of
translation.

-Peter