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

Patrick Mevzek <pm@dotandco.com> Fri, 02 November 2018 04:54 UTC

Return-Path: <pm@dotandco.com>
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 23A8E12D4EA for <regext@ietfa.amsl.com>; Thu, 1 Nov 2018 21:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=n85J+dGS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JqxYxXYm
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 OPiN4DB_5Esx for <regext@ietfa.amsl.com>; Thu, 1 Nov 2018 21:54:39 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FEF3129C6A for <regext@ietf.org>; Thu, 1 Nov 2018 21:54:39 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 99D62223A1 for <regext@ietf.org>; Fri, 2 Nov 2018 00:54:38 -0400 (EDT)
Received: from web6 ([10.202.2.216]) by compute3.internal (MEProxy); Fri, 02 Nov 2018 00:54:38 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:date; s=fm1; bh=UznBAI4iJ1ootJrrkhB4XU5GpF xFHkXgnrfBXEoK1v0=; b=n85J+dGS9H84a8nk6J4YJXs/Hq8EC4trQSddjbkbNx 1/7wTTUPUdAjFPWOb+kK1Q1w3En8uD5uXsLtnrYrAv0Ax0MBzqXxIeC3NJn/VZtx Uf3pmSGXYtNQIDnnqacSHFzz4OJISKHzor33BQPbYew0sk3sG8LL3UArfcsTEtwu Ko/Lu/q9g6rM5tcJT/gcNzZ1kr54fE/Oj+qzCfY0iUHJoPfH67Nm9/ZyyGWZ6Ks9 TtVuDg02KXYdo/S6lnOgFVTHyFhor0jDxschHuAs+6kgz7Rbf8JzovVGMoyvOnPQ mPYy/cyp3rxPYKQu4y/Xgm6E91pdHQMs75rkvj3kUsbQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=UznBAI 4iJ1ootJrrkhB4XU5GpFxFHkXgnrfBXEoK1v0=; b=JqxYxXYmMptCOa5oLLx767 HXpDtD26qubLkZv+BCmTrg6hr7jVB8/nUbuLTNP7721kz3WPYOm1A1f4vyWpuoIU ywzKpAebF7wG3armucbfnWLAQ41yEac2r1q3ufa98iFxG5oKKmu1TXUtdmw0tXC8 7efH7cFowXDijxWnUn8Z0+nWvfLbIXU2etVVIsJrtFRvcqWkBk3r0KQ0NC+bDuDJ MQdiI1g0FE3CNLYs4Cak1op0Nf0IG3WkkQvFrGen2mUIyuREPiKzx8/YOQYdPitd m3nFvqDaMy752KypYFFsW1x0mMYSnPQdvi9EQX/c4RHDk0IMTfXyRHjmPVw+rgvg ==
X-ME-Sender: <xms:jtjbW6YBhCNVUsz-EVNn4O8k-r7OC8zNXhj__13ZZ8QJx4VWH8lfgfP6lKM>
X-ME-Proxy: <xmx:jtjbW7RkM265RdYQEUEvoDcUohYEAAUo9c9NsdENb9Y0u8ZZQiJR7w> <xmx:jtjbW6IBDJpGMRjUbHLQboA0o_r7v34UokMqpfc0mHZWzpgNjgaymA> <xmx:jtjbW6VOXiBG3c0qL71kAhSB9UzqOR6dtveEG53VfSpJub8rdnzaGA> <xmx:jtjbW2R8ZqLk5M17dL9QAfkdRhX7T_UjObGs_Vtq2RnstT49e-INJw> <xmx:jtjbW6BUDQBFhnr_j4HWYnBbD5XVcw_KaH9mWPXMM-ukpvh1uIlF4Q> <xmx:jtjbWzTXKc5AT2WflqG71iFBtsNORLYUHKn-_PPf0mVBFBcOGva7Vg>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 08C144146; Fri, 2 Nov 2018 00:54:37 -0400 (EDT)
Message-Id: <1541134477.2549895.1563050056.54421396@webmail.messagingengine.com>
From: Patrick Mevzek <pm@dotandco.com>
To: regext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-21384fa2
Date: Fri, 02 Nov 2018 05:54:37 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/zllhH9OnRTfRmubUT-0vl4rbzB0>
Subject: [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: Fri, 02 Nov 2018 04:54:41 -0000

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