Re: [art] Modern Network Unicode

"Manger, James" <James.H.Manger@team.telstra.com> Mon, 08 July 2019 02:22 UTC

Return-Path: <James.H.Manger@team.telstra.com>
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 B8CD11200FF for <art@ietfa.amsl.com>; Sun, 7 Jul 2019 19:22:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=team.telstra.com
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 xeGGM-NTg4zn for <art@ietfa.amsl.com>; Sun, 7 Jul 2019 19:22:17 -0700 (PDT)
Received: from ipxcvo.tcif.telstra.com.au (ipxcvo.tcif.telstra.com.au [203.35.135.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 624EB1200D8 for <art@ietf.org>; Sun, 7 Jul 2019 19:22:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.63,465,1557151200"; d="scan'208";a="202467787"
X-Amp-Result: SKIPPED(no attachment in message)
Received: from unknown (HELO ipcbvi.tcif.telstra.com.au) ([10.97.217.204]) by ipocvi.tcif.telstra.com.au with ESMTP; 08 Jul 2019 12:22:14 +1000
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipcbvi.tcif.telstra.com.au with ESMTP; 08 Jul 2019 12:21:55 +1000
Received: from wsapp5585.srv.dir.telstra.com (10.75.3.67) by WSMSG3705.srv.dir.telstra.com (172.49.40.203) with Microsoft SMTP Server (TLS) id 8.3.485.1; Mon, 8 Jul 2019 12:18:44 +1000
Received: from wsapp5584.srv.dir.telstra.com (10.75.131.20) by wsapp5585.srv.dir.telstra.com (10.75.3.67) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 8 Jul 2019 12:18:44 +1000
Received: from AUS01-SY3-obe.outbound.protection.outlook.com (10.172.229.125) by wsapp5584.srv.dir.telstra.com (10.75.131.20) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 8 Jul 2019 12:18:43 +1000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=team.telstra.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SJx5hiHXp3+x/mNrHjbT9WELhhqh3bu4EvcVcKlhAQ8=; b=NV1g4w6TDRzP/FwLo9HFNDLqupTvMTlBG9cOwVQXMFB/RC9zzSs7xkImfD5ttAY4lHklWLCNe5DKUUxvGtoG20q2Dqb6wKY5k5PenZiTTF7xHZK9wtMpBNrwMITV/Iw6xGDJsBJWvruq/vtgLUhN8asSmhD78ec2psFVZ6YVtMg=
Received: from SY2PR01MB2764.ausprd01.prod.outlook.com (52.134.190.138) by SY2PR01MB3114.ausprd01.prod.outlook.com (52.134.187.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.19; Mon, 8 Jul 2019 02:18:43 +0000
Received: from SY2PR01MB2764.ausprd01.prod.outlook.com ([fe80::ad81:55b8:5070:b4a6]) by SY2PR01MB2764.ausprd01.prod.outlook.com ([fe80::ad81:55b8:5070:b4a6%7]) with mapi id 15.20.2052.020; Mon, 8 Jul 2019 02:18:43 +0000
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Carsten Bormann <cabo@tzi.org>, "art@ietf.org" <art@ietf.org>
Thread-Topic: [art] Modern Network Unicode
Thread-Index: AQHVNQDTaSG9f25hI0SJlwjKSYpR5qa/+TLA
Date: Mon, 08 Jul 2019 02:18:42 +0000
Message-ID: <SY2PR01MB2764141CB5B9863D0B358C39E5F60@SY2PR01MB2764.ausprd01.prod.outlook.com>
References: <CE3AD543-5847-4CAA-9B37-B293BF74C7D8@tzi.org>
In-Reply-To: <CE3AD543-5847-4CAA-9B37-B293BF74C7D8@tzi.org>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.1.100.23
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=James.H.Manger@team.telstra.com;
x-originating-ip: [203.35.9.18]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 444fa598-da08-44c9-090f-08d7034a9950
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:SY2PR01MB3114;
x-ms-traffictypediagnostic: SY2PR01MB3114:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <SY2PR01MB3114DE27B5417BF4099C8FBCE5F60@SY2PR01MB3114.ausprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 00922518D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(346002)(39860400002)(136003)(366004)(396003)(199004)(189003)(13464003)(26005)(99286004)(478600001)(71190400001)(86362001)(71200400001)(186003)(316002)(74316002)(7696005)(476003)(2501003)(11346002)(6116002)(229853002)(446003)(3846002)(66066001)(25786009)(305945005)(102836004)(76176011)(7736002)(72206003)(53546011)(6506007)(486006)(966005)(66446008)(6306002)(66556008)(64756008)(81166006)(66476007)(2906002)(73956011)(256004)(68736007)(76116006)(52536014)(6436002)(66946007)(14454004)(53936002)(5660300002)(110136005)(6246003)(9686003)(8936002)(81156014)(55016002)(33656002)(8676002); DIR:OUT; SFP:1102; SCL:1; SRVR:SY2PR01MB3114; H:SY2PR01MB2764.ausprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: team.telstra.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: RAAWSmprJeqc6USL07WQCWFZx5wZvHHla7c+cZNf+4gX3as/59VP5cs8S7DwjX/fpfpjk86ReZUqCnw7rLivE4b/pGEfJoTg5GfzKSxso8ddAszgq+R7bmzymx4niXqA3o6QbKv++B6GA1lQb6cjxf83uO6CCaYyiMlYRH6nIPuiYy/ecIZ21cy6MeE+KE3xX/Ol5adMwQrvoGSirVtrt8kdk9C4pytSFwwbzKOUuq4dRK6wq6CNKZ5d4Y1SBzmsx1jUbDwmGruBM7Ba+qu7xB2m5rFX/chOnfm4WbT0CeMI5SVoooBXcGhvXppW1OrdK2Cjd+Nah7RZ6xNEF0IR813dzuk2oegs8g4n6YSupJX1zMBAValApthLFVIWlHe48h9XoXzZqOq5zJxpdwZagT6XjCAfJqkd+E3t6NDc3u4=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 444fa598-da08-44c9-090f-08d7034a9950
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2019 02:18:42.9667 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 49dfc6a3-5fb7-49f4-adea-c54e725bb854
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: James.H.Manger@team.telstra.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SY2PR01MB3114
X-OriginatorOrg: team.telstra.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/9RIIet5-x1FvMEHyE8ZB9Ff4qKk>
Subject: Re: [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: Mon, 08 Jul 2019 02:22:22 -0000

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

Would be nicer if it wasn't written as a diff from RFC5198 (Network Unicode). That is, if you could get all the rules directly from this doc. For instance, I assume Clean Modern Network Unicode must/should be NFC. Keep the RFC5198 comparisons for an informative annex.

ABNF for uchar doesn't exclude U+2028 and U+2029.

--
James Manger

-----Original Message-----
From: art <art-bounces@ietf.org> On Behalf Of Carsten Bormann
Sent: Monday, 8 July 2019 6:15 AM
To: art@ietf.org
Subject: [art] Modern Network Unicode

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

_______________________________________________
art mailing list
art@ietf.org
https://www.ietf.org/mailman/listinfo/art