IETF Logo Mail Archive

[apps-discuss] [APPS-REVIEW]apps-team review of , draft-cridland-acap-vendor-registry-01

Xiaodong Lee <lee@cnnic.cn> Fri, 15 October 2010 08:34 UTC

Return-Path: <lee@cnnic.cn>
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 C2B0F3A6C5D for <apps-discuss@core3.amsl.com>; Fri, 15 Oct 2010 01:34:15 -0700 (PDT)
X-Quarantine-ID: <7vyZVooj2n4U>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: -1.796
X-Spam-Level:
X-Spam-Status: No, score=-1.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
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 7vyZVooj2n4U for <apps-discuss@core3.amsl.com>; Fri, 15 Oct 2010 01:34:15 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id BD83B3A6877 for <apps-discuss@ietf.org>; Fri, 15 Oct 2010 01:34:14 -0700 (PDT)
Received: (eyou send program); Fri, 15 Oct 2010 16:35:31 +0800
Message-ID: <487131731.15611@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: lee@cnnic.cn
Received: from unknown (HELO [172.16.1.57]) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 15 Oct 2010 16:35:31 +0800
Message-ID: <4CB81249.7030407@cnnic.cn>
Date: Fri, 15 Oct 2010 16:35:21 +0800
From: Xiaodong Lee <lee@cnnic.cn>
Organization: CNNIC
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: apps-discuss@ietf.org, dave.cridland@isode.com, Alexey Melnikov <alexey.melnikov@isode.com>, Peter Saint-Andre <stpeter@stpeter.im>, apps-review@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 15 Oct 2010 08:56:47 -0700
Subject: [apps-discuss] [APPS-REVIEW]apps-team review of , draft-cridland-acap-vendor-registry-01
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: lee@cnnic.cn
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: Fri, 15 Oct 2010 08:34:15 -0000

  I have been selected as the Applications Area Review Team reviewer for 
this draft (for background on apps-review, please see 
http://www.apps.ietf.org/content/applications-area-review-team).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document shepherd 
or AD before posting a new version of the draft.

Document: draft-cridland-acap-vendor-registry-01

Title: The Internet Assigned Number Authority (IANA) Application 
Configurations Access Protocol (ACAP) Vendor Subtrees Registry

Reviewer: Xiaodong Lee

Review Date: Oct.15 2010

Review Summary: This draft is ready for publication as an Proposed 
Standard and should be revised before publication.

Major Issues:
This document extend the character set from ASCII to UNICODE for 
internationalization, it only defines the valid character scope of 
vendor-name, no string-prep procedures are defined, for example, to deal 
with the full-width and half-width problem, which may cause problems to 
registry.

Minor Issues:
section 3.2  "iana-vendor-tag     = 1*(ALPHA / DIGIT / SP / "-")".
4 types of characters are chosen. Need explanation why these 4 types? 
For example, why not "&" (ampersand)? which is also often appears in 
vendor-name.

Nits:
title: "... Application Configurations ..." should be "Configuration", 
according to RFC2244.

v2.23.0 | Report a Bug | By Email