Re: [apps-discuss] WGLC: draft-ietf-appsawg-about-uri-scheme-03.txt

Alexey Melnikov <alexey.melnikov@isode.com> Sat, 24 March 2012 12:29 UTC

Return-Path: <alexey.melnikov@isode.com>
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 6DC5621F8711 for <apps-discuss@ietfa.amsl.com>; Sat, 24 Mar 2012 05:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 1Tb3y+dLzYQe for <apps-discuss@ietfa.amsl.com>; Sat, 24 Mar 2012 05:29:39 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 950A221F870F for <apps-discuss@ietf.org>; Sat, 24 Mar 2012 05:29:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1332592178; d=isode.com; s=selector; i=@isode.com; bh=03Loo7RdSXbTwmMljND6KYmu4RdBdn+C01EF68pf3Sc=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=mF3jxNsbALRlxVph/o/9Hdlx/SId9vMl7E/Bp6JMdShqv3UoVdd//yBAH1VpxmA/Y0cHIP v053SRK+usTepeLbMqZBPwEQ+ZOyA3PVluej0fyKfOMpkbAf+3QQgniy56X9VmCUuLEh74 /HABQSioWhHDNL5Z4rmuOFoCiupoJvc=;
Received: from [130.129.18.66] (dhcp-1242.meeting.ietf.org [130.129.18.66]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <T22-MgAikhlt@rufus.isode.com>; Sat, 24 Mar 2012 12:29:38 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F6DBE37.5080403@isode.com>
Date: Sat, 24 Mar 2012 13:29:43 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Jiankang YAO <yaojk@cnnic.cn>, "\"Mykyta Yevstifeyev ( М. Євстіфеєв)\"" <evnikita2@gmail.com>
References: <503575970.11554@cnnic.cn> <4A10020DB6464A0BBA535BF75D21A9D9@LENOVO47E041CF>
In-Reply-To: <4A10020DB6464A0BBA535BF75D21A9D9@LENOVO47E041CF>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] WGLC: draft-ietf-appsawg-about-uri-scheme-03.txt
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: Sat, 24 Mar 2012 12:29:40 -0000

On 06/03/2012 01:00, Jiankang YAO wrote:
> Dear colleagues,
>
> This message starts a two-week WGLC on the draft
> draft-ietf-appsawg-about-uri-scheme-03.txt.
>
> Please help to review this draft.  If you support publication, please state as
> much on the list.  If you are opposed to publication, please state
> that on the list as well.  It is more/only helpful if you give your reasons for
> your position as part of your statement.
>
> Pls send your comments toapps-discuss@ietf.org  orappsawg-chairs@tools.ietf.org  or editors.
>
> The WGLC will end on March 20, 2012 at 1:00 UTC.
Hi,
Sorry, I've missed the WGLC. A couple of nits:

1. Introduction

    As use of "about" URIs has been quiet long-lasting, and the URIs have

s/quiet/quite

    been used without any proper registration and absent any proper
    specification, the necessity for the the latter two actions arises.
    The purpose of this document is to provide a stable specification for
    "about" URI scheme and correspondingly register it in the IANA
    registry.  Along, several provisions for handling the "about" URIs
    are set.


4.2. A Registry for Registered Tokens

    IANA is asked to set up a new registry entitled "'about' URI Special
    Purpose Tokens" following the guidelines below.

    The registry entries consist of 3 fields: Special-Purpose Token,
    Description and Reference.

Below you also have "Contact/Change Controller", so 4 or 5 fields, 
depending how you count.