IETF Logo Mail Archive

[art] Modern Network Unicode

Carsten Bormann <cabo@tzi.org> Sun, 07 July 2019 20:14 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92A741200B4 for <art@ietfa.amsl.com>; Sun, 7 Jul 2019 13:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 WMQd-PeN9CYa for <art@ietfa.amsl.com>; Sun, 7 Jul 2019 13:14:44 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C8E4120099 for <art@ietf.org>; Sun, 7 Jul 2019 13:14:44 -0700 (PDT)
Received: from [192.168.217.110] (p548DC676.dip0.t-ipconnect.de [84.141.198.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 45hfv61XXPzyP1; Sun, 7 Jul 2019 22:14:42 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
X-Mao-Original-Outgoing-Id: 584223278.688527-ffda993947fa01f603b1696d0e3a74b7
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Sun, 07 Jul 2019 22:14:41 +0200
Message-Id: <CE3AD543-5847-4CAA-9B37-B293BF74C7D8@tzi.org>
To: art@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/1bMdNOgaMfkk5B4RNmlbx782SG0>
Subject: [art] Modern Network Unicode
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jul 2019 20:14:47 -0000

This week, I have been asked twice (for independent drafts) what these
drafts should say about their usage of Unicode.  It turns out, we have
an RFC that is almost, but not entirely unlike what is needed to
reference for a new protocol that uses text: RFC 5198.
I have tried to build on that in the very short draft:

https://tools.ietf.org/html/draft-bormann-dispatch-modern-network-unicode

I would expect that such a specification, once completed, would be a
useful point of reference for any new protocols that need to use text
without any specific requirements imposed by their applications.
(Protocols that already have been around probably benefit less,
because there always are legacy considerations.)

I'm not yet asking for dispatching this document; right now I would
just like to receive feedback from this esteemed community to further
improve the document.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email