IETF Logo Mail Archive

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

Dave Thaler <dthaler@microsoft.com> Mon, 21 January 2019 20:36 UTC

Return-Path: <dthaler@microsoft.com>
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 A46AA1277CC for <t2trg@ietfa.amsl.com>; Mon, 21 Jan 2019 12:36:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.554
X-Spam-Level:
X-Spam-Status: No, score=-6.554 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 m7rIroD7rG8o for <t2trg@ietfa.amsl.com>; Mon, 21 Jan 2019 12:35:59 -0800 (PST)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-eopbgr790134.outbound.protection.outlook.com [40.107.79.134]) (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 16F581276D0 for <T2TRG@irtf.org>; Mon, 21 Jan 2019 12:35:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mDZcDobxHk8tAHha7cPKJHn5DZn6IdJOQRpHj7mVEa4=; b=bb7xw3w/zAC54FiUA/tdm9FZ9g4zDxBpOkCqOc45ODtqJoOaMRGCOx6RzWoX1utOYu99yiwr4Hx5OXveI63r7vFZYwTSv89IuuOwj8Cc6z1UyYAF4mAB3W3hFHunM5lGaWbrT0B1U1xrOoq3LZzGo5DpCxczjwMQq9S+YhBjKOw=
Received: from CY4PR21MB0168.namprd21.prod.outlook.com (10.173.192.150) by CY4PR21MB0134.namprd21.prod.outlook.com (10.173.189.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1558.7; Mon, 21 Jan 2019 20:35:53 +0000
Received: from CY4PR21MB0168.namprd21.prod.outlook.com ([fe80::a170:a2b7:8ea1:b401]) by CY4PR21MB0168.namprd21.prod.outlook.com ([fe80::a170:a2b7:8ea1:b401%2]) with mapi id 15.20.1558.014; Mon, 21 Jan 2019 20:35:53 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Carsten Bormann <cabo@tzi.org>
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>
Thread-Topic: [T2TRG] draft-hartke-t2trg-ciri-00 review
Thread-Index: AQHUsbaoN2sOHNFPSUOGL+7Ra8iqEKW6JRwQgAAID4CAAABRsA==
Date: Mon, 21 Jan 2019 20:35:52 +0000
Message-ID: <CY4PR21MB016884C73B7F842FFF5A53C1A39F0@CY4PR21MB0168.namprd21.prod.outlook.com>
References: <58aa0ae4-b3fe-abf7-9bda-4908ef0b3fd7@ericsson.com> <CY4PR21MB0168C83AF295761F73FCDF7FA39F0@CY4PR21MB0168.namprd21.prod.outlook.com> <A0D234F0-51D8-4543-9344-43999C304D73@tzi.org>
In-Reply-To: <A0D234F0-51D8-4543-9344-43999C304D73@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=dthaler@ntdev.microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-01-21T20:35:51.8126254Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=c07c07d4-d0b3-4610-9f24-6a5c88e82679; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic
x-originating-ip: [73.59.106.235]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR21MB0134; 6:Jb90r6+VSGzo7szPe7q1UnEQOze/ia6BEWAWrMu91PFLEoU9Dn+y3062nCNsnkLCWPp7VSQXIMMzGM+Q1C4N7BW/8ofTfR+bUgC4t6zWGXAzlkxYolYSxrox7G+7qusAArJVMsLSWEd6BHah2pPiTzvWJUQPySAnM4z+8UbVe/oX5e8zG5cGMRF9Lj43tHdjO3+xucvDkTo/F/dLtV86/kltLqQ9yzC0Hv+tMiZ7xWsPMG+BZ7cvJa4/2x/4C+TIRLQK/Versd7n5K/oPrj34AX11viyuZxU1yDPiel58JwlqlMiv81pv9aN/xECTdvNJaZKpUwXZKXgZeJtyUJeb9P8f2578woS0TzidARx7tjjYBJT1xobWUleIaoVNJEv2zt7HDsKYqDs1agqKiyvgSPp7J36yRy7XiWSxXeGMtI2ocJaUOcb4zhGJd9CT035YmyDFqN7s03F5FFjec8g9A==; 5:+yOJFEMt7Ws57sEVeQ/E+KABfW2o10y+t0LeI8mEeS1CEFAnuuaeVu/H/dTtkNHEiXSzAucDKgAJ5eg0Tc2yDBxUq9cCBRi71RuEMrdodvVq3+IMETN95+XMJCIFYTQOo+hZd+slkCtk/eIFz6CZbwoSohvIJbRO6JhP14E/cbnSMt6Xok92P2xka0sgFyxzOmjdbMP5ETg/Fq0j8gnTpA==; 7:tBKpeYCUI3BQe0HfuMh50lg7Z1EDV9UC+VNBAyZDm3tzlNHxw6GjoktCYoCmZ8XMhv31IHRwOpLOpnlEQlc7ECRkHYyJMT+ieiUvZDpOv8TzCEue8tBRUQHzoVY6j7oI16vLJ77knaPgguZD4z+uig==
x-ms-office365-filtering-correlation-id: 24e15b95-ce28-469c-93d5-08d67fe009b3
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600109)(711020)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:CY4PR21MB0134;
x-ms-traffictypediagnostic: CY4PR21MB0134:
x-ms-exchange-purlcount: -3
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com;
x-microsoft-antispam-prvs: <CY4PR21MB013449C767F768AF3CA76833A39F0@CY4PR21MB0134.namprd21.prod.outlook.com>
x-forefront-prvs: 0924C6A0D5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(39860400002)(376002)(366004)(396003)(346002)(13464003)(189003)(199004)(53546011)(66066001)(6506007)(102836004)(14454004)(7696005)(76176011)(106356001)(26005)(9686003)(2906002)(53936002)(105586002)(256004)(8936002)(81156014)(81166006)(10290500003)(10090500001)(8990500004)(66574012)(478600001)(86612001)(8676002)(86362001)(305945005)(33656002)(55016002)(97736004)(71190400001)(71200400001)(229853002)(99286004)(6436002)(486006)(446003)(6116002)(316002)(6916009)(4326008)(186003)(25786009)(22452003)(74316002)(68736007)(3846002)(54906003)(6246003)(476003)(7736002)(11346002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR21MB0134; H:CY4PR21MB0168.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: xUbRYSmrLH3X7LxjpFCRYqoPKuJZp+WV3T0DtW2mBZsPtO/qWh9q0vg5zeT4+i/aPa5i50bFWCfVnXd0ge2XMmxctEYzEVVC0z3i4TwAHklvibs9yDICLteDdRtgD3LL1AdWH4u84vGGDYS1xKDgquj4yHtUK6kcG6agS3gpdWDXYbKcfvEZaELbPt9Zwww3SE8Pick2WRWfqYOX5V+jhv1Wc+Dg5lBqyz5kChHXsyg1PUd2KevO560GhfgD0Sb3yVtoPRlVcVoT1xnNUHTZ8D0vIhQ+iR+VxtpzgyyWktnW8N2zdi0EzXYcWuI/Vl9gySD/0wBcU5Cd1KJS7MO2UO3Z5DeoWuQV1M0N59JI9iyZza8nf4YW72jI8WfqNplh6lUFQzSVFMz4xpoyBQEdYoVO0jd5U5JO/FJHD3B/9jQ=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 24e15b95-ce28-469c-93d5-08d67fe009b3
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2019 20:35:53.0058 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0134
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/un9BLAz-XDvidC843Dx-OwHjcao>
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:36:01 -0000

Once you have COAP/HTTP proxies, you pull in all that baggage.

Furthermore, the conventional wisdom is that there's no problem that
putting IRIs on the wire solves that isn't better solved by putting URIs
on the wire.

I understand you're asking for pointers, and I'll bring that up with the
IETF Internationalization Directorate that's now being formed.

Dave

-----Original Message-----
From: Carsten Bormann <cabo@tzi.org> 
Sent: Monday, January 21, 2019 12:32 PM
To: Dave Thaler <dthaler@microsoft.com>
Cc: Ari Keränen <ari.keranen@ericsson.com>; draft-hartke-t2trg-ciri@ietf.org; T2TRG@irtf.org
Subject: Re: [T2TRG] draft-hartke-t2trg-ciri-00 review

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