IETF Logo Mail Archive

Re: [regext] draft-ietf-regext-bundling-registration and characters representation

"Jiankang Yao" <yaojk@cnnic.cn> Sun, 04 November 2018 13:00 UTC

Return-Path: <yaojk@cnnic.cn>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC9412D4EC for <regext@ietfa.amsl.com>; Sun, 4 Nov 2018 05:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Cuf-09kZCHuR for <regext@ietfa.amsl.com>; Sun, 4 Nov 2018 05:00:11 -0800 (PST)
Received: from cnnic.cn (smtp13.cnnic.cn [218.241.118.13]) by ietfa.amsl.com (Postfix) with ESMTP id 97622127332 for <regext@ietf.org>; Sun, 4 Nov 2018 05:00:03 -0800 (PST)
Received: by ajax-webmail-ocmail02.zx.nicx.cn (Coremail) ; Sun, 4 Nov 2018 20:59:47 +0800 (GMT+08:00)
X-Originating-IP: [159.226.7.2]
Date: Sun, 04 Nov 2018 20:59:47 +0800
X-CM-HeaderCharset: UTF-8
From: Jiankang Yao <yaojk@cnnic.cn>
To: Patrick Mevzek <pm@dotandco.com>
Cc: regext@ietf.org
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT3.0.8 dev build 20171117(fcd8b4ed) Copyright (c) 2002-2018 www.mailtech.cn cnnic
In-Reply-To: <1541134477.2549895.1563050056.54421396@webmail.messagingengine.com>
References: <1541134477.2549895.1563050056.54421396@webmail.messagingengine.com>
X-SendMailWithSms: false
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-ID: <5e99188d.7e7.166deced010.Coremail.yaojk@cnnic.cn>
X-Coremail-Locale: zh_CN
X-CM-TRANSID: AQAAf0DZ4PxD7d5bgJIGAA--.1201W
X-CM-SenderInfo: x1dryyw6fq0xffof0/1tbiAQATDSVCN4vkuQAAsZ
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Yb4OhU6hu0zmPV33GBw274y5JGU>
Subject: Re: [regext] draft-ietf-regext-bundling-registration and characters representation
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 13:00:14 -0000

Hellow Patrick Mevzek,

   Thanks.

   Your suggestion is very good.   RFC7997 is an informational RFC, and shows a direction. 
   Because the popular form of RFC is TXT, the TXT can not display non ASCII very well.
   I can use the natvie unicode characters in draft, but many readers will not display it correctly.
   According to my current understanding,  U+XXXX is still the proper way to be easily understood by most readers.
   Many years ago, IETF EAI WG also discussed this related issue.
   I still do not see which rfc uses the natvie unicode characters directly.

   
   If possilbe, I may suggest to add some texts in the draft, which says "in future, the natvie unicode characters instead of U+XXXX notation are suggested to use in the document"

Best Regards
Jiankang Yao

> -----原始邮件-----
> 发件人: "Patrick Mevzek" <pm@dotandco.com>
> 发送时间: 2018-11-02 12:54:37 (星期五)
> 收件人: regext@ietf.org
> 抄送: 
> 主题: [regext] draft-ietf-regext-bundling-registration and characters representation
> 
> Hello,
> 
> This draft, by essence, needs and uses a lot of characters outside of ASCII and for these use the U+XXXX notation.
> 
> There is now however RFC7997 (The Use of Non-ASCII Characters in RFCs) and among other things it says:
> 
> - the encoding of future RFCs will be in UTF-8
> - Where the use of non-ASCII characters is purely part of an example
>    and not otherwise required for correct protocol operation, escaping
>    the non-ASCII character is not required.
> - The RFC Editor encourages the use of the U+ notation except within a
>    code component where one must follow the rules of the programming
>    language in which the code is being written.
> 
> 
> So maybe the XML examples could be rewritten by using the native unicode characters
> instead of the U+ notation, as I believe it would make them far more understandable.
> 
> In the text, the other recommendations of the above RFC could be applied to have
> more standardized handling.
> 
> -- 
>   Patrick Mevzek
>   pm@dotandco.com
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

v2.23.0 | Report a Bug | By Email