[apps-discuss] 回复: Re: AppsDir review of draft-ietf-nfsv4-rfc3530bis-25

"Jiankang Yao" <yaojk@cnnic.cn> Wed, 08 May 2013 06:20 UTC

Return-Path: <yaojk@cnnic.cn>
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 935E421F8606 for <apps-discuss@ietfa.amsl.com>; Tue, 7 May 2013 23:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -91.399
X-Spam-Level:
X-Spam-Status: No, score=-91.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, J_CHICKENPOX_54=0.6, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1, SARE_SUB_ENC_GB2312=1.345, 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 x7xjtfUPhfGK for <apps-discuss@ietfa.amsl.com>; Tue, 7 May 2013 23:20:32 -0700 (PDT)
Received: from cnnic.cn (unknown [218.241.105.202]) by ietfa.amsl.com (Postfix) with SMTP id 3B21621F9057 for <apps-discuss@ietf.org>; Tue, 7 May 2013 23:20:28 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO healthyao-think) (127.0.0.1) by 127.0.0.1 with SMTP; Wed, 08 May 2013 14:20:21 +0800
Date: Wed, 08 May 2013 14:20:21 +0800
From: Jiankang Yao <yaojk@cnnic.cn>
To: "Haynes, Tom" <Tom.Haynes@netapp.com>
References: <6E0E2EDBD7BF49FF94AD9DBA96C88E07@LENOVO47E041CF>, <3A330EAE-1D6F-439E-9378-D569A9233D5F@netapp.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2013050814191964838318@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart272565780552_=----"
Cc: "<iesg@ietf.org>" <iesg@ietf.org>, "<apps-discuss@ietf.org>" <apps-discuss@ietf.org>
Subject: [apps-discuss] 回复: Re: AppsDir review of draft-ietf-nfsv4-rfc3530bis-25
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: yaojk <yaojk@cnnic.cn>
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: Wed, 08 May 2013 06:20:36 -0000


thanks for your kind reply.
Your suggested change is one way to improve this document.
but I suggest you to ask more internationalization experts' comments about this internationalization issue in the apps-discuss list.

Regards



Jiankang Yao

From: Haynes, Tom
Date: 2013-05-08 12:23
To: Jiankang YAO
CC: ; 
Subject: Re: AppsDir review of draft-ietf-nfsv4-rfc3530bis-25
Hi  Jiankang,

I spoke with our internationalization expert and they describe that our use of
stringprep is informative and as a guideline.

As such, we will move the reference to no longer be normative and thus
keep the document to refer to the existing version of UNICODE.

Thanks,
Tom

On Apr 12, 2013, at 12:57 AM, Jiankang YAO <yaojk@cnnic.cn> wrote:

> I have been selected as the Applications Area Directorate reviewer 
> for this draft (for background on appsdir, please 
> see 
> http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate 
> ).  
> Please resolve these comments along with any other comments 
> you may receive. Please wait for direction from your document 
> shepherd or AD before posting a new version of the draft.
> 
> Document: 
> draft-ietf-nfsv4-rfc3530bis-25 
> Title: 
> Network File System (NFS) Version 4 Protocol
> 
> 
> Reviewer: Jiankang Yao
> Review Date: April 12, 2013
> 
> Summary:
> 
> This draft is very long. I mainly focus on section 12 of this document.This part is about internationalization.
> 
> Major issue:none.
> 
> Minor issue:
> 
>  This part refer to ISO.10646-1.1993, which is almost same to UNICODE 3.2. The RFC3454 referred by this document is also based on ISO.10646-1.1993. The problem is that the UNICODE has been updated to Version 6.2 from version 3.2. RFC3454 may not work for UNICODE 6.2.
>  Should this document be updated to refer to the new version of UNICODE?
> 
> 
> 
> Best Regards
> 
> Jiankang Yao