IETF Logo Mail Archive

Re: [T2TRG] draft-hartke-t2trg-ciri-00 review

Carsten Bormann <cabo@tzi.org> Mon, 21 January 2019 20:31 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60519126BED; Mon, 21 Jan 2019 12:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=unavailable 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 W21oVN-ivUe0; Mon, 21 Jan 2019 12:31:49 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 698C3124408; Mon, 21 Jan 2019 12:31:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x0LKVZ6k019478; Mon, 21 Jan 2019 21:31:40 +0100 (CET)
Received: from [192.168.217.116] (p54A6CC50.dip0.t-ipconnect.de [84.166.204.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 43k39f55Mqz1Br6; Mon, 21 Jan 2019 21:31:34 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CY4PR21MB0168C83AF295761F73FCDF7FA39F0@CY4PR21MB0168.namprd21.prod.outlook.com>
Date: Mon, 21 Jan 2019 21:31:33 +0100
Cc: Ari Keränen <ari.keranen@ericsson.com>, "draft-hartke-t2trg-ciri@ietf.org" <draft-hartke-t2trg-ciri@ietf.org>, "T2TRG@irtf.org" <T2TRG@irtf.org>
X-Mao-Original-Outgoing-Id: 569795492.247372-3a5cacd512cc2531a46bde78b944b981
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0D234F0-51D8-4543-9344-43999C304D73@tzi.org>
References: <58aa0ae4-b3fe-abf7-9bda-4908ef0b3fd7@ericsson.com> <CY4PR21MB0168C83AF295761F73FCDF7FA39F0@CY4PR21MB0168.namprd21.prod.outlook.com>
To: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/CWbUmGWUk1scKv6qEummVT51wgk>
Subject: Re: [T2TRG] draft-hartke-t2trg-ciri-00 review
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2019 20:31:50 -0000

Hi Dave,

I’m not sure that we need to carry all that baggage.
E.g.:

> P.S.: An example of one incompatibility between RFC 3987 and what is widely implemented
> in browsers, is how percent encoding is interpreted.  In RFC 3987 it's percent-encoded UTF-8,
> whereas in implementations it's percent-encoded in whatever the charset is of the document
> (or whatever) you got the IRI out of, which may or may not be UTF-8.   Again this is just one
> of many examples.

“Then don’t do that.”  For CORE, we already have decided to inhabit a UTF-8-only world.
We also may not need to use percent encoding at all for CIRIs.

In summary, I’m not sure the experience the Internationalization community has with IRIs carries very far in the simplified world created by CORE and CIRIs.

But I would sure be interested which problems IRIs created, in particular those that were not with legacy encodings.
Further pointers are very welcome.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email