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

Dave Thaler <dthaler@microsoft.com> Mon, 21 January 2019 23:22 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 72A7212D4ED for <t2trg@ietfa.amsl.com>; Mon, 21 Jan 2019 15:22:35 -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 w61y_10vikC6 for <t2trg@ietfa.amsl.com>; Mon, 21 Jan 2019 15:22:32 -0800 (PST)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-eopbgr820118.outbound.protection.outlook.com [40.107.82.118]) (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 511A212D4E7 for <T2TRG@irtf.org>; Mon, 21 Jan 2019 15:22:32 -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=DBmNihVhWP5v2/Ev+q0rBL4gtIrZ83/o57brLi6ORNc=; b=fQm7fgjyp7rt4kBDxFshTtO4xVJqlskbH4cbBTjDPFHOVXLfZpKQawmEl6Ldtgr4uRe9tRPKLvg0ngp1sptYbCeE+n4JUWTxwLiv5sZTx49QkHiSQVqGP8KWOa2ECrEDO21YDJ87I1NiByF/lBYg7dXgF2+yagZZZ0tRZSlZVA8=
Received: from CY4PR21MB0168.namprd21.prod.outlook.com (10.173.192.150) by CY4PR21MB0789.namprd21.prod.outlook.com (10.175.121.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1558.6; Mon, 21 Jan 2019 23:22:30 +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 23:22:30 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Klaus Hartke <hartke@projectcool.de>
CC: Carsten Bormann <cabo@tzi.org>, "draft-hartke-t2trg-ciri@ietf.org" <draft-hartke-t2trg-ciri@ietf.org>, Ari Keränen <ari.keranen@ericsson.com>, "T2TRG@irtf.org" <T2TRG@irtf.org>
Thread-Topic: [T2TRG] draft-hartke-t2trg-ciri-00 review
Thread-Index: AQHUsbaoN2sOHNFPSUOGL+7Ra8iqEKW6JRwQgAAID4CAAABRsIAAGBeAgAAVt/A=
Date: Mon, 21 Jan 2019 23:22:29 +0000
Message-ID: <CY4PR21MB0168CEDC3F1EB41FCD21AD28A39F0@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> <CY4PR21MB016884C73B7F842FFF5A53C1A39F0@CY4PR21MB0168.namprd21.prod.outlook.com> <CAAzbHva=YjK5j=W9aFDikYrLLJQ+pDcRy2HV71e0JbyHu_1BBw@mail.gmail.com>
In-Reply-To: <CAAzbHva=YjK5j=W9aFDikYrLLJQ+pDcRy2HV71e0JbyHu_1BBw@mail.gmail.com>
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-21T23:22:26.7924117Z; 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=a09f309f-4b9e-47f3-9147-5322cc1726cc; 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; CY4PR21MB0789; 6:C1I4eFqnHaM0nYWILKilQcRTKJRC34hLu3ETEk3RU9i3hNf3HU2hRg+o/j2e6k4UEMb+VyYV71gRaIaI9P+K0dXKEh8BN+EnVNE1q2gtCNPqyjH2+ZXTtA4pnz4iX3ce9vswZjYP7No21ZVeKvC0e8UTESGJeVoMGJ+2wx75khSj0cUgDbnwoz3BlghBvayH8KTS4vt3nAWz/bSGylOv6ksNnz7Vb7qsiDcYLDiYnD4s0cbPce9SMNuJhMAVcepTIhkH1DVNZmucmI23DEeE8OKvIZJkyxezsz2YYfuALz6aOqt1sF8SFdVFN5NAmtl4eg+YwgZcOkrRfBIuzolmH7Ww45bDSP2qXxNI6rSzZWVkSUHV41Q6vK46VeUn/qgXeZj2nhYr7mHdPs111RfE9baW5c5ZKhw9Bmdj63l0o+lhnkXwwfwxu47UDe2vgm8lCNVvm1dA8SHcQRZyzYihWA==; 5:sV1pdJSeI5Y64hnJ0ucsUEN7Mo+sSp4hAsdDKV8c86j16A7p7OQ3YbANMiL5uz1fh/U/KvmbtL1eGFEZW995NobEcRbs1alywYalVNMNWqU0OCnQwU/ddevYimTBrXfPEV6BDp4XqnQcgPHcmmnYyGc8kPHkx42kpCVbU3gO0jdmM4B4I8EjEAtpVzkkb4BK42gOioE/qTM6baTvEa7D2A==; 7:ARl+8PMLQ/ikeiU5q2/S2CY8Nscfw9rRhaxfBKSEoAagbTwxfRuMIzmOJi2oA7rsUVhl7BtKbYS2C6EVSqO0eCZIxXuHr4US3JdVTRztondlr+Hbh31rf4q40GNF0ilVcrEFwYkm7aWQJ/5EGVC84w==
x-ms-office365-filtering-correlation-id: d38121e8-ecfb-4a6b-d608-08d67ff75055
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600109)(711020)(4618075)(2017052603328)(7193020); SRVR:CY4PR21MB0789;
x-ms-traffictypediagnostic: CY4PR21MB0789:
x-ms-exchange-purlcount: 2
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com;
x-microsoft-antispam-prvs: <CY4PR21MB0789D122E24E3CD52A7B63CAA39F0@CY4PR21MB0789.namprd21.prod.outlook.com>
x-forefront-prvs: 0924C6A0D5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(136003)(396003)(366004)(376002)(189003)(199004)(54094003)(13464003)(2906002)(55016002)(86362001)(3846002)(305945005)(6116002)(476003)(68736007)(86612001)(74316002)(66066001)(4326008)(93886005)(7736002)(105586002)(316002)(10090500001)(256004)(446003)(99286004)(11346002)(22452003)(76176011)(8936002)(14454004)(97736004)(106356001)(8990500004)(6916009)(10290500003)(6506007)(54906003)(9686003)(71200400001)(478600001)(53546011)(966005)(53936002)(26005)(102836004)(229853002)(25786009)(186003)(81156014)(8676002)(6436002)(7696005)(33656002)(6246003)(486006)(6306002)(71190400001)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR21MB0789; 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: X9inLOnHIrnvJD2uKbFxjYTLDRDPSRl0GXCNJyzssCnT7epP3g36Qr1nVO9ikv1HfadDNPUUvuXlPyP0naIKcojaXD3EyTUHGoNroF2tigkst1dMsxmzcV8YwNEaS9nrVtkS0vi/S2LfVGJ6iisuOl7ZJOf6LhoH0gJR94y2rVjNBAsmpKuDUwEyfSa3u6NmjgD+KacEiOK4hJOAN+++00Jzc+QeQUXtq8Y/v5s4Yb2a8AfcXyL4UPUR1G+v38tWgn6TKgOO13lGdrjHB8cHM5MsBsLSmgNIXHXB1TdwiUYjzZCrMqNX4l/ZbC/7y3+ygL+TZge4GGZf6xn/bECk9O9z5S7TeiUmwCmGTxrg5vecTOG+iMBxA6WbLPrGEgQ1oc7b06ysBqokbIXwHQIwO/2g2MST+snDuS2vuaqLzXs=
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: d38121e8-ecfb-4a6b-d608-08d67ff75055
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2019 23:22:29.7173 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0789
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/GMLjouVIW69jByvCXwYE36Mhk20>
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 23:22:35 -0000

I agree that "Recompose the CBOR-encoded IRI components to a URI" could be
done without referencing RFC 3987 and without using the term "IRI" (as opposed to CIRI
which you can define).  Although I wonder if in so doing, you'd run into all the same
issues that failed to achieve consensus with the rfc3987bis.

And I also agree that draft-hartke-t2trg-coral-06 likely has the same issues because
it uses IRIs instead of URIs.

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

Dave Thaler wrote:
> Once you have COAP/HTTP proxies, you pull in all that baggage.

Right. Currently, converting a CIRI to CoAP options is defined as:

1. Recompose the CBOR-encoded IRI components to an IRI 2. Convert the IRI to a URI according to RFC 3987 3. Decompose the URI to CoAP options according to RFC 7252

It sounds like a good idea to rewrite section 4.2 to output a URI and define the conversion as:

1. Recompose the CBOR-encoded IRI components to a URI 2. Decompose the URI to CoAP options according to RFC 7252

> 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.

The Semantic Web relies extensively on IRIs, and some formats like Turtle put IRIs "on the wire" rather than URIs. E.g.:

   @prefix loc: <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fexample.org%2Flocation%2F&amp;data=02%7C01%7Cdthaler%40microsoft.com%7Cc9d0643be43d49fc77ab08d67febbc9f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636837047803044411&amp;sdata=AiwjzFDEBICXw%2B%2BpJOUok5l1eTBaszbiQl8YW6n91Ng%3D&amp;reserved=0> .

   loc:Montréal a loc:city .

Would this be considered "UI layer"? If not, I'm not sure if URIs would improve things:

   loc:Montr%C3%A9al a loc:city .

(Is that even valid?)

Since the CoRAL textual format [1] uses IRIs in a similar way, some advice on IRIs in formats intended to be read and written by humans would be very welcome.

Klaus

[1] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-hartke-t2trg-coral-06&amp;data=02%7C01%7Cdthaler%40microsoft.com%7Cc9d0643be43d49fc77ab08d67febbc9f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636837047803044411&amp;sdata=HbsWjAZLY%2B6kw2qQrarD6pt2478qZsZcRyflKk5VoRE%3D&amp;reserved=0