Re: [apps-discuss] OPS-DIR review of draft-ietf-appsawg-uri-scheme-reg-04

Qin Wu <bill.wu@huawei.com> Mon, 13 April 2015 05:57 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: expand-draft-ietf-appsawg-uri-scheme-reg.all@virtual.ietf.org
Delivered-To: apps-discuss@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id E911B1B2D30; Sun, 12 Apr 2015 22:57:40 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-appsawg-uri-scheme-reg.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-appsawg-uri-scheme-reg.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1581B2D2F for <xfilter-draft-ietf-appsawg-uri-scheme-reg.all@ietfa.amsl.com>; Sun, 12 Apr 2015 22:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.216
X-Spam-Level: *
X-Spam-Status: No, score=1.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id giM806FcMoRk for <xfilter-draft-ietf-appsawg-uri-scheme-reg.all@ietfa.amsl.com>; Sun, 12 Apr 2015 22:57:37 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4DD21B2D2B for <draft-ietf-appsawg-uri-scheme-reg.all@ietf.org>; Sun, 12 Apr 2015 22:57:37 -0700 (PDT)
Received: from szxga01-in.huawei.com ([58.251.152.64]:38092) by zinfandel.tools.ietf.org with esmtps (TLS1.0:RSA_ARCFOUR_128_SHA1:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <bill.wu@huawei.com>) id 1YhXNH-0006J1-Hr for draft-ietf-appsawg-uri-scheme-reg.all@tools.ietf.org; Sun, 12 Apr 2015 22:57:37 -0700
Received: from 172.24.2.119 (EHLO nkgeml406-hub.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CMA54726; Mon, 13 Apr 2015 13:57:21 +0800 (CST)
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Mon, 13 Apr 2015 13:57:18 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Dave Thaler <dthaler@microsoft.com>
Thread-Topic: OPS-DIR review of draft-ietf-appsawg-uri-scheme-reg-04
Thread-Index: AdBVqoBBzKB16QZoQqSP3Y7FahtJFgXyo5LgAg5jYQA=
Date: Mon, 13 Apr 2015 05:57:18 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8471994B@nkgeml501-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA846DC8C6@nkgeml501-mbs.china.huawei.com> <BY2PR03MB412EFFA41F5A99FE96EE4E7A3F20@BY2PR03MB412.namprd03.prod.outlook.com>
In-Reply-To: <BY2PR03MB412EFFA41F5A99FE96EE4E7A3F20@BY2PR03MB412.namprd03.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA8471994Bnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-SA-Exim-Connect-IP: 58.251.152.64
X-SA-Exim-Rcpt-To: draft-ietf-appsawg-uri-scheme-reg.all@tools.ietf.org
X-SA-Exim-Mail-From: bill.wu@huawei.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Resent-To: draft-ietf-appsawg-uri-scheme-reg.all@ietf.org
Resent-Message-Id: <20150413055737.B4DD21B2D2B@ietfa.amsl.com>
Resent-Date: Sun, 12 Apr 2015 22:57:37 -0700
Resent-From: bill.wu@huawei.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/draft-ietf-appsawg-uri-scheme-reg.all@tools/mPnZkVUNE3lPX2XZLaYDZERiFwc>
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/gNrr9MOaDCZoodkbbOlezTupVMM>
X-Mailman-Approved-At: Mon, 13 Apr 2015 08:54:46 -0700
Cc: "draft-ietf-appsawg-uri-scheme-reg.all@tools.ietf.org" <draft-ietf-appsawg-uri-scheme-reg.all@tools.ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>
Subject: Re: [apps-discuss] OPS-DIR review of draft-ietf-appsawg-uri-scheme-reg-04
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 13 Apr 2015 05:57:41 -0000

Thanks Dave for clarification, you address my comments.

-Qin
发件人: Dave Thaler [mailto:dthaler@microsoft.com]
发送时间: 2015年4月3日 2:49
收件人: Qin Wu
抄送: ops-dir@ietf.org; draft-ietf-appsawg-uri-scheme-reg.all@tools.ietf.org
主题: RE: OPS-DIR review of draft-ietf-appsawg-uri-scheme-reg-04

Thanks Qin for your review.  Below is what we did in -05..

From: Qin Wu [mailto:bill.wu@huawei.com]
Sent: Tuesday, March 3, 2015 4:07 AM
To: ops-dir@ietf.org<mailto:ops-dir@ietf.org>; draft-ietf-appsawg-uri-scheme-reg.all@tools.ietf.org<mailto:draft-ietf-appsawg-uri-scheme-reg.all@tools.ietf.org>
Subject: OPS-DIR review of draft-ietf-appsawg-uri-scheme-reg-04


Folks:

I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.



This draft discusses Guidelines and Registration Procedures for URI Schemes. It looks Operations and Management Review Checklist defined in RFC5706 doesn't apply since there is no new protocol or protocol extension defined in this draft.

I think this draft is ready for publication. Here are a few editorial comments:



1.       Section 1, last two paragraphs
s/Interationalized/Internationalized
s/accomodate/accommodate

[DT] Done


2.       Section 1, last two paragraphs
It looks these two paragraphs more fit into Scheme definition requirements section, why split it out from section 3? would it be good to incorporate these two paragraphs into section 3, No,?

[DT] Done.


3.       Section 3, the 6th paragraph said:
“
The URI scheme name registration procedure can be used in such an event.
”

Pointing to section 7 would be good.



[DT] Done.  Martin Durst said the same in his review.



4.       Section 4 and 5

Are there guidelines for permanent URI Scheme Registration if there is permanent URI Scheme Registration? Or Permanent URI Scheme Registration can only be possible by upgrading provision URI Scheme Registration?



[DT] Not sure we parsed your question correctly, but as co-authors we discussed and believe the draft is already clear about a couple points:

1)      “Can you register a new permanent scheme, or must you go to provisional first?”  A: can go directly to permanent, as discussed in section 7.2 (intro sentence plus point 3).

2)      “Can you update an existing permanent scheme?” A: yes, as discussed in section 7.3.



-Qin