Re: [apps-discuss] I-D Action: draft-ietf-appsawg-about-uri-scheme-00.txt

Frank Ellermann <> Tue, 18 October 2011 06:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 196C91F0C70 for <>; Mon, 17 Oct 2011 23:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=-0.097, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ipqTADo+Qirc for <>; Mon, 17 Oct 2011 23:52:51 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 684B71F0C6E for <>; Mon, 17 Oct 2011 23:52:51 -0700 (PDT)
Received: by wyh22 with SMTP id 22so259529wyh.31 for <>; Mon, 17 Oct 2011 23:52:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=EmDjWGy3PW7ZK38Aan2rLM8esmWPy1O3c8vaRq01px4=; b=HkCUyuXKqaDwXN7f0CnpBVSEPsm8vnzQoryDyzrr1C9utXI6q+nHo5oF9Cb8uCQKmd xhA8LeUNG7EEBNdmdtksb1vc3KG7CHFYbRLJUSBG+HjZplSzWUy4VKZkLJRjGDnVOHw1 1kp1OCylB14z2b83P/t0y2HLzqnvrZZ3qFyAs=
Received: by with SMTP id 1mr387744wbl.77.1318920766088; Mon, 17 Oct 2011 23:52:46 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 17 Oct 2011 23:52:06 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: Frank Ellermann <>
Date: Tue, 18 Oct 2011 08:52:06 +0200
Message-ID: <>
To: Jiankang YAO <>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-about-uri-scheme-00.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 18 Oct 2011 06:52:52 -0000

On 18 October 2011 08:09, Jiankang YAO wrote:

>  Pls kindly help to review it before 25 Oct.

Section 2.1:
Please replace 'segment' by '*pchar' and import pchar
instead of segment from STD 66.  The * indicates the
main point "zero or more" (unlike <segment-nz>), and
pchar is for me clearer than segment:  Above all it's
none of the five terms for slightly different paths.

The SPU gibberish is just ugly, please replace it by
"registered token" or similar.  Ditto SPT.  Get rid
of almost all MUSTard in this perfectly harmless URI
scheme, only about:blank deserves a MUST.

For more than six months I try to get about:about in
this draft, nothing happened.  Instead there are tons
of obscure terms (SPU, SPT), a pointless registry for
one word (blank), and additional tons of MUSTs and
MUST NOTs dealing with something that doesn't exist.

This draft is now in the worst state for this year,
that is not very encouraging for this trivial task.

Claiming that there are no about: IRIs makes no sense
as soon as there is an <about-query>, cf. RFC 3987
<iquery> and <ifragment>.