
From nobody Fri Mar  3 16:03:49 2017
Return-Path: <agenda@ietf.org>
X-Original-To: t2trg@irtf.org
Delivered-To: t2trg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7CF51299D3; Fri,  3 Mar 2017 15:55:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <ari.keranen@ericsson.com>, <t2trg-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148858533994.15846.3506419243037592048.idtracker@ietfa.amsl.com>
Date: Fri, 03 Mar 2017 15:55:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/uBrwhYzFzBSbXo6kkcDwXgssmiU>
Cc: t2trg@irtf.org, irtf-chair@irtf.org
Subject: [T2TRG] t2trg - Requested session has been scheduled for IETF 98
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Fri, 03 Mar 2017 23:55:40 -0000

Dear Ari KerÃ¤nen,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

t2trg Session 1 (1:30:00)
    Monday, Afternoon Session I 1300-1500
    Room Name: Vevey 1/2 size: 200
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: Thing-to-Thing
Area Name: IRTF
Session Requester: Ari KerÃ¤nen

Number of Sessions: 1
Length of Session(s):  1.5 Hours
Number of Attendees: 120
Conflicts to Avoid: 
 First Priority: apparea core ace 6tisch lpwan 6lo roll ice icnrg cbor
 Second Priority: dnssd saag irtfopen
 Third Priority: lwig httpbis detnet quic


People who must be present:
  Carsten Bormann
  Ari Keranen

Resources Requested:
  Meetecho support in room

Special Requests:
  Please also avoid any IoT related BOFs that might come up.
---------------------------------------------------------


From nobody Fri Mar  3 16:25:27 2017
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 9C65612706D; Fri,  3 Mar 2017 16:25:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 frFQV70myTzd; Fri,  3 Mar 2017 16:25:00 -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 03E0B128AB0; Fri,  3 Mar 2017 16:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v240Oj9j005097; Sat, 4 Mar 2017 01:24:45 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (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 3vZmyj0KjVzDJ6h; Sat,  4 Mar 2017 01:24:45 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <880044A0-E3F0-436D-BB45-6751A01EDB6B@tzi.org>
Date: Sat, 4 Mar 2017 01:24:44 +0100
X-Mao-Original-Outgoing-Id: 510279884.362881-152b94dac84d17b5022d5bfde5097d7b
Content-Transfer-Encoding: quoted-printable
Message-Id: <B47D2599-0FB8-46FB-B8A6-89637583B30D@tzi.org>
References: <880044A0-E3F0-436D-BB45-6751A01EDB6B@tzi.org>
To: ace@ietf.org, "core@ietf.org WG" <core@ietf.org>, cose@ietf.org, cbor@ietf.org, t2trg@irtf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/mtuRImvc5ffJ8-opU7Fptu2RQgA>
Subject: [T2TRG] Constrained Node/Network Cluster @ IETF98: FINAL AGENDA
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Sat, 04 Mar 2017 00:25:02 -0000

Here is my usual eclectic condensed agenda based on the "FINAL" AGENDA
for IETF98.  Remember that agenda definitions are never really
"FINAL"...  "While this is considered the final agenda for printing,
changes may be made to the agenda up until and during the
meeting. Updates will be reflected on the web versions of the agenda."

Compared to the draft agenda, this has mostly room changes.  v6ops
moved around, and tsvarea got extended to an almost four-hour meeting.

All times are CDT (UTC-0500) -- yes, the US will be on DST already for
a couple of weeks, while Europe moves over right on Mar 26th.
(The browser timezone function still is not yet reinstated on
https://datatracker.ietf.org/meeting/agenda-utc, for those who want to
listen from remote.)

Gr=C3=BC=C3=9Fe, Carsten


SUNDAY, March 26, 2017

0900-1700       IRTF*** icnrg, with some t2trg-related items on the =
agenda


MONDAY, March 27, 2017

0900-1130  Morning Session I
Zurich A	ART	dispatch	Dispatch WG
Zurich D	INT	homenet	Home Networking WG
Zurich C	SEC ***	ace	Authentication and Authorization for =
Constrained Environments WG

1300-1500  Afternoon Session I
Vevey 1/2	IRTF***	t2trg	Thing-to-Thing
Zurich A	OPS	anima	Autonomic Networking Integrated Model =
and Approach WG
Zurich B	RTG	bier	Bit Indexed Explicit Replication WG
Zurich G	RTG	detnet	Deterministic Networking WG
Zurich E/F	TSV	tsvarea	Transport Area Open Meeting

1520-1650  Afternoon Session II
Zurich A	SEC	tokbind	Token Binding WG
Zurich E/F	TSV	tsvarea	Transport Area Open Meeting

1710-1810  Afternoon Session III
Zurich E/F	GEN	wugh	WGs Using GitHub BOF
Zurich D	INT ***	lwig	Light-Weight Implementation Guidance WG
Montreux 3	SEC	curdle	CURves, Deprecating and a Little more =
Encryption WG
Zurich C	SEC	oauth	Web Authorization Protocol WG
Vevey 1/2	TSV	tsvwg	Transport Area Working Group WG

TUESDAY, March 28, 2017

0900-1130  Morning Session I
Zurich C	INT ***	6tisch	IPv6 over the TSCH mode of IEEE =
802.15.4e WG
Zurich D	IRTF	maprg	Measurement and Analysis for Protocols
Zurich E/F	SEC	tls	Transport Layer Security WG

1300-1430  Afternoon Session I
Zurich C	ART ***	core	Constrained RESTful Environments WG
Zurich D	INT	intarea	Internet Area Working Group WG
Zurich A	RTG	babel	Babel routing protocol WG

1450-1620  Afternoon Session II
Zurich G	ART	uta	Using TLS in Applications WG
Zurich E/F	SEC ***	teep	A Protocol for Dynamic Trusted Execution =
Environment Enablement BOF

1640-1840  Afternoon Session III
Zurich B	INT	dnssd	Extensions for Scalable DNS Service =
Discovery  WG
Zurich E/F	TSV	taps	Transport Services WG

WEDNESDAY, March 29, 2017

0900-1130  Morning Session I
Zurich A	INT ***	6lo	IPv6 over Networks of =
Resource-constrained Nodes WG

1300-1500  Afternoon Session I
Zurich C	INT ***	lpwan	IPv6 over Low Power Wide-Area Networks =
WG
Zurich A	OPS	v6ops	IPv6 Operations WG
Montreux 3	TSV	tcpinc	TCP Increased Security WG

THURSDAY, March 30, 2017

0900-1130  Morning Session I
Zurich D	INT	6man	IPv6 Maintenance WG
Zurich C	IRTF	icnrg	Information-Centric Networking
Zurich E/F	RTG	rtgarea	Routing Area Open Meeting
Vevey 1/2	TSV	quic	QUIC WG

1300-1500  Afternoon Session I
Zurich B	ART ***	cbor	Concise Binary Object Representation =
Maintenance and Extensions WG
Zurich G	SEC	acme	Automated Certificate Management =
Environment WG
Zurich A	TSV	tsvwg	Transport Area Working Group WG

1520-1720  Afternoon Session II
Zurich D	SEC	saag	Security Area Open Meeting

1740-1840  Afternoon Session III
Zurich B	RTG ***	roll	Routing Over Low power and Lossy =
networks WG

FRIDAY, March 31, 2017

0900-1130  Morning Session I
Vevey 1/2	ART	httpbis	Hypertext Transfer Protocol WG
Zurich E/F	INT	ipwave	IP Wireless Access in Vehicular =
Environments WG
Zurich A	OPS	anima	Autonomic Networking Integrated Model =
and Approach WG
Zurich C	SEC	oauth	Web Authorization Protocol WG

1150-1320  Afternoon Session I
Zurich C	ART ***	core	Constrained RESTful Environments WG



From nobody Mon Mar  6 06:57:26 2017
Return-Path: <ari.keranen@ericsson.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 5FDDA1295DA for <t2trg@ietfa.amsl.com>; Mon,  6 Mar 2017 06:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 doFzl8y_SMvI for <t2trg@ietfa.amsl.com>; Mon,  6 Mar 2017 06:57:22 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 8F37D129588 for <t2trg@irtf.org>; Mon,  6 Mar 2017 06:57:22 -0800 (PST)
X-AuditID: c1b4fb3a-29b639800000484c-20-58bd78d0ca36
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id AB.8F.18508.0D87DB85; Mon,  6 Mar 2017 15:57:20 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0319.002; Mon, 6 Mar 2017 15:57:15 +0100
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: Amsterdam meetings' logistics & agenda details
Thread-Index: AQHSlonxleZBgX7qL0CidxM9BalpNQ==
Date: Mon, 6 Mar 2017 14:57:14 +0000
Message-ID: <6E7D1975-5BF0-433E-A4E8-7AD0A2F02CBB@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DB5A6474509FD247A44FF0FCCD9D79B7@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyM2K7h+6Fir0RBvfOmVscmXKX1eL9gx4W ByaPyRsPs3lMW5QZwBTFZZOSmpNZllqkb5fAlXHp8V2WgsuMFRtXHmBrYFzN2MXIySEhYCJx +e8Cti5GLg4hgXWMEmvn9bGBJIQEFjFK3NzuCGKzCdhLTF7zEaxBREBVYuPMjawgNrOAksSB a1uYQWxhAXOJhavmQNXYSDx428YCYetJTJjeAFbDIqAisfn8USCbg4MXaOacXcUgYUYBMYnv p9YwQYwUl7j1ZD4TxG0CEkv2nGeGsEUlXj7+xwphK0k0LnkCdYKexI2pU9ggbGuJo8uOQsW1 JZYtfA3WyysgKHFy5hOWCYwis5CsmIWkfRaS9llI2mchaV/AyLqKUbQ4tbg4N93ISC+1KDO5 uDg/Ty8vtWQTIzBGDm75bbWD8eBzx0OMAhyMSjy8BTP2RAixJpYVV+YeYpTgYFYS4X2QszdC iDclsbIqtSg/vqg0J7X4EKM0B4uSOK/ZyvvhQgLpiSWp2ampBalFMFkmDk6pBsbUrlc/Ld++ zbn1vjlvb9fh6fNXKCvFHfoqVeG5JZRlVZW3wCGP27bnvkexCt4TuvW4JoTB+YLRwVXf5Gbm 8q6cdUyUmfmRWvnvfTopHQxs308mRD/57BNzpO53iG3Z6uq0Nfa8b2JWZtRra3xNr/9wYR3/ V+vH8+Zbfxbb7OIpt9OFzW1lRIUSS3FGoqEWc1FxIgA6vcKYjQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/SYXQyJfmSeCoFH3Ly5pS5Tlhx4A>
Cc: Carsten Bormann <cabo@tzi.org>
Subject: [T2TRG] Amsterdam meetings' logistics & agenda details
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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, 06 Mar 2017 14:57:24 -0000

Hi all,

We have now updated the agenda and logistics details (location and remote p=
articipation) of the Amsterdam T2TRG and joint OCF meetings: https://github=
.com/t2trg/2017-03-ocf/


Cheers,
Ari=


From nobody Mon Mar  6 09:00:06 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 812D112989C for <t2trg@ietfa.amsl.com>; Mon,  6 Mar 2017 09:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 d8pATnUUOckP for <t2trg@ietfa.amsl.com>; Mon,  6 Mar 2017 09:00:03 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E5E71294FB for <T2TRG@irtf.org>; Mon,  6 Mar 2017 09:00:00 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MD9NE-1cUSOX319Y-00GWky for <T2TRG@irtf.org>; Mon, 06 Mar 2017 17:59:57 +0100
To: "t2trg@irtf.org" <T2TRG@irtf.org>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
Date: Mon, 6 Mar 2017 17:59:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="hd7wfHBQvE1vKHXfFpIfPq71MaPaIqq1F"
X-Provags-ID: V03:K0:3/82rgTvHrBjmWJi8UXcH6TW3FZYuPucQNsGl10azL4nNRI0Hh2 e5yAoT5YJwpJUy650L2ZYeDdh3oJz8kvtWZ0+y1hasA9mS7QnVF7RVaLZPz04kkHgXy/D8W r704XerHRMuSudPyjAtlxmdrcrZMe4pKkkJtHLuLPt0l86jEaalW8E5arikf02vgxHkfNKs H72cXIKqZOLS/ce5Lupdw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:3DFoJdNB++U=:gVBkF3t+AhInu/YDLbMDSq qFpEbULNxCEUcRdViVcDdB/c55XCfFR8UaNIC5mJ1XmlcetRUHXgXDvfLML79ucTkQ6W1ZHya GvNVAN5OIJlN9mGJy/03Ft+JMUy9ggnrVjzRcvgPRQNCfye1+HeQmDlx1GJ6Ph2aKF4VU3zkk +AwKFm+I73rQNqauKsArUXb/xk0unk0BYNPV9e0EKGVgNusBDewP88JkncznfirgDSDVZYT0/ CspSa7dsSYLWNbrNQqylI8DWTOPx8jI1emYVKjQ0vF5kfGqjSzRNxBqOvzZS7p1CHe9TdONyl pgwIxku2kTHUlKw/IceP8szKWSKgtr8jHhC8770B49iYi1yO9Twzs1mgXC1JddpDg+40qy9Cv +/TyQPJoXKVYuhknivAEraGEP30XMo87wBUsuAfHBvTqVrspjGItVyVsXkUPIZ7DHu+yri0ej Xu3yJSjhiSuERIQyj2+JeR0JeRCt1J+1aTfhGqMwatGnVxMIkAXHhbzYCueu3mb/N4XXMOp+B OkvfyPX6E91vp230dcnJVB1jlTQ2F1yzujd8vOqZTmAHYQHxl/qy6hWGuNdvR6km1bDeqOGeH AEZQoyP7MsZR7VDEe574UM/PgYN6hESLLxP/oMASrtLyKz5a2SKJk2NSGNCAnhyASydpKILEP aeAgUqkAZF7SSbgRR6FS/8BjxPmHH/az0kSTOfKdzFF/ZQqRz5Y4jIP4sM3p6d/mxUnmsz0fo mVZnDR8B+eUW//9S1phmt9Ugm3Wrz53B98aDcMHTmt9W3f5+WaZTfrBVaZ4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/0M2TncTzTBLguFVf2X93BEmNFsY>
Subject: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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, 06 Mar 2017 17:00:05 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--hd7wfHBQvE1vKHXfFpIfPq71MaPaIqq1F
Content-Type: multipart/mixed; boundary="lOv63GdXdSlJmDcwHCDRUUaeEDqlQLpuL";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: "t2trg@irtf.org" <T2TRG@irtf.org>
Message-ID: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
Subject: RESTful Design & Security

--lOv63GdXdSlJmDcwHCDRUUaeEDqlQLpuL
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi all,

reading through
https://tools.ietf.org/html/draft-keranen-t2trg-rest-iot-03 I was
wondering whether there are some thoughts regarding security protection.

=46rom the web we know that TLS goes very well with RESTful designs.

However, when dealing with intermediaries in the IoT space, such as it
happens with interconnecting different IoT islands, RESTful protocols
appear to run into challenges.

The challenge is quite simple: an application layer security for a
RESTful protocol has to protect some (or must?) header fields.
Intermediaries often change or, in case of a protocol translation from
one IoT technology to another one, completely rebuild header fields.
This breaks application layer security mechanisms.

Needless to say that these challenges have also been observed in other
protocols as well, such as HTTP and even SIP.

What is the story for providing application layer security?

Ciao
Hannes


--lOv63GdXdSlJmDcwHCDRUUaeEDqlQLpuL--

--hd7wfHBQvE1vKHXfFpIfPq71MaPaIqq1F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYvZWMAAoJEGhJURNOOiAtsBIIAKMePuv0cC2CP79250sz8Ooe
lMMf255xi9zEFhvtzM4v2bIrXe9YtPhY0LQhU2Ai5P2sEPox7KS6e/PFK9Rjfbgc
8YZFu5MD4OaMmumWK5BORgW1P9bj8WdGxQVNbORl8DnIYfImiL+wds75Tx8dkceo
0Q58Ueobscm8Q+vyoBG42oZLaQ1M6h/Pm0ZsxHSJn9c0cnqxphrlRfo/iKpeESrx
L/n49RJ2QVX/eJzI/AxmayqieRL0mrIxgPxxITPSM6qchTfckBQ3B5lXAqzUEYpz
M4hWLkgJlA4mS+cnZtvoemW9Oekmc52ewT+AiE4rUXzACQLOPRbmCdwmYxea0E4=
=7q8u
-----END PGP SIGNATURE-----

--hd7wfHBQvE1vKHXfFpIfPq71MaPaIqq1F--


From nobody Mon Mar  6 12:20:09 2017
Return-Path: <ari.keranen@ericsson.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 6587B1294C0 for <t2trg@ietfa.amsl.com>; Mon,  6 Mar 2017 12:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 ED_j1-G3-ZBn for <t2trg@ietfa.amsl.com>; Mon,  6 Mar 2017 12:20:07 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 DC9DE12940E for <T2TRG@irtf.org>; Mon,  6 Mar 2017 12:20:06 -0800 (PST)
X-AuditID: c1b4fb25-8a2a398000007fa8-5e-58bdc474ce11
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by  (Symantec Mail Security) with SMTP id BD.75.32680.474CDB85; Mon,  6 Mar 2017 21:20:04 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0319.002; Mon, 6 Mar 2017 21:20:02 +0100
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpsnqy+AoCImUUiOE0neEUa+86GIMBaA
Date: Mon, 6 Mar 2017 20:20:02 +0000
Message-ID: <09D28E31-4D5E-47D8-B8D1-E849F12D5720@ericsson.com>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
In-Reply-To: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0E25149D4B05FF4E99EE31DC9BDFF976@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7jW7Jkb0RBjfPGlks3XmP1eL9gx4W ByaPxZv2s3lM3niYLYApissmJTUnsyy1SN8ugSvjxrb7TAWHuCuadlxlbmDczNnFyMkhIWAi 8XryeeYuRi4OIYF1jBKXzp9ngXAWMUrMuvuOBaSKTcBeYvKaj4wgtoiAocT1mdNZQWxmAVWJ qYfugdUIC+hJbJmxlxWiRl/i5Kketi5GDiDbSOLhXVuQMIuAisTLjXuYQWxeoJFTdq9gBCkR ErCS2PmBDSTMKWAtcbdzEzuIzSggJvH91BomiE3iEreezGeCuFlAYsme88wQtqjEy8f/WCFs JYlFtz9D1etJ3Jg6hQ3Ctpb4s+UoVFxbYtnC11AnCEqcnPmEZQKj2CwkK2YhaZ+FpH0WkvZZ SNoXMLKuYhQtTi1Oyk03MtZLLcpMLi7Oz9PLSy3ZxAiMqoNbfqvuYLz8xvEQowAHoxIPb0Hl 3ggh1sSy4srcQ4wSHMxKIrwPcoBCvCmJlVWpRfnxRaU5qcWHGKU5WJTEec1W3g8XEkhPLEnN Tk0tSC2CyTJxcEo1MFpOWM31tvWKdoopS+iXhfaXG2KlFrIcNtHbe11H6TvXlLbbBw/3zTvn cmup0Pxj+xZE6mfOXh8qceH++chbJt+uXrwpyfEiY8K7rVGdsc/6dr94qFd8r+rOqtIHfEv5 E77uzPf61Pb2ku0L16/C5k28WXeMnY497VhjuG6J057v9dtXB1xI+p+qxFKckWioxVxUnAgA 4r8m06YCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/OY2PkF58XCD_DxVIy10-C7OBDbc>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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, 06 Mar 2017 20:20:08 -0000

Hi Hannes,

I agree that the draft is currently thin on the security side and some reco=
mmendations would be useful.

What would you recommend for the application security issue you mentioned b=
elow?


Cheers,
Ari

> On 06 Mar 2017, at 18:59, Hannes Tschofenig <hannes.tschofenig@gmx.net> w=
rote:
>=20
> Hi all,
>=20
> reading through
> https://tools.ietf.org/html/draft-keranen-t2trg-rest-iot-03 I was
> wondering whether there are some thoughts regarding security protection.
>=20
> From the web we know that TLS goes very well with RESTful designs.
>=20
> However, when dealing with intermediaries in the IoT space, such as it
> happens with interconnecting different IoT islands, RESTful protocols
> appear to run into challenges.
>=20
> The challenge is quite simple: an application layer security for a
> RESTful protocol has to protect some (or must?) header fields.
> Intermediaries often change or, in case of a protocol translation from
> one IoT technology to another one, completely rebuild header fields.
> This breaks application layer security mechanisms.
>=20
> Needless to say that these challenges have also been observed in other
> protocols as well, such as HTTP and even SIP.
>=20
> What is the story for providing application layer security?
>=20
> Ciao
> Hannes
>=20
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg


From nobody Tue Mar  7 09:39:31 2017
Return-Path: <mcr+ietf@sandelman.ca>
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 88D951295CD for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 09:39:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 0Hn3am_UI1rY for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 09:39:29 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82D5112959B for <T2TRG@irtf.org>; Tue,  7 Mar 2017 09:39:29 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id EC0DA203CA; Tue,  7 Mar 2017 13:02:05 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E75AD636BB; Tue,  7 Mar 2017 12:39:26 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 07 Mar 2017 12:39:26 -0500
Message-ID: <10144.1488908366@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/4vXlNZiWtv4Qx9eecggtcK9dWYU>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Tue, 07 Mar 2017 17:39:30 -0000

--=-=-=
Content-Type: text/plain


Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
    > Needless to say that these challenges have also been observed in other
    > protocols as well, such as HTTP and even SIP.

    > What is the story for providing application layer security?

OSCOAP seems to be end-to-end to me.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAli+8E0ACgkQgItw+93Q
3WXYFwf5AdE5Rioqt5mVBB+f/j6JbrPdIQ+dfdvZQkbYpvs1aiA/agAI8cLKnbEw
hwAbW657sqKeWljhcWUT+7GvGY66GR05UPeMhhjGAyM+C7EChU8KTL4D4Tb2a/8j
H9QTLGrqnOfGXO6s2HUiE0+FPz5hyB65FUDUgBpCQVq3JP8/EKdFcM65XvRGWzZ/
1pMkcUubfunkS3h6sbUm/Ze2i5txn5p6hH7dV9KEOJvUXeW/TwhXsXkp2EQ0Cyq/
Rr5dMfs7CeeCtdQASFSiXt8F3DjjMmXVqabH8uGSoVvB2cHMZoJIY86gKckyBK+s
3er1eO+f0OJLc0sequIj7Vb4E1Mtfw==
=9UnS
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  7 10:39:40 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 7F9861294C1 for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 10:39:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 x4tiIiH3nFW7 for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 10:39:36 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA41112948C for <T2TRG@irtf.org>; Tue,  7 Mar 2017 10:39:35 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LfBX6-1bwWnf1mbA-00olXn; Tue, 07 Mar 2017 19:39:27 +0100
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
Date: Tue, 7 Mar 2017 19:39:24 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <10144.1488908366@obiwan.sandelman.ca>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nrMPRTFHct4IN3tJMCciwVS2ngmc9HB0G"
X-Provags-ID: V03:K0:2W9gxmw452xQDNhpnx/bgq6fo8jS861TgCLcoh6gLvFu3y7lo/f xYjdtqZJQ7tUWKK162eFLe2krYlhNJDs1gqpa0UY9T32QwsVx1RM4XWnAh7vV8l70N+Fl/P JVrJv03kw0xOCMaY52n/NsgxXFv5347dGRGW7iPDFR3Sen86sm7ViHvooJtyLpW+67e0UzP /jINbI07jzmGWTy0V0M3Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:MtyFXUheBbI=:1wbMILmdK9Zcyqylm+KmbK UAKsZ9VGku/qiM1BkinipU1uD20Ku9IwMC3br5xw4vjXBIEnn8dChXJarmgaDTS8+6TV6ZYe+ pZUhuiOH16pWpVa5QXieqdpPRlPNvb9gQNCufGSP8leFcELi96vAoGIF7/2h42Imp2U7618f5 4Jhxaqmlj3FZthoxZQhKcS219Y5dwCkjRvB8gQBkcIO3pOM16kgR6XSrM+xiajEIk/mFXRLi7 2ctg9ukofJzgVZ8An9PiECg6s5ovuS3gw8zH9ZO1ms7npg4XqoO1siRjcHQzaufmiVmKHuVp5 Svmv++3afkCqd9NQfMi3ZI7F8fGmQ3ByPlghIvWyvL0iwCUsECP/jkRH9ZqaTFve7O51zsB46 81L3GEQavl5ND9SrhOEqcy4uA3EoJO4IBdwlL9tm90kdoBekfp4cSLjZh43H3znZeEQGx7KoJ a6gJlieq5u9/Y08TV6vOCXkzH+ArwuMMiPUWkE+FGCeeMb6SIDxChXnevsMPEq5YNSryUs22J R0Q4pAEWu3dSl3XclRxzzIVUBXEluJaHJcMET7YNwqx3wcYLpURu1lFe/tOhKaEeww9MUacpf UwGFo5BQ9FlyzvvVay52SMIYjS4NW3EEosc6EBEZRr8JuHCseEyzns+pUU2aEP1/vQz4ZKCTP uweYN2jjUx+KVZdkZ1xFT9NWUf/5LBQ3S0YcOOIMLZ6qhGrfRmPKEcVaQXRrgv73swUxv4Vji v4Bpl7Y+mkS0k4OSZ2D1m/0/f0GABvvEEpkZx4JLvsVnE+YuMEsD1ZujUbQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/j3oev195rmMqZY7rQv8M03uIqHU>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Tue, 07 Mar 2017 18:39:38 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--nrMPRTFHct4IN3tJMCciwVS2ngmc9HB0G
Content-Type: multipart/mixed; boundary="XwPAs2u33ODeMq6agpAb3DI3XPPBnoJkE";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Message-ID: <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
In-Reply-To: <10144.1488908366@obiwan.sandelman.ca>

--XwPAs2u33ODeMq6agpAb3DI3XPPBnoJkE
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

OSCOAP does not work when

* you mix protocols,
* use a middlebox for some processing interactions (such as data
aggregation), and
* when one of the protocols is a non-RESTful protocol, such as BLE or MQT=
T.

Unfortunately, these the use cases we are facing in current IoT
deployments. For similar reasons we cannot use RFC 8075 either.

Maybe you are seeing different deployment environments.

Ciao
Hannes

On 03/07/2017 06:39 PM, Michael Richardson wrote:
>=20
> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>     > Needless to say that these challenges have also been observed in =
other
>     > protocols as well, such as HTTP and even SIP.
>=20
>     > What is the story for providing application layer security?
>=20
> OSCOAP seems to be end-to-end to me.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20


--XwPAs2u33ODeMq6agpAb3DI3XPPBnoJkE--

--nrMPRTFHct4IN3tJMCciwVS2ngmc9HB0G
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYvv5dAAoJEGhJURNOOiAtdsAH/1SuHeUd4u9+BynSvvxbTKFq
FPO/nrXc1JmGCRrtt/OcH53QB9dOil6zUSebZDct/gFemmfiMHrUw+VBWnyVHgLI
qC4z3dcGk6C4DBAklCqfFcwfZCHcxS+yHbNBlQVdJoPYlui+49AlvTRfLDCC79ES
GziaYlJpM1lP0S7gQ+GmUtyBp6vVzZCNFHH4QoW3Lv3Vz12d7PG6F9+vg5JuTA/Y
00PtRekGw62OgTz1gjnc2jNAXfHiJW7riuVMzUZoUa/IsZNrqqOrG9yY2iJlnxUq
+njyZI6vdFYHNewyyhxZjO4xuFTYWmIBiIW7F7XgXJVbh48Cfe74srW2u9s10wo=
=eaAO
-----END PGP SIGNATURE-----

--nrMPRTFHct4IN3tJMCciwVS2ngmc9HB0G--


From nobody Tue Mar  7 10:45:14 2017
Return-Path: <matthias.kovatsch@siemens.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 F0E15129467 for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 10:45:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.918
X-Spam-Level: 
X-Spam-Status: No, score=-6.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=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 pV1CAbqTiYtF for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 10:45:11 -0800 (PST)
Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) (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 58F751294A8 for <T2TRG@irtf.org>; Tue,  7 Mar 2017 10:45:11 -0800 (PST)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id v27Ij8DP025057 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 7 Mar 2017 19:45:08 +0100
Received: from DEFTHW99ERKMSX.ww902.siemens.net (defthw99erkmsx.ww902.siemens.net [139.22.70.147]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id v27Ij7K8020064 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Mar 2017 19:45:07 +0100
Received: from DENBGAT9ER8MSX.ww902.siemens.net (139.22.70.86) by DEFTHW99ERKMSX.ww902.siemens.net (139.22.70.147) with Microsoft SMTP Server (TLS) id 14.3.339.0; Tue, 7 Mar 2017 19:45:07 +0100
Received: from DEFTHW99EL4MSX.ww902.siemens.net ([169.254.5.206]) by DENBGAT9ER8MSX.ww902.siemens.net ([139.22.70.86]) with mapi id 14.03.0339.000; Tue, 7 Mar 2017 19:45:06 +0100
From: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>
To: "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpshLU+67EadNU+/wTUKb0HGTaGJlY0AgAAQwgCAABJb3g==
Date: Tue, 7 Mar 2017 18:45:05 +0000
Message-ID: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca>, <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
In-Reply-To: <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98DEFTHW99EL4MSXw_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/dlZoKZjz9ki4X2Yd7PyDBVUoOpE>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Tue, 07 Mar 2017 18:45:13 -0000

--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98DEFTHW99EL4MSXw_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On big propaganda tour? :P

Regards
Matthias


Sent from my phone, limitations might apply.

-----Original Message-----
From: Hannes Tschofenig [hannes.tschofenig@gmx.net]
Received: Tuesday, 07 Mar 2017, 19:39
To: Michael Richardson [mcr+ietf@sandelman.ca]
CC: t2trg@irtf.org [T2TRG@irtf.org]
Subject: Re: [T2TRG] RESTful Design & Security

OSCOAP does not work when

* you mix protocols,
* use a middlebox for some processing interactions (such as data
aggregation), and
* when one of the protocols is a non-RESTful protocol, such as BLE or MQTT.

Unfortunately, these the use cases we are facing in current IoT
deployments. For similar reasons we cannot use RFC 8075 either.

Maybe you are seeing different deployment environments.

Ciao
Hannes

On 03/07/2017 06:39 PM, Michael Richardson wrote:
>
> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>     > Needless to say that these challenges have also been observed in ot=
her
>     > protocols as well, such as HTTP and even SIP.
>
>     > What is the story for providing application layer security?
>
> OSCOAP seems to be end-to-end to me.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -=3D IPv6 IoT consulting =3D-
>
>
>


--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98DEFTHW99EL4MSXw_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11p=
t; color:black">
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11=
pt; color:black">On big propaganda tour? :P<br>
<br>
Regards<br>
Matthias <br>
<br>
<br>
Sent from my phone, limitations might apply.<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Hannes Tschofenig [hannes.tschofenig@gmx.net]<br>
<b>Received:</b> Tuesday, 07 Mar 2017, 19:39<br>
<b>To:</b> Michael Richardson [mcr&#43;ietf@sandelman.ca]<br>
<b>CC:</b> t2trg@irtf.org [T2TRG@irtf.org]<br>
<b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security<br>
<br>
</span></span></div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">OSCOAP does not work when<br>
<br>
* you mix protocols,<br>
* use a middlebox for some processing interactions (such as data<br>
aggregation), and<br>
* when one of the protocols is a non-RESTful protocol, such as BLE or MQTT.=
<br>
<br>
Unfortunately, these the use cases we are facing in current IoT<br>
deployments. For similar reasons we cannot use RFC 8075 either.<br>
<br>
Maybe you are seeing different deployment environments.<br>
<br>
Ciao<br>
Hannes<br>
<br>
On 03/07/2017 06:39 PM, Michael Richardson wrote:<br>
&gt; <br>
&gt; Hannes Tschofenig &lt;hannes.tschofenig@gmx.net&gt; wrote:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Needless to say that these challenges hav=
e also been observed in other<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; protocols as well, such as HTTP and even =
SIP.<br>
&gt; <br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; What is the story for providing applicati=
on layer security?<br>
&gt; <br>
&gt; OSCOAP seems to be end-to-end to me.<br>
&gt; <br>
&gt; --<br>
&gt; Michael Richardson &lt;mcr&#43;IETF@sandelman.ca&gt;, Sandelman Softwa=
re Works<br>
&gt;&nbsp; -=3D IPv6 IoT consulting =3D-<br>
&gt; <br>
&gt; <br>
&gt; <br>
<br>
</div>
</span></font>
</body>
</html>

--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98DEFTHW99EL4MSXw_--


From nobody Tue Mar  7 11:10:55 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 9713E1294A3 for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 11:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 t5GshhWdQRma for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 11:10:46 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF73012949F for <T2TRG@irtf.org>; Tue,  7 Mar 2017 11:10:45 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Ldq9D-1c2gDG2uWJ-00izTt; Tue, 07 Mar 2017 20:10:37 +0100
To: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
Date: Tue, 7 Mar 2017 20:10:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HcQKe5NSPefaEL118SR6hSrQGnxMWLPj0"
X-Provags-ID: V03:K0:mtTGy1MnFfbSlgWATxzXXoNndXiYB8NUDW4UeXBGCLd3/7u1gAU KcsWTD6NArTIdjl8hrPmdfsEP/oaEuIdGQrb68gIQCfJ1xCz4bGgxtQhuqGfikeM67xPjVw J2XqctPIhCZhtqj5VSZZas79qWSScNxBdPPxXV93BqFn5d3OoKA55vgOkeO0k8ZETw4TNhX NQXIBEqmPizHfP4t5e9Iw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:EH+YFw2RbgQ=:mDo+V6bQWm77VZDphfh/LN 7qHz7/n4ICLvFhP0t2PYYeHnA3VcWajJdRdDLZyj9obaTTlji73mqDetupilvRzOeKGhkXn3M NYDlKyOCx5O9kzHQEsGLLdumNEtZZzzYzSRLQlH++pzO5tLBmkQj5ark7dz/HNz3WNiC9kd7b IwyaJhqhKjdn7fzM+9rLa3HSnpycvc8SHfB8g4AzlO1raXVZq2mHGmd4dlWElBkKdSDBUQPbM 3dvds7Fcu7lz2CR0HG6+sKDafTo7A8i2m/EqdBrgyQTvD3t/aIF1o5tZbkj9/T2dngZwOlbLf ZvdIUBEcE1sN+B5p7R6e+9pJymbV17B0GFJCQP02cnWGYCVgOAR0A2lABfHnIG0HspITOh+EX msina14c5okNM/ICLEUfFJhlg8eVWSvfzgzh8pwO70M9n8FERhjbSEnjOIFBoHbYSNYDAdt2A WT86KD9y5kk9kvH2GDaehNwSF8d+8/3PBeK1j6SWBc2TcRMKpEQ997ro+/TfC6d4A/bMQb+4W 3oGbRVmPHNVMJWbvacvh8Xb1HVhInFJjMf1zY71wpLLJwu1DGYWDEsvmH38OojLQ6e+gY9bVA eU1chXuoBGDKGkSvuthmRkQRiyWX8KWGZiljdEKmJDqU6GB+Fzf5FVbSr1nzM34tMwjnoyaFr iC8oJW8jKGM1qYc/xusu5eE1EbuZBh3/v26DaForfEs2MoSJzqoPZ17RnpXrnnyAi+Y6Ww+QY yxezTAQBxWMtix1+bG18IWdhKSeXrCMtEwu4va8iVKnIO5bFD+fWBzQAO3Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/D4W63735rlfrtDmNUm-Nw4-bIaY>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Tue, 07 Mar 2017 19:10:47 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--HcQKe5NSPefaEL118SR6hSrQGnxMWLPj0
Content-Type: multipart/mixed; boundary="1VLXPgntgEXlUWwAwiHmImKesGhgQ8L6B";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>,
 "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Message-ID: <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
In-Reply-To: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>

--1VLXPgntgEXlUWwAwiHmImKesGhgQ8L6B
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Matthias,

I know that this is a research group and everyone can create whatever
they want.

We briefly talked about security at the IoT directorate conference call
and I would be interesting to hear what works and what does not work for
others.

Ciao
Hannes


On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
> On big propaganda tour? :P
>=20
> Regards
> Matthias
>=20
>=20
> Sent from my phone, limitations might apply.
>=20
> -----Original Message-----
> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
> *Received:* Tuesday, 07 Mar 2017, 19:39
> *To:* Michael Richardson [mcr+ietf@sandelman.ca]
> *CC:* t2trg@irtf.org [T2TRG@irtf.org]
> *Subject:* Re: [T2TRG] RESTful Design & Security
>=20
> OSCOAP does not work when
>=20
> * you mix protocols,
> * use a middlebox for some processing interactions (such as data
> aggregation), and
> * when one of the protocols is a non-RESTful protocol, such as BLE or M=
QTT.
>=20
> Unfortunately, these the use cases we are facing in current IoT
> deployments. For similar reasons we cannot use RFC 8075 either.
>=20
> Maybe you are seeing different deployment environments.
>=20
> Ciao
> Hannes
>=20
> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>=20
>> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>     > Needless to say that these challenges have also been observed in=
 other
>>     > protocols as well, such as HTTP and even SIP.
>>=20
>>     > What is the story for providing application layer security?
>>=20
>> OSCOAP seems to be end-to-end to me.
>>=20
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>  -=3D IPv6 IoT consulting =3D-
>>=20
>>=20
>>=20
>=20
>=20
>=20
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg
>=20


--1VLXPgntgEXlUWwAwiHmImKesGhgQ8L6B--

--HcQKe5NSPefaEL118SR6hSrQGnxMWLPj0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYvwWsAAoJEGhJURNOOiAtGv8H/1nVpGLHdy4DvJb7MKDuYN/3
qlrca+eHhSpp7aYKf8nAnuG9uNeg3GniP3u4wP2lzZqdRx1H4t+UH68xshHki7xx
GWm9rSAOJhKeqqPELe2bEzk9T9SwJS5hpFts3R17/zwMa6Xy+BBiGvN/sHXC7wiG
VsmmvfpttNPyw3d+kh9uZZ/4zS9rSbfNdg2pSbgXBM3Mp57L0Nh5kyDyucYsQ8e6
KODjB0pLEBpg8yCLro9SGvxmWiQtIVYk2mowXY3CRnxxCu23wNqBhgs5/iOqGu9v
OlnotW7neowTVdAGI2rbxd2DHGiBxHRwrCz136Bz0LlwsNpH400Jwi9TNkEUVmo=
=itx0
-----END PGP SIGNATURE-----

--HcQKe5NSPefaEL118SR6hSrQGnxMWLPj0--


From nobody Tue Mar  7 11:36:43 2017
Return-Path: <matthias.kovatsch@siemens.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 6B07F1294CC for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 11:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.918
X-Spam-Level: 
X-Spam-Status: No, score=-6.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=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 daey23jJdX1V for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 11:36:41 -0800 (PST)
Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) (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 E25F512940F for <T2TRG@irtf.org>; Tue,  7 Mar 2017 11:36:40 -0800 (PST)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id v27Jab1S009607 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 7 Mar 2017 20:36:38 +0100
Received: from DEFTHW99ERNMSX.ww902.siemens.net (defthw99ernmsx.ww902.siemens.net [139.22.70.141]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id v27JabPw026337 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Mar 2017 20:36:37 +0100
Received: from DENBGAT9ERCMSX.ww902.siemens.net (139.22.70.82) by DEFTHW99ERNMSX.ww902.siemens.net (139.22.70.141) with Microsoft SMTP Server (TLS) id 14.3.339.0; Tue, 7 Mar 2017 20:36:37 +0100
Received: from DEFTHW99EL4MSX.ww902.siemens.net ([169.254.5.206]) by DENBGAT9ERCMSX.ww902.siemens.net ([139.22.70.82]) with mapi id 14.03.0339.000; Tue, 7 Mar 2017 20:36:36 +0100
From: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>
To: "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpshLU+67EadNU+/wTUKb0HGTaGJlY0AgAAQwgCAABJb3v//9luAgAAYCfw=
Date: Tue, 7 Mar 2017 19:36:35 +0000
Message-ID: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>, <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
In-Reply-To: <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA313FDEFTHW99EL4MSXw_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/9Dzb5pStMTzDzuPFIo3rq5eTx6s>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Tue, 07 Mar 2017 19:36:42 -0000

--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA313FDEFTHW99EL4MSXw_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Fair enough.

Yes, I am on this IoT Directorate. I would say a large fraction of the T2TR=
G participants has been arguing that the Internet of Gateways is not a good=
 approach. Your security-related summary proves this point.

I personally don't see end-to-end security happening if we keep mixing appl=
ication protocols, keep using black-magic middleboxes, and keep using propr=
ietary interfaces at the device level. We need something end-to-end (or T2T=
) for end-to-end security.

Best wishes
Matthias



Sent from my phone, limitations might apply.

-----Original Message-----
From: Hannes Tschofenig [hannes.tschofenig@gmx.net]
Received: Tuesday, 07 Mar 2017, 20:10
To: Kovatsch, Matthias (CT RDA NEC EMB-DE) [matthias.kovatsch@siemens.com];=
 mcr+ietf@sandelman.ca [mcr+ietf@sandelman.ca]
CC: T2TRG@irtf.org [T2TRG@irtf.org]
Subject: Re: [T2TRG] RESTful Design & Security

Hi Matthias,

I know that this is a research group and everyone can create whatever
they want.

We briefly talked about security at the IoT directorate conference call
and I would be interesting to hear what works and what does not work for
others.

Ciao
Hannes


On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
> On big propaganda tour? :P
>
> Regards
> Matthias
>
>
> Sent from my phone, limitations might apply.
>
> -----Original Message-----
> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
> *Received:* Tuesday, 07 Mar 2017, 19:39
> *To:* Michael Richardson [mcr+ietf@sandelman.ca]
> *CC:* t2trg@irtf.org [T2TRG@irtf.org]
> *Subject:* Re: [T2TRG] RESTful Design & Security
>
> OSCOAP does not work when
>
> * you mix protocols,
> * use a middlebox for some processing interactions (such as data
> aggregation), and
> * when one of the protocols is a non-RESTful protocol, such as BLE or MQT=
T.
>
> Unfortunately, these the use cases we are facing in current IoT
> deployments. For similar reasons we cannot use RFC 8075 either.
>
> Maybe you are seeing different deployment environments.
>
> Ciao
> Hannes
>
> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>
>> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>     > Needless to say that these challenges have also been observed in o=
ther
>>     > protocols as well, such as HTTP and even SIP.
>>
>>     > What is the story for providing application layer security?
>>
>> OSCOAP seems to be end-to-end to me.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>  -=3D IPv6 IoT consulting =3D-
>>
>>
>>
>
>
>
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg
>


--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA313FDEFTHW99EL4MSXw_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11p=
t; color:black">
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11=
pt; color:black">Fair enough.<br>
<br>
Yes, I am on this IoT Directorate. I would say a large fraction of the T2TR=
G participants has been arguing that the Internet of Gateways is not a good=
 approach. Your security-related summary proves this point.<br>
<br>
I personally don't see end-to-end security happening if we keep mixing appl=
ication protocols, keep using black-magic middleboxes, and keep using propr=
ietary interfaces at the device level. We need something end-to-end (or T2T=
) for end-to-end security.<br>
<br>
Best wishes<br>
Matthias <br>
<br>
<br>
<br>
Sent from my phone, limitations might apply.<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Hannes Tschofenig [hannes.tschofenig@gmx.net]<br>
<b>Received:</b> Tuesday, 07 Mar 2017, 20:10<br>
<b>To:</b> Kovatsch, Matthias (CT RDA NEC EMB-DE) [matthias.kovatsch@siemen=
s.com]; mcr&#43;ietf@sandelman.ca [mcr&#43;ietf@sandelman.ca]<br>
<b>CC:</b> T2TRG@irtf.org [T2TRG@irtf.org]<br>
<b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security<br>
<br>
</span></span></div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Hi Matthias,<br>
<br>
I know that this is a research group and everyone can create whatever<br>
they want.<br>
<br>
We briefly talked about security at the IoT directorate conference call<br>
and I would be interesting to hear what works and what does not work for<br=
>
others.<br>
<br>
Ciao<br>
Hannes<br>
<br>
<br>
On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:<br>
&gt; On big propaganda tour? :P<br>
&gt; <br>
&gt; Regards<br>
&gt; Matthias<br>
&gt; <br>
&gt; <br>
&gt; Sent from my phone, limitations might apply.<br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]<br>
&gt; *Received:* Tuesday, 07 Mar 2017, 19:39<br>
&gt; *To:* Michael Richardson [mcr&#43;ietf@sandelman.ca]<br>
&gt; *CC:* t2trg@irtf.org [T2TRG@irtf.org]<br>
&gt; *Subject:* Re: [T2TRG] RESTful Design &amp; Security<br>
&gt; <br>
&gt; OSCOAP does not work when<br>
&gt; <br>
&gt; * you mix protocols,<br>
&gt; * use a middlebox for some processing interactions (such as data<br>
&gt; aggregation), and<br>
&gt; * when one of the protocols is a non-RESTful protocol, such as BLE or =
MQTT.<br>
&gt; <br>
&gt; Unfortunately, these the use cases we are facing in current IoT<br>
&gt; deployments. For similar reasons we cannot use RFC 8075 either.<br>
&gt; <br>
&gt; Maybe you are seeing different deployment environments.<br>
&gt; <br>
&gt; Ciao<br>
&gt; Hannes<br>
&gt; <br>
&gt; On 03/07/2017 06:39 PM, Michael Richardson wrote:<br>
&gt;&gt; <br>
&gt;&gt; Hannes Tschofenig &lt;hannes.tschofenig@gmx.net&gt; wrote:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Needless to say that these challenges=
 have also been observed in other<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; protocols as well, such as HTTP and e=
ven SIP.<br>
&gt;&gt; <br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; What is the story for providing appli=
cation layer security?<br>
&gt;&gt; <br>
&gt;&gt; OSCOAP seems to be end-to-end to me.<br>
&gt;&gt; <br>
&gt;&gt; --<br>
&gt;&gt; Michael Richardson &lt;mcr&#43;IETF@sandelman.ca&gt;, Sandelman So=
ftware Works<br>
&gt;&gt;&nbsp; -=3D IPv6 IoT consulting =3D-<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; T2TRG mailing list<br>
&gt; T2TRG@irtf.org<br>
&gt; <a href=3D"https://www.irtf.org/mailman/listinfo/t2trg">https://www.ir=
tf.org/mailman/listinfo/t2trg</a><br>
&gt; <br>
<br>
</div>
</span></font>
</body>
</html>

--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA313FDEFTHW99EL4MSXw_--


From nobody Tue Mar  7 11:47:21 2017
Return-Path: <robby.simpson@ge.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 E240A12943D for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 11:47:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.47
X-Spam-Level: 
X-Spam-Status: No, score=0.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, KHOP_DYNAMIC=1.08, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Wd7ST06CT66G for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 11:47:19 -0800 (PST)
Received: from mx0a-00176a03.pphosted.com (mx0b-00176a03.pphosted.com [67.231.157.48]) (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 94E00129426 for <T2TRG@irtf.org>; Tue,  7 Mar 2017 11:47:19 -0800 (PST)
Received: from pps.filterd (m0048206.ppops.net [127.0.0.1]) by m0048206.ppops.net-00176a03. (8.16.0.20/8.16.0.20) with SMTP id v27JhNWA037651 for <T2TRG@irtf.org>; Tue, 7 Mar 2017 14:47:16 -0500
From: "Simpson, Robby (GE Energy Connections)" <robby.simpson@ge.com>
To: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSl3orfKb6ZYt5XUa+CpMeNeBpv6GJdGmA
Date: Tue, 7 Mar 2017 19:47:04 +0000
Message-ID: <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
In-Reply-To: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
authentication-results: siemens.com; dkim=none (message not signed) header.d=none;siemens.com; dmarc=none action=none header.from=ge.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [205.173.88.26]
x-ms-office365-filtering-correlation-id: 2e57d109-8ff0-48d6-8dbe-08d46592bb4a
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DM3P101MB0089;
x-microsoft-exchange-diagnostics: 1; DM3P101MB0089; 7:uSWM5lCsCpllDiJkTH47XnAANZAER7LZgsnC9h1rweg/Bwx6HI+7eXb8uwWdlrMKIdKJJI4vb91gC5M9o6HE9E+YEDwYVXR08ns3P1GGIN526DIYHOmknhoAZazBZPl7qAYiNhb180PDAHbBlAGubP5kD4ic940Th80I/8dIS97ob8XhPFLaowjYeY3pypy4Mgw2U/YJBBRqYba7Dy1/X1GiRgTmGVRv8aLEoXRXsjOilMUG5GU2+K386K/5V6yA3CNsdaVaQSjPVG+nwLVSMJt7ZxwzlVFWF37TkOh5yUVK0I5oCHphxG1IgxWhLfW04EL8JDZI2yGqURnppGu8mQ==
x-microsoft-antispam-prvs: <DM3P101MB008985B2EB38EEC21A659ABE882F0@DM3P101MB0089.NAMP101.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:(10436049006162)(192374486261705)(248736688235697)(106981052589767)(126837547833334)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123564025)(20161123558025)(20161123560025)(20161123555025)(20161123562025)(6072148); SRVR:DM3P101MB0089; BCL:0; PCL:0; RULEID:; SRVR:DM3P101MB0089; 
x-forefront-prvs: 0239D46DB6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39450400003)(39830400002)(39410400002)(377454003)(24454002)(13464003)(6512007)(66066001)(7736002)(236005)(54896002)(53936002)(2950100002)(6306002)(38730400002)(6246003)(3846002)(5660300001)(6116002)(102836003)(33656002)(2906002)(15650500001)(229853002)(122556002)(8676002)(83716003)(8936002)(3280700002)(6506006)(606005)(82746002)(6436002)(6486002)(83506001)(50986999)(54356999)(2501003)(76176999)(36756003)(93886004)(4001350100001)(2900100001)(3660700001)(86362001)(53546006)(106116001)(4326008)(189998001)(7110500001)(2420400007)(7906003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM3P101MB0089; H:DM3P101MB0089.NAMP101.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_0216378E89764D4EA307AEE5FD00BDA6GEcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Mar 2017 19:47:04.5438 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 15ccb6d1-d335-4996-b6f9-7b6925f08121
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM3P101MB0089
X-OriginatorOrg: ge.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-07_15:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703070155
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/MWpURkWckSSs_WF7C1pDauv3wYU>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Tue, 07 Mar 2017 19:47:21 -0000

--_000_0216378E89764D4EA307AEE5FD00BDA6GEcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

UGVyc29uYWxseSwgSeKAmW0gYSBiaWcgZmFuIG9mIGVuZC10by1lbmQgYW5kIHRoaW5rIHRoYXQg
aXMgdGhlIGNvcnJlY3QgYXBwcm9hY2guDQoNCkhvd2V2ZXIsIHByYWdtYXRpY2FsbHksIEkgcmVh
bGl6ZSB0aGlzIGlzIG5vdCBhbHdheXMgcG9zc2libGUuDQoNCkkgaGF2ZW7igJl0IGZvbGxvd2Vk
IGl0IGZvciBhIHdoaWxlLCBidXQgdGhlcmUgd2FzIHNvbWUgYWN0aXZpdHkgaW4gaHR0cGJpcyBh
dCBvbmUgcG9pbnQgZm9yIHJlc291cmNlL29iamVjdC1sZXZlbCBzZWN1cml0eSAoaHR0cHM6Ly90
b29scy5pZXRmLm9yZy93Zy9odHRwYmlzL2RyYWZ0LWlldGYtaHR0cGJpcy1lbmNyeXB0aW9uLWVu
Y29kaW5nLykuICBJZiB3ZSBsaW1pdCB0aGUgZGlzY3Vzc2lvbiB0byBwcm90b2NvbHMgdGhhdCBz
dXBwb3J0IGNvbnRlbnQgY29kaW5ncyAoZS5nLiwgSFRUUCBhbmQgQ29BUCksIHRoZW4gSSB3b3Vs
ZCB0aGluayBkZWZpbmluZyBhIGNvZGluZyB0aGF0IHNwZWNpZmllcyB0aGUgcmVzb3VyY2UtbGV2
ZWwgc2VjdXJpdHkgYXNwZWN0cyB3b3VsZCBhY2hpZXZlIHF1aXRlIGEgbG90IGFuZCB3b3VsZCBi
ZSBhYmxlIHRvIHByZXNlcnZlIGFzcGVjdHMgdGhyb3VnaCBwcm90b2NvbCBjb252ZXJzaW9uLg0K
DQotIFJvYmJ5DQoNCg0KUm9iYnkgU2ltcHNvbiwgUGhEDQpTeXN0ZW0gQXJjaGl0ZWN0DQpHRQ0K
R3JpZCBTb2x1dGlvbnMNCk06ICsxIDQwNCAyMTkgMTg1MQ0KUm9iYnkuU2ltcHNvbkBHRS5jb20N
Cg0KDQpGcm9tOiBUMlRSRyA8dDJ0cmctYm91bmNlc0BpcnRmLm9yZz4gb24gYmVoYWxmIG9mICJL
b3ZhdHNjaCwgTWF0dGhpYXMiIDxtYXR0aGlhcy5rb3ZhdHNjaEBzaWVtZW5zLmNvbT4NCkRhdGU6
IFR1ZXNkYXksIE1hcmNoIDcsIDIwMTcgYXQgMjozNiBQTQ0KVG86ICJoYW5uZXMudHNjaG9mZW5p
Z0BnbXgubmV0IiA8aGFubmVzLnRzY2hvZmVuaWdAZ214Lm5ldD4sICJtY3IraWV0ZkBzYW5kZWxt
YW4uY2EiIDxtY3IraWV0ZkBzYW5kZWxtYW4uY2E+DQpDYzogIlQyVFJHQGlydGYub3JnIiA8VDJU
UkdAaXJ0Zi5vcmc+DQpTdWJqZWN0OiBFWFQ6IFJlOiBbVDJUUkddIFJFU1RmdWwgRGVzaWduICYg
U2VjdXJpdHkNCg0KRmFpciBlbm91Z2guDQoNClllcywgSSBhbSBvbiB0aGlzIElvVCBEaXJlY3Rv
cmF0ZS4gSSB3b3VsZCBzYXkgYSBsYXJnZSBmcmFjdGlvbiBvZiB0aGUgVDJUUkcgcGFydGljaXBh
bnRzIGhhcyBiZWVuIGFyZ3VpbmcgdGhhdCB0aGUgSW50ZXJuZXQgb2YgR2F0ZXdheXMgaXMgbm90
IGEgZ29vZCBhcHByb2FjaC4gWW91ciBzZWN1cml0eS1yZWxhdGVkIHN1bW1hcnkgcHJvdmVzIHRo
aXMgcG9pbnQuDQoNCkkgcGVyc29uYWxseSBkb24ndCBzZWUgZW5kLXRvLWVuZCBzZWN1cml0eSBo
YXBwZW5pbmcgaWYgd2Uga2VlcCBtaXhpbmcgYXBwbGljYXRpb24gcHJvdG9jb2xzLCBrZWVwIHVz
aW5nIGJsYWNrLW1hZ2ljIG1pZGRsZWJveGVzLCBhbmQga2VlcCB1c2luZyBwcm9wcmlldGFyeSBp
bnRlcmZhY2VzIGF0IHRoZSBkZXZpY2UgbGV2ZWwuIFdlIG5lZWQgc29tZXRoaW5nIGVuZC10by1l
bmQgKG9yIFQyVCkgZm9yIGVuZC10by1lbmQgc2VjdXJpdHkuDQoNCkJlc3Qgd2lzaGVzDQpNYXR0
aGlhcw0KDQoNCg0KU2VudCBmcm9tIG15IHBob25lLCBsaW1pdGF0aW9ucyBtaWdodCBhcHBseS4N
Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEhhbm5lcyBUc2Nob2ZlbmlnIFto
YW5uZXMudHNjaG9mZW5pZ0BnbXgubmV0XQ0KUmVjZWl2ZWQ6IFR1ZXNkYXksIDA3IE1hciAyMDE3
LCAyMDoxMA0KVG86IEtvdmF0c2NoLCBNYXR0aGlhcyAoQ1QgUkRBIE5FQyBFTUItREUpIFttYXR0
aGlhcy5rb3ZhdHNjaEBzaWVtZW5zLmNvbV07IG1jcitpZXRmQHNhbmRlbG1hbi5jYSBbbWNyK2ll
dGZAc2FuZGVsbWFuLmNhXQ0KQ0M6IFQyVFJHQGlydGYub3JnIFtUMlRSR0BpcnRmLm9yZ10NClN1
YmplY3Q6IFJlOiBbVDJUUkddIFJFU1RmdWwgRGVzaWduICYgU2VjdXJpdHkNCkhpIE1hdHRoaWFz
LA0KDQpJIGtub3cgdGhhdCB0aGlzIGlzIGEgcmVzZWFyY2ggZ3JvdXAgYW5kIGV2ZXJ5b25lIGNh
biBjcmVhdGUgd2hhdGV2ZXINCnRoZXkgd2FudC4NCg0KV2UgYnJpZWZseSB0YWxrZWQgYWJvdXQg
c2VjdXJpdHkgYXQgdGhlIElvVCBkaXJlY3RvcmF0ZSBjb25mZXJlbmNlIGNhbGwNCmFuZCBJIHdv
dWxkIGJlIGludGVyZXN0aW5nIHRvIGhlYXIgd2hhdCB3b3JrcyBhbmQgd2hhdCBkb2VzIG5vdCB3
b3JrIGZvcg0Kb3RoZXJzLg0KDQpDaWFvDQpIYW5uZXMNCg0KDQpPbiAwMy8wNy8yMDE3IDA3OjQ1
IFBNLCBLb3ZhdHNjaCwgTWF0dGhpYXMgd3JvdGU6DQo+IE9uIGJpZyBwcm9wYWdhbmRhIHRvdXI/
IDpQDQo+DQo+IFJlZ2FyZHMNCj4gTWF0dGhpYXMNCj4NCj4NCj4gU2VudCBmcm9tIG15IHBob25l
LCBsaW1pdGF0aW9ucyBtaWdodCBhcHBseS4NCj4NCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4gKkZyb206KiBIYW5uZXMgVHNjaG9mZW5pZyBbaGFubmVzLnRzY2hvZmVuaWdAZ214Lm5l
dF0NCj4gKlJlY2VpdmVkOiogVHVlc2RheSwgMDcgTWFyIDIwMTcsIDE5OjM5DQo+ICpUbzoqIE1p
Y2hhZWwgUmljaGFyZHNvbiBbbWNyK2lldGZAc2FuZGVsbWFuLmNhXQ0KPiAqQ0M6KiB0MnRyZ0Bp
cnRmLm9yZyBbVDJUUkdAaXJ0Zi5vcmddDQo+ICpTdWJqZWN0OiogUmU6IFtUMlRSR10gUkVTVGZ1
bCBEZXNpZ24gJiBTZWN1cml0eQ0KPg0KPiBPU0NPQVAgZG9lcyBub3Qgd29yayB3aGVuDQo+DQo+
ICogeW91IG1peCBwcm90b2NvbHMsDQo+ICogdXNlIGEgbWlkZGxlYm94IGZvciBzb21lIHByb2Nl
c3NpbmcgaW50ZXJhY3Rpb25zIChzdWNoIGFzIGRhdGENCj4gYWdncmVnYXRpb24pLCBhbmQNCj4g
KiB3aGVuIG9uZSBvZiB0aGUgcHJvdG9jb2xzIGlzIGEgbm9uLVJFU1RmdWwgcHJvdG9jb2wsIHN1
Y2ggYXMgQkxFIG9yIE1RVFQuDQo+DQo+IFVuZm9ydHVuYXRlbHksIHRoZXNlIHRoZSB1c2UgY2Fz
ZXMgd2UgYXJlIGZhY2luZyBpbiBjdXJyZW50IElvVA0KPiBkZXBsb3ltZW50cy4gRm9yIHNpbWls
YXIgcmVhc29ucyB3ZSBjYW5ub3QgdXNlIFJGQyA4MDc1IGVpdGhlci4NCj4NCj4gTWF5YmUgeW91
IGFyZSBzZWVpbmcgZGlmZmVyZW50IGRlcGxveW1lbnQgZW52aXJvbm1lbnRzLg0KPg0KPiBDaWFv
DQo+IEhhbm5lcw0KPg0KPiBPbiAwMy8wNy8yMDE3IDA2OjM5IFBNLCBNaWNoYWVsIFJpY2hhcmRz
b24gd3JvdGU6DQo+Pg0KPj4gSGFubmVzIFRzY2hvZmVuaWcgPGhhbm5lcy50c2Nob2ZlbmlnQGdt
eC5uZXQ+IHdyb3RlOg0KPj4gICAgID4gTmVlZGxlc3MgdG8gc2F5IHRoYXQgdGhlc2UgY2hhbGxl
bmdlcyBoYXZlIGFsc28gYmVlbiBvYnNlcnZlZCBpbiBvdGhlcg0KPj4gICAgID4gcHJvdG9jb2xz
IGFzIHdlbGwsIHN1Y2ggYXMgSFRUUCBhbmQgZXZlbiBTSVAuDQo+Pg0KPj4gICAgID4gV2hhdCBp
cyB0aGUgc3RvcnkgZm9yIHByb3ZpZGluZyBhcHBsaWNhdGlvbiBsYXllciBzZWN1cml0eT8NCj4+
DQo+PiBPU0NPQVAgc2VlbXMgdG8gYmUgZW5kLXRvLWVuZCB0byBtZS4NCj4+DQo+PiAtLQ0KPj4g
TWljaGFlbCBSaWNoYXJkc29uIDxtY3IrSUVURkBzYW5kZWxtYW4uY2E+LCBTYW5kZWxtYW4gU29m
dHdhcmUgV29ya3MNCj4+ICAtPSBJUHY2IElvVCBjb25zdWx0aW5nID0tDQo+Pg0KPj4NCj4+DQo+
DQo+DQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+IFQyVFJHIG1haWxpbmcgbGlzdA0KPiBUMlRSR0BpcnRmLm9yZw0KPiBodHRwczovL3d3dy5p
cnRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3QydHJnPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBv
aW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fd3d3LmlydGYub3JnX21haWxtYW5fbGlzdGluZm9f
dDJ0cmcmZD1Ed01GLWcmYz1JVl9jbEF6b1BERTI1M3haZEh1aWxSZ3p0eWhfUmlWM3dVckxyRFFZ
V1NJJnI9NHcxM3ZkQ1ZFVWpfdmFDU1FOZEtSZjI1TzBQNGlhVm4wNEVsWExyQl9hayZtPWs3SXFD
NGxPU0JlRzV5WlQzbHdBWWdmcTdpc1BUSjF4N2xob3NVNHNJMFUmcz02RnlHaURUVy1VMzFGcHZ1
TXdwa1ZkaHBwSDRYTGN2bEFQUGlNcXZUVUlvJmU9Pg0KPg0K

--_000_0216378E89764D4EA307AEE5FD00BDA6GEcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <14BEC4C7F99B044C9237D1D141E2DCD0@NAMP101.PROD.OUTLOOK.COM>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpDb25zb2xhczsNCglwYW5vc2UtMToyIDExIDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBE
ZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0K
CXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGluaywgc3Bhbi5Nc29IeXBl
cmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNv
cmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCnAuZW1haWxxdW90ZSwgbGkuZW1haWxxdW90ZSwgZGl2LmVtYWlscXVv
dGUNCgl7bXNvLXN0eWxlLW5hbWU6ZW1haWxxdW90ZTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1h
cmdpbi1sZWZ0OjEuMHB0Ow0KCWJvcmRlcjpub25lOw0KCXBhZGRpbmc6MGluOw0KCWZvbnQtc2l6
ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0Kc3Bhbi5FbWFpbFN0
eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6Q2Fs
aWJyaTsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4ubXNvSW5zDQoJe21zby1zdHlsZS10eXBl
OmV4cG9ydC1vbmx5Ow0KCW1zby1zdHlsZS1uYW1lOiIiOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7DQoJY29sb3I6dGVhbDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl
eHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtz
aXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2
LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFk
Pg0KPGJvZHkgYmdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0i
cHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj5QZXJz
b25hbGx5LCBJ4oCZbSBhIGJpZyBmYW4gb2YgZW5kLXRvLWVuZCBhbmQgdGhpbmsgdGhhdCBpcyB0
aGUgY29ycmVjdCBhcHByb2FjaC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJp
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj5Ib3dldmVyLCBw
cmFnbWF0aWNhbGx5LCBJIHJlYWxpemUgdGhpcyBpcyBub3QgYWx3YXlzIHBvc3NpYmxlLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OkNhbGlicmkiPkkgaGF2ZW7igJl0IGZvbGxvd2VkIGl0IGZvciBhIHdoaWxl
LCBidXQgdGhlcmUgd2FzIHNvbWUgYWN0aXZpdHkgaW4gaHR0cGJpcyBhdCBvbmUgcG9pbnQgZm9y
IHJlc291cmNlL29iamVjdC1sZXZlbCBzZWN1cml0eSAoPGEgaHJlZj0iaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy93Zy9odHRwYmlzL2RyYWZ0LWlldGYtaHR0cGJpcy1lbmNyeXB0aW9uLWVuY29kaW5n
LykiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvd2cvaHR0cGJpcy9kcmFmdC1pZXRmLWh0dHBiaXMt
ZW5jcnlwdGlvbi1lbmNvZGluZy8pPC9hPi4mbmJzcDsNCiBJZiB3ZSBsaW1pdCB0aGUgZGlzY3Vz
c2lvbiB0byBwcm90b2NvbHMgdGhhdCBzdXBwb3J0IGNvbnRlbnQgY29kaW5ncyAoZS5nLiwgSFRU
UCBhbmQgQ29BUCksIHRoZW4gSSB3b3VsZCB0aGluayBkZWZpbmluZyBhIGNvZGluZyB0aGF0IHNw
ZWNpZmllcyB0aGUgcmVzb3VyY2UtbGV2ZWwgc2VjdXJpdHkgYXNwZWN0cyB3b3VsZCBhY2hpZXZl
IHF1aXRlIGEgbG90IGFuZCB3b3VsZCBiZSBhYmxlIHRvIHByZXNlcnZlIGFzcGVjdHMgdGhyb3Vn
aCBwcm90b2NvbA0KIGNvbnZlcnNpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2Fs
aWJyaSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+LSBSb2Ji
eTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5Sb2JieSBTaW1w
c29uLCBQaEQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNr
Ij5TeXN0ZW0gQXJjaGl0ZWN0PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTpDb25zb2xhcztj
b2xvcjpibGFjayI+R0U8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9y
OmJsYWNrIj5HcmlkIFNvbHV0aW9uczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6Q29uc29s
YXM7Y29sb3I6YmxhY2siPk06ICYjNDM7MSA0MDQgMjE5IDE4NTE8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuMHB0O2Zv
bnQtZmFtaWx5OkNvbnNvbGFzO2NvbG9yOmJsYWNrIj5Sb2JieS5TaW1wc29uQEdFLmNvbTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0
O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj4N
CjwvYj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTtjb2xvcjpibGFjayI+VDJUUkcg
Jmx0O3QydHJnLWJvdW5jZXNAaXJ0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiAmcXVvdDtLb3ZhdHNj
aCwgTWF0dGhpYXMmcXVvdDsgJmx0O21hdHRoaWFzLmtvdmF0c2NoQHNpZW1lbnMuY29tJmd0Ozxi
cj4NCjxiPkRhdGU6IDwvYj5UdWVzZGF5LCBNYXJjaCA3LCAyMDE3IGF0IDI6MzYgUE08YnI+DQo8
Yj5UbzogPC9iPiZxdW90O2hhbm5lcy50c2Nob2ZlbmlnQGdteC5uZXQmcXVvdDsgJmx0O2hhbm5l
cy50c2Nob2ZlbmlnQGdteC5uZXQmZ3Q7LCAmcXVvdDttY3ImIzQzO2lldGZAc2FuZGVsbWFuLmNh
JnF1b3Q7ICZsdDttY3ImIzQzO2lldGZAc2FuZGVsbWFuLmNhJmd0Ozxicj4NCjxiPkNjOiA8L2I+
JnF1b3Q7VDJUUkdAaXJ0Zi5vcmcmcXVvdDsgJmx0O1QyVFJHQGlydGYub3JnJmd0Ozxicj4NCjxi
PlN1YmplY3Q6IDwvYj5FWFQ6IFJlOiBbVDJUUkddIFJFU1RmdWwgRGVzaWduICZhbXA7IFNlY3Vy
aXR5PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmk7Y29sb3I6YmxhY2siPkZhaXIgZW5vdWdoLjxi
cj4NCjxicj4NClllcywgSSBhbSBvbiB0aGlzIElvVCBEaXJlY3RvcmF0ZS4gSSB3b3VsZCBzYXkg
YSBsYXJnZSBmcmFjdGlvbiBvZiB0aGUgVDJUUkcgcGFydGljaXBhbnRzIGhhcyBiZWVuIGFyZ3Vp
bmcgdGhhdCB0aGUgSW50ZXJuZXQgb2YgR2F0ZXdheXMgaXMgbm90IGEgZ29vZCBhcHByb2FjaC4g
WW91ciBzZWN1cml0eS1yZWxhdGVkIHN1bW1hcnkgcHJvdmVzIHRoaXMgcG9pbnQuPGJyPg0KPGJy
Pg0KSSBwZXJzb25hbGx5IGRvbid0IHNlZSBlbmQtdG8tZW5kIHNlY3VyaXR5IGhhcHBlbmluZyBp
ZiB3ZSBrZWVwIG1peGluZyBhcHBsaWNhdGlvbiBwcm90b2NvbHMsIGtlZXAgdXNpbmcgYmxhY2st
bWFnaWMgbWlkZGxlYm94ZXMsIGFuZCBrZWVwIHVzaW5nIHByb3ByaWV0YXJ5IGludGVyZmFjZXMg
YXQgdGhlIGRldmljZSBsZXZlbC4gV2UgbmVlZCBzb21ldGhpbmcgZW5kLXRvLWVuZCAob3IgVDJU
KSBmb3IgZW5kLXRvLWVuZCBzZWN1cml0eS48YnI+DQo8YnI+DQpCZXN0IHdpc2hlczxicj4NCk1h
dHRoaWFzIDxicj4NCjxicj4NCjxicj4NCjxicj4NClNlbnQgZnJvbSBteSBwaG9uZSwgbGltaXRh
dGlvbnMgbWlnaHQgYXBwbHkuPGJyPg0KPGJyPg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0g
PGJyPg0KPGI+RnJvbTo8L2I+IEhhbm5lcyBUc2Nob2ZlbmlnIFtoYW5uZXMudHNjaG9mZW5pZ0Bn
bXgubmV0XTxicj4NCjxiPlJlY2VpdmVkOjwvYj4gVHVlc2RheSwgMDcgTWFyIDIwMTcsIDIwOjEw
PGJyPg0KPGI+VG86PC9iPiBLb3ZhdHNjaCwgTWF0dGhpYXMgKENUIFJEQSBORUMgRU1CLURFKSBb
bWF0dGhpYXMua292YXRzY2hAc2llbWVucy5jb21dOyBtY3ImIzQzO2lldGZAc2FuZGVsbWFuLmNh
IFttY3ImIzQzO2lldGZAc2FuZGVsbWFuLmNhXTxicj4NCjxiPkNDOjwvYj4gVDJUUkdAaXJ0Zi5v
cmcgW1QyVFJHQGlydGYub3JnXTxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW1QyVFJHXSBSRVNU
ZnVsIERlc2lnbiAmYW1wOyBTZWN1cml0eTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPkhpIE1hdHRoaWFzLDxicj4NCjxicj4NCkkg
a25vdyB0aGF0IHRoaXMgaXMgYSByZXNlYXJjaCBncm91cCBhbmQgZXZlcnlvbmUgY2FuIGNyZWF0
ZSB3aGF0ZXZlcjxicj4NCnRoZXkgd2FudC48YnI+DQo8YnI+DQpXZSBicmllZmx5IHRhbGtlZCBh
Ym91dCBzZWN1cml0eSBhdCB0aGUgSW9UIGRpcmVjdG9yYXRlIGNvbmZlcmVuY2UgY2FsbDxicj4N
CmFuZCBJIHdvdWxkIGJlIGludGVyZXN0aW5nIHRvIGhlYXIgd2hhdCB3b3JrcyBhbmQgd2hhdCBk
b2VzIG5vdCB3b3JrIGZvcjxicj4NCm90aGVycy48YnI+DQo8YnI+DQpDaWFvPGJyPg0KSGFubmVz
PGJyPg0KPGJyPg0KPGJyPg0KT24gMDMvMDcvMjAxNyAwNzo0NSBQTSwgS292YXRzY2gsIE1hdHRo
aWFzIHdyb3RlOjxicj4NCiZndDsgT24gYmlnIHByb3BhZ2FuZGEgdG91cj8gOlA8YnI+DQomZ3Q7
IDxicj4NCiZndDsgUmVnYXJkczxicj4NCiZndDsgTWF0dGhpYXM8YnI+DQomZ3Q7IDxicj4NCiZn
dDsgPGJyPg0KJmd0OyBTZW50IGZyb20gbXkgcGhvbmUsIGxpbWl0YXRpb25zIG1pZ2h0IGFwcGx5
Ljxicj4NCiZndDsgPGJyPg0KJmd0OyAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCiZn
dDsgKkZyb206KiBIYW5uZXMgVHNjaG9mZW5pZyBbaGFubmVzLnRzY2hvZmVuaWdAZ214Lm5ldF08
YnI+DQomZ3Q7ICpSZWNlaXZlZDoqIFR1ZXNkYXksIDA3IE1hciAyMDE3LCAxOTozOTxicj4NCiZn
dDsgKlRvOiogTWljaGFlbCBSaWNoYXJkc29uIFttY3ImIzQzO2lldGZAc2FuZGVsbWFuLmNhXTxi
cj4NCiZndDsgKkNDOiogdDJ0cmdAaXJ0Zi5vcmcgW1QyVFJHQGlydGYub3JnXTxicj4NCiZndDsg
KlN1YmplY3Q6KiBSZTogW1QyVFJHXSBSRVNUZnVsIERlc2lnbiAmYW1wOyBTZWN1cml0eTxicj4N
CiZndDsgPGJyPg0KJmd0OyBPU0NPQVAgZG9lcyBub3Qgd29yayB3aGVuPGJyPg0KJmd0OyA8YnI+
DQomZ3Q7ICogeW91IG1peCBwcm90b2NvbHMsPGJyPg0KJmd0OyAqIHVzZSBhIG1pZGRsZWJveCBm
b3Igc29tZSBwcm9jZXNzaW5nIGludGVyYWN0aW9ucyAoc3VjaCBhcyBkYXRhPGJyPg0KJmd0OyBh
Z2dyZWdhdGlvbiksIGFuZDxicj4NCiZndDsgKiB3aGVuIG9uZSBvZiB0aGUgcHJvdG9jb2xzIGlz
IGEgbm9uLVJFU1RmdWwgcHJvdG9jb2wsIHN1Y2ggYXMgQkxFIG9yIE1RVFQuPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7IFVuZm9ydHVuYXRlbHksIHRoZXNlIHRoZSB1c2UgY2FzZXMgd2UgYXJlIGZhY2lu
ZyBpbiBjdXJyZW50IElvVDxicj4NCiZndDsgZGVwbG95bWVudHMuIEZvciBzaW1pbGFyIHJlYXNv
bnMgd2UgY2Fubm90IHVzZSBSRkMgODA3NSBlaXRoZXIuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IE1h
eWJlIHlvdSBhcmUgc2VlaW5nIGRpZmZlcmVudCBkZXBsb3ltZW50IGVudmlyb25tZW50cy48YnI+
DQomZ3Q7IDxicj4NCiZndDsgQ2lhbzxicj4NCiZndDsgSGFubmVzPGJyPg0KJmd0OyA8YnI+DQom
Z3Q7IE9uIDAzLzA3LzIwMTcgMDY6MzkgUE0sIE1pY2hhZWwgUmljaGFyZHNvbiB3cm90ZTo8YnI+
DQomZ3Q7Jmd0OyA8YnI+DQomZ3Q7Jmd0OyBIYW5uZXMgVHNjaG9mZW5pZyAmbHQ7aGFubmVzLnRz
Y2hvZmVuaWdAZ214Lm5ldCZndDsgd3JvdGU6PGJyPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgJmd0OyBOZWVkbGVzcyB0byBzYXkgdGhhdCB0aGVzZSBjaGFsbGVuZ2VzIGhhdmUg
YWxzbyBiZWVuIG9ic2VydmVkIGluIG90aGVyPGJyPg0KJmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgJmd0OyBwcm90b2NvbHMgYXMgd2VsbCwgc3VjaCBhcyBIVFRQIGFuZCBldmVuIFNJ
UC48YnI+DQomZ3Q7Jmd0OyA8YnI+DQomZ3Q7Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IFdoYXQgaXMgdGhlIHN0b3J5IGZvciBwcm92aWRpbmcgYXBwbGljYXRpb24gbGF5ZXIgc2Vj
dXJpdHk/PGJyPg0KJmd0OyZndDsgPGJyPg0KJmd0OyZndDsgT1NDT0FQIHNlZW1zIHRvIGJlIGVu
ZC10by1lbmQgdG8gbWUuPGJyPg0KJmd0OyZndDsgPGJyPg0KJmd0OyZndDsgLS08YnI+DQomZ3Q7
Jmd0OyBNaWNoYWVsIFJpY2hhcmRzb24gJmx0O21jciYjNDM7SUVURkBzYW5kZWxtYW4uY2EmZ3Q7
LCBTYW5kZWxtYW4gU29mdHdhcmUgV29ya3M8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAtPSBJUHY2IElv
VCBjb25zdWx0aW5nID0tPGJyPg0KJmd0OyZndDsgPGJyPg0KJmd0OyZndDsgPGJyPg0KJmd0OyZn
dDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyBfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgVDJUUkcgbWFp
bGluZyBsaXN0PGJyPg0KJmd0OyBUMlRSR0BpcnRmLm9yZzxicj4NCiZndDsgPGEgaHJlZj0iaHR0
cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX193d3cuaXJ0
Zi5vcmdfbWFpbG1hbl9saXN0aW5mb190MnRyZyZhbXA7ZD1Ed01GLWcmYW1wO2M9SVZfY2xBem9Q
REUyNTN4WmRIdWlsUmd6dHloX1JpVjN3VXJMckRRWVdTSSZhbXA7cj00dzEzdmRDVkVVal92YUNT
UU5kS1JmMjVPMFA0aWFWbjA0RWxYTHJCX2FrJmFtcDttPWs3SXFDNGxPU0JlRzV5WlQzbHdBWWdm
cTdpc1BUSjF4N2xob3NVNHNJMFUmYW1wO3M9NkZ5R2lEVFctVTMxRnB2dU13cGtWZGhwcEg0WExj
dmxBUFBpTXF2VFVJbyZhbXA7ZT0iPg0KaHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby90MnRyZzwvYT48YnI+DQomZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_0216378E89764D4EA307AEE5FD00BDA6GEcom_--


From nobody Tue Mar  7 12:02:36 2017
Return-Path: <matthias.kovatsch@siemens.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 D7D1B129569 for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 12:02:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.929
X-Spam-Level: 
X-Spam-Status: No, score=-4.929 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=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 RHDkhG6G--Q2 for <t2trg@ietfa.amsl.com>; Tue,  7 Mar 2017 12:02:33 -0800 (PST)
Received: from david.siemens.de (david.siemens.de [192.35.17.14]) (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 20F49129531 for <T2TRG@irtf.org>; Tue,  7 Mar 2017 12:02:32 -0800 (PST)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id v27K2Qb6030624 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 7 Mar 2017 21:02:26 +0100
Received: from DEFTHW99ERGMSX.ww902.siemens.net (defthw99ergmsx.ww902.siemens.net [139.22.70.132]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id v27K2Pfx027112 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Mar 2017 21:02:25 +0100
Received: from DENBGAT9ERRMSX.ww902.siemens.net (139.22.70.197) by DEFTHW99ERGMSX.ww902.siemens.net (139.22.70.132) with Microsoft SMTP Server (TLS) id 14.3.339.0; Tue, 7 Mar 2017 21:02:25 +0100
Received: from DEFTHW99EL4MSX.ww902.siemens.net ([169.254.5.206]) by DENBGAT9ERRMSX.ww902.siemens.net ([139.22.70.197]) with mapi id 14.03.0339.000; Tue, 7 Mar 2017 21:02:25 +0100
From: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>
To: "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>, "robby.simpson@ge.com" <robby.simpson@ge.com>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpshLU+67EadNU+/wTUKb0HGTaGJlY0AgAAQwgCAABJb3v//9luAgAAYCfz///IoAIAAFQ0g
Date: Tue, 7 Mar 2017 20:02:24 +0000
Message-ID: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA3219@DEFTHW99EL4MSX.ww902.siemens.net>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>, <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com>
In-Reply-To: <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA3219DEFTHW99EL4MSXw_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/i9NXR8Kbo7S1zYtKb4Zmk3lJUxI>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Tue, 07 Mar 2017 20:02:36 -0000

--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA3219DEFTHW99EL4MSXw_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Yes, that sounds very reasonable. It does include changing the (end-)device=
s to support this new approach.

In the W3C Web of Things, we have the idea to retrofit information such as =
encoding and security aspects through interface descriptions that can be us=
ed across multiple IoT protocols (WoT Thing Description). Still it requires=
 to upgrade what is accepted and served by the devices within the protocol =
used...

Ciao
Matthias


Sent from my phone, limitations might apply.

-----Original Message-----
From: Simpson, Robby (GE Energy Connections) [robby.simpson@ge.com]
Received: Tuesday, 07 Mar 2017, 20:47
To: Kovatsch, Matthias (CT RDA NEC EMB-DE) [matthias.kovatsch@siemens.com];=
 hannes.tschofenig@gmx.net [hannes.tschofenig@gmx.net]; mcr+ietf@sandelman.=
ca [mcr+ietf@sandelman.ca]
CC: T2TRG@irtf.org [T2TRG@irtf.org]
Subject: Re: [T2TRG] RESTful Design & Security

Personally, I=92m a big fan of end-to-end and think that is the correct app=
roach.

However, pragmatically, I realize this is not always possible.

I haven=92t followed it for a while, but there was some activity in httpbis=
 at one point for resource/object-level security (https://tools.ietf.org/wg=
/httpbis/draft-ietf-httpbis-encryption-encoding/).  If we limit the discuss=
ion to protocols that support content codings (e.g., HTTP and CoAP), then I=
 would think defining a coding that specifies the resource-level security a=
spects would achieve quite a lot and would be able to preserve aspects thro=
ugh protocol conversion.

- Robby


Robby Simpson, PhD
System Architect
GE
Grid Solutions
M: +1 404 219 1851
Robby.Simpson@GE.com


From: T2TRG <t2trg-bounces@irtf.org> on behalf of "Kovatsch, Matthias" <mat=
thias.kovatsch@siemens.com>
Date: Tuesday, March 7, 2017 at 2:36 PM
To: "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>, "mcr+ietf@sand=
elman.ca" <mcr+ietf@sandelman.ca>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: EXT: Re: [T2TRG] RESTful Design & Security

Fair enough.

Yes, I am on this IoT Directorate. I would say a large fraction of the T2TR=
G participants has been arguing that the Internet of Gateways is not a good=
 approach. Your security-related summary proves this point.

I personally don't see end-to-end security happening if we keep mixing appl=
ication protocols, keep using black-magic middleboxes, and keep using propr=
ietary interfaces at the device level. We need something end-to-end (or T2T=
) for end-to-end security.

Best wishes
Matthias



Sent from my phone, limitations might apply.

-----Original Message-----
From: Hannes Tschofenig [hannes.tschofenig@gmx.net]
Received: Tuesday, 07 Mar 2017, 20:10
To: Kovatsch, Matthias (CT RDA NEC EMB-DE) [matthias.kovatsch@siemens.com];=
 mcr+ietf@sandelman.ca [mcr+ietf@sandelman.ca]
CC: T2TRG@irtf.org [T2TRG@irtf.org]
Subject: Re: [T2TRG] RESTful Design & Security
Hi Matthias,

I know that this is a research group and everyone can create whatever
they want.

We briefly talked about security at the IoT directorate conference call
and I would be interesting to hear what works and what does not work for
others.

Ciao
Hannes


On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
> On big propaganda tour? :P
>
> Regards
> Matthias
>
>
> Sent from my phone, limitations might apply.
>
> -----Original Message-----
> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
> *Received:* Tuesday, 07 Mar 2017, 19:39
> *To:* Michael Richardson [mcr+ietf@sandelman.ca]
> *CC:* t2trg@irtf.org [T2TRG@irtf.org]
> *Subject:* Re: [T2TRG] RESTful Design & Security
>
> OSCOAP does not work when
>
> * you mix protocols,
> * use a middlebox for some processing interactions (such as data
> aggregation), and
> * when one of the protocols is a non-RESTful protocol, such as BLE or MQT=
T.
>
> Unfortunately, these the use cases we are facing in current IoT
> deployments. For similar reasons we cannot use RFC 8075 either.
>
> Maybe you are seeing different deployment environments.
>
> Ciao
> Hannes
>
> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>
>> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>     > Needless to say that these challenges have also been observed in o=
ther
>>     > protocols as well, such as HTTP and even SIP.
>>
>>     > What is the story for providing application layer security?
>>
>> OSCOAP seems to be end-to-end to me.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>  -=3D IPv6 IoT consulting =3D-
>>
>>
>>
>
>
>
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg<https://urldefense.proofpoint=
.com/v2/url?u=3Dhttps-3A__www.irtf.org_mailman_listinfo_t2trg&d=3DDwMF-g&c=
=3DIV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=3D4w13vdCVEUj_vaCSQNdKRf25=
O0P4iaVn04ElXLrB_ak&m=3Dk7IqC4lOSBeG5yZT3lwAYgfq7isPTJ1x7lhosU4sI0U&s=3D6Fy=
GiDTW-U31FpvuMwpkVdhppH4XLcvlAPPiMqvTUIo&e=3D>
>

--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA3219DEFTHW99EL4MSXw_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Consolas}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.emailquote, li.emailquote, div.emailquote
	{margin-right:0in;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman"}
span.EmailStyle18
	{font-family:Calibri;
	color:windowtext}
span.msoIns
	{text-decoration:underline;
	color:teal}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
	{}
-->
</style>
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11=
pt; color:black">Yes, that sounds very reasonable. It does include changing=
 the (end-)devices to support this new approach.<br>
<br>
In the W3C Web of Things, we have the idea to retrofit information such as =
encoding and security aspects through interface descriptions that can be us=
ed across multiple IoT protocols (WoT Thing Description). Still it requires=
 to upgrade what is accepted and
 served by the devices within the protocol used...<br>
<br>
Ciao<br>
Matthias <br>
<br>
<br>
Sent from my phone, limitations might apply.<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Simpson, Robby (GE Energy Connections) [robby.simpson@ge.com]<=
br>
<b>Received:</b> Tuesday, 07 Mar 2017, 20:47<br>
<b>To:</b> Kovatsch, Matthias (CT RDA NEC EMB-DE) [matthias.kovatsch@siemen=
s.com]; hannes.tschofenig@gmx.net [hannes.tschofenig@gmx.net]; mcr&#43;ietf=
@sandelman.ca [mcr&#43;ietf@sandelman.ca]<br>
<b>CC:</b> T2TRG@irtf.org [T2TRG@irtf.org]<br>
<b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security<br>
<br>
</span></span>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">Personally, I=92m a big fan of end-to-end and think that is the correct a=
pproach.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">However, pragmatically, I realize this is not always possible.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">I haven=92t followed it for a while, but there was some activity in httpb=
is at one point for resource/object-level security (<a href=3D"https://tool=
s.ietf.org/wg/httpbis/draft-ietf-httpbis-encryption-encoding/)">https://too=
ls.ietf.org/wg/httpbis/draft-ietf-httpbis-encryption-encoding/)</a>.&nbsp;
 If we limit the discussion to protocols that support content codings (e.g.=
, HTTP and CoAP), then I would think defining a coding that specifies the r=
esource-level security aspects would achieve quite a lot and would be able =
to preserve aspects through protocol
 conversion.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">- Robby</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">&nbsp;</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt; font-family:Consolas=
; color:black">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt; font-family:Consolas=
; color:black">Robby Simpson, PhD</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt; font-family:Consolas=
; color:black">System Architect</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt; font-family:Consolas=
; color:black">GE</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt; font-family:Consolas=
; color:black">Grid Solutions</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt; font-family:Consolas=
; color:black">M: &#43;1 404 219 1851</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt; font-family:Consolas=
; color:black">Robby.Simpson@GE.com</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:Calibri=
">&nbsp;</span></p>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-family:Calibri; color:black">=
From: </span>
</b><span style=3D"font-family:Calibri; color:black">T2TRG &lt;t2trg-bounce=
s@irtf.org&gt; on behalf of &quot;Kovatsch, Matthias&quot; &lt;matthias.kov=
atsch@siemens.com&gt;<br>
<b>Date: </b>Tuesday, March 7, 2017 at 2:36 PM<br>
<b>To: </b>&quot;hannes.tschofenig@gmx.net&quot; &lt;hannes.tschofenig@gmx.=
net&gt;, &quot;mcr&#43;ietf@sandelman.ca&quot; &lt;mcr&#43;ietf@sandelman.c=
a&gt;<br>
<b>Cc: </b>&quot;T2TRG@irtf.org&quot; &lt;T2TRG@irtf.org&gt;<br>
<b>Subject: </b>EXT: Re: [T2TRG] RESTful Design &amp; Security</span></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:11.0pt; font-family:Calibri; color:black">Fair enough.<br>
<br>
Yes, I am on this IoT Directorate. I would say a large fraction of the T2TR=
G participants has been arguing that the Internet of Gateways is not a good=
 approach. Your security-related summary proves this point.<br>
<br>
I personally don't see end-to-end security happening if we keep mixing appl=
ication protocols, keep using black-magic middleboxes, and keep using propr=
ietary interfaces at the device level. We need something end-to-end (or T2T=
) for end-to-end security.<br>
<br>
Best wishes<br>
Matthias <br>
<br>
<br>
<br>
Sent from my phone, limitations might apply.<br>
<br>
-----Original Message----- <br>
<b>From:</b> Hannes Tschofenig [hannes.tschofenig@gmx.net]<br>
<b>Received:</b> Tuesday, 07 Mar 2017, 20:10<br>
<b>To:</b> Kovatsch, Matthias (CT RDA NEC EMB-DE) [matthias.kovatsch@siemen=
s.com]; mcr&#43;ietf@sandelman.ca [mcr&#43;ietf@sandelman.ca]<br>
<b>CC:</b> T2TRG@irtf.org [T2TRG@irtf.org]<br>
<b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt">Hi Matthias,<br>
<br>
I know that this is a research group and everyone can create whatever<br>
they want.<br>
<br>
We briefly talked about security at the IoT directorate conference call<br>
and I would be interesting to hear what works and what does not work for<br=
>
others.<br>
<br>
Ciao<br>
Hannes<br>
<br>
<br>
On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:<br>
&gt; On big propaganda tour? :P<br>
&gt; <br>
&gt; Regards<br>
&gt; Matthias<br>
&gt; <br>
&gt; <br>
&gt; Sent from my phone, limitations might apply.<br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]<br>
&gt; *Received:* Tuesday, 07 Mar 2017, 19:39<br>
&gt; *To:* Michael Richardson [mcr&#43;ietf@sandelman.ca]<br>
&gt; *CC:* t2trg@irtf.org [T2TRG@irtf.org]<br>
&gt; *Subject:* Re: [T2TRG] RESTful Design &amp; Security<br>
&gt; <br>
&gt; OSCOAP does not work when<br>
&gt; <br>
&gt; * you mix protocols,<br>
&gt; * use a middlebox for some processing interactions (such as data<br>
&gt; aggregation), and<br>
&gt; * when one of the protocols is a non-RESTful protocol, such as BLE or =
MQTT.<br>
&gt; <br>
&gt; Unfortunately, these the use cases we are facing in current IoT<br>
&gt; deployments. For similar reasons we cannot use RFC 8075 either.<br>
&gt; <br>
&gt; Maybe you are seeing different deployment environments.<br>
&gt; <br>
&gt; Ciao<br>
&gt; Hannes<br>
&gt; <br>
&gt; On 03/07/2017 06:39 PM, Michael Richardson wrote:<br>
&gt;&gt; <br>
&gt;&gt; Hannes Tschofenig &lt;hannes.tschofenig@gmx.net&gt; wrote:<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; Needless to say that these challenges=
 have also been observed in other<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; protocols as well, such as HTTP and e=
ven SIP.<br>
&gt;&gt; <br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; &gt; What is the story for providing appli=
cation layer security?<br>
&gt;&gt; <br>
&gt;&gt; OSCOAP seems to be end-to-end to me.<br>
&gt;&gt; <br>
&gt;&gt; --<br>
&gt;&gt; Michael Richardson &lt;mcr&#43;IETF@sandelman.ca&gt;, Sandelman So=
ftware Works<br>
&gt;&gt;&nbsp; -=3D IPv6 IoT consulting =3D-<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; T2TRG mailing list<br>
&gt; T2TRG@irtf.org<br>
&gt; <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.=
irtf.org_mailman_listinfo_t2trg&amp;d=3DDwMF-g&amp;c=3DIV_clAzoPDE253xZdHui=
lRgztyh_RiV3wUrLrDQYWSI&amp;r=3D4w13vdCVEUj_vaCSQNdKRf25O0P4iaVn04ElXLrB_ak=
&amp;m=3Dk7IqC4lOSBeG5yZT3lwAYgfq7isPTJ1x7lhosU4sI0U&amp;s=3D6FyGiDTW-U31Fp=
vuMwpkVdhppH4XLcvlAPPiMqvTUIo&amp;e=3D">
https://www.irtf.org/mailman/listinfo/t2trg</a><br>
&gt; </span></p>
</div>
</div>
</div>
</body>
</html>

--_000_4EBB3DDD0FBF694CA2A87838DF129B3C01AA3219DEFTHW99EL4MSXw_--


From nobody Wed Mar  8 00:30:39 2017
Return-Path: <goran.selander@ericsson.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 8F6AA129570 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 00:30:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 4lj9mUvO3MpH for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 00:30:36 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 A3CF6127071 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 00:30:35 -0800 (PST)
X-AuditID: c1b4fb2d-effff7000000290a-29-58bfc128f2bd
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by  (Symantec Mail Security) with SMTP id 61.1B.10506.821CFB85; Wed,  8 Mar 2017 09:30:33 +0100 (CET)
Received: from ESESSMB107.ericsson.se ([169.254.7.76]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0319.002; Wed, 8 Mar 2017 09:30:32 +0100
From: =?utf-8?B?R8O2cmFuIFNlbGFuZGVy?= <goran.selander@ericsson.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpsnFV1UjpOgG0yLh2UXCglOtqGJlY0AgAAQwQCAAPj4gA==
Date: Wed, 8 Mar 2017 08:30:30 +0000
Message-ID: <D4E5582E.78797%goran.selander@ericsson.com>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
In-Reply-To: <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-ID: <88BE9FDD52D2A54BB92F3F1D2A182626@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsUyM2K7lq7mwf0RBv/uSFks3XmP1aLnUD+7 xfsHPSwOzB6LN+1n85i88TCbR8ucPcwBzFFcNimpOZllqUX6dglcGY+/bWEt+OVYMWmSdQPj AocuRk4OCQETiWubNrB0MXJxCAmsY5S49nAGO4SziFHi2J0WNpAqNgEXiQcNj5hAbBGBeIkp f0+xgNjMAqoSUw/dA7OFBfQktszYywpRoy9x8lQPG4TtJDHhB0Qvi4CKxIeJL8BqeAUsJH5f g7CFBKYwSkx5rdrFyMHBKWAtcfxHFkiYUUBM4vupNUwQq8Qlbj2ZzwRxtIDEkj3nmSFsUYmX j/+BjREFOmH58zVQcSWJtYe3s4CMZBbQlFi/Sx9ijLXExkO97BC2osSU7ofsENcISpyc+YRl AqP4LCTbZiF0z0LSPQtJ9ywk3QsYWVcxihanFhfnphsZ66UWZSYXF+fn6eWllmxiBEbfwS2/ dXcwrn7teIhRgINRiYf3w6l9EUKsiWXFlbmHGCU4mJVEeCUW7o8Q4k1JrKxKLcqPLyrNSS0+ xCjNwaIkzmu28n64kEB6YklqdmpqQWoRTJaJg1OqgbE5JuTid2MhNeNN586fnLn12vZ9j5Yn Pn386qJxyKSuiOu7Xu19O7/hg67IjPbPs9SECl7G5SWm7fM7HfknYLn2hZdbvq4OfZTAcMts x4VHTbZrW1dcze9aWi+/13jPHpdF754EntBe+khQTCQue8NiRy1RlbjyY5zXlgjy3FmUl2bG Ozmw7mepEktxRqKhFnNRcSIAJM8F3boCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/rqOVjO1nPRTogO6o-xaIlUqgqLg>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 08:30:37 -0000

SGkgSGFubmVzLCBhbmQgYWxsLA0KDQpTaW5jZSBIYW5uZXMgaXMgc28gZWFnZXIgdG8gc3RhdGUg
d2hhdCBoZSB0aGlua3MgT1NDT0FQIGRvZXNu4oCZdCB3b3JrIGZvcg0KKHdoaWNoIHdlIGFsbCB1
bmRlcnN0YW5kIGlzIHRoZSByZWFzb24gZm9yIHN0YXJ0aW5nIHRoaXMgdGhyZWFkIGluIHRoZQ0K
Zmlyc3QgcGxhY2UgSiksIGFsbG93IG1lIHRvIGJhbGFuY2UgdGhpcyBieSBvdXRsaW5pbmcgdGhl
IGVuZC10by1lbmQNCnNlY3VyaXR5IHNldHRpbmdzIHdoZXJlIHBlb3BsZSBwbGFuIHRvIHVzZSBP
U0NPQVAgc28gZmFyLg0KDQpCdXQgZmlyc3QgdGhlIHN0b3J5IGFib3V0IGFwcGxpY2F0aW9uIGxh
eWVyIHNlY3VyaXR5LCBSRVNUIGFuZA0KaW50ZXJtZWRpYXJ5IG5vZGVzICh3aGljaCB3YXMgdGhl
IHF1ZXN0aW9uIGFza2VkKToNCg0KSWYgdGhlIGludGVybWVkaWFyeSBpcyByZXF1aXJlZCB0byBw
ZXJmb3JtIG9wZXJhdGlvbnMgb24gZW5jcnlwdGVkIGRhdGENCihzdWNoIGFzIGRhdGEgYWdncmVn
YXRpb24gYnkgbm9uLXRydXN0ZWQgaW50ZXJtZWRpYXJ5KSwgdGhlcmUgYXJlDQp0ZWNobmlxdWVz
IHN1Y2ggYXMgaG9tb21vcnBoaWMgZW5jcnlwdGlvbiwgYnV0IHRoZSBhcHBsaWNhdGlvbiBpbiB0
aGUNCmNsb3VkIHdvdWxkIGluIHRoaXMgY2FzZSBhbnl3YXkgaGF2ZSB0byB0cnVzdCB0aGUgaW50
ZXJtZWRpYXJ5IHRvIHBlcmZvcm0NCnRoZSByZXF1aXJlZCBvcGVyYXRpb24gc2luY2UgdGhlIGlu
dGVncml0eSBvZiB0aGUgbWVzc2FnZSB3b3VsZCBub3QgYmUNCnByZXNlcnZlZC4gQ2xlYXJseSwg
dGhpcyBpcyBub3QgYSBsaW1pdGF0aW9uIHNwZWNpZmljYWxseSBvZiBPU0NPQVAuDQoNClRoZSB0
eXBlIG9mIG9wZXJhdGlvbnMgeW91IGNhbiBleHBlY3QgYW4gaW50ZXJtZWRpYXJ5IHRvIHBlcmZv
cm0gYW5kIHN0aWxsDQpwcmVzZXJ2ZSBpbnRlZ3JpdHkgZW5kLXRvLWVuZCBpcyBtb3JlIGxpa2Ug
dGhlIHN1cHBvcnQgZm9yIFJFU1RmdWwNCm9wZXJhdGlvbnMgcGVyZm9ybWVkIGJ5IGEgQ29BUCBw
cm94eSAtIHRoZSBwcm94eSByZWFkcyBDb0FQIG1ldGEtZGF0YSBhbmQNCnBlcmZvcm1zIHZhcmlv
dXMgbWVzc2FnZS1yZWxhdGVkIG9wZXJhdGlvbnMuIElmIHlvdSBhcHBseSBzZWN1cml0eSBvbg0K
dHJhbnNwb3J0IGxheWVyIG9yIGJlbG93IChEVExTLCBJUHNlYyBldGMuKSB0aGVuIHRoZSBDb0FQ
IG1ldGEtZGF0YSBpcw0Kb25seSB2aXNpYmxlIHRvIHRoZSB0cnVzdGVkIGVuZHBvaW50IGZvciB0
aGUgc2VjdXJlIGNoYW5uZWwsIHdoaWNoIGVpdGhlcg0KbWFrZXMgaXQgdXNlbGVzcyBmb3IgdGhl
IGludGVybWVkaWFyeSBvciBtYWtlcyB0aGUgaW50ZXJtZWRpYXJ5IGEgdHJ1c3RlZA0KZW5kcG9p
bnQuIElmIHlvdSBhcHBseSBzZWN1cml0eSBvbiBhcHBsaWNhdGlvbiBsYXllciB0aGVuIGl0IGlz
IHBvc3NpYmxlDQpmb3IgYW4gaW50ZXJtZWRpYXJ5IHRvIHBlcmZvcm0gdGhlc2Ugb3BlcmF0aW9u
cyB3aGlsZSBwcmVzZXJ2aW5nDQppbnRlZ3JpdHkuIFRoZXJlIGFyZSB0d28gb3B0aW9uczoNCg0K
MS4gQXBwbHkgc2VjdXJpdHkgYWJvdmUgdGhlIHdlYiB0cmFuc2ZlciBsYXllciwgaS5lLiB0byBD
b0FQL0hUVFAgcGF5bG9hZCwNCmUuZy4gYnkgd3JhcHBpbmcgdGhlIHBheWxvYWQgaW4gdGhlIENP
U0UgZm9ybWF0LiBJbiB0aGlzIGNhc2UgdGhlIHNlY3VyZQ0KQ09TRSBvYmplY3QgaXMgaW5kZXBl
bmRlbnQgb2Ygd2ViIHRyYW5zZmVyIG1lY2hhbmlzbSBzbyB5b3UgY2FuIHN3aXRjaA0KYmV0d2Vl
biBlLmcuIEhUVFAgYW5kIENvQVAuIEhvd2V2ZXIsIHRoZSB3ZWIgdHJhbnNmZXIgbWV0YWRhdGEs
IGluY2x1ZGluZw0KZS5nLiB0aGUgUkVTVGZ1bCBtZXRob2QsIHJlc291cmNlIGV0Yy4gaXMgbm90
IHByb3RlY3RlZC4gVGhpcyBpcyBhbnl3YXkNCnVzZWZ1bCBpZiB0aGUgbWV0aG9kL3Jlc291cmNl
IGV0Yy4gaXMgaW1wbGljaXQgb3IgdGhlIGFwcGxpY2F0aW9uIHByb3ZpZGVzDQp0aGUgY29udGV4
dCwgZS5nLiBDb0FQIHB1Yi9zdWIuDQoNCjIuIEFwcGx5IHNlY3VyaXR5IHRvIHRoZSB3ZWIgdHJh
bnNmZXIgbGF5ZXIsIGkuZS4gcHJvdGVjdCBub3Qgb25seSBDb0FQDQpwYXlsb2FkIGJ1dCBhbHNv
IENvQVAgbWV0YSBkYXRhIChoZWFkZXJzIGFuZCBvcHRpb25zKSBpbiBzdWNoIGEgd2F5IHRoYXQN
CmNlcnRhaW4gQ29BUCBwcm94eSBvcGVyYXRpb25zIGNhbiBzdGlsbCBiZSBwZXJmb3JtZWQgKGUu
Zy4gb25seSBpbnRlZ3JpdHkNCnByb3RlY3RpbmcgdGhlIFJFU1RmdWwgbWV0aG9kIGFsbG93aW5n
IHRoZSBwcm94eSB0byByZWFkIGJ1dCBub3QgY2hhbmdlKS4NClRoaXMgaXMgd2hhdCBPU0NPQVAg
ZG9lcy4NCg0KVGhlIHJlYXNvbnMgd2h5IHBlb3BsZSBhcmUgaW50ZXJlc3RlZCBpbiBPU0NPQVAs
IGJlc2lkZXMgZW5kLXRvLWVuZA0Kc2VjdXJpdHkgYW5kIHN1cHBvcnQgZm9yIENvQVAgcHJveHkg
b3BlcmF0aW9ucyB3aGljaCBpcyBlLmcuIHVzZWQgaW4NCjZ0aXNjaCBzZWN1cmUgam9pbiwgaW5j
bHVkZToNCg0KLSBPU0NPQVAgd29ya3MgZXNzZW50aWFsbHkgd2hlcmV2ZXIgQ29BUCB3b3JrcyAo
VURQLCBUQ1AsIFNNUywgQkxFLA0KODAyLjE1LjQgSUUsICAuIC4gLikgYW5kIHByb3ZpZGVzIGVu
ZC10by1lbmQgc2VjdXJpdHkgaW5kZXBlbmRlbnRseSBvZiBob3cNCnRoZSB1bmRlcmx5aW5nIGxh
eWVycyBhcmUgYmVpbmcgc3dpdGNoZWQgYWxvbmcgdGhlIHBhdGguDQogDQoNCi0gT1NDT0FQIGlz
IHBvc3NpYmxlIHRvIGV4dGVuZGVkIHRvIHNlY3VyZSBDb0FQIG92ZXIgbXVsdGljYXN0IElQIChv
ciBDb0FQDQpncm91cCBjb21tdW5pY2F0aW9uIGluIGdlbmVyYWwgUkZDNzM5MCk6DQpodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtdGlsb2NhLWNvcmUtbXVsdGljYXN0LW9zY29hcA0K
DQotIE9TQ09BUCBpcyB2ZXJ5IGxpZ2h0d2VpZ2h0LiBSZWNlbnQgb3B0aW1pc2F0aW9ucyB0byBi
ZSBwdWJsaXNoZWQgYnkgdGhlDQpJRVRGIHN1Ym1pc3Npb24gY3V0b2ZmIHNocmluayB0aGUgbWVz
c2FnZSBvdmVyaGVhZCBkb3duIHRvIDEzIGJ5dGVzIGluIHRoZQ0KQ29BUCByZXF1ZXN0IGFuZCA5
IGJ5dGVzIGluIHRoZSBPU0NPQVAgcmVzcG9uc2UuIFRoaXMgaW5jbHVkZXMgdGhlIDggYnl0ZXMN
Ck1BQy4gV2l0aCBleGlzdGluZyBDb0FQIGFuZCBDT1NFIGltcGxlbWVudGF0aW9uLCBPU0NPQVAg
aXMgYSBtaW5vcg0KYWRkaXRpb24gaW4gdGVybXMgb2YgY29kZS4NCg0KDQpOb3cgZm9yIHRoZSBz
dGF0ZW1lbnRzIG1hZGUgYWJvdXQgT1NDT0FQOg0KDQo+IE9TQ09BUCBkb2VzIG5vdCB3b3JrIHdo
ZW4NCj4gKiB5b3UgbWl4IHByb3RvY29scywNCg0KZm9yIGdlbmVyYWwgd2ViIHRyYW5zZmVyIHBy
b3RvY29scyB0aGlzIGVpdGhlciByZXF1aXJlcyBwcm90ZWN0aW9uIG9uIGENCmxvd2VyIGxheWVy
LCB3aGljaCBwcmV2ZW50cyBhbiBpbnRlcm1lZGlhcnkgZnJvbSByZWFkaW5nIHRoZSBtZXRhZGF0
YSBhcw0Kd2UgaGF2ZSBzZWVuLCBvciB5b3UgY2FuIHJlc3RyaWN0IHByb3RlY3Rpb24gdG8gQ29B
UC9IVFRQIHBheWxvYWQgYXMgaW4gMS4NCmFib3ZlLiBCdXQgaWYgeW91IGNvbnNpZGVyIHNwZWNp
ZmljIHByb3RvY29scyB3aXRoIHNpbWlsYXIgc2VtYW50aWNzIHN1Y2gNCmFzIEhUVFAgYW5kIENv
QVAsIGl0IGlzIHBvc3NpYmxlIHRvIGRlZmluZSBhIG1hcHBpbmcgZm9yIGEgc3Vic2V0IG9mIHRo
ZQ0KbWV0YWRhdGEgZm9yIHdoaWNoIE9TQ09BUCB3b3VsZCBwcmVzZXJ2ZSBpbnRlZ3JpdHkgYW5k
IGNvbmZpZGVudGlhbGl0eQ0KYWxvbmcgdGhlIGxpbmVzIGVsYWJvcmF0ZWQgYnkgTWF0dGhpYXMg
aW4gdGhpcyB0aHJlYWQuIFdlIHN0YXJ0ZWQNCnNrZXRjaGluZyBvbiB0aGlzIGR1cmluZyBJRVRG
OTQgKHdpdGggc29tZSBvZiB0aGUgYXV0aG9ycyBvZiBSRkM4MDc1KSBidXQNCmhhdmUgbm90IGhh
ZCB0aW1lIHRvIGNvbnRpbnVlIHRoZSB3b3JrLiBXZSBhcmUgaGFwcHkgdG8gcHVyc3VlIHRoaXMg
d29yaw0KaWYgcGVvcGxlIHRoaW5rIHRoaXMgaXMgaW50ZXJlc3RpbmcuDQoNCj4gKiB1c2UgYSBt
aWRkbGVib3ggZm9yIHNvbWUgcHJvY2Vzc2luZyBpbnRlcmFjdGlvbnMgKHN1Y2ggYXMgZGF0YQ0K
PiBhZ2dyZWdhdGlvbiksIGFuZA0KPg0KDQpUaGlzIGlzIG5vdCBhIGxpbWl0YXRpb24gc3BlY2lm
aWNhbGx5IG9mIE9TQ09BUCBhcyBtb3RpdmF0ZWQgYWJvdmUuDQoNCj4gKiB3aGVuIG9uZSBvZiB0
aGUgcHJvdG9jb2xzIGlzIGEgbm9uLVJFU1RmdWwgcHJvdG9jb2wsIHN1Y2ggYXMgQkxFIG9yDQo+
TVFUVC4NCj4NCg0KDQpJIHRob3VnaHQgdGhlIHF1ZXN0aW9uIHdhcyBob3cgdG8gcHJvdGVjdCB0
aGUgUkVTVGZ1bCBvcGVyYXRpb25zLCB3aGljaA0KY2xlYXJseSBpc27igJl0IHJlbGV2YW50IHdo
ZW4gb25lIG9mIHRoZSBwcm90b2NvbHMgaXMgbm9uLVJFU1RmdWwgSi4gQW55d2F5LA0KT1NDT0FQ
IHdvcmtzIHdoZXJlIENvQVAgZG9lcywgZS5nLiBvdmVyIEJMRS4gUGxhaW4gQ09TRSB3b3JrcyBh
bnl3aGVyZQ0KKGJ1dCBkb2VzIG5vdCBwcm90ZWN0IHRoZSBSRVNUIHNlbWFudGljcykuDQoNCldl
IHdlcmUgY29uc2lkZXJpbmcgdG8gc3RhcnQgaW1wbGVtZW50aW5nIE9TQ09BUCBpbiBtYmVkIHJp
Z2h0IGFmdGVyIHRoZQ0KdXBjb21pbmcgSUVURiwgYnV0IG1heWJlIHdlIHNob3VsZCBnbyBmb3Ig
c29tZSBvdGhlciBPUyBzaW5jZSBBUk0gaXMgc28NCm5lZ2F0aXZlLiBJZiBhbnlvbmUgaXMgY29u
c2lkZXJpbmcgaW1wbGVtZW50YXRpbmcgT1NDT0FQIG9yIGhhcyBhDQpwcmVmZXJlbmNlIGZvciBh
IHBhcnRpY3VsYXIgT1MsIHBsZWFzZSBsZXQgdXMga25vdy4gKEV4aXN0aW5nDQppbXBsZW1lbnRh
dGlvbnMgSSBrbm93IG9mIGFyZSBDb250aWtpIE9TIChNYXJ0aW4gR3VubmFyc3NvbiksIEMtc2hh
cnAgKEppbQ0KU2NoYWFkKSwgUHl0aG9uIChDaHJpc3RpYW4gQW1zw7xzcyksIEphdmEgKEpvYWtp
bSBCcm9yc3Nvbi9MdWR3aWcgU2VpdHopDQphbmQgTWFsacWhYSBWdcSNaW5pxIcgaGFzIGFubm91
bmNlZCB0byBpbXBsZW1lbnQgaW4gT3BlbldTTiBiZWZvcmUgdGhlDQpzdW1tZXIuKQ0KDQpHw7Zy
YW4NCg0KDQoNCk9uIDIwMTctMDMtMDcgMTk6MzksICJUMlRSRyBvbiBiZWhhbGYgb2YgSGFubmVz
IFRzY2hvZmVuaWciDQo8dDJ0cmctYm91bmNlc0BpcnRmLm9yZyBvbiBiZWhhbGYgb2YgaGFubmVz
LnRzY2hvZmVuaWdAZ214Lm5ldD4gd3JvdGU6DQoNCj5PU0NPQVAgZG9lcyBub3Qgd29yayB3aGVu
DQo+DQo+KiB5b3UgbWl4IHByb3RvY29scywNCj4qIHVzZSBhIG1pZGRsZWJveCBmb3Igc29tZSBw
cm9jZXNzaW5nIGludGVyYWN0aW9ucyAoc3VjaCBhcyBkYXRhDQo+YWdncmVnYXRpb24pLCBhbmQN
Cj4qIHdoZW4gb25lIG9mIHRoZSBwcm90b2NvbHMgaXMgYSBub24tUkVTVGZ1bCBwcm90b2NvbCwg
c3VjaCBhcyBCTEUgb3INCj5NUVRULg0KPg0KPlVuZm9ydHVuYXRlbHksIHRoZXNlIHRoZSB1c2Ug
Y2FzZXMgd2UgYXJlIGZhY2luZyBpbiBjdXJyZW50IElvVA0KPmRlcGxveW1lbnRzLiBGb3Igc2lt
aWxhciByZWFzb25zIHdlIGNhbm5vdCB1c2UgUkZDIDgwNzUgZWl0aGVyLg0KPg0KPk1heWJlIHlv
dSBhcmUgc2VlaW5nIGRpZmZlcmVudCBkZXBsb3ltZW50IGVudmlyb25tZW50cy4NCj4NCj5DaWFv
DQo+SGFubmVzDQo+DQo+T24gMDMvMDcvMjAxNyAwNjozOSBQTSwgTWljaGFlbCBSaWNoYXJkc29u
IHdyb3RlOg0KPj4gDQo+PiBIYW5uZXMgVHNjaG9mZW5pZyA8aGFubmVzLnRzY2hvZmVuaWdAZ214
Lm5ldD4gd3JvdGU6DQo+PiAgICAgPiBOZWVkbGVzcyB0byBzYXkgdGhhdCB0aGVzZSBjaGFsbGVu
Z2VzIGhhdmUgYWxzbyBiZWVuIG9ic2VydmVkIGluDQo+Pm90aGVyDQo+PiAgICAgPiBwcm90b2Nv
bHMgYXMgd2VsbCwgc3VjaCBhcyBIVFRQIGFuZCBldmVuIFNJUC4NCj4+IA0KPj4gICAgID4gV2hh
dCBpcyB0aGUgc3RvcnkgZm9yIHByb3ZpZGluZyBhcHBsaWNhdGlvbiBsYXllciBzZWN1cml0eT8N
Cj4+IA0KPj4gT1NDT0FQIHNlZW1zIHRvIGJlIGVuZC10by1lbmQgdG8gbWUuDQo+PiANCj4+IC0t
DQo+PiBNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitJRVRGQHNhbmRlbG1hbi5jYT4sIFNhbmRlbG1h
biBTb2Z0d2FyZSBXb3Jrcw0KPj4gIC09IElQdjYgSW9UIGNvbnN1bHRpbmcgPS0NCj4+IA0KPj4g
DQo+PiANCj4NCg0K


From nobody Wed Mar  8 01:26:14 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 F1C081293F0 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 01:26:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 2fRm8FN0_2Yb for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 01:26:11 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23BD412943F for <T2TRG@irtf.org>; Wed,  8 Mar 2017 01:26:05 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MgbTj-1cwlL61Jrz-00NwmR; Wed, 08 Mar 2017 10:25:51 +0100
To: "Simpson, Robby (GE Energy Connections)" <robby.simpson@ge.com>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <24aded2f-738f-2518-ccc3-9a21eec5d879@gmx.net>
Date: Wed, 8 Mar 2017 10:25:48 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BHMRguBPPpGT81c6cjo5H5KTN3F3DnphQ"
X-Provags-ID: V03:K0:camYaTghNWcADNMVu7SmLPn8YJqnLr5K9hyShG/sGQ2uzXhLYv2 i4EqPg4QLUvnq+4fMI6rKmY9QWM0jPPqBoDwvWiZlSt1Bsqv0yZP1zod7FDT4dnpEcIs5Rm NcctGyjdEb9PAsY8KEDRAFhCDeT69nr1YzElhYLnG0DtMHVU+2nBjZxHIR9hRv7X7nC16YS IOloRxLF+3Ixo5i6+8dCA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:/DBhjjHx/jo=:NXkOu2TugW4dhSgI1SOWVj M+qLovqsU1FfooX2RRjHYsD/hd3kLq5L7HjmdpUAjG5OlW4KcdCmUGsF5fP1qz7SaQnfjwhVr zlCkUXbovFUFnZ0P63YsvXuwP/kWUYqxJCl7tynqqgAovB5xgCyx7LcnuTfpmwRItdDB31muv RSYbrKbwabUla8RTq+/sA6zAVuahQhsiWQ5HehQdbesub2vOVnmZ+magwAFR8xdxW1UhG5V9K 7w7GceUdSG0s+q/dgXy/zFAXBfjaNO77A1MmLY6ghEasOK7OjHAHy+hArusNEW8ON6I9lm5in TDQQp4Tfofx97vBdYcbPlny8GaBmkud0whU3Fjv+tj7cYTlqPFLqwEivvAMPOLyTI7LRCOjKB NBLq0EtuuBWudGWbnosEl0r2/YVLrnDXmkmLvvM9ZRsFbPwzN4bfNq7UtWmn5Ih5lrHiXVYEt qe8nGh0WtYejfzytOjF98qG9GoKQD+WMc/661ROU72ipVyuF/sUNP8Pnmov/g1J84RSuYzi3v VxGA0rhFc4I0c/sxabVaHSGtX25cBYeALVo8t+n4FNMYndFNN+N3Ln/WBzS7wpGjQ8KXPzedv Jm1ZnKjGgULWOVmxv0Qnh7aXZW38OhzFKqTIkGpUbWqG1MYl5cobktf7QWpTTFYWu2bYrfL/r lw1de69AAAU3gZ1euMyQa5GYPURYHOjLr3+OZ2HQn76uuPc8UNubatpQfLythlSEPyomLiGDA 3KkOGYY60J3O4/LMSv8d/GgAlHV9KbUV0DXfDNSuv7mN3BsW3XotVkEhfbo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/udupDIKwn2JQIJmKo3P2327mzOk>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 09:26:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--BHMRguBPPpGT81c6cjo5H5KTN3F3DnphQ
Content-Type: multipart/mixed; boundary="JrArPo6BdXBci9hNolG3ScklGq5qtwB7K";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: "Simpson, Robby (GE Energy Connections)" <robby.simpson@ge.com>,
 "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>,
 "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Message-ID: <24aded2f-738f-2518-ccc3-9a21eec5d879@gmx.net>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
 <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
 <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com>
In-Reply-To: <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com>

--JrArPo6BdXBci9hNolG3ScklGq5qtwB7K
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Thanks for the pointer to the document, Robby. I wasn't aware of this
spec and I have to gain a better understanding of why JOSE/COSE isn't
applicable but it is certainly a worthwhile path to explore.

Ciao
Hannes


On 03/07/2017 08:47 PM, Simpson, Robby (GE Energy Connections) wrote:
> Personally, I=E2=80=99m a big fan of end-to-end and think that is the c=
orrect
> approach.
>=20
> =20
>=20
> However, pragmatically, I realize this is not always possible.
>=20
> =20
>=20
> I haven=E2=80=99t followed it for a while, but there was some activity =
in
> httpbis at one point for resource/object-level security
> (https://tools.ietf.org/wg/httpbis/draft-ietf-httpbis-encryption-encodi=
ng/).=20
> If we limit the discussion to protocols that support content codings
> (e.g., HTTP and CoAP), then I would think defining a coding that
> specifies the resource-level security aspects would achieve quite a lot=

> and would be able to preserve aspects through protocol conversion.
>=20
> =20
>=20
> - Robby
>=20
> =20
>=20
> =20
>=20
> Robby Simpson, PhD
>=20
> System Architect
>=20
> GE
>=20
> Grid Solutions
>=20
> M: +1 404 219 1851
>=20
> Robby.Simpson@GE.com
>=20
> =20
>=20
> =20
>=20
> *From: *T2TRG <t2trg-bounces@irtf.org> on behalf of "Kovatsch, Matthias=
"
> <matthias.kovatsch@siemens.com>
> *Date: *Tuesday, March 7, 2017 at 2:36 PM
> *To: *"hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>,
> "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
> *Cc: *"T2TRG@irtf.org" <T2TRG@irtf.org>
> *Subject: *EXT: Re: [T2TRG] RESTful Design & Security
>=20
> =20
>=20
> Fair enough.
>=20
> Yes, I am on this IoT Directorate. I would say a large fraction of the
> T2TRG participants has been arguing that the Internet of Gateways is no=
t
> a good approach. Your security-related summary proves this point.
>=20
> I personally don't see end-to-end security happening if we keep mixing
> application protocols, keep using black-magic middleboxes, and keep
> using proprietary interfaces at the device level. We need something
> end-to-end (or T2T) for end-to-end security.
>=20
> Best wishes
> Matthias
>=20
>=20
>=20
> Sent from my phone, limitations might apply.
>=20
> -----Original Message-----
> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
> *Received:* Tuesday, 07 Mar 2017, 20:10
> *To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
> [matthias.kovatsch@siemens.com]; mcr+ietf@sandelman.ca
> [mcr+ietf@sandelman.ca]
> *CC:* T2TRG@irtf.org [T2TRG@irtf.org]
> *Subject:* Re: [T2TRG] RESTful Design & Security
>=20
> Hi Matthias,
>=20
> I know that this is a research group and everyone can create whatever
> they want.
>=20
> We briefly talked about security at the IoT directorate conference call=

> and I would be interesting to hear what works and what does not work fo=
r
> others.
>=20
> Ciao
> Hannes
>=20
>=20
> On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
>> On big propaganda tour? :P
>>=20
>> Regards
>> Matthias
>>=20
>>=20
>> Sent from my phone, limitations might apply.
>>=20
>> -----Original Message-----
>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>> *Received:* Tuesday, 07 Mar 2017, 19:39
>> *To:* Michael Richardson [mcr+ietf@sandelman.ca]
>> *CC:* t2trg@irtf.org [T2TRG@irtf.org]
>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>=20
>> OSCOAP does not work when
>>=20
>> * you mix protocols,
>> * use a middlebox for some processing interactions (such as data
>> aggregation), and
>> * when one of the protocols is a non-RESTful protocol, such as BLE or =
MQTT.
>>=20
>> Unfortunately, these the use cases we are facing in current IoT
>> deployments. For similar reasons we cannot use RFC 8075 either.
>>=20
>> Maybe you are seeing different deployment environments.
>>=20
>> Ciao
>> Hannes
>>=20
>> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>>=20
>>> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>>     > Needless to say that these challenges have also been observed i=
n other
>>>     > protocols as well, such as HTTP and even SIP.
>>>=20
>>>     > What is the story for providing application layer security?
>>>=20
>>> OSCOAP seems to be end-to-end to me.
>>>=20
>>> --
>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>>  -=3D IPv6 IoT consulting =3D-
>>>=20
>>>=20
>>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> T2TRG mailing list
>> T2TRG@irtf.org
>> https://www.irtf.org/mailman/listinfo/t2trg
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.irtf.org_ma=
ilman_listinfo_t2trg&d=3DDwMF-g&c=3DIV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLr=
DQYWSI&r=3D4w13vdCVEUj_vaCSQNdKRf25O0P4iaVn04ElXLrB_ak&m=3Dk7IqC4lOSBeG5y=
ZT3lwAYgfq7isPTJ1x7lhosU4sI0U&s=3D6FyGiDTW-U31FpvuMwpkVdhppH4XLcvlAPPiMqv=
TUIo&e=3D>
>>=20
>=20


--JrArPo6BdXBci9hNolG3ScklGq5qtwB7K--

--BHMRguBPPpGT81c6cjo5H5KTN3F3DnphQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYv84dAAoJEGhJURNOOiAtQfwH/2qgT042/yM9bJI2pUj0RUIl
WEaBD8qs7hg2i5221OlhSYppvSXuSIcNLXJY5/kJ/XQe1wNe0Nx5n0vSF4auAonV
f0nBjHwtcQDgxbAwHtnjCWoV9dTv6p91kjMSZbFGQMvmSahUagp5j7xYBswB8xIL
90fDbBPEZBchenlepl1kEBCkbp2MI144dSaAeZq3lGox0a3ri0mJPI3BXpbH1sn5
SpQjLfqRLaDsyDtw0H0htYDyL0rygfEwZ/eKYe1magnSKR3B4oRNPcscIjivmxoh
tVJ/tNgMVGIb63QmaTOVvcfMTqxcEPBAy/F0Ts4dBvUJKVaNSSucR+YHBvoKs9U=
=PKHM
-----END PGP SIGNATURE-----

--BHMRguBPPpGT81c6cjo5H5KTN3F3DnphQ--


From nobody Wed Mar  8 01:44:16 2017
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 F0DA912943F for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 01:44:14 -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=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 goY2Sux6TcmF for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 01:44:14 -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 AA023129431 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 01:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v289h5pQ027289; Wed, 8 Mar 2017 10:43:05 +0100 (CET)
Received: from eduroam-cart-clients-173.wlan.uni-bremen.de (eduroam-cart-clients-173.wlan.uni-bremen.de [134.102.145.173]) (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 3vdT9533mtzDJ1q; Wed,  8 Mar 2017 10:43:05 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <24aded2f-738f-2518-ccc3-9a21eec5d879@gmx.net>
Date: Wed, 8 Mar 2017 10:43:04 +0100
X-Mao-Original-Outgoing-Id: 510658984.289594-e0c2c7061e560aa2d98161f00a560cae
Content-Transfer-Encoding: quoted-printable
Message-Id: <BFB2C8F0-0E60-4560-8FC8-761F46CB1A89@tzi.org>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <0216378E-8976-4D4E-A307-AEE5FD00BDA6@GE.com> <24aded2f-738f-2518-ccc3-9a21eec5d879@gmx.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/g4cRWX2FabcnIQrscPXCUItoTE0>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "Simpson, Robby \(GE Energy Connections\)" <robby.simpson@ge.com>, "T2TRG@irtf.org" <T2TRG@irtf.org>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 09:44:15 -0000

On 8 Mar 2017, at 10:25, Hannes Tschofenig <hannes.tschofenig@gmx.net> =
wrote:
>=20
> why JOSE/COSE isn=E2=80=99t applicable

JOSE/COSE is generally applicable to the problem space.

The specific draft mentioned additionally undertakes to do some =
streaming integrity, where partially delivered messages can already be =
authenticated as such.  Compare the ongoing discussion of block-wise =
transfer for OSCOAP.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  8 01:59:41 2017
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 3403012944F for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 01:59:39 -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=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 VGpy9ZICFaSf for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 01:59:37 -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 7314812943F for <T2TRG@irtf.org>; Wed,  8 Mar 2017 01:59:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v289xX0k013161; Wed, 8 Mar 2017 10:59:33 +0100 (CET)
Received: from eduroam-cart-clients-173.wlan.uni-bremen.de (eduroam-cart-clients-173.wlan.uni-bremen.de [134.102.145.173]) (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 3vdTX55XtRzDJ2P; Wed,  8 Mar 2017 10:59:33 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
Date: Wed, 8 Mar 2017 10:59:33 +0100
X-Mao-Original-Outgoing-Id: 510659973.046975-67c8683569ac0463f9f9ee0684521a3e
Content-Transfer-Encoding: quoted-printable
Message-Id: <90526DF1-4620-4C0B-AE5D-17543D54861D@tzi.org>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/I4N91TzQ3pGQ23rZ94Wa6w_E_qE>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 09:59:39 -0000

On 6 Mar 2017, at 17:59, Hannes Tschofenig <hannes.tschofenig@gmx.net> =
wrote:
>=20
> =46rom the web we know that TLS goes very well with RESTful designs.

HTTPS works well as long as your security is binary: You switch it off =
or you switch it on; there are no different security requirements for =
different applications.  With this restriction, you can encode =
=E2=80=9Csecurity=3Don=E2=80=9D in the URI (here: by choosing a =
different URI scheme, which unfortunately has other side effects).  (The =
disadvantages of coloring all cases with the same brush are also well =
known in the Big Web; I=E2=80=99m not discussing this here.  EV certs =
are a weird way to try escaping this restriction, but aren=E2=80=99t =
generally applicable to REST applications.)

It is well understood that we currently don=E2=80=99t have a good way to =
associate more extensive security information with a URI when that is =
required.  This comes up again and again (say, =
https://github.com/core-wg/oscoap/issues/41).  Is augmenting the URI by =
other information as in link-format the right way to do this in a more =
general scope?  This is an interesting subject for discussion.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  8 02:02:54 2017
Return-Path: <lear@cisco.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 EDB2912945E for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 zkpr_pBhsJ55 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:02:50 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1B7912944F for <T2TRG@irtf.org>; Wed,  8 Mar 2017 02:02:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13864; q=dns/txt; s=iport; t=1488967370; x=1490176970; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=OHKInk2L+JK8MAW5BfNXw4Q/BqaLQZldjEeBCCmTWgk=; b=Hkkj8JAFVrXQmELmeM1xgL++Ywg+mFECNpHPxmwcGsl7aSW2H6Up1GLX HkWKXqRGC9giikKsIDtAhc53qDglnJgYTz5IAwerkjWokI7IsVPzvbYyE ZHXf6evgUUEOtGetXOBN7keBTBQGYGE4e37p1Xidouv17+q9nFhgcJGl6 M=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AMCQB/1b9Y/xbLJq1UCRkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJugUQDJ2CDYIoMc5A5H5ALhS2CDR8BCoJCgzYCgnMYAQIBAQE?= =?us-ascii?q?BAQEBayiFFQEBAQQBASEKOwYLDAQJAhUCASoCAicoCAYBDAYCAQGJYwMVDpIwn?= =?us-ascii?q?VmCJiuKUwEBAQEBAQEBAQEBAQEBAQEBAQEBAQ4KBYhTCIJiglGBXIMtgl8FlXi?= =?us-ascii?q?GO4N4ggmMN4pOhlGTPR84gQMiFQgXFT+GVT81ihMBAQE?=
X-IronPort-AV: E=Sophos;i="5.36,262,1486425600";  d="asc'?scan'208,217";a="653103522"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2017 10:02:47 +0000
Received: from [10.61.255.19] ([10.61.255.19]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v28A2k86027867; Wed, 8 Mar 2017 10:02:47 GMT
To: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>
Date: Wed, 8 Mar 2017 11:02:45 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pAtqxFEcAmPSO1vvvwnWJEIhII0WTCp5M"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/VAx39_WyCx5jQ_HpdlblUY4N5bY>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 10:02:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pAtqxFEcAmPSO1vvvwnWJEIhII0WTCp5M
Content-Type: multipart/mixed; boundary="2DqbIeVOKOPqnRqtpIPdTx8TA1JjB7D0n";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>,
 "hannes.tschofenig@gmx.net" <hannes.tschofenig@gmx.net>,
 "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Message-ID: <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
 <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
In-Reply-To: <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>

--2DqbIeVOKOPqnRqtpIPdTx8TA1JjB7D0n
Content-Type: multipart/alternative;
 boundary="------------5D7DDA8B15646D0A2893E331"

This is a multi-part message in MIME format.
--------------5D7DDA8B15646D0A2893E331
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Matthias,

I think the key question that everyone seems to be dancing around is this=
:

What is an Internet host in the context of IoT?  What are the minimum
qualities it must possess?  I don't mean this to be a vote, but more of
a law of physics sort of thing.  For instance, does a host have a secure
unique identity?  What capabilities must it have?  I would expect them
to be very few, but there are assuredly some...

Eliot


On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
> Fair enough.
>
> Yes, I am on this IoT Directorate. I would say a large fraction of the
> T2TRG participants has been arguing that the Internet of Gateways is
> not a good approach. Your security-related summary proves this point.
>
> I personally don't see end-to-end security happening if we keep mixing
> application protocols, keep using black-magic middleboxes, and keep
> using proprietary interfaces at the device level. We need something
> end-to-end (or T2T) for end-to-end security.
>
> Best wishes
> Matthias
>
>
>
> Sent from my phone, limitations might apply.
>
> -----Original Message-----
> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
> *Received:* Tuesday, 07 Mar 2017, 20:10
> *To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
> [matthias.kovatsch@siemens.com]; mcr+ietf@sandelman.ca
> [mcr+ietf@sandelman.ca]
> *CC:* T2TRG@irtf.org [T2TRG@irtf.org]
> *Subject:* Re: [T2TRG] RESTful Design & Security
>
> Hi Matthias,
>
> I know that this is a research group and everyone can create whatever
> they want.
>
> We briefly talked about security at the IoT directorate conference call=

> and I would be interesting to hear what works and what does not work fo=
r
> others.
>
> Ciao
> Hannes
>
>
> On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
> > On big propaganda tour? :P
> >
> > Regards
> > Matthias
> >
> >
> > Sent from my phone, limitations might apply.
> >
> > -----Original Message-----
> > *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
> > *Received:* Tuesday, 07 Mar 2017, 19:39
> > *To:* Michael Richardson [mcr+ietf@sandelman.ca]
> > *CC:* t2trg@irtf.org [T2TRG@irtf.org]
> > *Subject:* Re: [T2TRG] RESTful Design & Security
> >
> > OSCOAP does not work when
> >
> > * you mix protocols,
> > * use a middlebox for some processing interactions (such as data
> > aggregation), and
> > * when one of the protocols is a non-RESTful protocol, such as BLE
> or MQTT.
> >
> > Unfortunately, these the use cases we are facing in current IoT
> > deployments. For similar reasons we cannot use RFC 8075 either.
> >
> > Maybe you are seeing different deployment environments.
> >
> > Ciao
> > Hannes
> >
> > On 03/07/2017 06:39 PM, Michael Richardson wrote:
> >>
> >> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
> >>     > Needless to say that these challenges have also been observed
> in other
> >>     > protocols as well, such as HTTP and even SIP.
> >>
> >>     > What is the story for providing application layer security?
> >>
> >> OSCOAP seems to be end-to-end to me.
> >>
> >> --
> >> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=

> >>  -=3D IPv6 IoT consulting =3D-
> >>
> >>
> >>
> >
> >
> >
> > _______________________________________________
> > T2TRG mailing list
> > T2TRG@irtf.org
> > https://www.irtf.org/mailman/listinfo/t2trg
> >
>
>
>
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg


--------------5D7DDA8B15646D0A2893E331
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Matthias,</p>
    <p>I think the key question that everyone seems to be dancing around
      is this:</p>
    <p>What is an Internet host in the context of IoT?=C2=A0 What are the=

      minimum qualities it must possess?=C2=A0 I don't mean this to be a
      vote, but more of a law of physics sort of thing.=C2=A0 For instanc=
e,
      does a host have a secure unique identity?=C2=A0 What capabilities =
must
      it have?=C2=A0 I would expect them to be very few, but there are
      assuredly some...</p>
    <p>Eliot<br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">On 3/7/17 8:36 PM, Kovatsch, Matthias
      wrote:<br>
    </div>
    <blockquote
cite=3D"mid:4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902=
=2Esiemens.net"
      type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8">
      <meta name=3D"Generator" content=3D"Microsoft Exchange Server">
      <!-- converted from text -->
      <style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; bord=
er-left: #800000 2px solid; } --></style>
      <div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:11pt; color:black">
        <span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif;
          font-size:11pt; color:black">Fair enough.<br>
          <br>
          Yes, I am on this IoT Directorate. I would say a large
          fraction of the T2TRG participants has been arguing that the
          Internet of Gateways is not a good approach. Your
          security-related summary proves this point.<br>
          <br>
          I personally don't see end-to-end security happening if we
          keep mixing application protocols, keep using black-magic
          middleboxes, and keep using proprietary interfaces at the
          device level. We need something end-to-end (or T2T) for
          end-to-end security.<br>
          <br>
          Best wishes<br>
          Matthias <br>
          <br>
          <br>
          <br>
          Sent from my phone, limitations might apply.<br>
          <br>
          <span style=3D"color:black">-----Original Message----- <br>
            <b>From:</b> Hannes Tschofenig [<a class=3D"moz-txt-link-abbr=
eviated" href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.=
net</a>]<br>
            <b>Received:</b> Tuesday, 07 Mar 2017, 20:10<br>
            <b>To:</b> Kovatsch, Matthias (CT RDA NEC EMB-DE)
            [<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:matthia=
s.kovatsch@siemens.com">matthias.kovatsch@siemens.com</a>]; <a class=3D"m=
oz-txt-link-abbreviated" href=3D"mailto:mcr+ietf@sandelman.ca">mcr+ietf@s=
andelman.ca</a>
            [<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:mcr+iet=
f@sandelman.ca">mcr+ietf@sandelman.ca</a>]<br>
            <b>CC:</b> <a class=3D"moz-txt-link-abbreviated" href=3D"mail=
to:T2TRG@irtf.org">T2TRG@irtf.org</a> [<a class=3D"moz-txt-link-abbreviat=
ed" href=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>]<br>
            <b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security<br>=

            <br>
          </span></span></div>
      <font size=3D"2"><span style=3D"font-size:10pt;">
          <div class=3D"PlainText">Hi Matthias,<br>
            <br>
            I know that this is a research group and everyone can create
            whatever<br>
            they want.<br>
            <br>
            We briefly talked about security at the IoT directorate
            conference call<br>
            and I would be interesting to hear what works and what does
            not work for<br>
            others.<br>
            <br>
            Ciao<br>
            Hannes<br>
            <br>
            <br>
            On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:<br>
            &gt; On big propaganda tour? :P<br>
            &gt; <br>
            &gt; Regards<br>
            &gt; Matthias<br>
            &gt; <br>
            &gt; <br>
            &gt; Sent from my phone, limitations might apply.<br>
            &gt; <br>
            &gt; -----Original Message-----<br>
            &gt; *From:* Hannes Tschofenig [<a class=3D"moz-txt-link-abbr=
eviated" href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.=
net</a>]<br>
            &gt; *Received:* Tuesday, 07 Mar 2017, 19:39<br>
            &gt; *To:* Michael Richardson [<a class=3D"moz-txt-link-abbre=
viated" href=3D"mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>]<=
br>
            &gt; *CC:* <a class=3D"moz-txt-link-abbreviated" href=3D"mail=
to:t2trg@irtf.org">t2trg@irtf.org</a> [<a class=3D"moz-txt-link-abbreviat=
ed" href=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>]<br>
            &gt; *Subject:* Re: [T2TRG] RESTful Design &amp; Security<br>=

            &gt; <br>
            &gt; OSCOAP does not work when<br>
            &gt; <br>
            &gt; * you mix protocols,<br>
            &gt; * use a middlebox for some processing interactions
            (such as data<br>
            &gt; aggregation), and<br>
            &gt; * when one of the protocols is a non-RESTful protocol,
            such as BLE or MQTT.<br>
            &gt; <br>
            &gt; Unfortunately, these the use cases we are facing in
            current IoT<br>
            &gt; deployments. For similar reasons we cannot use RFC 8075
            either.<br>
            &gt; <br>
            &gt; Maybe you are seeing different deployment environments.<=
br>
            &gt; <br>
            &gt; Ciao<br>
            &gt; Hannes<br>
            &gt; <br>
            &gt; On 03/07/2017 06:39 PM, Michael Richardson wrote:<br>
            &gt;&gt; <br>
            &gt;&gt; Hannes Tschofenig <a class=3D"moz-txt-link-rfc2396E"=
 href=3D"mailto:hannes.tschofenig@gmx.net">&lt;hannes.tschofenig@gmx.net&=
gt;</a>
            wrote:<br>
            &gt;&gt;=C2=A0=C2=A0=C2=A0=C2=A0 &gt; Needless to say that th=
ese challenges have
            also been observed in other<br>
            &gt;&gt;=C2=A0=C2=A0=C2=A0=C2=A0 &gt; protocols as well, such=
 as HTTP and even
            SIP.<br>
            &gt;&gt; <br>
            &gt;&gt;=C2=A0=C2=A0=C2=A0=C2=A0 &gt; What is the story for p=
roviding
            application layer security?<br>
            &gt;&gt; <br>
            &gt;&gt; OSCOAP seems to be end-to-end to me.<br>
            &gt;&gt; <br>
            &gt;&gt; --<br>
            &gt;&gt; Michael Richardson <a class=3D"moz-txt-link-rfc2396E=
" href=3D"mailto:mcr+IETF@sandelman.ca">&lt;mcr+IETF@sandelman.ca&gt;</a>=
,
            Sandelman Software Works<br>
            &gt;&gt;=C2=A0 -=3D IPv6 IoT consulting =3D-<br>
            &gt;&gt; <br>
            &gt;&gt; <br>
            &gt;&gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; <br>
            &gt; _______________________________________________<br>
            &gt; T2TRG mailing list<br>
            &gt; <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2T=
RG@irtf.org">T2TRG@irtf.org</a><br>
            &gt; <a moz-do-not-send=3D"true"
              href=3D"https://www.irtf.org/mailman/listinfo/t2trg">https:=
//www.irtf.org/mailman/listinfo/t2trg</a><br>
            &gt; <br>
            <br>
          </div>
        </span></font>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
T2TRG mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2TR=
G@irtf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.irtf.org/mailman/l=
istinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------5D7DDA8B15646D0A2893E331--

--2DqbIeVOKOPqnRqtpIPdTx8TA1JjB7D0n--

--pAtqxFEcAmPSO1vvvwnWJEIhII0WTCp5M
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJYv9bGAAoJEIe2a0bZ0noz+tcH/02toftlen9Kx8/5UO6bikxX
iezgTN0+WF4Jwu3HGhHyFkJf9WXdVbWtxGFpxK7qfaZ1W9DRkUzm+Z0JtP7gSw0a
K4SIXiicbj1d7JLo/Uvhz8nN2HTTeVlDuiSN3Onp/H0TuCtcCYwH1ypFM+0IOnAx
EAzgriJR7zwG99YcSHCwu0aLMux6LEzkUwa/O3JPWvq9WFcyxoZGjUjNTJKVmQHK
XvVDh2qQo1GkbSXJj71eH1I6vX9vAlqmRd7j04JJXPHBms87nXhSR9fUa9xl3xmq
+MlsZiklGGxwO89hks3E3JBtmaG4X+ib3wAIhUdftAA6+cIHioUBg5Ar/jd1yTk=
=AivH
-----END PGP SIGNATURE-----

--pAtqxFEcAmPSO1vvvwnWJEIhII0WTCp5M--


From nobody Wed Mar  8 02:09:08 2017
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 5D290129571 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:09:06 -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=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 wGdD4JzRQXBH for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:09:00 -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 71FEB127071 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 02:09:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v28A8tXY022850; Wed, 8 Mar 2017 11:08:55 +0100 (CET)
Received: from eduroam-cart-clients-173.wlan.uni-bremen.de (eduroam-cart-clients-173.wlan.uni-bremen.de [134.102.145.173]) (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 3vdTkv2jhkzDJ2g; Wed,  8 Mar 2017 11:08:55 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <D4E5582E.78797%goran.selander@ericsson.com>
Date: Wed, 8 Mar 2017 11:08:54 +0100
X-Mao-Original-Outgoing-Id: 510660534.395416-ced280a27a377af5c82020bdceb53174
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE24E6F2-4B93-4507-AD43-E490B81B7E66@tzi.org>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <D4E5582E.78797%goran.selander@ericsson.com>
To: =?utf-8?Q?G=C3=B6ran_Selander?= <goran.selander@ericsson.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/sIjS7gAabA0nquAn_DAnAlsPeIE>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 10:09:06 -0000

On 8 Mar 2017, at 09:30, G=C3=B6ran Selander =
<goran.selander@ericsson.com> wrote:
>=20
> 1. Apply security above the web transfer layer, i.e. to CoAP/HTTP =
payload,
> e.g. by wrapping the payload in the COSE format. In this case the =
secure
> COSE object is independent of web transfer mechanism so you can switch
> between e.g. HTTP and CoAP. However, the web transfer metadata, =
including
> e.g. the RESTful method, resource etc. is not protected. This is =
anyway
> useful if the method/resource etc. is implicit or the application =
provides
> the context, e.g. CoAP pub/sub.

Apart from the HTTPS straightjacket I just discussed, this is the other =
interesting design issue about RESTful security.

Should we design all objects being interchanged in such a way that they =
can be signed by themselves, which implies that they don=E2=80=99t need =
context to interpret them?

E.g., if I

GET coap://bathroom.cabo.space/temperature

a typical result in a REST world might be a CBOR or JSON object saying

[{"u":"Cel","v":23.125}]

But there is no point in signing that object by itself; it does not mean =
anything useful.

A signed object would need to include the fact that this is about my =
bathroom, and some freshness information (such as the current time).  If =
you don=E2=80=99t want to use absolute time for freshness, you would =
include a request nonce, which makes this object useless for a different =
request, so you might as well bind it to the request in other ways =
(e.g., include the URI instead of some generic semantic information =
tying this to my bathroom).

The OSCOAP approach is to simply bind responses to the relevant =
information in the request, so all this happens =E2=80=9Cautomatically=E2=80=
=9D (you wish).

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar  8 02:17:56 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 DF12D129466 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 Ga0YVSEAqwdE for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:17:52 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C1961293D8 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 02:17:51 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MRjd7-1crqBT3KDB-00SwNd; Wed, 08 Mar 2017 11:17:43 +0100
To: =?UTF-8?Q?G=c3=b6ran_Selander?= <goran.selander@ericsson.com>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <D4E5582E.78797%goran.selander@ericsson.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net>
Date: Wed, 8 Mar 2017 11:17:39 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <D4E5582E.78797%goran.selander@ericsson.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="1CsoP06rTijdAvDFWntsTwmn8fM13uFjv"
X-Provags-ID: V03:K0:PU5uLGiiFKepb05+K5YYg03kmMUiAjCfwqUdAx/RL6pOdVIaodC rp3gb1Aj4T1nBgCYspqlFSopXUNZgYYQ42rjbhWSdJDFz24MB5upniPdqIj0vZxLFKYyo7t I5agmcTzYBU1zf+onCBuuGiIpL0OgZRo4y0aEQYKYMj/5wNigdSpu1BpR6MZiZx/YbfcdMj YeiK/kmMdFYGfqyhryujg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:UD0Vvz+i/tY=:dqKonnaf2WWZ0pjmW3I4xP JxL203d0u1oYvq7qCnU8i9MmHARXt4JnQqtsVz5K6KuagGz7+ChLBEZZKUGX4ZjVzEusimWe5 bYNz6eelXYzpaY59BwT8UeV4U+kxt7EYMnJpY+rhC54jSqnAc/leNbViz35S0pEJJmmFPEtBh bAdiT8eWZRPRimmhiRq4OqHdSzEw0zBq1t4VXzqAfWO2XP6NPx1JcSrnUDK3rTKQfZ7PNeNZM uPBQf9g5B0BX7OQbujAwmERU+CCm98dB8WQJ6IV9Rs16utaNwD3sZMHWt8mHDSDf6gsnzmHsY NjinSLUoxLq8FVu3AhGNRUEzdKBNCZUvfqiDs5w67YU6B92Lej35p2uCOYJlvaOuSSvZw4GTv PzZ+vYzdNXJo9GkLu/5ZKOg/reYx8b8RJs5zc44zdfC8uAkDkYSm+FCnjNeUKO6kFyHUgX9mB Up0brb94r2DlM0tPfHPOu/66JLYPDr5pWxITiKMm8P+z7Jj1iQtI/jiLNIqhT8DBMBybNsH/Z ajqTuNsW6K0rB3eODZeqsZrbhqa2hcUalNBtAD1CFfQJVQwf1DU9ce1DyJrWztU2F91ncXqfi gidMHjKtCSf1p0GkD9WV0rHOAYuOC/4kDnrZM2eYyAUSm5c8Wa3gOLOxB+BcF27MkbGwqaBMh 6alxX+9w8af+jdT7us+qZgv0ROPaQBpq5GEW3P6mjoxTsXXSJ29z1J8b3siUyXjnlb1NbKyOB y8Utn+c4e8jdBaFtswfwy4BI8UDedeXzybSh71Vfgbx6yrBdqvSeYgXLPYE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/96tf4Ga0CadMzA3PeqkJYIMzGc4>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 10:17:56 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--1CsoP06rTijdAvDFWntsTwmn8fM13uFjv
Content-Type: multipart/mixed; boundary="Se6bS3GWRtNBGAoQK6rTiipriEnLuawHx";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: =?UTF-8?Q?G=c3=b6ran_Selander?= <goran.selander@ericsson.com>,
 Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Message-ID: <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <D4E5582E.78797%goran.selander@ericsson.com>
In-Reply-To: <D4E5582E.78797%goran.selander@ericsson.com>

--Se6bS3GWRtNBGAoQK6rTiipriEnLuawHx
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Goeran,

as you have seen that Michael asked me about OSCOAP; I didn't want to go
there.

I had initially planned to provide a response addressing each of your
points but I guess it is time for me to realize that you do not care
about the challenges we encounter in our deployments.

Ciao
Hannes

On 03/08/2017 09:30 AM, G=C3=B6ran Selander wrote:
> Hi Hannes, and all,
>=20
> Since Hannes is so eager to state what he thinks OSCOAP doesn=E2=80=99t=
 work for
> (which we all understand is the reason for starting this thread in the
> first place J), allow me to balance this by outlining the end-to-end
> security settings where people plan to use OSCOAP so far.
>=20
> But first the story about application layer security, REST and
> intermediary nodes (which was the question asked):
>=20
> If the intermediary is required to perform operations on encrypted data=

> (such as data aggregation by non-trusted intermediary), there are
> techniques such as homomorphic encryption, but the application in the
> cloud would in this case anyway have to trust the intermediary to perfo=
rm
> the required operation since the integrity of the message would not be
> preserved. Clearly, this is not a limitation specifically of OSCOAP.
>=20
> The type of operations you can expect an intermediary to perform and st=
ill
> preserve integrity end-to-end is more like the support for RESTful
> operations performed by a CoAP proxy - the proxy reads CoAP meta-data a=
nd
> performs various message-related operations. If you apply security on
> transport layer or below (DTLS, IPsec etc.) then the CoAP meta-data is
> only visible to the trusted endpoint for the secure channel, which eith=
er
> makes it useless for the intermediary or makes the intermediary a trust=
ed
> endpoint. If you apply security on application layer then it is possibl=
e
> for an intermediary to perform these operations while preserving
> integrity. There are two options:
>=20
> 1. Apply security above the web transfer layer, i.e. to CoAP/HTTP paylo=
ad,
> e.g. by wrapping the payload in the COSE format. In this case the secur=
e
> COSE object is independent of web transfer mechanism so you can switch
> between e.g. HTTP and CoAP. However, the web transfer metadata, includi=
ng
> e.g. the RESTful method, resource etc. is not protected. This is anyway=

> useful if the method/resource etc. is implicit or the application provi=
des
> the context, e.g. CoAP pub/sub.
>=20
> 2. Apply security to the web transfer layer, i.e. protect not only CoAP=

> payload but also CoAP meta data (headers and options) in such a way tha=
t
> certain CoAP proxy operations can still be performed (e.g. only integri=
ty
> protecting the RESTful method allowing the proxy to read but not change=
).
> This is what OSCOAP does.
>=20
> The reasons why people are interested in OSCOAP, besides end-to-end
> security and support for CoAP proxy operations which is e.g. used in
> 6tisch secure join, include:
>=20
> - OSCOAP works essentially wherever CoAP works (UDP, TCP, SMS, BLE,
> 802.15.4 IE,  . . .) and provides end-to-end security independently of =
how
> the underlying layers are being switched along the path.
> =20
>=20
> - OSCOAP is possible to extended to secure CoAP over multicast IP (or C=
oAP
> group communication in general RFC7390):
> https://tools.ietf.org/html/draft-tiloca-core-multicast-oscoap
>=20
> - OSCOAP is very lightweight. Recent optimisations to be published by t=
he
> IETF submission cutoff shrink the message overhead down to 13 bytes in =
the
> CoAP request and 9 bytes in the OSCOAP response. This includes the 8 by=
tes
> MAC. With existing CoAP and COSE implementation, OSCOAP is a minor
> addition in terms of code.
>=20
>=20
> Now for the statements made about OSCOAP:
>=20
>> OSCOAP does not work when
>> * you mix protocols,
>=20
> for general web transfer protocols this either requires protection on a=

> lower layer, which prevents an intermediary from reading the metadata a=
s
> we have seen, or you can restrict protection to CoAP/HTTP payload as in=
 1.
> above. But if you consider specific protocols with similar semantics su=
ch
> as HTTP and CoAP, it is possible to define a mapping for a subset of th=
e
> metadata for which OSCOAP would preserve integrity and confidentiality
> along the lines elaborated by Matthias in this thread. We started
> sketching on this during IETF94 (with some of the authors of RFC8075) b=
ut
> have not had time to continue the work. We are happy to pursue this wor=
k
> if people think this is interesting.
>=20
>> * use a middlebox for some processing interactions (such as data
>> aggregation), and
>>
>=20
> This is not a limitation specifically of OSCOAP as motivated above.
>=20
>> * when one of the protocols is a non-RESTful protocol, such as BLE or
>> MQTT.
>>
>=20
>=20
> I thought the question was how to protect the RESTful operations, which=

> clearly isn=E2=80=99t relevant when one of the protocols is non-RESTful=
 J. Anyway,
> OSCOAP works where CoAP does, e.g. over BLE. Plain COSE works anywhere
> (but does not protect the REST semantics).
>=20
> We were considering to start implementing OSCOAP in mbed right after th=
e
> upcoming IETF, but maybe we should go for some other OS since ARM is so=

> negative. If anyone is considering implementating OSCOAP or has a
> preference for a particular OS, please let us know. (Existing
> implementations I know of are Contiki OS (Martin Gunnarsson), C-sharp (=
Jim
> Schaad), Python (Christian Ams=C3=BCss), Java (Joakim Brorsson/Ludwig S=
eitz)
> and Mali=C5=A1a Vu=C4=8Dini=C4=87 has announced to implement in OpenWSN=
 before the
> summer.)
>=20
> G=C3=B6ran
>=20
>=20
>=20
> On 2017-03-07 19:39, "T2TRG on behalf of Hannes Tschofenig"
> <t2trg-bounces@irtf.org on behalf of hannes.tschofenig@gmx.net> wrote:
>=20
>> OSCOAP does not work when
>>
>> * you mix protocols,
>> * use a middlebox for some processing interactions (such as data
>> aggregation), and
>> * when one of the protocols is a non-RESTful protocol, such as BLE or
>> MQTT.
>>
>> Unfortunately, these the use cases we are facing in current IoT
>> deployments. For similar reasons we cannot use RFC 8075 either.
>>
>> Maybe you are seeing different deployment environments.
>>
>> Ciao
>> Hannes
>>
>> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>>
>>> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>>     > Needless to say that these challenges have also been observed i=
n
>>> other
>>>     > protocols as well, such as HTTP and even SIP.
>>>
>>>     > What is the story for providing application layer security?
>>>
>>> OSCOAP seems to be end-to-end to me.
>>>
>>> --
>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>>  -=3D IPv6 IoT consulting =3D-
>>>
>>>
>>>
>>
>=20


--Se6bS3GWRtNBGAoQK6rTiipriEnLuawHx--

--1CsoP06rTijdAvDFWntsTwmn8fM13uFjv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYv9pEAAoJEGhJURNOOiAt6+cH/0bX4oq44FajvQiV+XoS3M7d
Mj1b9tMwonnaqL6JSQtw3LmdZiYOMeuxOduWOQpFv1AA6f6LB4tJlKPQL1lLM/E0
8kjYfh56hohWLr+6RngIOEccjS4k4cadFFVEHxiMs/I8d7/6UGZJmd/jV6VH64D+
OhgKh6gbMG4o1tCIeLBlg2eSqZgVlgLVmrYSkxZYVwmL7lP0Ew2j5z5vcXZ8han5
j4PSFg05RDEny6l2+D+7spiSdkbJjDFpZgjadngxiaZvMObGYRV9Copd5+Dwgbpx
A9cA0XwcNZzWi2q6tN5gKbU3tzMB+eJzoOKFOXtQHvU4ochr9O6JRMI213P/TjI=
=FG4g
-----END PGP SIGNATURE-----

--1CsoP06rTijdAvDFWntsTwmn8fM13uFjv--


From nobody Wed Mar  8 02:31:07 2017
Return-Path: <goran.selander@ericsson.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 E3A7712944F for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:31:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 0MFKFofGCxhI for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 02:31:03 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 95856127071 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 02:31:03 -0800 (PST)
X-AuditID: c1b4fb3a-29b639800000484c-28-58bfdd6526a3
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 46.2E.18508.56DDFB85; Wed,  8 Mar 2017 11:31:01 +0100 (CET)
Received: from ESESSMB107.ericsson.se ([169.254.7.76]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0319.002; Wed, 8 Mar 2017 11:31:00 +0100
From: =?utf-8?B?R8O2cmFuIFNlbGFuZGVy?= <goran.selander@ericsson.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpsnFV1UjpOgG0yLh2UXCglOtqGJlY0AgAAQwQCAAPj4gIAADS2AgAAUfAA=
Date: Wed, 8 Mar 2017 10:31:00 +0000
Message-ID: <D4E599A4.7891E%goran.selander@ericsson.com>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <D4E5582E.78797%goran.selander@ericsson.com> <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net>
In-Reply-To: <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-ID: <47CBF9E48B02A84E9C54BEC35FA41110@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFIsWRmVeSWpSXmKPExsUyM2K7vW7q3f0RBkfPClss3XmP1aLnUD+7 xfsHPSwOzB6LN+1n85i88TCbR8ucPcwBzFFcNimpOZllqUX6dglcGVPnvGUtaGGrOLHxC3MD 4wfWLkZODgkBE4kHT3+zdTFycQgJrGOU+DuhgwXCWcQo0XLwHzNIFZuAi8SDhkdMILaIQLzE lL+nWEBsZgFViamH7oHZwgJ6Eltm7GWFqNGXOHmqhw3C9pNYMfs6WA2LgIpE99slYHFeAQuJ qc9/Qm3+wigx8dN1sASngLXE0U07wBYzCohJfD+1hglimbjErSfzmSDOFpBYsuc8M4QtKvHy 8T+wxaJARyx/vgYqriSx9vB2oMUcQL2aEut36UOMsZbY8nE91EhFiSndD9kh7hGUODnzCcsE RvFZSLbNQuiehaR7FpLuWUi6FzCyrmIULU4tLs5NNzLSSy3KTC4uzs/Ty0st2cQIjMGDW35b 7WA8+NzxEKMAB6MSD68B8/4IIdbEsuLK3EOMEhzMSiK8IreAQrwpiZVVqUX58UWlOanFhxil OViUxHnNVt4PFxJITyxJzU5NLUgtgskycXBKNTDG/6z6dDKvz/T+X66d6a+7tl16fG5byML1 Z+q4HK3v/OK2ns7nxXzv+JWolYbvEvT/VF0q28O380OdY2QGw/VSucMtVqLb/t845jJ/7i0R 5nmf7P9curP8aaBLN6vSFKbbnRzP/tb/cw7o35+fkiGgwq9y9OWtZ46bpcst1sRzzJbzuKbK 8VFWiaU4I9FQi7moOBEAY2nAor0CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/q9rcSc6XgOOGthc3uVnq1rvfvqw>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 10:31:06 -0000

SGkgSGFubmVzLA0KDQpPbiAyMDE3LTAzLTA4IDExOjE3LCAiSGFubmVzIFRzY2hvZmVuaWciIDxo
YW5uZXMudHNjaG9mZW5pZ0BnbXgubmV0PiB3cm90ZToNCg0KPkkgaGFkIGluaXRpYWxseSBwbGFu
bmVkIHRvIHByb3ZpZGUgYSByZXNwb25zZSBhZGRyZXNzaW5nIGVhY2ggb2YgeW91cg0KPnBvaW50
cyBidXQgSSBndWVzcyBpdCBpcyB0aW1lIGZvciBtZSB0byByZWFsaXplIHRoYXQgeW91IGRvIG5v
dCBjYXJlDQo+YWJvdXQgdGhlIGNoYWxsZW5nZXMgd2UgZW5jb3VudGVyIGluIG91ciBkZXBsb3lt
ZW50cy4NCg0KSSBhbSBpbnRlcmVzdGVkIGluIHRoZSBjaGFsbGVuZ2VzIHlvdSBtZWV0IGluIHlv
dXIgZGVwbG95bWVudHMuIEJ1dCBpZg0KT1NDT0FQIGRvZXNu4oCZdCBhZGRyZXNzIHlvdXIgaXNz
dWVzIGl0IGRvZXNu4oCZdCBtZWFuIHRoYXQgaXQgaXMgdXNlbGVzcywNCndoaWNoIGlzIHRoZSBp
bXByZXNzaW9uIEkgaGF2ZSBnb3QgKHJpZ2h0IG9yIHdyb25nKSBmcm9tIHlvdXIgcHJldmlvdXMN
CmlucHV0cyB0byB0aGUgSUVURiBvbiB0aGUgdG9waWMuDQoNCg0KR8O2cmFuDQoNCg==


From nobody Wed Mar  8 06:14:08 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 AE6C8129698 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 06:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 KGWsiGh0ioVo for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 06:14:06 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4B23129472 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 06:14:05 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MDhba-1d2hNQ2PvS-00H4kg; Wed, 08 Mar 2017 15:13:58 +0100
To: =?UTF-8?Q?G=c3=b6ran_Selander?= <goran.selander@ericsson.com>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <D4E5582E.78797%goran.selander@ericsson.com> <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net> <D4E599A4.7891E%goran.selander@ericsson.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <054b4b83-2034-d5a3-9f0f-e395bdb7cd8f@gmx.net>
Date: Wed, 8 Mar 2017 15:13:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <D4E599A4.7891E%goran.selander@ericsson.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="32GW4DPLFX0XM07BgAKcl09htknsm7Tq3"
X-Provags-ID: V03:K0:uNaMKbJJFfaED5bH2rM/57Kil/rW1PJFmt/xLg2gOnLRGjyKhlE nG3U/flp5soi2S55JORoJmpYgD4Dc8WHWR2Q3Zl7XWFHnWR+V4BVGuzWS79iG9B1e2bMnAt LmKxa6t2W+xexuFxepGA+4OlClV/N8pUYxHHb2zBVsY6ahd8nK0Jo7AHi9KG/Cyu4UiTBeD uwI/rzj0C9y/pkjBIApAA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Skoqs+1ZMPY=:Dw+7lNjavbyKeAgdRafiCO 4hFHpZYZJ2d7GdcN/gwBjyE+p977hrp9Hf/CWkylxWI+SZiWxxLoD1KPozNeHzQMqJAw77IWZ CN6qWKTG4gj5BwmP8CSWWNQzIVdpAwt8MkpoQ+tDKRcHYzNdaHTwh2CKSTYgBo3zkEtDxfhw3 1jC9vN5nLC5u0aBvmywtY2z5/naxLFhYg/DQaLW6324aL9PH26KNH0tqOFCtEKSHN7RECNOkm ZQbq7RQgV4S8vYt/hTxOjbMBA1wHI799/LmMPvgz8y2q+zMHGv7S7BL5odVFJiABTQdnYYgQ/ EYtCpTWP650oGtp1C3QdZMRRnFJh9+BmM+x9VVTPsZlYkP/CSzTJd2BP9eskKuOG6bsm2eWsF 8pAsvtHEE2lIP4xd6zNoJS6Iz47hOjJGodwc19lDtb5N1Oaf4z/JWSrivj3yetJ9/KxO3iA9O 1cJygFbf0elTxWYPBQIacuAR+CI4pYggOJwtpGKJJ4MEqPP1FBX/6vtk/VkFf/3nQVVQO4y35 4DJ8dPVd3q3K2w8lqkWyHD7tM5ivFNXbMfYmcvB+WubxyI7rkDqjZv6srN9QPvT74DUjLSfSR 9dyJ4w2+ikIX4GbzkHn/pgRs1guyv6GTOJCn44UeTndVOAS2ezo21YFFEdRMdgkbpC4syEBwW x2v6yOoNEjes9eelY05mOTCeJXUnik9CUdPKkqkF0ST0YluUfjfPxa9taogp6vTBPrjB7OxqQ pMR++FTT4hDFg2EKH/HlWxAc07DOhJhs1fKKn/ug/2b7BzwQQHdeNv9cZVU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/DRyjWakvmhEH-YvsJfBv7C57MRk>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 14:14:08 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--32GW4DPLFX0XM07BgAKcl09htknsm7Tq3
Content-Type: multipart/mixed; boundary="dSGxacoUVjWUdpgSVWAIcP4E6GcumDxU4";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: =?UTF-8?Q?G=c3=b6ran_Selander?= <goran.selander@ericsson.com>,
 Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "t2trg@irtf.org" <T2TRG@irtf.org>
Message-ID: <054b4b83-2034-d5a3-9f0f-e395bdb7cd8f@gmx.net>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <D4E5582E.78797%goran.selander@ericsson.com>
 <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net>
 <D4E599A4.7891E%goran.selander@ericsson.com>
In-Reply-To: <D4E599A4.7891E%goran.selander@ericsson.com>

--dSGxacoUVjWUdpgSVWAIcP4E6GcumDxU4
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Goeran,

On 03/08/2017 11:31 AM, G=C3=B6ran Selander wrote:
> Hi Hannes,
>=20
> On 2017-03-08 11:17, "Hannes Tschofenig" <hannes.tschofenig@gmx.net> wr=
ote:
>=20
>> I had initially planned to provide a response addressing each of your
>> points but I guess it is time for me to realize that you do not care
>> about the challenges we encounter in our deployments.
>=20
> I am interested in the challenges you meet in your deployments. But if
> OSCOAP doesn=E2=80=99t address your issues it doesn=E2=80=99t mean that=
 it is useless,
> which is the impression I have got (right or wrong) from your previous
> inputs to the IETF on the topic.

When Michael said that OSCOAP is the solution for end-to-end security I
had to respond. Either Michael is not aware of the limitations or they
do not matter for his use cases.

But more generally, there are two ways to do standardization:

Approach A: Let a thousand flowers bloom
Approach B: Try to minimize the number of solutions

We seem to be more and more focused on approach A. This has the benefit
that both the leadership and the folks working on the specifications are
happy. Unfortunately, there is a price to pay in the future when
companies end up having lots of solutions to choose from. They are
confused and fewer products are interoperable as a result. This is not
necessarily a new situation since we have seen the results also in other
security areas.

Ciao
Hannes



--dSGxacoUVjWUdpgSVWAIcP4E6GcumDxU4--

--32GW4DPLFX0XM07BgAKcl09htknsm7Tq3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYwBGkAAoJEGhJURNOOiAtuxoH/jjmYbUe/Rd/zwcIGN3+FFZH
JGWDh+ujU3uny6fVR5/5Kl+LuaaWQM4zSdTtB+0cdTFhwdThI3A5i/DyOegtRwjr
w2YFEsKOuKj8uOvKZSgMLXGpoF1v2l3OpwFWp7XrmUO5dz/96McZbsGMOGF+Ruxv
tHzZlhekfZxZB8JwQM+Oy0DqZ0tBHqhbfMY5MeSdn3uITud76Qqf/Rc2JrMxYCAA
nkOwpg69iaUuGwJXCwcau9lj8PI600SDDO69dHfNlJ5lWOlF8uWNi12t4xjXB01e
tjjIY308dJJuN21kLi7wTNDnZ8dJ0FVHH1jZ1OUtw17c3oHvBnrlXMbIVq4Y550=
=5AXD
-----END PGP SIGNATURE-----

--32GW4DPLFX0XM07BgAKcl09htknsm7Tq3--


From nobody Wed Mar  8 06:14:21 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 3EA23129472 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 06:14:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 4wR4NWO5Ixv2 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 06:14:12 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70A701296A3 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 06:14:11 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MNq8p-1ct2CY1ZAh-007Sx3; Wed, 08 Mar 2017 15:13:21 +0100
To: Eliot Lear <lear@cisco.com>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net>
Date: Wed, 8 Mar 2017 15:13:17 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2A0iDmrRhaFIF2kTbkhPDtFKGbb6J2WlE"
X-Provags-ID: V03:K0:gveoeiRQ/5QnMEXmStI4fW9humUrBH9AlRaUdjoeIXA0iFn9Ep9 d0S7B0UMbNrIQExDDHB8ajfOlXxHENDwPW7BygA5lltcCj5cjWU2y+qpzz++UXAKzvatzR8 sFo4VnfWWRuMGmfR2ZXB5lSyArpnUC8s5UzX2tfxSmEe0lBHNg7fszP3XD1H4jCzXwxE1sO rJ1SWnJl4VJanVdnuFhQg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:krhzPMV4e0w=:cno9Q3RH9QgRpUkEBOKu1a fntL3FYROpDtxLpiQlTGDjUZJ76TleC6uUK1jOin+vuCaiSNlrQ2tFbn3GK2A3PxqsmO1Um0C xN1O/WjYkak8UkwWzS0+tHzXMHgMWfe1sf3boUF0BHeLPl7cdW5Zg1GXnkiPlTeKykhOGVEyY Tt1tLXmjqmSfckrdn8uBz8eDXeJyRciIapU1olTPkHD3fgFtdTAS4tpSxY8puUPtfv8kdFTVy /sjhX1U3Al3imB6THWiQZWA92Kkj8akjbvBRdUNxjlI3faq1FkgHPdb89R3Fn4Cp6nWa4jULH 9LpplZrur6K1NQd1GZtm0Y8zMNEqSP2f9fttRJTyJYNbitEuQOMNqv7o7CG+dgp61ddW/+gEU i6jT3BIPGW5h1BMUpToL2Gwvg31BWMu1+U0IOIEv51Ge7lClRRRzMoeuqwFaH3ELelF05MhFj 1A4FCBE/Fx8Rfjj6A/R0uluL5ycxlxSxCVKPWckRTIOooRTLwyirvBN1IZqJn/RrJA9vaH5Vt YMBClOgbQgkZ2fyUxakxIOFpU0LURZB9gIT01EFckqn0nrsyogUkOTDGtnY69+qE9JtiUrqJt XCRsS3+ozXuK4MiK1f0alKbwXgrTjLu5aKmuDL9syyFn77oBDUAjSQm6KLpRf1sKYC6FRhYC5 8CbWcAVoBorLZmHhRuvjSog+1mRqV3Y3UPQDJbrcZjWwqXcGjBueRkuphlD2crmmfVHkCRfrD X4pf94jP653vQGP5NYDyF2/tR+RbpL+iwkU23/SX7nWrLI+zJCuOvbt5XsY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/wfr_0ToDZqOzVt_zPSIhKzzD5JY>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 14:14:19 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2A0iDmrRhaFIF2kTbkhPDtFKGbb6J2WlE
Content-Type: multipart/mixed; boundary="REBtEqopeGG080fFMqDJNNNHpx30E3Wix";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: Eliot Lear <lear@cisco.com>,
 "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>,
 "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Message-ID: <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
 <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
 <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>
In-Reply-To: <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>

--REBtEqopeGG080fFMqDJNNNHpx30E3Wix
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Eliot,

this would indeed be a good conversation to have. I have tried to
trigger it a couple of times in context of the IoT device classes but it
is very hard to get people to state what their minimum assumptions are.

I believe it has to do with the type of standardization approach we are
exercising today and this gives us a hard time to describe the big
picture of how the various building blocks are supposed to work
together. In fact, the picture becomes extremely complex and fragmented
since there are just so many options while at the same time we envision
super constrained devices. The T2TRG security document
(draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about
normal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.

Ciao
Hannes

On 03/08/2017 11:02 AM, Eliot Lear wrote:
> Matthias,
>=20
> I think the key question that everyone seems to be dancing around is th=
is:
>=20
> What is an Internet host in the context of IoT?  What are the minimum
> qualities it must possess?  I don't mean this to be a vote, but more of=

> a law of physics sort of thing.  For instance, does a host have a secur=
e
> unique identity?  What capabilities must it have?  I would expect them
> to be very few, but there are assuredly some...
>=20
> Eliot
>=20
>=20
> On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
>> Fair enough.
>>
>> Yes, I am on this IoT Directorate. I would say a large fraction of the=

>> T2TRG participants has been arguing that the Internet of Gateways is
>> not a good approach. Your security-related summary proves this point.
>>
>> I personally don't see end-to-end security happening if we keep mixing=

>> application protocols, keep using black-magic middleboxes, and keep
>> using proprietary interfaces at the device level. We need something
>> end-to-end (or T2T) for end-to-end security.
>>
>> Best wishes
>> Matthias
>>
>>
>>
>> Sent from my phone, limitations might apply.
>>
>> -----Original Message-----
>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>> *Received:* Tuesday, 07 Mar 2017, 20:10
>> *To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
>> [matthias.kovatsch@siemens.com]; mcr+ietf@sandelman.ca
>> [mcr+ietf@sandelman.ca]
>> *CC:* T2TRG@irtf.org [T2TRG@irtf.org]
>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>
>> Hi Matthias,
>>
>> I know that this is a research group and everyone can create whatever
>> they want.
>>
>> We briefly talked about security at the IoT directorate conference cal=
l
>> and I would be interesting to hear what works and what does not work f=
or
>> others.
>>
>> Ciao
>> Hannes
>>
>>
>> On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
>> > On big propaganda tour? :P
>> >
>> > Regards
>> > Matthias
>> >
>> >
>> > Sent from my phone, limitations might apply.
>> >
>> > -----Original Message-----
>> > *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>> > *Received:* Tuesday, 07 Mar 2017, 19:39
>> > *To:* Michael Richardson [mcr+ietf@sandelman.ca]
>> > *CC:* t2trg@irtf.org [T2TRG@irtf.org]
>> > *Subject:* Re: [T2TRG] RESTful Design & Security
>> >
>> > OSCOAP does not work when
>> >
>> > * you mix protocols,
>> > * use a middlebox for some processing interactions (such as data
>> > aggregation), and
>> > * when one of the protocols is a non-RESTful protocol, such as BLE
>> or MQTT.
>> >
>> > Unfortunately, these the use cases we are facing in current IoT
>> > deployments. For similar reasons we cannot use RFC 8075 either.
>> >
>> > Maybe you are seeing different deployment environments.
>> >
>> > Ciao
>> > Hannes
>> >
>> > On 03/07/2017 06:39 PM, Michael Richardson wrote:
>> >>
>> >> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>> >>     > Needless to say that these challenges have also been observed=

>> in other
>> >>     > protocols as well, such as HTTP and even SIP.
>> >>
>> >>     > What is the story for providing application layer security?
>> >>
>> >> OSCOAP seems to be end-to-end to me.
>> >>
>> >> --
>> >> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Work=
s
>> >>  -=3D IPv6 IoT consulting =3D-
>> >>
>> >>
>> >>
>> >
>> >
>> >
>> > _______________________________________________
>> > T2TRG mailing list
>> > T2TRG@irtf.org
>> > https://www.irtf.org/mailman/listinfo/t2trg
>> >
>>
>>
>>
>> _______________________________________________
>> T2TRG mailing list
>> T2TRG@irtf.org
>> https://www.irtf.org/mailman/listinfo/t2trg
>=20


--REBtEqopeGG080fFMqDJNNNHpx30E3Wix--

--2A0iDmrRhaFIF2kTbkhPDtFKGbb6J2WlE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYwBF9AAoJEGhJURNOOiAtSQkH/2UCjjTjPHwlbJR2fLEt2LJs
J4E+ZTKIljfEGpS7fbq8CiDWB9IeYh0jL6SuYcByeb3CRdLTgutiC1RFyo2kwRYB
47PZ1Yos5bFlRkDdc4qcUSizEtoIMS2ZCpV2Qlrr2+Du77Tj9ucKr9zNta92N8zh
sSFW01tnTzflP7RslhF3QYu2VEzt/NN/WtHWJsyOGx86Z4S9XwkRNqqUHmpbsnFz
9W7KfPwtXdFkH9n/F1D68u1CeSNdZ8mt/BNMDubTLQ9jBWZAkSN5gXo1GulrY8Z7
4odJMCu6T9rMNdXtn/DToYzJ7Cpttycglc4CXja+p5MCvgbFRHIuJ29KXkGf8uk=
=ZlOf
-----END PGP SIGNATURE-----

--2A0iDmrRhaFIF2kTbkhPDtFKGbb6J2WlE--


From nobody Wed Mar  8 06:54:22 2017
Return-Path: <stephen.nightingale@nist.gov>
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 EF5BA129514 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 06:54:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 8V_-_G323RR6 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 06:54:18 -0800 (PST)
Received: from wsget1.nist.gov (wsget1.nist.gov [IPv6:2610:20:6005:13::150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1323512949E for <t2trg@irtf.org>; Wed,  8 Mar 2017 06:54:17 -0800 (PST)
Received: from WSGHUB1.xchange.nist.gov (129.6.42.34) by wsget1.nist.gov (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 8 Mar 2017 09:59:48 -0500
Received: from postmark.nist.gov (129.6.16.94) by mail-g.nist.gov (129.6.42.33) with Microsoft SMTP Server id 14.3.319.2; Wed, 8 Mar 2017 09:54:15 -0500
Received: from [129.6.140.15] ([129.6.140.15])	by postmark.nist.gov (8.13.8/8.13.1) with ESMTP id v28Es4WC029618	for <t2trg@irtf.org>; Wed, 8 Mar 2017 09:54:04 -0500
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <D4E5582E.78797%goran.selander@ericsson.com> <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net> <D4E599A4.7891E%goran.selander@ericsson.com> <054b4b83-2034-d5a3-9f0f-e395bdb7cd8f@gmx.net>
To: <t2trg@irtf.org>
From: "Nightingale, J. Stephen (Fed)" <night@nist.gov>
Organization: NIST
Message-ID: <441ed39b-9dac-b9fc-7c20-bd703ccd86d7@nist.gov>
Date: Wed, 8 Mar 2017 09:54:04 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <054b4b83-2034-d5a3-9f0f-e395bdb7cd8f@gmx.net>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-NIST-MailScanner-Information: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/BLmAV4gSfOYyCWD-M7kgFQWdG5I>
Subject: [T2TRG] The Many Headed Hydra
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: night@nist.gov
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 14:54:20 -0000

.. of failing to unsubscribe from this mailgroup.
After going to the mailman site listed at the bottom of each message, thus:

   T2TRG mailing list
   T2TRG@irtf.org
   https://www.irtf.org/mailman/listinfo/t2trg

and trying to unsubscribe and failing, the next step is to send a direct 
message to t2trg-request.  Of course the well-known typo site 'ietf.org' 
fails to recognize any such group as t2trg, so finally you land on 
't2trg-request@irtf.org' with a subject and body marked unsubscribe. 
And yet the flood of T2TRG messages continues unabated.

I shouldn't have to deal with this through my mail service's Spam 
filter.  I'm running a dozen mailman groups myself and am familiar 
enough with the interface. People on my mailgroups don't have a problem 
unsubscribing.  So don't give me any snarky RTFM responses.

Please make it possible to unsubscribe from this mailgroup.

Stephen Nightingale.


From nobody Wed Mar  8 07:28:43 2017
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 5A4F51296F3 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 07:28:41 -0800 (PST)
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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3] 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 ZtvQYiH3vOei for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 07:28:38 -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 9125712966B for <t2trg@irtf.org>; Wed,  8 Mar 2017 07:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v28FSUEe014300; Wed, 8 Mar 2017 16:28:30 +0100 (CET)
Received: from [100.81.7.56] (ip-109-40-1-216.web.vodafone.de [109.40.1.216]) (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 3vdcqf1gwLzDJDK; Wed,  8 Mar 2017 16:28:30 +0100 (CET)
Content-Type: multipart/alternative; boundary=Apple-Mail-15CA0259-5318-4094-9D32-D6884871B1E6
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <441ed39b-9dac-b9fc-7c20-bd703ccd86d7@nist.gov>
Date: Wed, 8 Mar 2017 16:28:28 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <485600A8-F13D-4735-A89C-B18D22C2BB77@tzi.org>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <D4E5582E.78797%goran.selander@ericsson.com> <ac6d1edc-e884-726e-9b70-1d26f917ea33@gmx.net> <D4E599A4.7891E%goran.selander@ericsson.com> <054b4b83-2034-d5a3-9f0f-e395bdb7cd8f@gmx.net> <441ed39b-9dac-b9fc-7c20-bd703ccd86d7@nist.gov>
To: night@nist.gov
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/nhy8zCxe1L2Ubt9an7tqtJ690zs>
Cc: t2trg@irtf.org
Subject: Re: [T2TRG] The Many Headed Hydra
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 15:28:41 -0000

--Apple-Mail-15CA0259-5318-4094-9D32-D6884871B1E6
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi Stephen,

This list has the headers inserted that should allow a modern mail reader to=
 offer an unsubscribe button (my iphone certainly does). If you tried someth=
ing else and that failed, please do send the error messages you got to Ari o=
r me.

Sent from mobile

> On 8 Mar 2017, at 15:54, Nightingale, J. Stephen (Fed) <night@nist.gov> wr=
ote:
>=20
>=20
> .. of failing to unsubscribe from this mailgroup.
> After going to the mailman site listed at the bottom of each message, thus=
:
>=20
>  T2TRG mailing list
>  T2TRG@irtf.org
>  https://www.irtf.org/mailman/listinfo/t2trg
>=20
> and trying to unsubscribe and failing, the next step is to send a direct m=
essage to t2trg-request.  Of course the well-known typo site 'ietf.org' fail=
s to recognize any such group as t2trg, so finally you land on 't2trg-reques=
t@irtf.org' with a subject and body marked unsubscribe. And yet the flood of=
 T2TRG messages continues unabated.
>=20
> I shouldn't have to deal with this through my mail service's Spam filter. =
 I'm running a dozen mailman groups myself and am familiar enough with the i=
nterface. People on my mailgroups don't have a problem unsubscribing.  So do=
n't give me any snarky RTFM responses.
>=20
> Please make it possible to unsubscribe from this mailgroup.
>=20
> Stephen Nightingale.
>=20
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg
>=20

--Apple-Mail-15CA0259-5318-4094-9D32-D6884871B1E6
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Hi Stephen,</div><div id=3D"AppleMailS=
ignature"><br></div><div id=3D"AppleMailSignature">This list has the headers=
 inserted that should allow a modern mail reader to offer an unsubscribe but=
ton (my iphone certainly does). If you tried something else and that failed,=
 please do send the error messages you got to Ari or me.<br><br>Sent from&nb=
sp;<span style=3D"font-size: 13pt;">mobile</span></div><div><br>On 8 Mar 201=
7, at 15:54, Nightingale, J. Stephen (Fed) &lt;<a href=3D"mailto:night@nist.=
gov">night@nist.gov</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><d=
iv><span></span><br><span>.. of failing to unsubscribe from this mailgroup.<=
/span><br><span>After going to the mailman site listed at the bottom of each=
 message, thus:</span><br><span></span><br><span> &nbsp;T2TRG mailing list</=
span><br><span> &nbsp;<a href=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a></=
span><br><span> &nbsp;<a href=3D"https://www.irtf.org/mailman/listinfo/t2trg=
">https://www.irtf.org/mailman/listinfo/t2trg</a></span><br><span></span><br=
><span>and trying to unsubscribe and failing, the next step is to send a dir=
ect message to t2trg-request. &nbsp;Of course the well-known typo site '<a h=
ref=3D"http://ietf.org">ietf.org</a>' fails to recognize any such group as t=
2trg, so finally you land on '<a href=3D"mailto:t2trg-request@irtf.org">t2tr=
g-request@irtf.org</a>' with a subject and body marked unsubscribe. And yet t=
he flood of T2TRG messages continues unabated.</span><br><span></span><br><s=
pan>I shouldn't have to deal with this through my mail service's Spam filter=
. &nbsp;I'm running a dozen mailman groups myself and am familiar enough wit=
h the interface. People on my mailgroups don't have a problem unsubscribing.=
 &nbsp;So don't give me any snarky RTFM responses.</span><br><span></span><b=
r><span>Please make it possible to unsubscribe from this mailgroup.</span><b=
r><span></span><br><span>Stephen Nightingale.</span><br><span></span><br><sp=
an>_______________________________________________</span><br><span>T2TRG mai=
ling list</span><br><span><a href=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</=
a></span><br><span><a href=3D"https://www.irtf.org/mailman/listinfo/t2trg">h=
ttps://www.irtf.org/mailman/listinfo/t2trg</a></span><br><span></span><br></=
div></blockquote></body></html>=

--Apple-Mail-15CA0259-5318-4094-9D32-D6884871B1E6--


From nobody Wed Mar  8 07:31:55 2017
Return-Path: <oscar.garcia-morchon@philips.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 380C01296E8 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 07:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=philips.onmicrosoft.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 ORlHsfrBYjhK for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 07:31:51 -0800 (PST)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10120.outbound.protection.outlook.com [40.107.1.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BDDF129535 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 07:31:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Philips.onmicrosoft.com; s=selector1-philips-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=kKyFbUQ3qJ+08DQm6avkte8egZnsEcoIqTN7d1yuj38=; b=sKVHhsN9CZPsrgG5+2HCL7BuBfqjwmGPR9ES2s8N97YMv5xi05XeLQApRnAMCGWmaMOBafoA3np/f7HXTMltI6vhXEBvaNH611zDjOj/xwrjsFCJIyHhpabiT8GQTYLF/93FBfMurci63k5bDTkEn1HckmIShvPIHwOGsp5T4rw=
Received: from VI1P122CA0008.EURP122.PROD.OUTLOOK.COM (129.75.142.82) by DB6P122MB0038.EURP122.PROD.OUTLOOK.COM (129.75.140.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12; Wed, 8 Mar 2017 15:31:47 +0000
Received: from AM1FFO11FD040.protection.gbl (2a01:111:f400:7e00::169) by VI1P122CA0008.outlook.office365.com (2603:10a6:820:1c::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12 via Frontend Transport; Wed, 8 Mar 2017 15:31:47 +0000
Authentication-Results: spf=neutral (sender IP is 23.103.247.180) smtp.mailfrom=philips.com; gmx.net; dkim=none (message not signed) header.d=none;gmx.net; dmarc=none action=none header.from=philips.com;
Received-SPF: Neutral (protection.outlook.com: 23.103.247.180 is neither permitted nor denied by domain of philips.com)
Received: from 011-smtp-out.Philips.com (23.103.247.180) by AM1FFO11FD040.mail.protection.outlook.com (10.174.64.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.7 via Frontend Transport; Wed, 8 Mar 2017 15:31:46 +0000
Received: from DB5PR9001MB0165.MGDPHG.emi.philips.com (141.251.190.209) by DB5PR9001MB0167.MGDPHG.emi.philips.com (141.251.190.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.12; Wed, 8 Mar 2017 15:31:46 +0000
Received: from DB5PR9001MB0165.MGDPHG.emi.philips.com ([141.251.190.209]) by DB5PR9001MB0165.MGDPHG.emi.philips.com ([141.251.190.209]) with mapi id 15.01.0933.026; Wed, 8 Mar 2017 15:31:46 +0000
From: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Eliot Lear <lear@cisco.com>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpstzow5GSCUy0qO2HV2fKAQj6GJplEAgAAQwQCAAAGWgIAAByCAgAAHRICAAPIBgIAARgCAgAASgzA=
Date: Wed, 8 Mar 2017 15:31:46 +0000
Message-ID: <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com> <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net>
In-Reply-To: <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2.247.245.210]
X-MS-Office365-Filtering-Correlation-Id: c6f0f599-9e16-4e8d-7a0f-08d466383b8c
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB5PR9001MB0167.MGDPHG.emi.philips.com
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:23.103.247.180; IPV:NLI; CTRY:; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39850400002)(39840400002)(39450400003)(39860400002)(2980300002)(24454002)(13464003)(199003)(189002)(85714005)(377454003)(374574003)(9170700003)(8676002)(15650500001)(2950100002)(55016002)(356003)(38730400002)(4326008)(23676002)(189998001)(50986999)(305945005)(53546006)(229853002)(24736003)(76176999)(8936002)(50466002)(54356999)(6306002)(53936002)(81166006)(6246003)(7696004)(2906002)(106116001)(86362001)(108616004)(5660300001)(105586002)(3846002)(6116002)(93886004)(33646002)(2900100001)(102836003)(106466001)(7736002)(66066001)(47776003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6P122MB0038; H:011-smtp-out.Philips.com; FPR:; SPF:Neutral; MLV:sfv; A:1; MX:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; AM1FFO11FD040; 1:PIOeSPaFn4kbXrNNCxnaDf98Wev2Ra2c/sWPL9XmLecN8cUWsT8cWs7IjMoAE4tR1PtlvFgtn5TJ+P6xqlDav14C7ABhzaKxJwkx7WDf5f1sKRXqCkiSi76qJRtd2LHvMlZzOUq2iQaG2CcbHZAsE8PX27h+nGpzI/xLlTUQ9WtttzS3UVmtc0S88gsaJNKuYd+MqcBitjPNdiLWOb4C0XpVpYJN3LlIbjHWJj/SBO1u99cOuzBCZ5kE6QF3di81rsL9uHSlGuAN1ZHYUkIoAarqNBZfOj38vlFQ07sR3DFL/pGqiSJ9Mmrl8d2wuUCyhIuIWev0LEF8VTBjJUZ5MDI9/XZsgazqM2aN8EC6XufT1haIPytL63Q8HCdUiD4/TnUMw12VZq6hb/3NiXhRX4SVpaGE14sQD5BktJVaXdRjm29lmUb6HloDyl+gwQUdT+pG+j41omC8ZVHhJ4wrcjLgyfSdCKqIOgshtBjzxDrdBogQPH71eyG4u1AXSIhfD+6DU+51ifOlG7KcTJ8a1c4wCEUVindosYoOo7GWM6k=
X-CrossPremisesHeadersPromoted: AM1FFO11FD040.protection.gbl
X-CrossPremisesHeadersFiltered: AM1FFO11FD040.protection.gbl
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB6P122MB0038;
X-Microsoft-Exchange-Diagnostics: 1; DB6P122MB0038; 3:LYBgY+/4BjcpfeDZBV5r2C5zm3M18HpIbh7iyX2Q/aaxeTRTikETuaXcF7E5O7NAuGCVUHuPzJRVfiP/OBUQp7RAFWhQhP5CTlLmcqkZNcP7EfdplpDzMgt8rEDgP14fccXgkycli+JJ8XoKRbCLDF6BoHTCDEDR9HRtT+CyUhyLlQmsd8dO6PASURAts99enzK+WhdxcMZTUMxXUdpqfNwpM6SDQ9lH91yiKKeSY+N8zIWW4O7kRlmEw47rgTZg+Ijufr57EP+/gtRuD19fjJfwE8M47knUWKxmRIeRFzjNnV6j/+ZjN+Pjcagob6zkNpQ6W7CyoBTC804mJ/Cw2UUeC8xFqIsPd4LHGPwHVJ6t3ximF3/KFdYUYatwck3m; 25:6pgIaT5hdHqk2NzTMir6T+Noes4aNM275wTS1KgP6kaqYZe3/yI54Rc4/KaHEVGbaz0cp01du12gxXqc+bMVo4Oa2PkbPtaZJR7wU9KK/nD26fdpbd10loRuiBeHdGlzPWlW4RIimkcdI8J/CJWPz+bIYzDizj6y0Oewe/K/SiXYZJe/ew7LzAP+6rtNa9eNQZOo7JfLNbTzfu8ZVKRto99PMbBZpHqCikm4JOG5zdFIV/1YNo9uY1pxMjoceis5T4qouVbaovokgUNnKzZCSQS6ZokVwPqSiBnuUB3fXrH8TbY1gq7PRNMsIQtSVVTt2F0nEiO9wmSMNmLEZ66h8X72NUCXO5w65DQIYz23EbfdXgQKQrUfYH1KNy89yWjfTxB6sccBwm/GAdz8QlnhiZh7aow2OVKGQCe6vXXVAgppA5lyOP6jgv7N9beLNIhdzWc28EhSU+GB2SZOJ+jwmg==
X-Microsoft-Exchange-Diagnostics: 1; DB6P122MB0038; 31:PAoAxu8wCO4aad6lr3K1WuqlxZQ+93IE85ZMPDd3l/3IWxAsiAZCZvH3lXdCoKGFvQJsuh3gJS0Ymkmo66ROpCMlL11jEHFS7jBOamFHfmWHHEe6T0zOwfqUWYreER/wWH6SmYC/Vl46m5xzXqj9CDY08AZNNWCG2uH3iKFOP51xbdjfns8yLHARu6xcrg2K7hAoIZjkBlVLXOZm1qIcqtcWFy8C0Z6jzH8vMVLxEYwEhy1BbEm9zxN9ZrIWYXqsDP9S69/VRdJkD9aQyYs57u2ZFtm4121DYcDEZcAEfkw=; 20:Ri2vBtbVRxmDVWaq/pota2O0A5+3LZwu5Nhxjo/ol5JVH6KNlKgb5e+6mEkO5Lr/oVgFdwWXxryX5AcbfLWlTbO96ZbqtnModP4fOfTqEjS5qp72rpdLOEF7Mi8xdbj/0yJg03AVOLJ+p/R7ht8m9CJbnwVfIiByG1usuujYTAdV5Lg2skvqyvAR/w+NOlwYPUEW6+vwjXFWpUHkLh+jeioAn8BcJHgmj8XEXy7VrYDClH2Uj4wiflVIPBpxzW5k2bDLBfgbv0IwTbFfT2A7jBKwJPl5qklgq5cS/3YW1zmvYVxDsCs4HO682xxKAXhj2iDcWF8V98fiu7UE+aMJ6PuPlUFzWi7IiEms3UkcWmzNLRYYI70GCM+YfbVQWRLJkaEysoHHw3AtUKdxubPGJOY0/aqpKnO6P6pziVV8NewfMQ1JaDRRivY0FNu3rdDRl7O0yo8RKu92bOtVFs4XZacXcnAkXlcYkUj6LX1qc+oZyOaD+qT2plRDXR5S7jTc
X-Microsoft-Antispam-PRVS: <DB6P122MB0038BB25CDB23BD21F705D96C82E0@DB6P122MB0038.EURP122.PROD.OUTLOOK.COM>
X-Exchange-Antispam-Report-Test: UriScan:(192374486261705)(248736688235697)(95692535739014)(126837547833334); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(8121501046)(5005006)(13016025)(13018025)(3002001)(10201501046)(6055026)(6041248)(20161123560025)(20161123555025)(20161123564025)(20161123558025)(20161123562025)(6072148); SRVR:DB6P122MB0038; BCL:0; PCL:0; RULEID:; SRVR:DB6P122MB0038; 
X-Microsoft-Exchange-Diagnostics: 1; DB6P122MB0038; 4:uD9/FhcjFSqfoCd4ltOdZfzw8rZyzgYTtk/5Nz5Aqswt7WgJjQhhX3y0QqLcVmIbYV5SCwOShasJt8q3QIKX39frLA4BzLoO1vpkme5GHffXh7p/cie6J2Uc0YxCRk5XIfwcLMhnVcl4GVloAnbD2HNS+YCTKH8+PLGBhomf3jFTFHlSCdEnVm0owQFT7tr+MjIcV9aiQn+WKuxi0vtwBCM1qrMNsLUwW+Abmd9QngH7hbJEAjaYzqO1YLi8BKC3/zj/ESYKPklhQ5QZ3b0FezMV7TLcsLE6nJsvZw1Zvvyke3XcPe2g4TyhmnyDATwlvIvHkE9T+TIkZKEo5d7hRwmNSLwwyvUvvNrfQ2TS0vE8wbzc3+JfAAdxRf1zPGRSVzZP1Uo+pVV9K08zMucRu6Tg2bDzaT7aZAefr0IHh69E0TF4vFn/84/OeNxydSh5I2zM/rQ1p08aW5OsNkC2Rup0Fpabiz+RCABHS3yZqAO373tVH6JeeQa5ZC9t9wvrMQtvaEf+NkyRh4zesZQYzh8huLx8Z43kdfasohWIEwlx5Xk9an4B9Ud0NbUUFGEz0apL/DvdW1y3rtjjgH+2hXlCFf3ZPPjbP9uuFejGPGEuXIZ/mBEGqm0XCqZnRy7R7hC2CHpiYzbQ64b1vx4NrLaDmShJ/TZbVxl5wRb98QWJfUK2+iAVg4rBwQkjJgQRPfP1yfzqKLahfqY6ICD2SVW4r7Dj1dYDpsALjlUKjkkKVQDEGTL4d2I6kB3ruL5R2X6cHVgyleeKE90pF7tvse+V2ivYghdHOsGl2I1QbNE=
X-Forefront-PRVS: 02408926C4
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjZQMTIyTUIwMDM4OzIzOmR6YnFBcDNlb2lTUytsV1lMc1ovVHFWMXlh?= =?utf-8?B?dkpacTlXdjRjNHZxeTVYZ0w1STJyeWczODRjN2xDaUNZV3JMaWNEdTFUUmFn?= =?utf-8?B?Rk9HYnhsN1Y1eXZDOC9CMkdsMG1IeFJHTm5sM2ZPRzUwSTVrS2FJVnh6MitH?= =?utf-8?B?cWpXOU5CLzNyRW5oaDg1TVdCOFhPWHkwcXNVdDJrWUxMNHNjLzJyNTUyTHN6?= =?utf-8?B?SFdIdzVrUk50dUduWmhHeGhvNExxcFJkNXphdGxrQjhtNlg0RmFEL1NLbnAz?= =?utf-8?B?SGJGdHFYeC9oN2lvVGlZVGRJZWsxejBWS25Tc0NLelEzbHdiZGhSeHJEalFk?= =?utf-8?B?cjZtdTRwcnh5czFnZmlBVTZLcUxXdHU3SlRocjRuSzZuejFnL0YzM3RqTEJx?= =?utf-8?B?OFBMbHBWVHhBbDl1VVFRN1ZFS1J1TWxwaHZONHIvOFJQYmtzdHVjWm44OUlJ?= =?utf-8?B?bndEY3lMenVuTW5FeFRyVXVwUWFLekdQWnltQ29JcnJMNnVjK0JnRmhOS1M2?= =?utf-8?B?b3VYa0d2QUVXaWVzN3ZoSklMWUFaMS94VTdhd2ticnBKRUlsRkVjMW1odUNu?= =?utf-8?B?OE45RzZDYUxIelIrSHJSanErZ28wUmUzMjFyTUxDb1M2cXZGSk9kdElGcng0?= =?utf-8?B?SUgxdGQ1U0IyV2hXVmdoVGx1RVI4eTczVzF6dHkzWDRPS0RLUUtKOU5TK3cz?= =?utf-8?B?cEUvejVSbFEyQkNobHlJRjBMRHNIdFJXQzkyVW9jeE1EazBRK3VZRVVoVzh1?= =?utf-8?B?V3l0NHphUng1L29nVGU5KzZKOTF4NHhCMnBCdzJEMy9QWm51NWRoNlJvY2tY?= =?utf-8?B?aE0vZWRZYVRTbHBVZE1qcEdYd2wrTnRicW92Z0NrSWwyV0phUkZmNVdWdEdn?= =?utf-8?B?Rm1tbHBMWW5xVW51VFYxQmNLbXJaNk9jVVA5WlJSRWVmZmhOZ3ZGN096MUNK?= =?utf-8?B?R25OT2pBYUt6d1ZIbHo4RzBhSWxXbVhiUFlkZFR6V1NJK0Nwbk1uZFN1dVhW?= =?utf-8?B?MUV3VXE4SDlmSnNSSm5xNURxUFVRODFhNUsvbXI4alV2V2U3WUNUcm1DTzBs?= =?utf-8?B?MnpWZjVhRjNqUDJrR3phZXB0NDVLK1dZRnBOcWcyNnluT1FOZzByQXlSZ1lt?= =?utf-8?B?bGlrMkZMM28rc2dEMTErSkJiYVlZclUvdldIWU1sem9iak1uVkRlVVlzTDV6?= =?utf-8?B?L05DN1hBbkNWalQwMVpSOVZDV2cvUnN0ZVdtdkh4WjFyRjRwaXVHYm5aWTU1?= =?utf-8?B?WWpXQjhCZURPeVFGcFJMNnl3UytpeVY5c0JyUkx5QWNtNHFjQnJtSE15SkEy?= =?utf-8?B?eUo2N1h4a2l6eEd5STVOaktGWWRFcXVvTldwS0toelpYMkkyMW1BWDNzOHZ0?= =?utf-8?B?NW9VQnpocGQ1dzhDZWJUSUxZNjNVL2thMkZSLzZmRG9Iek5TclRURnhiamxy?= =?utf-8?B?WGNld0Q1MEZaUHExWFo3em1ZNmllWGNuU1l3Sm5zTVdoZnJuTGtEUGxPck1S?= =?utf-8?B?THY5SmJDM0w3MndKUTh0NmxDdDc3QW0welZNQVJaY0RaSE9XM1I0dXVlbVIv?= =?utf-8?B?QUcwbUVVNnl5TjJFZFZueVBLWWN5bUQyanRNZDFjUWtSOXR5Z3M2bE1YQUxD?= =?utf-8?B?SDcwdXpkU1FZVkJwaTZWNHY4UkhuRHFwUE1xODZGWi9BazZTb1RyanNhNFVy?= =?utf-8?B?VVB0Z0VEY2tVNGRxZW1seVFCcEJrQTVOZ3ZnVEk2Nm1GSmJ4SEZhM0lpeHVZ?= =?utf-8?Q?Zb6C//Qgn6v+jn4cj6tHRYnDoKUL4tt7Hxh0g=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DB6P122MB0038; 6:yY5i0e6sBITd0oDHiHjJmb7F9R/VPOW5Bo3aY5bTovtmW7XgGgGR/mU3EnUjKv5KeC67DQQ2f2K4GKeGJAf7yOee4667ic6+GhEvIEFlAn+6ZUDzxN/BfgKR2BdF1ogUxyMFRxAw89PMscOOvBLUiyuWhEQf0bWyQR5ibr8LN60k8cIqdYY0jvTM1M0JbxSBrbp169mrhfVd/c2ENJ6uJY0OUVOYUm47HhCxfRPx5zxfTpX4uW5b0jYrP85RXJJzbTcSLGG5OlUz5+4V6lAtvrV6tpKn5THlnWgRD+dVM4PQpytDXFSY8MpQiH8QKV4Km9NMV1xo1sK1tYQ4UIbc2k46nUF4YRDv337+m92TdIOz0LXIX615mR3+k3b2J7pmxEXphYbPe91PULwVdpcr6zwkpZtIfkuAbu108IWSG24=; 5:hNyK9/cZB/ON+PnMrp6ROm+z8NhZrKoq+fbsBsKKWxI0qCdB4H28sDvIrkNQRjAdEO9J7cp1QbeAsOxHOIcmsNvuqO73ILnLBYxeGRpVhoNZi8wLKbOlnxMhhsWvi0UCMQ/nNi1O4IFm26hM54U2ZA==; 24:3AJ9yBV0v76MyrNYdWWffOoDEU4kSoDxtZ7+3xJJ0thHoayOilspUbETO0QW1DZzPnKdgB/bbXSjB6fHEI66NGps6S80abbcHHCC1LTmqLM=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB6P122MB0038; 7:Wx0xMnD/TDcNGKEAkji64o7suaVHnBsATntaVqPnAbWcbIluNKEeq5IAXW5eO2ObRfcZXtMDRbpaNy/mVgT9qdJFS69rjx2afnCC35PwDMZmr57GnP5u9Oej4MxqILnzolRw9/CkZpbVNtdJGKhn0G+KTvv5hVMFN6UkzbII7QuC7flXrA/u7H6zfJ2HVrnjJjsKgq3yTcGznOjx5p8MN4LVBYKUUWIHJ0ytvFeOa9rSMnsVy+Td9IddrxzTnqGCdK4wf1WBGH2P1sYuThOPipwRRWJqa/SgGccenKKLVm6LqeZoD0P/UUGV0mM/lhBxLgbbwTpaiQlJX/VIs/C7pw==
X-OriginatorOrg: philips.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Mar 2017 15:31:46.8722 (UTC)
X-MS-Exchange-CrossTenant-Id: 1a407a2d-7675-4d17-8692-b3ac285306e4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=1a407a2d-7675-4d17-8692-b3ac285306e4; Ip=[23.103.247.180];  Helo=[011-smtp-out.Philips.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6P122MB0038
X-MS-Exchange-CrossPremises-AuthAs: Internal
X-MS-Exchange-CrossPremises-AuthMechanism: 04
X-MS-Exchange-CrossPremises-AuthSource: DB5PR9001MB0165.MGDPHG.emi.philips.com
X-MS-Exchange-CrossPremises-SCL: 1
X-MS-Exchange-CrossPremises-messagesource: StoreDriver
X-MS-Exchange-CrossPremises-BCC: 
X-MS-Exchange-CrossPremises-originalclientipaddress: 2.247.245.210
X-MS-Exchange-CrossPremises-disclaimer-hash: 7fd5309d68bb4378c576a4d2c2ad972d336f5eb0475879c2a0b14da1aac98972
X-MS-Exchange-CrossPremises-processed-by-journaling: Journal Agent
X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
X-MS-Exchange-CrossPremises-Antispam-ScanContext: DIR:Originating; SFV:NSPM; SKIP:0; 
X-OrganizationHeadersPreserved: DB6P122MB0038.EURP122.PROD.OUTLOOK.COM
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/lLfY1ZnzHPGWu1_UE1JX3MbXsiw>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 15:31:54 -0000

SGkgSGFubmVzLA0KDQp0aGUgZG9jdW1lbnQgIiBkcmFmdC1pcnRmLXQydHJnLWlvdC1zZWNjb25z
LTAxIiBzdW1tYXJpemVzIHByb3RvY29scy4gIEJ1dCBJIGRvIG5vdCB0aGluayB0aGF0IHdlIGRv
IHRoaXMgaGFwcGlseSBidXQgc2VyaW91c2x5LiBTdW1tYXJpemluZyBleGlzdGluZyBwcm90b2Nv
bHMvd29yayBpcyBvbmUgb2YgdGhlIGdvYWxzIG9mIHRoZSBkb2N1bWVudC4NCg0KVGhlIGRvY3Vt
ZW50IGFsc28gYWNrbm93bGVkZ2VzIHRoYXQgZGV2aWNlcyBoYXZlIGRpZmZlcmVudCBjYXBhYmls
aXRpZXMgYW5kIHJlcXVpcmVtZW50cywgYWxzbyBpbiB0ZXJtcyBvZiBzZWN1cml0eS4gSW4gbXkg
dmlldywgdGhpcyBmaXRzIHdpdGggdGhlIGlkZWEgb2YgbWluaW11bSByZXF1aXJlbWVudHMuIEl0
IHdvdWxkIGJlIGdyZWF0IHRvIGhhdmUgeW91ciBpbnB1dCBvbiB5b3VyIHVzZSBjYXNlcyBhbmQg
eW91ciB2aWV3cyBvbiBtaW5pbXVtIGFzc3VtcHRpb25zIGluIGRpZmZlcmVudCBkZXBsb3ltZW50
IHNjZW5hcmlvcy9zZWN1cml0eSBjYXBhYmlsaXRpZXMgb2YgZGlmZmVyZW50IHR5cGVzIG9mIGRl
dmljZXMuDQoNCkNoZWVycywgT3NjYXIuDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IFQyVFJHIFttYWlsdG86dDJ0cmctYm91bmNlc0BpcnRmLm9yZ10gT24gQmVoYWxmIE9m
IEhhbm5lcyBUc2Nob2ZlbmlnDQpTZW50OiBXZWRuZXNkYXksIE1hcmNoIDgsIDIwMTcgMzoxMyBQ
TQ0KVG86IEVsaW90IExlYXIgPGxlYXJAY2lzY28uY29tPjsgS292YXRzY2gsIE1hdHRoaWFzIDxt
YXR0aGlhcy5rb3ZhdHNjaEBzaWVtZW5zLmNvbT47IG1jcitpZXRmQHNhbmRlbG1hbi5jYQ0KQ2M6
IFQyVFJHQGlydGYub3JnDQpTdWJqZWN0OiBSZTogW1QyVFJHXSBSRVNUZnVsIERlc2lnbiAmIFNl
Y3VyaXR5DQoNCkhpIEVsaW90LA0KDQp0aGlzIHdvdWxkIGluZGVlZCBiZSBhIGdvb2QgY29udmVy
c2F0aW9uIHRvIGhhdmUuIEkgaGF2ZSB0cmllZCB0byB0cmlnZ2VyIGl0IGEgY291cGxlIG9mIHRp
bWVzIGluIGNvbnRleHQgb2YgdGhlIElvVCBkZXZpY2UgY2xhc3NlcyBidXQgaXQgaXMgdmVyeSBo
YXJkIHRvIGdldCBwZW9wbGUgdG8gc3RhdGUgd2hhdCB0aGVpciBtaW5pbXVtIGFzc3VtcHRpb25z
IGFyZS4NCg0KSSBiZWxpZXZlIGl0IGhhcyB0byBkbyB3aXRoIHRoZSB0eXBlIG9mIHN0YW5kYXJk
aXphdGlvbiBhcHByb2FjaCB3ZSBhcmUgZXhlcmNpc2luZyB0b2RheSBhbmQgdGhpcyBnaXZlcyB1
cyBhIGhhcmQgdGltZSB0byBkZXNjcmliZSB0aGUgYmlnIHBpY3R1cmUgb2YgaG93IHRoZSB2YXJp
b3VzIGJ1aWxkaW5nIGJsb2NrcyBhcmUgc3VwcG9zZWQgdG8gd29yayB0b2dldGhlci4gSW4gZmFj
dCwgdGhlIHBpY3R1cmUgYmVjb21lcyBleHRyZW1lbHkgY29tcGxleCBhbmQgZnJhZ21lbnRlZCBz
aW5jZSB0aGVyZSBhcmUganVzdCBzbyBtYW55IG9wdGlvbnMgd2hpbGUgYXQgdGhlIHNhbWUgdGlt
ZSB3ZSBlbnZpc2lvbiBzdXBlciBjb25zdHJhaW5lZCBkZXZpY2VzLiBUaGUgVDJUUkcgc2VjdXJp
dHkgZG9jdW1lbnQNCihkcmFmdC1pcnRmLXQydHJnLWlvdC1zZWNjb25zLTAxKSBjb25maXJtcyB0
aGlzIGFuZCBoYXBwaWx5IHRhbGtzIGFib3V0IG5vcm1hbCBJUHNlYy9JS0UsIGRpZXQgSVBzZWMs
IEhJUCwgTUlLRVksIE9TQ09BUCwgSk9TRSwgQ09TRSwgZXRjLiBldGMuDQoNCkNpYW8NCkhhbm5l
cw0KDQpPbiAwMy8wOC8yMDE3IDExOjAyIEFNLCBFbGlvdCBMZWFyIHdyb3RlOg0KPiBNYXR0aGlh
cywNCj4NCj4gSSB0aGluayB0aGUga2V5IHF1ZXN0aW9uIHRoYXQgZXZlcnlvbmUgc2VlbXMgdG8g
YmUgZGFuY2luZyBhcm91bmQgaXMgdGhpczoNCj4NCj4gV2hhdCBpcyBhbiBJbnRlcm5ldCBob3N0
IGluIHRoZSBjb250ZXh0IG9mIElvVD8gIFdoYXQgYXJlIHRoZSBtaW5pbXVtDQo+IHF1YWxpdGll
cyBpdCBtdXN0IHBvc3Nlc3M/ICBJIGRvbid0IG1lYW4gdGhpcyB0byBiZSBhIHZvdGUsIGJ1dCBt
b3JlDQo+IG9mIGEgbGF3IG9mIHBoeXNpY3Mgc29ydCBvZiB0aGluZy4gIEZvciBpbnN0YW5jZSwg
ZG9lcyBhIGhvc3QgaGF2ZSBhDQo+IHNlY3VyZSB1bmlxdWUgaWRlbnRpdHk/ICBXaGF0IGNhcGFi
aWxpdGllcyBtdXN0IGl0IGhhdmU/ICBJIHdvdWxkDQo+IGV4cGVjdCB0aGVtIHRvIGJlIHZlcnkg
ZmV3LCBidXQgdGhlcmUgYXJlIGFzc3VyZWRseSBzb21lLi4uDQo+DQo+IEVsaW90DQo+DQo+DQo+
IE9uIDMvNy8xNyA4OjM2IFBNLCBLb3ZhdHNjaCwgTWF0dGhpYXMgd3JvdGU6DQo+PiBGYWlyIGVu
b3VnaC4NCj4+DQo+PiBZZXMsIEkgYW0gb24gdGhpcyBJb1QgRGlyZWN0b3JhdGUuIEkgd291bGQg
c2F5IGEgbGFyZ2UgZnJhY3Rpb24gb2YNCj4+IHRoZSBUMlRSRyBwYXJ0aWNpcGFudHMgaGFzIGJl
ZW4gYXJndWluZyB0aGF0IHRoZSBJbnRlcm5ldCBvZiBHYXRld2F5cw0KPj4gaXMgbm90IGEgZ29v
ZCBhcHByb2FjaC4gWW91ciBzZWN1cml0eS1yZWxhdGVkIHN1bW1hcnkgcHJvdmVzIHRoaXMgcG9p
bnQuDQo+Pg0KPj4gSSBwZXJzb25hbGx5IGRvbid0IHNlZSBlbmQtdG8tZW5kIHNlY3VyaXR5IGhh
cHBlbmluZyBpZiB3ZSBrZWVwDQo+PiBtaXhpbmcgYXBwbGljYXRpb24gcHJvdG9jb2xzLCBrZWVw
IHVzaW5nIGJsYWNrLW1hZ2ljIG1pZGRsZWJveGVzLCBhbmQNCj4+IGtlZXAgdXNpbmcgcHJvcHJp
ZXRhcnkgaW50ZXJmYWNlcyBhdCB0aGUgZGV2aWNlIGxldmVsLiBXZSBuZWVkDQo+PiBzb21ldGhp
bmcgZW5kLXRvLWVuZCAob3IgVDJUKSBmb3IgZW5kLXRvLWVuZCBzZWN1cml0eS4NCj4+DQo+PiBC
ZXN0IHdpc2hlcw0KPj4gTWF0dGhpYXMNCj4+DQo+Pg0KPj4NCj4+IFNlbnQgZnJvbSBteSBwaG9u
ZSwgbGltaXRhdGlvbnMgbWlnaHQgYXBwbHkuDQo+Pg0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4+ICpGcm9tOiogSGFubmVzIFRzY2hvZmVuaWcgW2hhbm5lcy50c2Nob2ZlbmlnQGdt
eC5uZXRdDQo+PiAqUmVjZWl2ZWQ6KiBUdWVzZGF5LCAwNyBNYXIgMjAxNywgMjA6MTANCj4+ICpU
bzoqIEtvdmF0c2NoLCBNYXR0aGlhcyAoQ1QgUkRBIE5FQyBFTUItREUpDQo+PiBbbWF0dGhpYXMu
a292YXRzY2hAc2llbWVucy5jb21dOyBtY3IraWV0ZkBzYW5kZWxtYW4uY2ENCj4+IFttY3IraWV0
ZkBzYW5kZWxtYW4uY2FdDQo+PiAqQ0M6KiBUMlRSR0BpcnRmLm9yZyBbVDJUUkdAaXJ0Zi5vcmdd
DQo+PiAqU3ViamVjdDoqIFJlOiBbVDJUUkddIFJFU1RmdWwgRGVzaWduICYgU2VjdXJpdHkNCj4+
DQo+PiBIaSBNYXR0aGlhcywNCj4+DQo+PiBJIGtub3cgdGhhdCB0aGlzIGlzIGEgcmVzZWFyY2gg
Z3JvdXAgYW5kIGV2ZXJ5b25lIGNhbiBjcmVhdGUgd2hhdGV2ZXINCj4+IHRoZXkgd2FudC4NCj4+
DQo+PiBXZSBicmllZmx5IHRhbGtlZCBhYm91dCBzZWN1cml0eSBhdCB0aGUgSW9UIGRpcmVjdG9y
YXRlIGNvbmZlcmVuY2UNCj4+IGNhbGwgYW5kIEkgd291bGQgYmUgaW50ZXJlc3RpbmcgdG8gaGVh
ciB3aGF0IHdvcmtzIGFuZCB3aGF0IGRvZXMgbm90DQo+PiB3b3JrIGZvciBvdGhlcnMuDQo+Pg0K
Pj4gQ2lhbw0KPj4gSGFubmVzDQo+Pg0KPj4NCj4+IE9uIDAzLzA3LzIwMTcgMDc6NDUgUE0sIEtv
dmF0c2NoLCBNYXR0aGlhcyB3cm90ZToNCj4+ID4gT24gYmlnIHByb3BhZ2FuZGEgdG91cj8gOlAN
Cj4+ID4NCj4+ID4gUmVnYXJkcw0KPj4gPiBNYXR0aGlhcw0KPj4gPg0KPj4gPg0KPj4gPiBTZW50
IGZyb20gbXkgcGhvbmUsIGxpbWl0YXRpb25zIG1pZ2h0IGFwcGx5Lg0KPj4gPg0KPj4gPiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gPiAqRnJvbToqIEhhbm5lcyBUc2Nob2ZlbmlnIFto
YW5uZXMudHNjaG9mZW5pZ0BnbXgubmV0XQ0KPj4gPiAqUmVjZWl2ZWQ6KiBUdWVzZGF5LCAwNyBN
YXIgMjAxNywgMTk6MzkNCj4+ID4gKlRvOiogTWljaGFlbCBSaWNoYXJkc29uIFttY3IraWV0ZkBz
YW5kZWxtYW4uY2FdDQo+PiA+ICpDQzoqIHQydHJnQGlydGYub3JnIFtUMlRSR0BpcnRmLm9yZ10N
Cj4+ID4gKlN1YmplY3Q6KiBSZTogW1QyVFJHXSBSRVNUZnVsIERlc2lnbiAmIFNlY3VyaXR5DQo+
PiA+DQo+PiA+IE9TQ09BUCBkb2VzIG5vdCB3b3JrIHdoZW4NCj4+ID4NCj4+ID4gKiB5b3UgbWl4
IHByb3RvY29scywNCj4+ID4gKiB1c2UgYSBtaWRkbGVib3ggZm9yIHNvbWUgcHJvY2Vzc2luZyBp
bnRlcmFjdGlvbnMgKHN1Y2ggYXMgZGF0YQ0KPj4gPiBhZ2dyZWdhdGlvbiksIGFuZA0KPj4gPiAq
IHdoZW4gb25lIG9mIHRoZSBwcm90b2NvbHMgaXMgYSBub24tUkVTVGZ1bCBwcm90b2NvbCwgc3Vj
aCBhcyBCTEUNCj4+IG9yIE1RVFQuDQo+PiA+DQo+PiA+IFVuZm9ydHVuYXRlbHksIHRoZXNlIHRo
ZSB1c2UgY2FzZXMgd2UgYXJlIGZhY2luZyBpbiBjdXJyZW50IElvVA0KPj4gPiBkZXBsb3ltZW50
cy4gRm9yIHNpbWlsYXIgcmVhc29ucyB3ZSBjYW5ub3QgdXNlIFJGQyA4MDc1IGVpdGhlci4NCj4+
ID4NCj4+ID4gTWF5YmUgeW91IGFyZSBzZWVpbmcgZGlmZmVyZW50IGRlcGxveW1lbnQgZW52aXJv
bm1lbnRzLg0KPj4gPg0KPj4gPiBDaWFvDQo+PiA+IEhhbm5lcw0KPj4gPg0KPj4gPiBPbiAwMy8w
Ny8yMDE3IDA2OjM5IFBNLCBNaWNoYWVsIFJpY2hhcmRzb24gd3JvdGU6DQo+PiA+Pg0KPj4gPj4g
SGFubmVzIFRzY2hvZmVuaWcgPGhhbm5lcy50c2Nob2ZlbmlnQGdteC5uZXQ+IHdyb3RlOg0KPj4g
Pj4gICAgID4gTmVlZGxlc3MgdG8gc2F5IHRoYXQgdGhlc2UgY2hhbGxlbmdlcyBoYXZlIGFsc28g
YmVlbg0KPj4gPj4gb2JzZXJ2ZWQNCj4+IGluIG90aGVyDQo+PiA+PiAgICAgPiBwcm90b2NvbHMg
YXMgd2VsbCwgc3VjaCBhcyBIVFRQIGFuZCBldmVuIFNJUC4NCj4+ID4+DQo+PiA+PiAgICAgPiBX
aGF0IGlzIHRoZSBzdG9yeSBmb3IgcHJvdmlkaW5nIGFwcGxpY2F0aW9uIGxheWVyIHNlY3VyaXR5
Pw0KPj4gPj4NCj4+ID4+IE9TQ09BUCBzZWVtcyB0byBiZSBlbmQtdG8tZW5kIHRvIG1lLg0KPj4g
Pj4NCj4+ID4+IC0tDQo+PiA+PiBNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitJRVRGQHNhbmRlbG1h
bi5jYT4sIFNhbmRlbG1hbiBTb2Z0d2FyZQ0KPj4gPj4gV29ya3MgIC09IElQdjYgSW9UIGNvbnN1
bHRpbmcgPS0NCj4+ID4+DQo+PiA+Pg0KPj4gPj4NCj4+ID4NCj4+ID4NCj4+ID4NCj4+ID4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+ID4gVDJUUkcg
bWFpbGluZyBsaXN0DQo+PiA+IFQyVFJHQGlydGYub3JnDQo+PiA+IGh0dHBzOi8vd3d3LmlydGYu
b3JnL21haWxtYW4vbGlzdGluZm8vdDJ0cmcNCj4+ID4NCj4+DQo+Pg0KPj4NCj4+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBUMlRSRyBtYWlsaW5n
IGxpc3QNCj4+IFQyVFJHQGlydGYub3JnDQo+PiBodHRwczovL3d3dy5pcnRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3QydHJnDQo+DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
ClRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gdGhpcyBtZXNzYWdlIG1heSBiZSBjb25maWRl
bnRpYWwgYW5kIGxlZ2FsbHkgcHJvdGVjdGVkIHVuZGVyIGFwcGxpY2FibGUgbGF3LiBUaGUgbWVz
c2FnZSBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSBhZGRyZXNzZWUocykuIElmIHlvdSBhcmUg
bm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHlvdSBhcmUgaGVyZWJ5IG5vdGlmaWVkIHRoYXQg
YW55IHVzZSwgZm9yd2FyZGluZywgZGlzc2VtaW5hdGlvbiwgb3IgcmVwcm9kdWN0aW9uIG9mIHRo
aXMgbWVzc2FnZSBpcyBzdHJpY3RseSBwcm9oaWJpdGVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuIElm
IHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHBsZWFzZSBjb250YWN0IHRoZSBz
ZW5kZXIgYnkgcmV0dXJuIGUtbWFpbCBhbmQgZGVzdHJveSBhbGwgY29waWVzIG9mIHRoZSBvcmln
aW5hbCBtZXNzYWdlLg0K


From nobody Wed Mar  8 07:47:06 2017
Return-Path: <lear@cisco.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 60B8612952B for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 07:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 OpMR5O7-eXE4 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 07:47:02 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18FDC12966C for <T2TRG@irtf.org>; Wed,  8 Mar 2017 07:47:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18604; q=dns/txt; s=iport; t=1488988022; x=1490197622; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=k2oKcMSAIOKuuy1qV1AKTU7pt1pr8yW3ZbY+7qVY+pk=; b=POnRktuN/nO+vjXHEZ8AwBQQG1J1RhhPWGaAOJRv0xlgZ4U8cSTCXzZ+ z+/wMAC62CNL/TMA9smUHUzAsMAAslhyDOaqTFWIeMd1+a99E1Mev23Hi RvDiF5N9zcSqdcbFvnHAoO1HG0ao1pCBBSWQOMwARNCQvmuUrdr+gFl9B s=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CYBgCcJsBY/xbLJq1VCRkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMngQsDJ2CDYIoMc5BZkAuFLYINHwEKgkKDNgKCfhgBAgEBAQE?= =?us-ascii?q?BAQFrKIUVAQEBAQIBAQEhRQYLBQcECxEEAQEBJwMCAicfCQgGAQwGAgEBiWMDD?= =?us-ascii?q?QgOsDiCJiuKVAEBAQEBAQEBAQEBAQEBAQEBAQEBAQ4KBYhTgWGBCYJRgVyDLYJ?= =?us-ascii?q?fBZV6hjyDeIIJjDeBe4UjgzGGUZM+HziBAyIVCBcVP4ZVPzWKEwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.36,264,1486425600";  d="asc'?scan'208,217";a="653113128"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2017 15:46:59 +0000
Received: from [10.61.175.247] ([10.61.175.247]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v28Fkwv4010872; Wed, 8 Mar 2017 15:46:59 GMT
To: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com> <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net> <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com>
Date: Wed, 8 Mar 2017 16:46:58 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0bKug3gQeqpwG98eoGRVIfOuhviejjD1V"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/sWW_ED2HgU9xY1y2UcPPOaNU1cI>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 15:47:04 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--0bKug3gQeqpwG98eoGRVIfOuhviejjD1V
Content-Type: multipart/mixed; boundary="QVRBQN9W5sOeWdPXUiCf7Bb7Kg3vXDGkl";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>,
 Hannes Tschofenig <hannes.tschofenig@gmx.net>,
 "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>,
 "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Message-ID: <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
 <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
 <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>
 <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net>
 <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>
In-Reply-To: <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>

--QVRBQN9W5sOeWdPXUiCf7Bb7Kg3vXDGkl
Content-Type: multipart/alternative;
 boundary="------------630D2CB5852EE2074B57136C"

This is a multi-part message in MIME format.
--------------630D2CB5852EE2074B57136C
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Oscar,

That's a great document.  In some ways, it's really several documents
all rolled up into one.  But Let me ask some leading questions:

  * Is my network-connected refrigerator a Thing or a component?
  * Is the thermostat in my network-connected refrigerator a Thing or a
    component?
  * Is my network-connected car a Thing or a component?
  * Is the engine that sits on the CAN bus a Thing or a component?

What distinguishes a Thing from a component and when do your security
considerations apply, and when do they not?

Eliot


On 3/8/17 4:31 PM, Garcia-Morchon O, Oscar wrote:
> Hi Hannes,
>
> the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols.  =
But I do not think that we do this happily but seriously. Summarizing exi=
sting protocols/work is one of the goals of the document.
>
> The document also acknowledges that devices have different capabilities=
 and requirements, also in terms of security. In my view, this fits with =
the idea of minimum requirements. It would be great to have your input on=
 your use cases and your views on minimum assumptions in different deploy=
ment scenarios/security capabilities of different types of devices.
>
> Cheers, Oscar.
>
>
> -----Original Message-----
> From: T2TRG [mailto:t2trg-bounces@irtf.org] On Behalf Of Hannes Tschofe=
nig
> Sent: Wednesday, March 8, 2017 3:13 PM
> To: Eliot Lear <lear@cisco.com>; Kovatsch, Matthias <matthias.kovatsch@=
siemens.com>; mcr+ietf@sandelman.ca
> Cc: T2TRG@irtf.org
> Subject: Re: [T2TRG] RESTful Design & Security
>
> Hi Eliot,
>
> this would indeed be a good conversation to have. I have tried to trigg=
er it a couple of times in context of the IoT device classes but it is ve=
ry hard to get people to state what their minimum assumptions are.
>
> I believe it has to do with the type of standardization approach we are=
 exercising today and this gives us a hard time to describe the big pictu=
re of how the various building blocks are supposed to work together. In f=
act, the picture becomes extremely complex and fragmented since there are=
 just so many options while at the same time we envision super constraine=
d devices. The T2TRG security document
> (draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about=
 normal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.
>
> Ciao
> Hannes
>
> On 03/08/2017 11:02 AM, Eliot Lear wrote:
>> Matthias,
>>
>> I think the key question that everyone seems to be dancing around is t=
his:
>>
>> What is an Internet host in the context of IoT?  What are the minimum
>> qualities it must possess?  I don't mean this to be a vote, but more
>> of a law of physics sort of thing.  For instance, does a host have a
>> secure unique identity?  What capabilities must it have?  I would
>> expect them to be very few, but there are assuredly some...
>>
>> Eliot
>>
>>
>> On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
>>> Fair enough.
>>>
>>> Yes, I am on this IoT Directorate. I would say a large fraction of
>>> the T2TRG participants has been arguing that the Internet of Gateways=

>>> is not a good approach. Your security-related summary proves this poi=
nt.
>>>
>>> I personally don't see end-to-end security happening if we keep
>>> mixing application protocols, keep using black-magic middleboxes, and=

>>> keep using proprietary interfaces at the device level. We need
>>> something end-to-end (or T2T) for end-to-end security.
>>>
>>> Best wishes
>>> Matthias
>>>
>>>
>>>
>>> Sent from my phone, limitations might apply.
>>>
>>> -----Original Message-----
>>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>> *Received:* Tuesday, 07 Mar 2017, 20:10
>>> *To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
>>> [matthias.kovatsch@siemens.com]; mcr+ietf@sandelman.ca
>>> [mcr+ietf@sandelman.ca]
>>> *CC:* T2TRG@irtf.org [T2TRG@irtf.org]
>>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>>
>>> Hi Matthias,
>>>
>>> I know that this is a research group and everyone can create whatever=

>>> they want.
>>>
>>> We briefly talked about security at the IoT directorate conference
>>> call and I would be interesting to hear what works and what does not
>>> work for others.
>>>
>>> Ciao
>>> Hannes
>>>
>>>
>>> On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
>>>> On big propaganda tour? :P
>>>>
>>>> Regards
>>>> Matthias
>>>>
>>>>
>>>> Sent from my phone, limitations might apply.
>>>>
>>>> -----Original Message-----
>>>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>>> *Received:* Tuesday, 07 Mar 2017, 19:39
>>>> *To:* Michael Richardson [mcr+ietf@sandelman.ca]
>>>> *CC:* t2trg@irtf.org [T2TRG@irtf.org]
>>>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>>>
>>>> OSCOAP does not work when
>>>>
>>>> * you mix protocols,
>>>> * use a middlebox for some processing interactions (such as data
>>>> aggregation), and
>>>> * when one of the protocols is a non-RESTful protocol, such as BLE
>>> or MQTT.
>>>> Unfortunately, these the use cases we are facing in current IoT
>>>> deployments. For similar reasons we cannot use RFC 8075 either.
>>>>
>>>> Maybe you are seeing different deployment environments.
>>>>
>>>> Ciao
>>>> Hannes
>>>>
>>>> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>>>> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>>>>     > Needless to say that these challenges have also been
>>>>> observed
>>> in other
>>>>>     > protocols as well, such as HTTP and even SIP.
>>>>>
>>>>>     > What is the story for providing application layer security?
>>>>>
>>>>> OSCOAP seems to be end-to-end to me.
>>>>>
>>>>> --
>>>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software
>>>>> Works  -=3D IPv6 IoT consulting =3D-
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> T2TRG mailing list
>>>> T2TRG@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/t2trg
>>>>
>>>
>>>
>>> _______________________________________________
>>> T2TRG mailing list
>>> T2TRG@irtf.org
>>> https://www.irtf.org/mailman/listinfo/t2trg
>
> ________________________________
> The information contained in this message may be confidential and legal=
ly protected under applicable law. The message is intended solely for the=
 addressee(s). If you are not the intended recipient, you are hereby noti=
fied that any use, forwarding, dissemination, or reproduction of this mes=
sage is strictly prohibited and may be unlawful. If you are not the inten=
ded recipient, please contact the sender by return e-mail and destroy all=
 copies of the original message.


--------------630D2CB5852EE2074B57136C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Oscar,</p>
    <p>That's a great document.=C2=A0 In some ways, it's really several
      documents all rolled up into one.=C2=A0 But Let me ask some leading=

      questions:</p>
    <ul>
      <li>Is my network-connected refrigerator a Thing or a component?</l=
i>
      <li>Is the thermostat in my network-connected refrigerator a Thing
        or a component?</li>
      <li>Is my network-connected car a Thing or a component?</li>
      <li>Is the engine that sits on the CAN bus a Thing or a component?<=
/li>
    </ul>
    <p>What distinguishes a Thing from a component and when do your
      security considerations apply, and when do they not?</p>
    <p>Eliot<br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">On 3/8/17 4:31 PM, Garcia-Morchon O,
      Oscar wrote:<br>
    </div>
    <blockquote
cite=3D"mid:d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.p=
hilips.com"
      type=3D"cite">
      <pre wrap=3D"">Hi Hannes,

the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols.  Bu=
t I do not think that we do this happily but seriously. Summarizing exist=
ing protocols/work is one of the goals of the document.

The document also acknowledges that devices have different capabilities a=
nd requirements, also in terms of security. In my view, this fits with th=
e idea of minimum requirements. It would be great to have your input on y=
our use cases and your views on minimum assumptions in different deployme=
nt scenarios/security capabilities of different types of devices.

Cheers, Oscar.


-----Original Message-----
From: T2TRG [<a class=3D"moz-txt-link-freetext" href=3D"mailto:t2trg-boun=
ces@irtf.org">mailto:t2trg-bounces@irtf.org</a>] On Behalf Of Hannes Tsch=
ofenig
Sent: Wednesday, March 8, 2017 3:13 PM
To: Eliot Lear <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:lear@cis=
co.com">&lt;lear@cisco.com&gt;</a>; Kovatsch, Matthias <a class=3D"moz-tx=
t-link-rfc2396E" href=3D"mailto:matthias.kovatsch@siemens.com">&lt;matthi=
as.kovatsch@siemens.com&gt;</a>; <a class=3D"moz-txt-link-abbreviated" hr=
ef=3D"mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>
Cc: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">=
T2TRG@irtf.org</a>
Subject: Re: [T2TRG] RESTful Design &amp; Security

Hi Eliot,

this would indeed be a good conversation to have. I have tried to trigger=
 it a couple of times in context of the IoT device classes but it is very=
 hard to get people to state what their minimum assumptions are.

I believe it has to do with the type of standardization approach we are e=
xercising today and this gives us a hard time to describe the big picture=
 of how the various building blocks are supposed to work together. In fac=
t, the picture becomes extremely complex and fragmented since there are j=
ust so many options while at the same time we envision super constrained =
devices. The T2TRG security document
(draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about n=
ormal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.

Ciao
Hannes

On 03/08/2017 11:02 AM, Eliot Lear wrote:
</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">Matthias,

I think the key question that everyone seems to be dancing around is this=
:

What is an Internet host in the context of IoT?  What are the minimum
qualities it must possess?  I don't mean this to be a vote, but more
of a law of physics sort of thing.  For instance, does a host have a
secure unique identity?  What capabilities must it have?  I would
expect them to be very few, but there are assuredly some...

Eliot


On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
</pre>
        <blockquote type=3D"cite">
          <pre wrap=3D"">Fair enough.

Yes, I am on this IoT Directorate. I would say a large fraction of
the T2TRG participants has been arguing that the Internet of Gateways
is not a good approach. Your security-related summary proves this point.

I personally don't see end-to-end security happening if we keep
mixing application protocols, keep using black-magic middleboxes, and
keep using proprietary interfaces at the device level. We need
something end-to-end (or T2T) for end-to-end security.

Best wishes
Matthias



Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [<a class=3D"moz-txt-link-abbreviated" href=3D"=
mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]
*Received:* Tuesday, 07 Mar 2017, 20:10
*To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
[<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:matthias.kovatsch@s=
iemens.com">matthias.kovatsch@siemens.com</a>]; <a class=3D"moz-txt-link-=
abbreviated" href=3D"mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca<=
/a>
[<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:mcr+ietf@sandelman.=
ca">mcr+ietf@sandelman.ca</a>]
*CC:* <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org=
">T2TRG@irtf.org</a> [<a class=3D"moz-txt-link-abbreviated" href=3D"mailt=
o:T2TRG@irtf.org">T2TRG@irtf.org</a>]
*Subject:* Re: [T2TRG] RESTful Design &amp; Security

Hi Matthias,

I know that this is a research group and everyone can create whatever
they want.

We briefly talked about security at the IoT directorate conference
call and I would be interesting to hear what works and what does not
work for others.

Ciao
Hannes


On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
</pre>
          <blockquote type=3D"cite">
            <pre wrap=3D"">On big propaganda tour? :P

Regards
Matthias


Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [<a class=3D"moz-txt-link-abbreviated" href=3D"=
mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]
*Received:* Tuesday, 07 Mar 2017, 19:39
*To:* Michael Richardson [<a class=3D"moz-txt-link-abbreviated" href=3D"m=
ailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>]
*CC:* <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:t2trg@irtf.org=
">t2trg@irtf.org</a> [<a class=3D"moz-txt-link-abbreviated" href=3D"mailt=
o:T2TRG@irtf.org">T2TRG@irtf.org</a>]
*Subject:* Re: [T2TRG] RESTful Design &amp; Security

OSCOAP does not work when

* you mix protocols,
* use a middlebox for some processing interactions (such as data
aggregation), and
* when one of the protocols is a non-RESTful protocol, such as BLE
</pre>
          </blockquote>
          <pre wrap=3D"">or MQTT.
</pre>
          <blockquote type=3D"cite">
            <pre wrap=3D"">
Unfortunately, these the use cases we are facing in current IoT
deployments. For similar reasons we cannot use RFC 8075 either.

Maybe you are seeing different deployment environments.

Ciao
Hannes

On 03/07/2017 06:39 PM, Michael Richardson wrote:
</pre>
            <blockquote type=3D"cite">
              <pre wrap=3D"">
Hannes Tschofenig <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:hanne=
s.tschofenig@gmx.net">&lt;hannes.tschofenig@gmx.net&gt;</a> wrote:
    &gt; Needless to say that these challenges have also been
observed
</pre>
            </blockquote>
          </blockquote>
          <pre wrap=3D"">in other
</pre>
          <blockquote type=3D"cite">
            <blockquote type=3D"cite">
              <pre wrap=3D"">    &gt; protocols as well, such as HTTP and=
 even SIP.

    &gt; What is the story for providing application layer security?

OSCOAP seems to be end-to-end to me.

--
Michael Richardson <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:mcr+=
IETF@sandelman.ca">&lt;mcr+IETF@sandelman.ca&gt;</a>, Sandelman Software
Works  -=3D IPv6 IoT consulting =3D-



</pre>
            </blockquote>
            <pre wrap=3D"">


_______________________________________________
T2TRG mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2TR=
G@irtf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.irtf.org/mailman/l=
istinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>

</pre>
          </blockquote>
          <pre wrap=3D"">


_______________________________________________
T2TRG mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2TR=
G@irtf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.irtf.org/mailman/l=
istinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>
</pre>
        </blockquote>
        <pre wrap=3D"">
</pre>
      </blockquote>
      <pre wrap=3D"">

________________________________
The information contained in this message may be confidential and legally=
 protected under applicable law. The message is intended solely for the a=
ddressee(s). If you are not the intended recipient, you are hereby notifi=
ed that any use, forwarding, dissemination, or reproduction of this messa=
ge is strictly prohibited and may be unlawful. If you are not the intende=
d recipient, please contact the sender by return e-mail and destroy all c=
opies of the original message.
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------630D2CB5852EE2074B57136C--

--QVRBQN9W5sOeWdPXUiCf7Bb7Kg3vXDGkl--

--0bKug3gQeqpwG98eoGRVIfOuhviejjD1V
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJYwCdyAAoJEIe2a0bZ0nozjbsH/jzpKvWP5DI2RCGrL5xwJxCu
wXXHWqWiNQNZEesLsvCjhbs0KCUxS+JKXuNzYKqSWnCMd4dawu0HqhOksd9F5ojL
H4LkutvH0C91biPOQJXaq5CSfepENOcytNAuEubMBfgrO9JrEkorQy4GB1HX7HQm
1v+JxC9f5XMeVbTxKxS/8kJhH4ih/1Tx7z2rRaRPd12vxt+AkvLwAH7BRJHHnPy1
phOL8oMompzmMhlTbHqW0yYZrMDpjQOG5wL0knia/0TvowCcnfFA16GXxRxQKNJo
6YfTF749uVYMds+nxIQamekmpaDZkuBxkYvUMWQDM7r85mRIjN85/iAmiGBSZk8=
=6o3b
-----END PGP SIGNATURE-----

--0bKug3gQeqpwG98eoGRVIfOuhviejjD1V--


From nobody Wed Mar  8 11:15:13 2017
Return-Path: <hannes.tschofenig@gmx.net>
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 D926D129524 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 11:15:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 e4deYdbH9no0 for <t2trg@ietfa.amsl.com>; Wed,  8 Mar 2017 11:15:10 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C51BD129464 for <T2TRG@irtf.org>; Wed,  8 Mar 2017 11:15:09 -0800 (PST)
Received: from [192.168.91.177] ([80.92.114.23]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M9KR0-1cyNHf0nUc-00ChGM; Wed, 08 Mar 2017 20:14:53 +0100
To: Carsten Bormann <cabo@tzi.org>, =?UTF-8?Q?G=c3=b6ran_Selander?= <goran.selander@ericsson.com>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <D4E5582E.78797%goran.selander@ericsson.com> <DE24E6F2-4B93-4507-AD43-E490B81B7E66@tzi.org>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <24c2c77b-27dd-9a58-7ffb-f6d38db2aaa9@gmx.net>
Date: Wed, 8 Mar 2017 20:14:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <DE24E6F2-4B93-4507-AD43-E490B81B7E66@tzi.org>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cSh77gnPNNeRsHd5wmXM6RgGbdlDAb9fd"
X-Provags-ID: V03:K0:/vZKbhUKfCTWav8NoM8BFFG3K//umXdcH3CE338+Vqps9ErLWjv amw4xuDS3Qm+kZieqPBUdty3UL67DQCt6ewmbssaHfiVYYpXHaqyLUfAxDObAj9v8rfe0V4 83kqZ7xhrpacoOZFowQ0ntA7cflKyarffvqn5q4EvQn9I1dIcpePXbQtH8KNSW0pEsG2Zum NHUssFGbf1Kp7fb/x7V8g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:i9ohR1Z6Vnw=:+pwjlzcsOotxnG1B/y1PR1 hfFaYhL79nVX5HdkA3794RdrXoOGG6X3IFctVl4Ktz9rsssHtcEeWFozDiKSqVkwynngdMKv3 LzwSCXsKgyTc8wE8/ispIH5DRHXF0JGcxpGRkUwtnVrhjkbFY1+Y604qm70hPTCDqi6LovjK+ BQAqcvLwlNBHEwRFjixnJtn13tuppVS8WfGgQW8KaQVEDKAC2fhGfXYo9T9PmkfvdhwpnjxbR fc6dmaycYfOpDs8qoDDmuCMmE/102AlL9aFHeMuShwkPDuEUbGn45luMCDj1zrukUjjeRDYRp hXNi0TlcXQQq86jqQCpQjKDqp1i+5yPPzzzPai/mUAcb3YNb/oBJFZAvY99Lthtd9VSotF2sV yOZMnXPNcyWPNrZ1+CDM+CdYpQFe9QZySRWEYpIxZS6DnCaTsc1IDFIMMQTtamR/ZJE5+fTz9 SCZhfppY3p47qVKGKfpqcb2wePUvostedM2V+ovWxtfv6QTvLrqKQ4eB1hxvIkHWWZRqkUX+S 7u5Z9hODKfDCvDDZGERt9s7NEp5pEoC/r6j4VABlCprxjf7+Z/ImpybLL8a4LW9tE/d166ykF ldrLaOLhz9ZzUXMm+y99dvBeE52+opmX3nLqEqRMhXWQVq92144PTzfKqeo+6XIORyTIz6aA0 nQiRyblrCApSYMYFZUGjyAjSqfwiE88eTDFYsFTALv56LuZBBqmxvGVjhlzBbBT0iAgxsmiMK jP7XUaZ0zXl0X6VlXUWa6lS72cVQiev0AGYfcOJSXbdSGxFaWW/Mf67d2qY=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/6HYHsP3Mf6BMcwe8pmDJqXypwqA>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "t2trg@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 08 Mar 2017 19:15:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--cSh77gnPNNeRsHd5wmXM6RgGbdlDAb9fd
Content-Type: multipart/mixed; boundary="snLspw5BiBn8UsO74w9Ese5Dg9D7UbEgJ";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: Carsten Bormann <cabo@tzi.org>,
 =?UTF-8?Q?G=c3=b6ran_Selander?= <goran.selander@ericsson.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>,
 "t2trg@irtf.org" <T2TRG@irtf.org>
Message-ID: <24c2c77b-27dd-9a58-7ffb-f6d38db2aaa9@gmx.net>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <D4E5582E.78797%goran.selander@ericsson.com>
 <DE24E6F2-4B93-4507-AD43-E490B81B7E66@tzi.org>
In-Reply-To: <DE24E6F2-4B93-4507-AD43-E490B81B7E66@tzi.org>

--snLspw5BiBn8UsO74w9Ese5Dg9D7UbEgJ
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Carsten,

an additional consideration is that confidentiality protection of the
payload still reveals a lot of information about what is being accessed
via the URI.

Ciao
Hannes

On 03/08/2017 11:08 AM, Carsten Bormann wrote:
> On 8 Mar 2017, at 09:30, G=C3=B6ran Selander <goran.selander@ericsson.c=
om>
> wrote:
>>=20
>> 1. Apply security above the web transfer layer, i.e. to CoAP/HTTP
>> payload, e.g. by wrapping the payload in the COSE format. In this
>> case the secure COSE object is independent of web transfer
>> mechanism so you can switch between e.g. HTTP and CoAP. However,
>> the web transfer metadata, including e.g. the RESTful method,
>> resource etc. is not protected. This is anyway useful if the
>> method/resource etc. is implicit or the application provides the
>> context, e.g. CoAP pub/sub.
>=20
> Apart from the HTTPS straightjacket I just discussed, this is the
> other interesting design issue about RESTful security.
>=20
> Should we design all objects being interchanged in such a way that
> they can be signed by themselves, which implies that they don=E2=80=99t=
 need
> context to interpret them?
>=20
> E.g., if I
>=20
> GET coap://bathroom.cabo.space/temperature
>=20
> a typical result in a REST world might be a CBOR or JSON object
> saying
>=20
> [{"u":"Cel","v":23.125}]
>=20
> But there is no point in signing that object by itself; it does not
> mean anything useful.
>=20
> A signed object would need to include the fact that this is about my
> bathroom, and some freshness information (such as the current time).
> If you don=E2=80=99t want to use absolute time for freshness, you would=

> include a request nonce, which makes this object useless for a
> different request, so you might as well bind it to the request in
> other ways (e.g., include the URI instead of some generic semantic
> information tying this to my bathroom).
>=20
> The OSCOAP approach is to simply bind responses to the relevant
> information in the request, so all this happens =E2=80=9Cautomatically=E2=
=80=9D (you
> wish).
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> _______________________________________________ T2TRG mailing list=20
> T2TRG@irtf.org https://www.irtf.org/mailman/listinfo/t2trg
>=20


--snLspw5BiBn8UsO74w9Ese5Dg9D7UbEgJ--

--cSh77gnPNNeRsHd5wmXM6RgGbdlDAb9fd
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYwFgqAAoJEGhJURNOOiAtLKoH/iTdgsHUbsC2fSpXKGDiol+G
Dz6b+fd78Zk1kzcu71JaHRDT8oJqsek7DsqVN9YexAtc96K8osPpeZHMTBPat84P
0FdFH0/wCNqU7QFUWZSq+INecvJuTWuejBWeURACM+3j6xn2scQehBYlPd12QECF
6s5IkqBzzQyPpW9GrhtSG8nMl3LzGVbZaMWwDRMyB16nC0Fe6olurZ9qtyVuF03+
0YLlLpVZaOSgY29PZu2+CccWrKQCQYD2qL61tXbxN6/Yusp9EFjrvE49Cppa9/5r
QLk+IFfynj+IH8Pz93WwVNacmCEAs2T+zwYHbC6aNLSLNwdc2rDMNN47Gg/Lmio=
=Sp0s
-----END PGP SIGNATURE-----

--cSh77gnPNNeRsHd5wmXM6RgGbdlDAb9fd--


From nobody Thu Mar  9 00:54:05 2017
Return-Path: <ari.keranen@ericsson.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 225901294BE for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 00:54:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 9ZdfvVp6Krqn for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 00:54:03 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 BE12B1294BB for <t2trg@irtf.org>; Thu,  9 Mar 2017 00:54:02 -0800 (PST)
X-AuditID: c1b4fb30-45bff70000007a5b-2b-58c11828f2dd
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by  (Symantec Mail Security) with SMTP id 80.55.31323.82811C85; Thu,  9 Mar 2017 09:54:01 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0319.002; Thu, 9 Mar 2017 09:53:59 +0100
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: T2TRG Amsterdam work meeting remote participation 
Thread-Index: AQHSmLKxQXGu18IGO0WmFk7THJkMCw==
Date: Thu, 9 Mar 2017 08:53:59 +0000
Message-ID: <FF7415BD-E3F2-408F-9502-8B2BE1EE749F@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B8E34C2AD2272049A1F6BE72998DFCDD@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyM2K7oq6mxMEIgyZ5i/cPelgcGD0mbzzM FsAYxWWTkpqTWZZapG+XwJWx6tc+loIPjBVvF31nbmA8xNjFyMEhIWAi0TLdtIuRi0NIYB2j xJd5NxghnEWMEt2/57F1MXJysAnYS0xe85ERxBYRUJXYOHMjK4gtLGAtcf/bZRaIuIPEpwdf oWw9ibdXn4PZLAIqEs0r3oDZvEBzZjW+B5vJKCAm8f3UGiYQm1lAXOLWk/lgtoSAgMSSPeeZ IWxRiZeP/7FC2EoSi25/hqrXk7gxdQobhG0tMaPjNTOErS2xbCGEzSsgKHFy5hOWCYzCs5Cs mIWkfRaS9llI2mchaV/AyLqKUbQ4tTgpN93ISC+1KDO5uDg/Ty8vtWQTIzDwD275bbCD8eVz x0OMAhyMSjy8BTIHIoRYE8uKK3MPMUpwMCuJ8O66BBTiTUmsrEotyo8vKs1JLT7EKM3BoiTO a7byfriQQHpiSWp2ampBahFMlomDU6qBceNK21lbzxZM/n+PM/v5v7/1ap0Gdfm3Sr4ffcn3 uOYKY4yrq/TE8y+UOZmUr8QedPiZxeDsv+/J429nX/ZFFJzYWBnaruReWCbhxcF/muHZDPGv 8W9mS8TaJU76uUGk3bbdsD3vg2NZ5vSHX69v+zOr7clm/k1bdyrxn/x60nDqac099+pT5iux FGckGmoxFxUnAgA91t0TeAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/7O2mIuyhtlvsd8rPWMOkVK8_-Gg>
Subject: [T2TRG] T2TRG Amsterdam work meeting remote participation
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 08:54:04 -0000

Hi,

Here's a link to Google hangout for remote participants:
https://hangouts.google.com/call/hirgqs7nl5ashoxqyfeakahezme

However, the Wi-Fi seems to be quite flaky and limited bandwidth so quality=
 may vary.



Cheers,
Ari=


From nobody Thu Mar  9 01:10:19 2017
Return-Path: <ari.keranen@ericsson.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 3B651129438 for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 01:10:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 ic7CtgOPMzrH for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 01:10:17 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 A4E451293EE for <t2trg@irtf.org>; Thu,  9 Mar 2017 01:10:16 -0800 (PST)
X-AuditID: c1b4fb25-4c7ff70000007fa8-78-58c11bf690d3
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id 9E.58.32680.6FB11C85; Thu,  9 Mar 2017 10:10:15 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Thu, 9 Mar 2017 10:10:13 +0100
From: =?utf-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: T2TRG Amsterdam work meeting remote participation 
Thread-Index: AQHSmLKxADJExsmFn0iq3HcsDIiFNqGMJ8KA
Date: Thu, 9 Mar 2017 09:10:13 +0000
Message-ID: <B62713B9-ECB0-4132-AA06-2AF975938154@ericsson.com>
References: <FF7415BD-E3F2-408F-9502-8B2BE1EE749F@ericsson.com>
In-Reply-To: <FF7415BD-E3F2-408F-9502-8B2BE1EE749F@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8509D9E9312E694EAD7A5E4397815FD9@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2J7oO536YMRBtufMFq8f9DD4sDoMXnj YbYAxigum5TUnMyy1CJ9uwSujA3/H7IWnGGt+Hh8HlMD4w7WLkZODgkBE4nr+1axdzFycQgJ rGOUWHmvjxXCWcQosWfZRHaQKjYBW4knrfvAOkQEVCU2ztwIZgsL2Ess+TCfBSLuIPHpwVco 20ji3faDjCA2i4CKRP/WA2BxXqD6jXcfgfUKAdmXrkxiBrE5gXo37v/EBmIzCohJfD+1hgnE ZhYQl7j1ZD4TxKUCEkv2nGeGsEUlXj7+B/WBksTaw9uB5nMA1WtKrN+lD9FqLfFi/nGoMYoS U7ofskOcIChxcuYTlgmMorOQbJiF0D0LSfcsJN2zkHQvYGRdxShanFqclJtuZKyXWpSZXFyc n6eXl1qyiREYKQe3/FbdwXj5jeMhRgEORiUe3gKZAxFCrIllxZW5hxglOJiVRHgvfN0fIcSb klhZlVqUH19UmpNafIhRmoNFSZzXbOX9cCGB9MSS1OzU1ILUIpgsEwenVANjYuJxi83JEi3N OQHzja8vSlshuDmUV2t/5Xsdtt+Kh960K+RsnblZ8v9q29gV7w6dP7rLJEGw2F3mV1lFxzbR 5Hed6heahO+9uK364c1z4y3X9sSFNYa7SD2c+XfunX0Jzu+8818L/55Y6vVktbNzT8r3LeJe 0pPzVd4+v2Z26PHPdvV/r5YfUGIpzkg01GIuKk4EAKBeOtCQAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/HuaQWhIlBa7vSc1odNtMGb2dJ4o>
Subject: Re: [T2TRG] T2TRG Amsterdam work meeting remote participation
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 09:10:18 -0000

QW5kIGxpdmUgbWVldGluZyBtaW51dGVzOg0KaHR0cHM6Ly9kb2NzLmdvb2dsZS5jb20vZG9jdW1l
bnQvZC8xT3dmYmEtYlZfaVZoakJuV3lhOVIzNGpNOGFpeE41OENBSGlyTkk4dVFjUS9lZGl0P3Vz
cD1zaGFyaW5nDQoNCihhYm91dCB0byBzdGFydCBpbiBmZXcgbWludXRlcykNCg0KDQpDaGVlcnMs
DQpBcmkNCg0KPiBPbiAwOSBNYXIgMjAxNywgYXQgMDk6NTMsIEFyaSBLZXLDpG5lbiA8YXJpLmtl
cmFuZW5AZXJpY3Nzb24uY29tPiB3cm90ZToNCj4gDQo+IEhpLA0KPiANCj4gSGVyZSdzIGEgbGlu
ayB0byBHb29nbGUgaGFuZ291dCBmb3IgcmVtb3RlIHBhcnRpY2lwYW50czoNCj4gaHR0cHM6Ly9o
YW5nb3V0cy5nb29nbGUuY29tL2NhbGwvaGlyZ3FzN25sNWFzaG94cXlmZWFrYWhlem1lDQo+IA0K
PiBIb3dldmVyLCB0aGUgV2ktRmkgc2VlbXMgdG8gYmUgcXVpdGUgZmxha3kgYW5kIGxpbWl0ZWQg
YmFuZHdpZHRoIHNvIHF1YWxpdHkgbWF5IHZhcnkuDQo+IA0KPiANCj4gDQo+IENoZWVycywNCj4g
QXJpDQoNCg==


From nobody Thu Mar  9 05:40:15 2017
Return-Path: <ari.keranen@ericsson.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 A713D129604 for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 05:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 D_pfENwIyw7J for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 05:40:13 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 F078E129600 for <t2trg@irtf.org>; Thu,  9 Mar 2017 05:40:12 -0800 (PST)
X-AuditID: c1b4fb2d-2eaca9800000290a-80-58c15b3a9997
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id 17.C7.10506.A3B51C85; Thu,  9 Mar 2017 14:40:11 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0319.002; Thu, 9 Mar 2017 14:40:08 +0100
From: =?utf-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: T2TRG Amsterdam work meeting remote participation 
Thread-Index: AQHSmLKxADJExsmFn0iq3HcsDIiFNqGMJ8KAgABLaYA=
Date: Thu, 9 Mar 2017 13:40:08 +0000
Message-ID: <17088D06-F695-42D9-A502-9913B3C98AD0@ericsson.com>
References: <FF7415BD-E3F2-408F-9502-8B2BE1EE749F@ericsson.com> <B62713B9-ECB0-4132-AA06-2AF975938154@ericsson.com>
In-Reply-To: <B62713B9-ECB0-4132-AA06-2AF975938154@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A8E0A620C7EB0842A997A5E7CB0EA8D2@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2K7h6519MEIg94ZfBbvH/SwODB6TN54 mC2AMYrLJiU1J7MstUjfLoErY8fB0+wFGzgqWraFNzBO4ehi5OSQEDCRePVgDmsXIxeHkMA6 RolJnyYyQziLGCV2HLnFAlLFJmAr8aR1HyuILSKgKrFx5kYwW1jAXmLJh/ksEHEHiU8PvkLZ VhKb9x1gA7FZBFQkHj84wwxi8wLVz+p6zg5iCwmUSnyetxOsnhOo98qiTrAaRgExie+n1jCB 2MwC4hK3nsxngrhUQGLJnvPMELaoxMvH/1ghbCWJxiVPgGwOoHpNifW79CFarSU2nmlmhbAV JaZ0P2SHOEFQ4uTMJywTGEVnIdkwC6F7FpLuWUi6ZyHpXsDIuopRtDi1uDg33chYL7UoM7m4 OD9PLy+1ZBMjME4Obvmtu4Nx9WvHQ4wCHIxKPLwFMgcihFgTy4orcw8xSnAwK4nw7roEFOJN SaysSi3Kjy8qzUktPsQozcGiJM5rtvJ+uJBAemJJanZqakFqEUyWiYNTqoHR4rT5g/Of5K+a 6Ma2P2NbFiB7l+v7N4anQtsPrdZkXuC05nbh7XvllzP5di8LrfkaZKbVeH77uWf63rXPhLct yj61I0dzx7TPAVLOwak6nh2Z3VnlXxnmc3/5smzLpzdLHr2q9G+Q5JSPb+WW83l38FTu1rI7 n3VlCk0nFSeY7fx2+ZrvnuIlSizFGYmGWsxFxYkAXmBjI48CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/P9yCkmEbSYECMWyGOwcLF6QBFWI>
Subject: Re: [T2TRG] T2TRG Amsterdam work meeting remote participation
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 13:40:14 -0000

U2VlbXMgdGhlIEdvb2dsZSBoYW5nb3V0IHNlc3Npb24gZGllZCBkdXJpbmcgbHVuY2ggYnJlYWss
IGJ1dCB3ZSBhcmUgbm93IGFib3V0IHRvIGNvbnRpbnVlLiBUaGUgbGluayBiZWxvdyBzaG91bGQg
c3RpbGwgd29yay4NCg0KDQpDaGVlcnMsDQpBcmkNCg0KPiBPbiAwOSBNYXIgMjAxNywgYXQgMTA6
MTAsIEFyaSBLZXLDpG5lbiA8YXJpLmtlcmFuZW5AZXJpY3Nzb24uY29tPiB3cm90ZToNCj4gDQo+
IEFuZCBsaXZlIG1lZXRpbmcgbWludXRlczoNCj4gaHR0cHM6Ly9kb2NzLmdvb2dsZS5jb20vZG9j
dW1lbnQvZC8xT3dmYmEtYlZfaVZoakJuV3lhOVIzNGpNOGFpeE41OENBSGlyTkk4dVFjUS9lZGl0
P3VzcD1zaGFyaW5nDQo+IA0KPiAoYWJvdXQgdG8gc3RhcnQgaW4gZmV3IG1pbnV0ZXMpDQo+IA0K
PiANCj4gQ2hlZXJzLA0KPiBBcmkNCj4gDQo+PiBPbiAwOSBNYXIgMjAxNywgYXQgMDk6NTMsIEFy
aSBLZXLDpG5lbiA8YXJpLmtlcmFuZW5AZXJpY3Nzb24uY29tPiB3cm90ZToNCj4+IA0KPj4gSGks
DQo+PiANCj4+IEhlcmUncyBhIGxpbmsgdG8gR29vZ2xlIGhhbmdvdXQgZm9yIHJlbW90ZSBwYXJ0
aWNpcGFudHM6DQo+PiBodHRwczovL2hhbmdvdXRzLmdvb2dsZS5jb20vY2FsbC9oaXJncXM3bmw1
YXNob3hxeWZlYWthaGV6bWUNCj4+IA0KPj4gSG93ZXZlciwgdGhlIFdpLUZpIHNlZW1zIHRvIGJl
IHF1aXRlIGZsYWt5IGFuZCBsaW1pdGVkIGJhbmR3aWR0aCBzbyBxdWFsaXR5IG1heSB2YXJ5Lg0K
Pj4gDQo+PiANCj4+IA0KPj4gQ2hlZXJzLA0KPj4gQXJpDQo+IA0KDQo=


From nobody Thu Mar  9 05:48:50 2017
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 8C1EF129615 for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 05:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 fA3NSSngbbDV for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 05:48:47 -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 6BBF1129613 for <t2trg@irtf.org>; Thu,  9 Mar 2017 05:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v29Dmisq003897 for <t2trg@irtf.org>; Thu, 9 Mar 2017 14:48:44 +0100 (CET)
Received: from sev.lan (ip4da8b3cb.direct-adsl.nl [77.168.179.203]) (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 3vfBZ36YCGzDH3q; Thu,  9 Mar 2017 14:48:43 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <17088D06-F695-42D9-A502-9913B3C98AD0@ericsson.com>
Date: Thu, 9 Mar 2017 14:48:43 +0100
X-Mao-Original-Outgoing-Id: 510760122.893738-602072778f35da2bcbaaea1d599ad226
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E254046-4FA7-4810-B4B6-DDD9D96F3C5E@tzi.org>
References: <FF7415BD-E3F2-408F-9502-8B2BE1EE749F@ericsson.com> <B62713B9-ECB0-4132-AA06-2AF975938154@ericsson.com> <17088D06-F695-42D9-A502-9913B3C98AD0@ericsson.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/qXOCAoOUrfCBYjvvc3P3K4bIRL8>
Subject: Re: [T2TRG] T2TRG Amsterdam work meeting remote participation
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 13:48:49 -0000

We did get a few weird effects here =E2=80=94 please try again if =
re-joining failed.

Gr=C3=BC=C3=9Fe, Carsten

> On 9 Mar 2017, at 14:40, Ari Ker=C3=A4nen <ari.keranen@ericsson.com> =
wrote:
>=20
> Seems the Google hangout session died during lunch break, but we are =
now about to continue. The link below should still work.
>=20
>=20
> Cheers,
> Ari
>=20
>> On 09 Mar 2017, at 10:10, Ari Ker=C3=A4nen <ari.keranen@ericsson.com> =
wrote:
>>=20
>> And live meeting minutes:
>> =
https://docs.google.com/document/d/1Owfba-bV_iVhjBnWya9R34jM8aixN58CAHirNI=
8uQcQ/edit?usp=3Dsharing
>>=20
>> (about to start in few minutes)
>>=20
>>=20
>> Cheers,
>> Ari
>>=20
>>> On 09 Mar 2017, at 09:53, Ari Ker=C3=A4nen =
<ari.keranen@ericsson.com> wrote:
>>>=20
>>> Hi,
>>>=20
>>> Here's a link to Google hangout for remote participants:
>>> https://hangouts.google.com/call/hirgqs7nl5ashoxqyfeakahezme
>>>=20
>>> However, the Wi-Fi seems to be quite flaky and limited bandwidth so =
quality may vary.
>>>=20
>>>=20
>>>=20
>>> Cheers,
>>> Ari
>>=20
>=20
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg
>=20
>=20


From nobody Thu Mar  9 06:28:08 2017
Return-Path: <mohit.m.sethi@ericsson.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 042A8128AC9 for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 06:28:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 sge5F3SqG3Gt for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 06:28:04 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 B898C129633 for <T2TRG@irtf.org>; Thu,  9 Mar 2017 06:28:03 -0800 (PST)
X-AuditID: c1b4fb2d-2eaca9800000290a-fd-58c166711d79
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by  (Symantec Mail Security) with SMTP id 0D.B3.10506.17661C85; Thu,  9 Mar 2017 15:28:01 +0100 (CET)
Received: from nomadiclab.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.23) with Microsoft SMTP Server id 14.3.319.2; Thu, 9 Mar 2017 15:27:56 +0100
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 59D7D4EE5E;	Thu,  9 Mar 2017 16:29:45 +0200 (EET)
Received: from [127.0.0.1] (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id ADE8D4E94F;	Thu,  9 Mar 2017 16:29:44 +0200 (EET)
To: Eliot Lear <lear@cisco.com>, "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com> <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net> <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com> <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com>
From: Mohit Sethi <mohit.m.sethi@ericsson.com>
Message-ID: <89276160-ad20-bc9b-0cbd-c3e1f647dc1e@ericsson.com>
Date: Thu, 9 Mar 2017 16:27:55 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com>
Content-Type: multipart/alternative; boundary="------------2B25B145CDCBFB10E518BA7A"
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDIsWRmVeSWpSXmKPExsUyM2K7qG5h2sEIgy0zjCyW7rzHavH1XweL ReOEF4wWPYf62S0a7lxgsXj/oIfFgc1jyu+NrB6LN+1n85i88TCbx4EDu5k8WubsYfbYfnIS UwBbFJdNSmpOZllqkb5dAldGV/NdtoK7Exgrms59Z2tgXFTWxcjJISFgIvFg81GWLkYuDiGB dYwS+2Y8YYZwtjJKvDg1jRXCWcso8XRZNxuEM49RYvbdDawg/cICehJbZuwFqxIR+M0osejM ZHaIqiMsEnca5jCBVDELqErsn9jABmKzAXV0njvODGLzCthLLHg1AWwSi4CKxLzVz8HiogIR EvOfrmKCqBGUODnzCdCFHBycArYSL/6JQIwMk9j4ahsbxBNqElfPbQJrFRJQl9jacYBxAqPQ LCTds5C0zAKaxAy0+cHWMoiwvMT2t3OYIWx9iet37rPCxJu3zmZewMi2ilG0OLW4ODfdyFgv tSgzubg4P08vL7VkEyMwzg5u+a27g3H1a8dDjAIcjEo8vAUyByKEWBPLiitzDzFKcDArifDu ugQU4k1JrKxKLcqPLyrNSS0+xCjNwaIkzmu28n64kEB6YklqdmpqQWoRTJaJg1OqgVHAYfkr rbn7Y6edPOd4ifXSzjamyIysqyd0uiYYrNG2uRPuJud9+sZ0p2tpSiLpN/8LvKnfmdei7O54 8sRjLsHVa/J/fDFxZm+9+sL0Ff+H43GZLyIiTKb7XVhbyyS4TE35Uskr2x9tuulKU8/PUZJb EFvKpDz1X87R5bxhQkqsAke/Z5za6KLEUpyRaKjFXFScCAAC/RzHrwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/JPa0u1fIZUVuc_DFeiKAxAK8v3k>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 14:28:06 -0000

--------------2B25B145CDCBFB10E518BA7A
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit

Hi Elliot

I wonder what difference does it make if we call something a thing, 
component, device, or machine. We have the terms thing-to-thing, 
device-to-device and machine-to-machine communication from different 
(standards) folks.

I would believe that if a thing is connected to another thing or 
network, then the security considerations apply.

Thanks
Mohit


On 03/08/2017 05:46 PM, Eliot Lear wrote:
>
> Oscar,
>
> That's a great document.  In some ways, it's really several documents 
> all rolled up into one.  But Let me ask some leading questions:
>
>   * Is my network-connected refrigerator a Thing or a component?
>   * Is the thermostat in my network-connected refrigerator a Thing or
>     a component?
>   * Is my network-connected car a Thing or a component?
>   * Is the engine that sits on the CAN bus a Thing or a component?
>
> What distinguishes a Thing from a component and when do your security 
> considerations apply, and when do they not?
>
> Eliot
>
>
> On 3/8/17 4:31 PM, Garcia-Morchon O, Oscar wrote:
>> Hi Hannes,
>>
>> the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols.  But I do not think that we do this happily but seriously. Summarizing existing protocols/work is one of the goals of the document.
>>
>> The document also acknowledges that devices have different capabilities and requirements, also in terms of security. In my view, this fits with the idea of minimum requirements. It would be great to have your input on your use cases and your views on minimum assumptions in different deployment scenarios/security capabilities of different types of devices.
>>
>> Cheers, Oscar.
>>
>>
>> -----Original Message-----
>> From: T2TRG [mailto:t2trg-bounces@irtf.org] On Behalf Of Hannes Tschofenig
>> Sent: Wednesday, March 8, 2017 3:13 PM
>> To: Eliot Lear<lear@cisco.com>; Kovatsch, Matthias<matthias.kovatsch@siemens.com>;mcr+ietf@sandelman.ca
>> Cc:T2TRG@irtf.org
>> Subject: Re: [T2TRG] RESTful Design & Security
>>
>> Hi Eliot,
>>
>> this would indeed be a good conversation to have. I have tried to trigger it a couple of times in context of the IoT device classes but it is very hard to get people to state what their minimum assumptions are.
>>
>> I believe it has to do with the type of standardization approach we are exercising today and this gives us a hard time to describe the big picture of how the various building blocks are supposed to work together. In fact, the picture becomes extremely complex and fragmented since there are just so many options while at the same time we envision super constrained devices. The T2TRG security document
>> (draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about normal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.
>>
>> Ciao
>> Hannes
>>
>> On 03/08/2017 11:02 AM, Eliot Lear wrote:
>>> Matthias,
>>>
>>> I think the key question that everyone seems to be dancing around is this:
>>>
>>> What is an Internet host in the context of IoT?  What are the minimum
>>> qualities it must possess?  I don't mean this to be a vote, but more
>>> of a law of physics sort of thing.  For instance, does a host have a
>>> secure unique identity?  What capabilities must it have?  I would
>>> expect them to be very few, but there are assuredly some...
>>>
>>> Eliot
>>>
>>>
>>> On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
>>>> Fair enough.
>>>>
>>>> Yes, I am on this IoT Directorate. I would say a large fraction of
>>>> the T2TRG participants has been arguing that the Internet of Gateways
>>>> is not a good approach. Your security-related summary proves this point.
>>>>
>>>> I personally don't see end-to-end security happening if we keep
>>>> mixing application protocols, keep using black-magic middleboxes, and
>>>> keep using proprietary interfaces at the device level. We need
>>>> something end-to-end (or T2T) for end-to-end security.
>>>>
>>>> Best wishes
>>>> Matthias
>>>>
>>>>
>>>>
>>>> Sent from my phone, limitations might apply.
>>>>
>>>> -----Original Message-----
>>>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>>> *Received:* Tuesday, 07 Mar 2017, 20:10
>>>> *To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
>>>> [matthias.kovatsch@siemens.com];mcr+ietf@sandelman.ca
>>>> [mcr+ietf@sandelman.ca]
>>>> *CC:*T2TRG@irtf.org  [T2TRG@irtf.org]
>>>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>>>
>>>> Hi Matthias,
>>>>
>>>> I know that this is a research group and everyone can create whatever
>>>> they want.
>>>>
>>>> We briefly talked about security at the IoT directorate conference
>>>> call and I would be interesting to hear what works and what does not
>>>> work for others.
>>>>
>>>> Ciao
>>>> Hannes
>>>>
>>>>
>>>> On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
>>>>> On big propaganda tour? :P
>>>>>
>>>>> Regards
>>>>> Matthias
>>>>>
>>>>>
>>>>> Sent from my phone, limitations might apply.
>>>>>
>>>>> -----Original Message-----
>>>>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>>>> *Received:* Tuesday, 07 Mar 2017, 19:39
>>>>> *To:* Michael Richardson [mcr+ietf@sandelman.ca]
>>>>> *CC:*t2trg@irtf.org  [T2TRG@irtf.org]
>>>>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>>>>
>>>>> OSCOAP does not work when
>>>>>
>>>>> * you mix protocols,
>>>>> * use a middlebox for some processing interactions (such as data
>>>>> aggregation), and
>>>>> * when one of the protocols is a non-RESTful protocol, such as BLE
>>>> or MQTT.
>>>>> Unfortunately, these the use cases we are facing in current IoT
>>>>> deployments. For similar reasons we cannot use RFC 8075 either.
>>>>>
>>>>> Maybe you are seeing different deployment environments.
>>>>>
>>>>> Ciao
>>>>> Hannes
>>>>>
>>>>> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>>>>> Hannes Tschofenig<hannes.tschofenig@gmx.net>  wrote:
>>>>>>      > Needless to say that these challenges have also been
>>>>>> observed
>>>> in other
>>>>>>      > protocols as well, such as HTTP and even SIP.
>>>>>>
>>>>>>      > What is the story for providing application layer security?
>>>>>>
>>>>>> OSCOAP seems to be end-to-end to me.
>>>>>>
>>>>>> --
>>>>>> Michael Richardson<mcr+IETF@sandelman.ca>, Sandelman Software
>>>>>> Works  -= IPv6 IoT consulting =-
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> T2TRG mailing list
>>>>> T2TRG@irtf.org
>>>>> https://www.irtf.org/mailman/listinfo/t2trg
>>>>>
>>>>
>>>> _______________________________________________
>>>> T2TRG mailing list
>>>> T2TRG@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/t2trg
>> ________________________________
>> The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
>
>
>
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg


--------------2B25B145CDCBFB10E518BA7A
Content-Type: text/html; charset="windows-1252"
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi Elliot</p>
    <p>I wonder what difference does it make if we call something a
      thing, component, device, or machine. We have the terms
      thing-to-thing, device-to-device and machine-to-machine
      communication from different (standards) folks. <br>
    </p>
    <p>I would believe that if a thing is connected to another thing or
      network, then the security considerations apply.</p>
    <p>Thanks<br>
      Mohit<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 03/08/2017 05:46 PM, Eliot Lear
      wrote:<br>
    </div>
    <blockquote
      cite="mid:2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com"
      type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <p>Oscar,</p>
      <p>That's a great document.  In some ways, it's really several
        documents all rolled up into one.  But Let me ask some leading
        questions:</p>
      <ul>
        <li>Is my network-connected refrigerator a Thing or a component?</li>
        <li>Is the thermostat in my network-connected refrigerator a
          Thing or a component?</li>
        <li>Is my network-connected car a Thing or a component?</li>
        <li>Is the engine that sits on the CAN bus a Thing or a
          component?</li>
      </ul>
      <p>What distinguishes a Thing from a component and when do your
        security considerations apply, and when do they not?</p>
      <p>Eliot<br>
      </p>
      <br>
      <div class="moz-cite-prefix">On 3/8/17 4:31 PM, Garcia-Morchon O,
        Oscar wrote:<br>
      </div>
      <blockquote
cite="mid:d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com"
        type="cite">
        <pre wrap="">Hi Hannes,

the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols.  But I do not think that we do this happily but seriously. Summarizing existing protocols/work is one of the goals of the document.

The document also acknowledges that devices have different capabilities and requirements, also in terms of security. In my view, this fits with the idea of minimum requirements. It would be great to have your input on your use cases and your views on minimum assumptions in different deployment scenarios/security capabilities of different types of devices.

Cheers, Oscar.


-----Original Message-----
From: T2TRG [<a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:t2trg-bounces@irtf.org">mailto:t2trg-bounces@irtf.org</a>] On Behalf Of Hannes Tschofenig
Sent: Wednesday, March 8, 2017 3:13 PM
To: Eliot Lear <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:lear@cisco.com">&lt;lear@cisco.com&gt;</a>; Kovatsch, Matthias <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:matthias.kovatsch@siemens.com">&lt;matthias.kovatsch@siemens.com&gt;</a>; <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>
Cc: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>
Subject: Re: [T2TRG] RESTful Design &amp; Security

Hi Eliot,

this would indeed be a good conversation to have. I have tried to trigger it a couple of times in context of the IoT device classes but it is very hard to get people to state what their minimum assumptions are.

I believe it has to do with the type of standardization approach we are exercising today and this gives us a hard time to describe the big picture of how the various building blocks are supposed to work together. In fact, the picture becomes extremely complex and fragmented since there are just so many options while at the same time we envision super constrained devices. The T2TRG security document
(draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about normal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.

Ciao
Hannes

On 03/08/2017 11:02 AM, Eliot Lear wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">Matthias,

I think the key question that everyone seems to be dancing around is this:

What is an Internet host in the context of IoT?  What are the minimum
qualities it must possess?  I don't mean this to be a vote, but more
of a law of physics sort of thing.  For instance, does a host have a
secure unique identity?  What capabilities must it have?  I would
expect them to be very few, but there are assuredly some...

Eliot


On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">Fair enough.

Yes, I am on this IoT Directorate. I would say a large fraction of
the T2TRG participants has been arguing that the Internet of Gateways
is not a good approach. Your security-related summary proves this point.

I personally don't see end-to-end security happening if we keep
mixing application protocols, keep using black-magic middleboxes, and
keep using proprietary interfaces at the device level. We need
something end-to-end (or T2T) for end-to-end security.

Best wishes
Matthias



Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]
*Received:* Tuesday, 07 Mar 2017, 20:10
*To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
[<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:matthias.kovatsch@siemens.com">matthias.kovatsch@siemens.com</a>]; <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>
[<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>]
*CC:* <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:T2TRG@irtf.org">T2TRG@irtf.org</a> [<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>]
*Subject:* Re: [T2TRG] RESTful Design &amp; Security

Hi Matthias,

I know that this is a research group and everyone can create whatever
they want.

We briefly talked about security at the IoT directorate conference
call and I would be interesting to hear what works and what does not
work for others.

Ciao
Hannes


On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
</pre>
            <blockquote type="cite">
              <pre wrap="">On big propaganda tour? :P

Regards
Matthias


Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]
*Received:* Tuesday, 07 Mar 2017, 19:39
*To:* Michael Richardson [<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>]
*CC:* <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:t2trg@irtf.org">t2trg@irtf.org</a> [<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>]
*Subject:* Re: [T2TRG] RESTful Design &amp; Security

OSCOAP does not work when

* you mix protocols,
* use a middlebox for some processing interactions (such as data
aggregation), and
* when one of the protocols is a non-RESTful protocol, such as BLE
</pre>
            </blockquote>
            <pre wrap="">or MQTT.
</pre>
            <blockquote type="cite">
              <pre wrap="">Unfortunately, these the use cases we are facing in current IoT
deployments. For similar reasons we cannot use RFC 8075 either.

Maybe you are seeing different deployment environments.

Ciao
Hannes

On 03/07/2017 06:39 PM, Michael Richardson wrote:
</pre>
              <blockquote type="cite">
                <pre wrap="">Hannes Tschofenig <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:hannes.tschofenig@gmx.net">&lt;hannes.tschofenig@gmx.net&gt;</a> wrote:
    &gt; Needless to say that these challenges have also been
observed
</pre>
              </blockquote>
            </blockquote>
            <pre wrap="">in other
</pre>
            <blockquote type="cite">
              <blockquote type="cite">
                <pre wrap="">    &gt; protocols as well, such as HTTP and even SIP.

    &gt; What is the story for providing application layer security?

OSCOAP seems to be end-to-end to me.

--
Michael Richardson <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:mcr+IETF@sandelman.ca">&lt;mcr+IETF@sandelman.ca&gt;</a>, Sandelman Software
Works  -= IPv6 IoT consulting =-



</pre>
              </blockquote>
              <pre wrap="">

_______________________________________________
T2TRG mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>

</pre>
            </blockquote>
            <pre wrap="">

_______________________________________________
T2TRG mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>
</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">
________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
</pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
T2TRG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>
<a class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------2B25B145CDCBFB10E518BA7A--


From nobody Thu Mar  9 06:32:46 2017
Return-Path: <oscar.garcia-morchon@philips.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 F2465129465 for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 06:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-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=philips.onmicrosoft.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 Ru7O_uW6E1Px for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 06:32:42 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40134.outbound.protection.outlook.com [40.107.4.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4DC412941E for <T2TRG@irtf.org>; Thu,  9 Mar 2017 06:32:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Philips.onmicrosoft.com; s=selector1-philips-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rbovY0d753yq8UUAzqBBOR4phPgawgNkY27nwa4X9eA=; b=WRssCzJv1yGc+66oBkCGnxlIhvDgdRgnGVxVmjLjt7lGFPJghq95rLLmrLkDBpRTwsCOorm1mOMA9STHm2rP/X5ivRnCws6WTAw95W6EPH37XHgDSFYsxZflTM3ZaWpklMlT19inJS9nr9sdM/yy1RIKfM76vK3KmWtWO8We1x8=
Received: from AM3P122CA0004.EURP122.PROD.OUTLOOK.COM (129.75.100.18) by AM4P122MB0083.EURP122.PROD.OUTLOOK.COM (129.75.167.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12; Thu, 9 Mar 2017 14:32:39 +0000
Received: from DB3FFO11FD030.protection.gbl (2a01:111:f400:7e04::190) by AM3P122CA0004.outlook.office365.com (2603:10a6:221:2::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.12 via Frontend Transport; Thu, 9 Mar 2017 14:32:39 +0000
Authentication-Results: spf=neutral (sender IP is 23.103.247.180) smtp.mailfrom=philips.com; irtf.org; dkim=none (message not signed) header.d=none;irtf.org; dmarc=none action=none header.from=philips.com;
Received-SPF: Neutral (protection.outlook.com: 23.103.247.180 is neither permitted nor denied by domain of philips.com)
Received: from 011-smtp-out.Philips.com (23.103.247.180) by DB3FFO11FD030.mail.protection.outlook.com (10.47.217.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.7 via Frontend Transport; Thu, 9 Mar 2017 14:32:39 +0000
Received: from DB5PR9001MB0165.MGDPHG.emi.philips.com (141.251.190.209) by DB5PR9001MB0167.MGDPHG.emi.philips.com (141.251.190.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.12; Thu, 9 Mar 2017 14:32:38 +0000
Received: from DB5PR9001MB0165.MGDPHG.emi.philips.com ([141.251.190.209]) by DB5PR9001MB0165.MGDPHG.emi.philips.com ([141.251.190.209]) with mapi id 15.01.0933.026; Thu, 9 Mar 2017 14:32:38 +0000
From: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>
To: Eliot Lear <lear@cisco.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpstzow5GSCUy0qO2HV2fKAQj6GJplEAgAAQwQCAAAGWgIAAByCAgAAHRICAAPIBgIAARgCAgAASgzCAAAepAIABH7a8
Date: Thu, 9 Mar 2017 14:32:38 +0000
Message-ID: <03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.philips.com>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com> <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net> <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>, <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com>
In-Reply-To: <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [77.168.179.203]
X-MS-Office365-Filtering-Correlation-Id: 67a61fbe-8f6d-4e17-1b35-08d466f9235a
Content-Type: multipart/alternative; boundary="_000_03443d82f2c94a5cad12978b4a3c54e4DB5PR9001MB0165MGDPHGem_"
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB5PR9001MB0167.MGDPHG.emi.philips.com
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:23.103.247.180; IPV:NLI; CTRY:; EFV:NLI; SFV:NSPM; SFS:(10019020)(39850400002)(39410400002)(39450400003)(39840400002)(39860400002)(2980300002)(24454002)(55904004)(377454003)(199003)(189002)(85714005)(13464003)(374574003)(9170700003)(7736002)(229853002)(108616004)(4326008)(24736003)(50986999)(76176999)(38730400002)(33646002)(7906003)(606005)(54356999)(53936002)(3846002)(102836003)(106466001)(7696004)(6116002)(512934002)(8936002)(8676002)(84326002)(6306002)(31430400001)(53546006)(5660300001)(236005)(106116001)(105586002)(93886004)(2950100002)(81166006)(6246003)(189998001)(2900100001)(15650500001)(356003)(2906002)(55016002)(54896002)(66066001)(86362001)(19627405001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4P122MB0083; H:011-smtp-out.Philips.com; FPR:; SPF:Neutral; MLV:sfv; A:1; MX:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DB3FFO11FD030; 1:OjScVTHrBP6K6jZdiKjBhNTk0yF/2iVoOmZLVYpkgpf5UF7Zd33uSJ9b/m9523WkNO/nbCKpTwBqcbVBMCxC89XorJ1IamTIjYv5GP6ikfjF9YzMrhPV8HxHs96+0STUq02nESP+p0VZzWuniq6WX+ik5aiX86ybhzAVELIGVqtFHE95vzkg/T6sIb/wCU23a87chULSisklgwjBKElHQy8Dd7zP7ClS1z9B6Nk8oRTd8cce+udGpmEbTjg9SkJ/HtoNPeOxTKRchRwlw4Uha52x9HJ4IireCsyooK/UtHHvi2K3cpYEzQHsooaRjEv/krxb2m9Zwdc9aw+4JK7NxJxKmY00Tjr/Ht/DWSE+ZCMz9PM+acOp0OnbmCwpQ/Kn3v8ak7pX6KwMUwRiqxO5+30alEgWW/tHeHelwWCp7PWjUZdXnjaoAwz5g3+iA8qvmEeYLhtDX8Hnv/MxDLKEiMZ4Ja/EgMMC47dzHIUr6n6e9oig9V9UQAEWkmLK5MbeAvZH7UTpETV4cXY6I/wxjXKaAumdyHZoVxib9L9tzvWIFKJgxI/aKc70i7HsX2nm
X-CrossPremisesHeadersPromoted: DB3FFO11FD030.protection.gbl
X-CrossPremisesHeadersFiltered: DB3FFO11FD030.protection.gbl
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM4P122MB0083;
X-Microsoft-Exchange-Diagnostics: 1; AM4P122MB0083; 3:4AcObSfxiqWQ6v738nAbUwvHKJ5vpjNOamKtpQb5IfLtYajOQL6c8Gb0DO7p2k59g4dbTTC3KdYZQJixTWi7UsHheH2r1Nj9X9H0mT+61fpeZm9leDxf1e0ek2PfWi0vNcJrynENt1ViXXKCH+Q2us1eW/u5CSYDcFJKuo/MCDiSRHTKyOtSeKCIepFIYPjoK7RPFl/hXrlA7QkvgFJOvMVxrkqyDc6XrVacn0hTJFMkS0oh0T5eW36c11mWQzzyGLCFNm9NavyHBvgibPOVO8gmrZZB9x65njo0YJcrDAmOiFayH6FX8WiWX3bXWk7ItAUhgdAHIer1DnV01PxpgJSQUL6+RDBm9HLckJFLTIM=; 25:VZd6ebqOeWYnwtNksIs04lxWMdYLP+NKMTcX0+XZs8YUQFg83SbC38qGCpJdPl+RV4Em0w8J+u5kaL0emxFogpSwUNaMMkTv6DhENfad+2NulNsAXYoGVvUmrPES0T4AZUIyoQwuTduhReEqtdIHoeK7TSNZWsEpfteKjaXxb87WeEDzyULzR7MkOg1JI5vp8QAwo2dTh9Jckt93u7zhkPi958a8D24k28pFB37Jcv3aqg55hChnZ8UgzHGPF0SRc1J6S2ah/L+8kib0abkWVnkPrXrkqOIYeWT8Wlj6SFlNgk3nRhc8zeejsT3h5y32kScR1wYXyzayVK1uhVOxbLoZB6ekW0ITZ4ERTWb6P9KzdfCJ/wDh58ZbTbcIBDUazDUlkJd6ukEHnwAHYX/+8M3bI1axLQfar7Hi4cnSjZg2uCowBkd5djZYkvXjvgojfXNc9V9zYW5pMMZ3ZatqPg==
X-Microsoft-Exchange-Diagnostics: 1; AM4P122MB0083; 31:zX5KNRdr3LNp5eI1sj3z8xdQzGGTsqbJQSGVDZ9vZQTDaXT8njvkuwEDRnF6RwT/RknNrF8x7c7W4Y0YG0hUO8d7uCEA+2gCI8b25v9cKtTIDC/0GYe5GRIg5JAIAIyzurc5ClyXXSqn/sSmGTtqh0OAH5xqPHCxSmuUxLC7GQkvIj+jiM1LKUCQ5KcSF6lffVj7o5h6FRxGUENi7pWNc9Wx5RvibGl7AEBHYPs9GLxJ1d+4MqaLTvNvNIihvPieWaqOpr3EJoCNEP5/A6YrRr69hUwFtfZ6YnB/9I89O0Q=; 20:1UBOTwNWQJdNUGy21hwroC8xuNaichL664jKj7dHRcI6qy9l45EAg1aAUneBazcEA5KDVmObS9itYox9TFhklujr5X3pCcs/3WViw2GqSBP30qPSAz3F+PiH3sh1h2emZL2k7Rer9aqIHdaSmsakEujZT0s1SQ4l6m+TBjWMt07f6TIjqoGvv/sNHo4oMP8XiQwr3OzjqHCzkqXtQLWrJAAs1a6Bxflxe8iQn6YOYg89wZaAaZ540KlLPYYj2tSAbwOm2fv5vR18kA8y3yAMuraWVVJD7ciMJcN4MvM3vqVsIvnrUW8ahYoxs6r+ZjtgchleX+gCFL6qLS5XOaxJVS4a6JwxjRkM4AN+hsM7CuS1pfnRfl7b5Bdg8a3Ybj/4mjuO8qmpKctYwogQc0VM9r9slts1j3LvJH2ktC3iYYFYW6XaJ9PJP0TfGE1wmf6clv6+uaNiK61pRSZGcNKzlOVcP4m3kcqVgq9PcXHH7bZsQldmFM24Xf8h1FWE06fa
X-Microsoft-Antispam-PRVS: <AM4P122MB0083EE6F22749742949AC091C8210@AM4P122MB0083.EURP122.PROD.OUTLOOK.COM>
X-Exchange-Antispam-Report-Test: UriScan:(192374486261705)(248736688235697)(95692535739014)(126837547833334); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(8121501046)(13016025)(5005006)(13018025)(3002001)(10201501046)(6055026)(6041248)(20161123564025)(20161123555025)(20161123560025)(20161123558025)(20161123562025)(6072148); SRVR:AM4P122MB0083; BCL:0; PCL:0; RULEID:; SRVR:AM4P122MB0083; 
X-Microsoft-Exchange-Diagnostics: 1; AM4P122MB0083; 4:qwq9XCI7OsKiVmw7y3IXaJcnYw8/azngIVQ4NJ3lQYhLmsxsqXeQVHt89mC1cwEhS/yizZsDKr3SEtWRb7hA9bIgJ+isyq2yg22Wg4ejNBoNDiWq6Cugtb/DuEeX55cnV1NHX7AoHY8czXMKn2K3Qyn3jzDRV1FbXTbWE5T+i60IAAOmmkymlKOBm5SUACn+56tnBAlBSWVapDBpVZ+NIlfwoy72PtL/xwl3oa6MFq+2ZERoABBW18laiMiTv8Wf+XB+xji1ytliG/Q2bKtJo0v0gs5PlHAf+QEydGGWGkl2jaME0s4PhxShf8bsb4Jq9f50aMefL7rEuaCMx4mYE5FyFbQb0Prj/yteDSphFt3bfENQSN3OS86fft1Pf5nGi2kb1f1DyatHa+HtDj1wqfddqa6dhcqPLiy6POaGQKdlabtY1tSJxDxZZyXVE9nnzb402LRbI+4Ce8Q4URHCmHu5lV8Ls1fR1IRK+MmUkaMT2SCcL/N97gyiLYxeE2n6hUlSnRW5czkjSV0hXxMiQCIGJooH7qKhuy7JSGtVmyyh+Mw3mA9sUobkodZ4lKe2vUfvAee9ji8l9bL2TklDJNY7oP2gfvm2Tc2tm5589j15bo6Ss4o8injzEtpJav+sNZMR4z+yegotrfA7Hw/uJ5ZkM4QJtvohAAzSAMMHIAifUeOKtEv/H7rCJuupi65M3EP3XE62qaoBpPzIjNohrjaJFe2b1+QhrG0oaApJjei8DtCQaHxnM7tYqzuZzu62RmPY4gtxRJeDmz5lOC6t7zQanOcwa1KbR6H6xHPxoEE=
X-Forefront-PRVS: 0241D5F98C
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; AM4P122MB0083; 23:3g5/EOsRWoTGdoK6Gpz6Qu8xuvJ5FR0lMiEbW85ta?= =?us-ascii?Q?znK7EXLFn4pZdJ1nh36flhr8xy6sV6OBUiFO6laYjN0o+Pyj8tQA4MC8yqfX?= =?us-ascii?Q?ASzWDNj2KAU+l4Fu6tl8wA2h7NFAaGOiM0NfQ8QVL6XYz51ZXhimlwkr4VaC?= =?us-ascii?Q?RjDVp8rgbUhX6br2c0/6vdw1kKN5zR6GOtSsiFYGkJ7gUxeeZPEl15H1zaHK?= =?us-ascii?Q?u5cciz1w7WDJw2XPU9YgBZ76VSkgm4zvHlaKwNEC7/pZ4MlueYfklb7fSFBm?= =?us-ascii?Q?xTQ8ozB65k+SFxgUicDhFTQIlVFqU3lhV5ubxe4LYW+E8ihX4u2mdFYTMR9d?= =?us-ascii?Q?SE0ZPOo/mzWvpRWz1wRJgeBeugaSQt99HqUp923gpDT+AOu1Whv+vSyub/kO?= =?us-ascii?Q?cptF5WKX1JjbRbSEOEgh4rZeW0NAH7DDjKcVw1Hahs2CLCHTA5YCpweQ7lV9?= =?us-ascii?Q?pddJmu32qWoFOPyv6dCfuVBizQ5d3V485aZ6yrTABsBDdlmAC/qbpvizM+d/?= =?us-ascii?Q?KeOiwzBfRGDVwpjDq7aXgptNM28aXQft+wgxOFOlxbmhzNXuPQgGES3jFAFD?= =?us-ascii?Q?4vM9aYgeEUwNbRW25l6OzR2/1amlZcQ69G7cocS1hqEvl27v0PYWq8LLQkmh?= =?us-ascii?Q?g3TBmjbSdR7VJuR3Fgts/8be7+Xy4nrxNvtzZF2aZpiGnS3oXX9us8pozaP9?= =?us-ascii?Q?TKIWalLo+7kXrfZcBJk27VowSu27oCLr2Gvw2BPbK6Dh1KJZ96L5x8PcRcvf?= =?us-ascii?Q?EdauMjd32bhp+FH+kbsZDzEIILo1mjbc2AQoZxkedN4+2X/FaMUsXVztL/ml?= =?us-ascii?Q?TiL6t6hXeMZwRf1CvUyxMRie/W7QKs5fvRyfBG5V64+Wr78AL+nxajxHT09m?= =?us-ascii?Q?DeIup3HSM8AtngnTDLpQ91ip4nx3OKrsLFbQ3I72dsRQbj2y+pn6937x07OP?= =?us-ascii?Q?7vNVbGs+CLz+KXFfp9zvs6LbLe8bsdSv+XgC+KpMbsaAwT0cFm5iw8RaMWj0?= =?us-ascii?Q?6pXH6pnJuYSMR6pJvXBOGIvBCkCPFp65ZPzrsD+e7YHdlKnX9BqQo/S2hlb3?= =?us-ascii?Q?hgdPP8AdDUEErjsxnPC3OE8R6dWQ89bPaHQTLLilT/2gcTIeyIhTWl4wjv2A?= =?us-ascii?Q?o0vX5KxA5xflUs+MPnidGqwR1/6riJXmp9M+/J+5IdWQeSj7VXq4nnwIEBTk?= =?us-ascii?Q?3s3FiibJJxjg72RMomuoIaTzp/lyIgLNeTo2GlyS696kSdR8E5hYtf8vgfpc?= =?us-ascii?Q?L9UD6hL7y0WGhmER1dxW38NCqjdBKMLei13SLvOQvaMaIJBLpxczHk8wlk1W?= =?us-ascii?Q?3cREtYqzJHO4LmyZxVwBjKtSH4k7PRYqI9riy0Ya8qD492Eqtc3JJpydp/Re?= =?us-ascii?Q?P082UYExGiiJoAlxaKhsLDBkq76/RR/GEFFXYhzvJG2K27y?=
X-Microsoft-Exchange-Diagnostics: 1; AM4P122MB0083; 6:MOUT1rKiydm81zr3jml0pMoIX89hKjr3PCK/kzsNS/DTEXQ0e8XlS8IGr0JpyhbMJYlKaFGkq/5TcsZiSSlrLtnQEMrNdT2JpqxXisscHV8mmjlPJBHVVyTp/Hjae1x/Nfe1CMStUWe5+hGeCuHSVk/VtySWvI6L9s2BHJ2ER5pkrf1U6twl0M5PD6kE4deO0kfheVzK6E5qSZxGIQVTJXVbW38soFKEQOoWxDvqsUCnAZl0Bip6y0kxSXynyOIZc4W6S4Kp7/k+VbT8krp2cA54FcZSoC1SWoEIotOSfEcKcag35aIkJyexDRJG5MAHO0ENhNc5X301OM4iUwf/NvZFUQZZpxSFherVtRerbngc4EbTDlkvyT94XZXgnLKsR70IYNhq8HpOTJ+m6lNDvcHpFUpJozLu3crhPSCd9+w=; 5:lEw9z1yvyDD/GPxqguMR358X0rMtdOKIIjI3bTXn9b7Y3ouF+VteUjlWB86iZfS/r+uOoSg9AIgwVtQ5rAyO2mTmKMHpgK0e82Hp2E73wwlTiLi+yYMXRSl5a8inKFoVc9HtJHuVNI2B6U9VLOyjUw==; 24:+ii8hBW14m/nlNUH4wnYjEKl8wh8FyvApEPDW6m2zdrJuissqKuHZj/Y3U7Fk/eykhkZxqx7hxgPPCsWUmE0A+pusDtaQlRvussWuKMuHF4=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; AM4P122MB0083; 7:kHTuXZJwZgxiTpIWa0l/zfyegB4MuQonfuO50+sfQuBuQVAUxfmj8EvdHStFs4WH4sqW5qH+uObrYGDM6XEDUrCpWNazYBP0e9I1se/z2ReWlVwDsO+Sr1aNF0rsnXEeNEQnapFpEcUhx3LNE+cpfgAsKJozPolTUmVHTclaZqvg1nHDbwhLjeALbv3e0CZPo26OhAqtZsAMoj2O+cg+1pdernf9aD74c1szIIn2dX2w9e5M5PP5IWSvPbl9+6eQHSa5X2t2vgKvrZy8O93Aa2qiN2AcfGFJa9Kr3gYeFqeyWTmRfKZG5Y9JF389udGFNx2j86JqsngQpsJMA9zmFQ==
X-OriginatorOrg: philips.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Mar 2017 14:32:39.1924 (UTC)
X-MS-Exchange-CrossTenant-Id: 1a407a2d-7675-4d17-8692-b3ac285306e4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=1a407a2d-7675-4d17-8692-b3ac285306e4; Ip=[23.103.247.180];  Helo=[011-smtp-out.Philips.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4P122MB0083
X-MS-Exchange-CrossPremises-AuthAs: Internal
X-MS-Exchange-CrossPremises-AuthMechanism: 04
X-MS-Exchange-CrossPremises-AuthSource: DB5PR9001MB0165.MGDPHG.emi.philips.com
X-MS-Exchange-CrossPremises-SCL: 1
X-MS-Exchange-CrossPremises-messagesource: StoreDriver
X-MS-Exchange-CrossPremises-BCC: 
X-MS-Exchange-CrossPremises-originalclientipaddress: 77.168.179.203
X-MS-Exchange-CrossPremises-processed-by-journaling: Journal Agent
X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
X-MS-Exchange-CrossPremises-Antispam-ScanContext: DIR:Originating; SFV:NSPM; SKIP:0; 
X-OrganizationHeadersPreserved: AM4P122MB0083.EURP122.PROD.OUTLOOK.COM
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/ef1qfcysP07ypnvL3sdPowHh5C4>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 14:32:45 -0000

--_000_03443d82f2c94a5cad12978b4a3c54e4DB5PR9001MB0165MGDPHGem_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Eliot,


i believe that your two examples (fridge and car) describe a system (fridge=
 and car) within a larger system (smart home or V2X). More complex scenario=
s exist.


You could analyze such scenarios by decomposing the larger system into subs=
ystems (domains) and applying the security considerations to each of the do=
mains in which the "smart things or smart components" in that domain talk t=
o each other.


Does this help you further?Would you analyze this in a different way? Do yo=
u think that this explanation should be included in the our document?


Cheers, Oscar.

________________________________
From: Eliot Lear <lear@cisco.com>
Sent: Wednesday, March 8, 2017 4:46 PM
To: Garcia-Morchon O, Oscar; Hannes Tschofenig; Kovatsch, Matthias; mcr+iet=
f@sandelman.ca
Cc: T2TRG@irtf.org
Subject: Re: [T2TRG] RESTful Design & Security


Oscar,

That's a great document.  In some ways, it's really several documents all r=
olled up into one.  But Let me ask some leading questions:

  *   Is my network-connected refrigerator a Thing or a component?
  *   Is the thermostat in my network-connected refrigerator a Thing or a c=
omponent?
  *   Is my network-connected car a Thing or a component?
  *   Is the engine that sits on the CAN bus a Thing or a component?

What distinguishes a Thing from a component and when do your security consi=
derations apply, and when do they not?

Eliot

On 3/8/17 4:31 PM, Garcia-Morchon O, Oscar wrote:

Hi Hannes,

the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols.  But =
I do not think that we do this happily but seriously. Summarizing existing =
protocols/work is one of the goals of the document.

The document also acknowledges that devices have different capabilities and=
 requirements, also in terms of security. In my view, this fits with the id=
ea of minimum requirements. It would be great to have your input on your us=
e cases and your views on minimum assumptions in different deployment scena=
rios/security capabilities of different types of devices.

Cheers, Oscar.


-----Original Message-----
From: T2TRG [mailto:t2trg-bounces@irtf.org] On Behalf Of Hannes Tschofenig
Sent: Wednesday, March 8, 2017 3:13 PM
To: Eliot Lear <lear@cisco.com><mailto:lear@cisco.com>; Kovatsch, Matthias =
<matthias.kovatsch@siemens.com><mailto:matthias.kovatsch@siemens.com>; mcr+=
ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>
Cc: T2TRG@irtf.org<mailto:T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security

Hi Eliot,

this would indeed be a good conversation to have. I have tried to trigger i=
t a couple of times in context of the IoT device classes but it is very har=
d to get people to state what their minimum assumptions are.

I believe it has to do with the type of standardization approach we are exe=
rcising today and this gives us a hard time to describe the big picture of =
how the various building blocks are supposed to work together. In fact, the=
 picture becomes extremely complex and fragmented since there are just so m=
any options while at the same time we envision super constrained devices. T=
he T2TRG security document
(draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about nor=
mal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.

Ciao
Hannes

On 03/08/2017 11:02 AM, Eliot Lear wrote:


Matthias,

I think the key question that everyone seems to be dancing around is this:

What is an Internet host in the context of IoT?  What are the minimum
qualities it must possess?  I don't mean this to be a vote, but more
of a law of physics sort of thing.  For instance, does a host have a
secure unique identity?  What capabilities must it have?  I would
expect them to be very few, but there are assuredly some...

Eliot


On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:


Fair enough.

Yes, I am on this IoT Directorate. I would say a large fraction of
the T2TRG participants has been arguing that the Internet of Gateways
is not a good approach. Your security-related summary proves this point.

I personally don't see end-to-end security happening if we keep
mixing application protocols, keep using black-magic middleboxes, and
keep using proprietary interfaces at the device level. We need
something end-to-end (or T2T) for end-to-end security.

Best wishes
Matthias



Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [hannes.tschofenig@gmx.net<mailto:hannes.tschofen=
ig@gmx.net>]
*Received:* Tuesday, 07 Mar 2017, 20:10
*To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
[matthias.kovatsch@siemens.com<mailto:matthias.kovatsch@siemens.com>]; mcr+=
ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>
[mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>]
*CC:* T2TRG@irtf.org<mailto:T2TRG@irtf.org> [T2TRG@irtf.org<mailto:T2TRG@ir=
tf.org>]
*Subject:* Re: [T2TRG] RESTful Design & Security

Hi Matthias,

I know that this is a research group and everyone can create whatever
they want.

We briefly talked about security at the IoT directorate conference
call and I would be interesting to hear what works and what does not
work for others.

Ciao
Hannes


On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:


On big propaganda tour? :P

Regards
Matthias


Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [hannes.tschofenig@gmx.net<mailto:hannes.tschofen=
ig@gmx.net>]
*Received:* Tuesday, 07 Mar 2017, 19:39
*To:* Michael Richardson [mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.c=
a>]
*CC:* t2trg@irtf.org<mailto:t2trg@irtf.org> [T2TRG@irtf.org<mailto:T2TRG@ir=
tf.org>]
*Subject:* Re: [T2TRG] RESTful Design & Security

OSCOAP does not work when

* you mix protocols,
* use a middlebox for some processing interactions (such as data
aggregation), and
* when one of the protocols is a non-RESTful protocol, such as BLE


or MQTT.


Unfortunately, these the use cases we are facing in current IoT
deployments. For similar reasons we cannot use RFC 8075 either.

Maybe you are seeing different deployment environments.

Ciao
Hannes

On 03/07/2017 06:39 PM, Michael Richardson wrote:


Hannes Tschofenig <hannes.tschofenig@gmx.net><mailto:hannes.tschofenig@gmx.=
net> wrote:
    > Needless to say that these challenges have also been
observed


in other


    > protocols as well, such as HTTP and even SIP.

    > What is the story for providing application layer security?

OSCOAP seems to be end-to-end to me.

--
Michael Richardson <mcr+IETF@sandelman.ca><mailto:mcr+IETF@sandelman.ca>, S=
andelman Software
Works  -=3D IPv6 IoT consulting =3D-





_______________________________________________
T2TRG mailing list
T2TRG@irtf.org<mailto:T2TRG@irtf.org>
https://www.irtf.org/mailman/listinfo/t2trg



_______________________________________________
T2TRG mailing list
T2TRG@irtf.org<mailto:T2TRG@irtf.org>
https://www.irtf.org/mailman/listinfo/t2trg


________________________________
The information contained in this message may be confidential and legally p=
rotected under applicable law. The message is intended solely for the addre=
ssee(s). If you are not the intended recipient, you are hereby notified tha=
t any use, forwarding, dissemination, or reproduction of this message is st=
rictly prohibited and may be unlawful. If you are not the intended recipien=
t, please contact the sender by return e-mail and destroy all copies of the=
 original message.



--_000_03443d82f2c94a5cad12978b4a3c54e4DB5PR9001MB0165MGDPHGem_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size: 12pt; colo=
r: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif, &quot;=
Apple Color Emoji&quot;, &quot;Segoe UI Emoji&quot;, NotoColorEmoji, &quot;=
Segoe UI Symbol&quot;, &quot;Android Emoji&quot;, EmojiSymbols, &quot;Apple=
 Color Emoji&quot;, &quot;Segoe UI Emoji&quot;, NotoColorEmoji, &quot;Segoe=
 UI Symbol&quot;, &quot;Android Emoji&quot;, EmojiSymbols;">
<p>Hi Eliot,</p>
<p><br>
</p>
<p>i believe that your two examples (fridge and car) describe a system (fri=
dge and car) within a larger system (smart home or V2X). More complex scena=
rios exist.</p>
<p><br>
</p>
<p>You could analyze such scenarios by decomposing the larger system into s=
ubsystems (domains) and&nbsp;applying the security&nbsp;considerations to e=
ach of the domains in which the &quot;smart&nbsp;things or smart&nbsp;compo=
nents&quot; in that domain talk to each other.&nbsp;</p>
<p><br>
</p>
<p>Does this help you further?Would you analyze this&nbsp;in a different wa=
y? Do you think that this explanation should be included in the our documen=
t?&nbsp;</p>
<p><br>
</p>
<p>Cheers, Oscar.</p>
<br>
<div style=3D"color:rgb(0,0,0)">
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Eliot Lear &lt;lear@c=
isco.com&gt;<br>
<b>Sent:</b> Wednesday, March 8, 2017 4:46 PM<br>
<b>To:</b> Garcia-Morchon O, Oscar; Hannes Tschofenig; Kovatsch, Matthias; =
mcr&#43;ietf@sandelman.ca<br>
<b>Cc:</b> T2TRG@irtf.org<br>
<b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security</font>
<div>&nbsp;</div>
</div>
<div>
<p>Oscar,</p>
<p>That's a great document.&nbsp; In some ways, it's really several documen=
ts all rolled up into one.&nbsp; But Let me ask some leading questions:</p>
<ul>
<li>Is my network-connected refrigerator a Thing or a component? </li><li>I=
s the thermostat in my network-connected refrigerator a Thing or a componen=
t?
</li><li>Is my network-connected car a Thing or a component? </li><li>Is th=
e engine that sits on the CAN bus a Thing or a component? </li></ul>
<p>What distinguishes a Thing from a component and when do your security co=
nsiderations apply, and when do they not?</p>
<p>Eliot<br>
</p>
<br>
<div class=3D"moz-cite-prefix">On 3/8/17 4:31 PM, Garcia-Morchon O, Oscar w=
rote:<br>
</div>
<blockquote type=3D"cite">
<pre>Hi Hannes,=0A=
=0A=
the document &quot; draft-irtf-t2trg-iot-seccons-01&quot; summarizes protoc=
ols.  But I do not think that we do this happily but seriously. Summarizing=
 existing protocols/work is one of the goals of the document.=0A=
=0A=
The document also acknowledges that devices have different capabilities and=
 requirements, also in terms of security. In my view, this fits with the id=
ea of minimum requirements. It would be great to have your input on your us=
e cases and your views on minimum assumptions in different deployment scena=
rios/security capabilities of different types of devices.=0A=
=0A=
Cheers, Oscar.=0A=
=0A=
=0A=
-----Original Message-----=0A=
From: T2TRG [<a class=3D"moz-txt-link-freetext" href=3D"mailto:t2trg-bounce=
s@irtf.org">mailto:t2trg-bounces@irtf.org</a>] On Behalf Of Hannes Tschofen=
ig=0A=
Sent: Wednesday, March 8, 2017 3:13 PM=0A=
To: Eliot Lear <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:lear@cisco=
.com">&lt;lear@cisco.com&gt;</a>; Kovatsch, Matthias <a class=3D"moz-txt-li=
nk-rfc2396E" href=3D"mailto:matthias.kovatsch@siemens.com">&lt;matthias.kov=
atsch@siemens.com&gt;</a>; <a class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:mcr&#43;ietf@sandelman.ca">mcr&#43;ietf@sandelman.ca</a>=0A=
Cc: <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2=
TRG@irtf.org</a>=0A=
Subject: Re: [T2TRG] RESTful Design &amp; Security=0A=
=0A=
Hi Eliot,=0A=
=0A=
this would indeed be a good conversation to have. I have tried to trigger i=
t a couple of times in context of the IoT device classes but it is very har=
d to get people to state what their minimum assumptions are.=0A=
=0A=
I believe it has to do with the type of standardization approach we are exe=
rcising today and this gives us a hard time to describe the big picture of =
how the various building blocks are supposed to work together. In fact, the=
 picture becomes extremely complex and fragmented since there are just so m=
any options while at the same time we envision super constrained devices. T=
he T2TRG security document=0A=
(draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about nor=
mal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.=0A=
=0A=
Ciao=0A=
Hannes=0A=
=0A=
On 03/08/2017 11:02 AM, Eliot Lear wrote:=0A=
</pre>
<blockquote type=3D"cite">
<pre>Matthias,=0A=
=0A=
I think the key question that everyone seems to be dancing around is this:=
=0A=
=0A=
What is an Internet host in the context of IoT?  What are the minimum=0A=
qualities it must possess?  I don't mean this to be a vote, but more=0A=
of a law of physics sort of thing.  For instance, does a host have a=0A=
secure unique identity?  What capabilities must it have?  I would=0A=
expect them to be very few, but there are assuredly some...=0A=
=0A=
Eliot=0A=
=0A=
=0A=
On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:=0A=
</pre>
<blockquote type=3D"cite">
<pre>Fair enough.=0A=
=0A=
Yes, I am on this IoT Directorate. I would say a large fraction of=0A=
the T2TRG participants has been arguing that the Internet of Gateways=0A=
is not a good approach. Your security-related summary proves this point.=0A=
=0A=
I personally don't see end-to-end security happening if we keep=0A=
mixing application protocols, keep using black-magic middleboxes, and=0A=
keep using proprietary interfaces at the device level. We need=0A=
something end-to-end (or T2T) for end-to-end security.=0A=
=0A=
Best wishes=0A=
Matthias=0A=
=0A=
=0A=
=0A=
Sent from my phone, limitations might apply.=0A=
=0A=
-----Original Message-----=0A=
*From:* Hannes Tschofenig [<a class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]=0A=
*Received:* Tuesday, 07 Mar 2017, 20:10=0A=
*To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)=0A=
[<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:matthias.kovatsch@sie=
mens.com">matthias.kovatsch@siemens.com</a>]; <a class=3D"moz-txt-link-abbr=
eviated" href=3D"mailto:mcr&#43;ietf@sandelman.ca">mcr&#43;ietf@sandelman.c=
a</a>=0A=
[<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:mcr&#43;ietf@sandelma=
n.ca">mcr&#43;ietf@sandelman.ca</a>]=0A=
*CC:* <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">=
T2TRG@irtf.org</a> [<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2=
TRG@irtf.org">T2TRG@irtf.org</a>]=0A=
*Subject:* Re: [T2TRG] RESTful Design &amp; Security=0A=
=0A=
Hi Matthias,=0A=
=0A=
I know that this is a research group and everyone can create whatever=0A=
they want.=0A=
=0A=
We briefly talked about security at the IoT directorate conference=0A=
call and I would be interesting to hear what works and what does not=0A=
work for others.=0A=
=0A=
Ciao=0A=
Hannes=0A=
=0A=
=0A=
On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:=0A=
</pre>
<blockquote type=3D"cite">
<pre>On big propaganda tour? :P=0A=
=0A=
Regards=0A=
Matthias=0A=
=0A=
=0A=
Sent from my phone, limitations might apply.=0A=
=0A=
-----Original Message-----=0A=
*From:* Hannes Tschofenig [<a class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]=0A=
*Received:* Tuesday, 07 Mar 2017, 19:39=0A=
*To:* Michael Richardson [<a class=3D"moz-txt-link-abbreviated" href=3D"mai=
lto:mcr&#43;ietf@sandelman.ca">mcr&#43;ietf@sandelman.ca</a>]=0A=
*CC:* <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:t2trg@irtf.org">=
t2trg@irtf.org</a> [<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2=
TRG@irtf.org">T2TRG@irtf.org</a>]=0A=
*Subject:* Re: [T2TRG] RESTful Design &amp; Security=0A=
=0A=
OSCOAP does not work when=0A=
=0A=
* you mix protocols,=0A=
* use a middlebox for some processing interactions (such as data=0A=
aggregation), and=0A=
* when one of the protocols is a non-RESTful protocol, such as BLE=0A=
</pre>
</blockquote>
<pre>or MQTT.=0A=
</pre>
<blockquote type=3D"cite">
<pre>Unfortunately, these the use cases we are facing in current IoT=0A=
deployments. For similar reasons we cannot use RFC 8075 either.=0A=
=0A=
Maybe you are seeing different deployment environments.=0A=
=0A=
Ciao=0A=
Hannes=0A=
=0A=
On 03/07/2017 06:39 PM, Michael Richardson wrote:=0A=
</pre>
<blockquote type=3D"cite">
<pre>Hannes Tschofenig <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:ha=
nnes.tschofenig@gmx.net">&lt;hannes.tschofenig@gmx.net&gt;</a> wrote:=0A=
    &gt; Needless to say that these challenges have also been=0A=
observed=0A=
</pre>
</blockquote>
</blockquote>
<pre>in other=0A=
</pre>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<pre>    &gt; protocols as well, such as HTTP and even SIP.=0A=
=0A=
    &gt; What is the story for providing application layer security?=0A=
=0A=
OSCOAP seems to be end-to-end to me.=0A=
=0A=
--=0A=
Michael Richardson <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:mcr&#4=
3;IETF@sandelman.ca">&lt;mcr&#43;IETF@sandelman.ca&gt;</a>, Sandelman Softw=
are=0A=
Works  -=3D IPv6 IoT consulting =3D-=0A=
=0A=
=0A=
=0A=
</pre>
</blockquote>
<pre>_______________________________________________=0A=
T2TRG mailing list=0A=
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2TRG@=
irtf.org</a>=0A=
<a class=3D"moz-txt-link-freetext" href=3D"https://www.irtf.org/mailman/lis=
tinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>=0A=
=0A=
</pre>
</blockquote>
<pre>_______________________________________________=0A=
T2TRG mailing list=0A=
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2TRG@=
irtf.org</a>=0A=
<a class=3D"moz-txt-link-freetext" href=3D"https://www.irtf.org/mailman/lis=
tinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a>=0A=
</pre>
</blockquote>
<pre></pre>
</blockquote>
<pre>________________________________=0A=
The information contained in this message may be confidential and legally p=
rotected under applicable law. The message is intended solely for the addre=
ssee(s). If you are not the intended recipient, you are hereby notified tha=
t any use, forwarding, dissemination, or reproduction of this message is st=
rictly prohibited and may be unlawful. If you are not the intended recipien=
t, please contact the sender by return e-mail and destroy all copies of the=
 original message.=0A=
</pre>
</blockquote>
<br>
</div>
</div>
</div>
</body>
</html>

--_000_03443d82f2c94a5cad12978b4a3c54e4DB5PR9001MB0165MGDPHGem_--


From nobody Thu Mar  9 06:59:20 2017
Return-Path: <hasan.derhamy@ltu.se>
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 BC45312964D for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 06:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 dv4ghmPQcTdO for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 06:59:16 -0800 (PST)
Received: from mxi.ltu.se (mxi.ltu.se [IPv6:2001:6b0:10:42::42:23]) (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 9ED33129665 for <T2TRG@irtf.org>; Thu,  9 Mar 2017 06:59:15 -0800 (PST)
Received: from ltuex1.ltuad.ltu.se (ltuex1.ltuad.ltu.se [130.240.20.71]) by mxi.ltu.se (8.14.4/8.14.4) with ESMTP id v29Ex1pQ020247 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 9 Mar 2017 15:59:01 +0100
Received: from ltuex1.ltuad.ltu.se (130.240.20.71) by ltuex1.ltuad.ltu.se (130.240.20.71) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Thu, 9 Mar 2017 15:59:01 +0100
Received: from ltuex1.ltuad.ltu.se ([fe80::c184:6d39:a728:cf6d]) by ltuex1.ltuad.ltu.se ([fe80::c184:6d39:a728:cf6d%14]) with mapi id 15.00.1236.000; Thu, 9 Mar 2017 15:59:01 +0100
From: Hasan Derhamy <hasan.derhamy@ltu.se>
To: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>, Eliot Lear <lear@cisco.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Thread-Topic: [T2TRG] RESTful Design & Security
Thread-Index: AQHSlpsig/ioJjJFqk+GH8j8vzJ1rKGJlY0AgAAQwgCAAAGWgIAAByCAgAAHRICAAPIBgIAARf+AgAAV7gCAAAQ/AIABfZAAgAAWDPA=
Date: Thu, 9 Mar 2017 14:59:00 +0000
Message-ID: <943f8c65ea1949d684e9f7af7b86f8a7@ltuex1.ltuad.ltu.se>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com> <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net> <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>, <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com> <03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.philips.com>
In-Reply-To: <03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.philips.com>
Accept-Language: en-GB, sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [130.240.20.100]
Content-Type: multipart/alternative; boundary="_000_943f8c65ea1949d684e9f7af7b86f8a7ltuex1ltuadltuse_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/UcqzYQxY8asFwTwz5Fq_d6VQECo>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 14:59:19 -0000

--_000_943f8c65ea1949d684e9f7af7b86f8a7ltuex1ltuadltuse_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Would be interesting to see how systems of systems gets mapped within your =
considerations.

http://sebokwiki.org/wiki/Systems_of_Systems_(SoS)



-Hasan




From: T2TRG [mailto:t2trg-bounces@irtf.org] On Behalf Of Garcia-Morchon O, =
Oscar
Sent: den 9 mars 2017 15:33
To: Eliot Lear; Hannes Tschofenig; Kovatsch, Matthias; mcr+ietf@sandelman.c=
a
Cc: T2TRG@irtf.org
Subject: Re: [T2TRG] RESTful Design & Security


Hi Eliot,



i believe that your two examples (fridge and car) describe a system (fridge=
 and car) within a larger system (smart home or V2X). More complex scenario=
s exist.



You could analyze such scenarios by decomposing the larger system into subs=
ystems (domains) and applying the security considerations to each of the do=
mains in which the "smart things or smart components" in that domain talk t=
o each other.



Does this help you further?Would you analyze this in a different way? Do yo=
u think that this explanation should be included in the our document?



Cheers, Oscar.

________________________________
From: Eliot Lear <lear@cisco.com<mailto:lear@cisco.com>>
Sent: Wednesday, March 8, 2017 4:46 PM
To: Garcia-Morchon O, Oscar; Hannes Tschofenig; Kovatsch, Matthias; mcr+iet=
f@sandelman.ca<mailto:mcr+ietf@sandelman.ca>
Cc: T2TRG@irtf.org<mailto:T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security


Oscar,

That's a great document.  In some ways, it's really several documents all r=
olled up into one.  But Let me ask some leading questions:

  *   Is my network-connected refrigerator a Thing or a component?
  *   Is the thermostat in my network-connected refrigerator a Thing or a c=
omponent?
  *   Is my network-connected car a Thing or a component?
  *   Is the engine that sits on the CAN bus a Thing or a component?

What distinguishes a Thing from a component and when do your security consi=
derations apply, and when do they not?

Eliot

On 3/8/17 4:31 PM, Garcia-Morchon O, Oscar wrote:

Hi Hannes,



the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols.  But =
I do not think that we do this happily but seriously. Summarizing existing =
protocols/work is one of the goals of the document.



The document also acknowledges that devices have different capabilities and=
 requirements, also in terms of security. In my view, this fits with the id=
ea of minimum requirements. It would be great to have your input on your us=
e cases and your views on minimum assumptions in different deployment scena=
rios/security capabilities of different types of devices.



Cheers, Oscar.





-----Original Message-----

From: T2TRG [mailto:t2trg-bounces@irtf.org] On Behalf Of Hannes Tschofenig

Sent: Wednesday, March 8, 2017 3:13 PM

To: Eliot Lear <lear@cisco.com><mailto:lear@cisco.com>; Kovatsch, Matthias =
<matthias.kovatsch@siemens.com><mailto:matthias.kovatsch@siemens.com>; mcr+=
ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>

Cc: T2TRG@irtf.org<mailto:T2TRG@irtf.org>

Subject: Re: [T2TRG] RESTful Design & Security



Hi Eliot,



this would indeed be a good conversation to have. I have tried to trigger i=
t a couple of times in context of the IoT device classes but it is very har=
d to get people to state what their minimum assumptions are.



I believe it has to do with the type of standardization approach we are exe=
rcising today and this gives us a hard time to describe the big picture of =
how the various building blocks are supposed to work together. In fact, the=
 picture becomes extremely complex and fragmented since there are just so m=
any options while at the same time we envision super constrained devices. T=
he T2TRG security document

(draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about nor=
mal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.



Ciao

Hannes



On 03/08/2017 11:02 AM, Eliot Lear wrote:

Matthias,



I think the key question that everyone seems to be dancing around is this:



What is an Internet host in the context of IoT?  What are the minimum

qualities it must possess?  I don't mean this to be a vote, but more

of a law of physics sort of thing.  For instance, does a host have a

secure unique identity?  What capabilities must it have?  I would

expect them to be very few, but there are assuredly some...



Eliot





On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:

Fair enough.



Yes, I am on this IoT Directorate. I would say a large fraction of

the T2TRG participants has been arguing that the Internet of Gateways

is not a good approach. Your security-related summary proves this point.



I personally don't see end-to-end security happening if we keep

mixing application protocols, keep using black-magic middleboxes, and

keep using proprietary interfaces at the device level. We need

something end-to-end (or T2T) for end-to-end security.



Best wishes

Matthias







Sent from my phone, limitations might apply.



-----Original Message-----

*From:* Hannes Tschofenig [hannes.tschofenig@gmx.net<mailto:hannes.tschofen=
ig@gmx.net>]

*Received:* Tuesday, 07 Mar 2017, 20:10

*To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)

[matthias.kovatsch@siemens.com<mailto:matthias.kovatsch@siemens.com>]; mcr+=
ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>

[mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>]

*CC:* T2TRG@irtf.org<mailto:T2TRG@irtf.org> [T2TRG@irtf.org<mailto:T2TRG@ir=
tf.org>]

*Subject:* Re: [T2TRG] RESTful Design & Security



Hi Matthias,



I know that this is a research group and everyone can create whatever

they want.



We briefly talked about security at the IoT directorate conference

call and I would be interesting to hear what works and what does not

work for others.



Ciao

Hannes





On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:

On big propaganda tour? :P



Regards

Matthias





Sent from my phone, limitations might apply.



-----Original Message-----

*From:* Hannes Tschofenig [hannes.tschofenig@gmx.net<mailto:hannes.tschofen=
ig@gmx.net>]

*Received:* Tuesday, 07 Mar 2017, 19:39

*To:* Michael Richardson [mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.c=
a>]

*CC:* t2trg@irtf.org<mailto:t2trg@irtf.org> [T2TRG@irtf.org<mailto:T2TRG@ir=
tf.org>]

*Subject:* Re: [T2TRG] RESTful Design & Security



OSCOAP does not work when



* you mix protocols,

* use a middlebox for some processing interactions (such as data

aggregation), and

* when one of the protocols is a non-RESTful protocol, such as BLE

or MQTT.

Unfortunately, these the use cases we are facing in current IoT

deployments. For similar reasons we cannot use RFC 8075 either.



Maybe you are seeing different deployment environments.



Ciao

Hannes



On 03/07/2017 06:39 PM, Michael Richardson wrote:

Hannes Tschofenig <hannes.tschofenig@gmx.net><mailto:hannes.tschofenig@gmx.=
net> wrote:

    > Needless to say that these challenges have also been

observed

in other

    > protocols as well, such as HTTP and even SIP.



    > What is the story for providing application layer security?



OSCOAP seems to be end-to-end to me.



--

Michael Richardson <mcr+IETF@sandelman.ca><mailto:mcr+IETF@sandelman.ca>, S=
andelman Software

Works  -=3D IPv6 IoT consulting =3D-







_______________________________________________

T2TRG mailing list

T2TRG@irtf.org<mailto:T2TRG@irtf.org>

https://www.irtf.org/mailman/listinfo/t2trg



_______________________________________________

T2TRG mailing list

T2TRG@irtf.org<mailto:T2TRG@irtf.org>

https://www.irtf.org/mailman/listinfo/t2trg

________________________________

The information contained in this message may be confidential and legally p=
rotected under applicable law. The message is intended solely for the addre=
ssee(s). If you are not the intended recipient, you are hereby notified tha=
t any use, forwarding, dissemination, or reproduction of this message is st=
rictly prohibited and may be unlawful. If you are not the intended recipien=
t, please contact the sender by return e-mail and destroy all copies of the=
 original message.


--_000_943f8c65ea1949d684e9f7af7b86f8a7ltuex1ltuadltuse_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:101920628;
	mso-list-template-ids:1835812956;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1093092907;
	mso-list-type:hybrid;
	mso-list-template-ids:1164067916 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Would be interesting to s=
ee how systems of systems gets mapped within your considerations.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><a href=3D"http://sebokwi=
ki.org/wiki/Systems_of_Systems_(SoS)">http://sebokwiki.org/wiki/Systems_of_=
Systems_(SoS)</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">-Hasan<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> T2TRG [m=
ailto:t2trg-bounces@irtf.org]
<b>On Behalf Of </b>Garcia-Morchon O, Oscar<br>
<b>Sent:</b> den 9 mars 2017 15:33<br>
<b>To:</b> Eliot Lear; Hannes Tschofenig; Kovatsch, Matthias; mcr&#43;ietf@=
sandelman.ca<br>
<b>Cc:</b> T2TRG@irtf.org<br>
<b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security<o:p></o:p></span>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi Eliot,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">i believe that your two examples (fridge and car) describe a sys=
tem (fridge and car) within a larger system (smart home or V2X). More compl=
ex scenarios exist.<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">You could analyze such scenarios by decomposing the larger syste=
m into subsystems (domains) and&nbsp;applying the security&nbsp;considerati=
ons to each of the domains in which the &quot;smart&nbsp;things or smart&nb=
sp;components&quot;
 in that domain talk to each other.&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Does this help you further?Would you analyze this&nbsp;in a diff=
erent way? Do you think that this explanation should be included in the our=
 document?&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Cheers, Oscar.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"> Eliot Lear &lt;<a href=3D"mailto:lear@cisco.com">lear@cis=
co.com</a>&gt;<br>
<b>Sent:</b> Wednesday, March 8, 2017 4:46 PM<br>
<b>To:</b> Garcia-Morchon O, Oscar; Hannes Tschofenig; Kovatsch, Matthias; =
<a href=3D"mailto:mcr&#43;ietf@sandelman.ca">
mcr&#43;ietf@sandelman.ca</a><br>
<b>Cc:</b> <a href=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a><br>
<b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
<div>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Oscar,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">That's a great document.&nbsp; In some ways, it's really several=
 documents all rolled up into one.&nbsp; But Let me ask some leading questi=
ons:<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Is m=
y network-connected refrigerator a Thing or a component?
<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"color:black;mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Is t=
he thermostat in my network-connected refrigerator a Thing or a component?
<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"color:black;mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Is m=
y network-connected car a Thing or a component?
<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"color:black;mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Is t=
he engine that sits on the CAN bus a Thing or a component?
<o:p></o:p></span></li></ul>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">What distinguishes a Thing from a component and when do your sec=
urity considerations apply, and when do they not?<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Eliot<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">On 3/8/17 4:31 PM, Garcia-Morchon O, Oscar w=
rote:<o:p></o:p></span></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">Hi Hannes,<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">the document &quot; draft-irtf-t2trg-iot-s=
eccons-01&quot; summarizes protocols.&nbsp; But I do not think that we do t=
his happily but seriously. Summarizing existing protocols/work is one of th=
e goals of the document.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">The document also acknowledges that device=
s have different capabilities and requirements, also in terms of security. =
In my view, this fits with the idea of minimum requirements. It would be gr=
eat to have your input on your use cases and your views on minimum assumpti=
ons in different deployment scenarios/security capabilities of different ty=
pes of devices.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Cheers, Oscar.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">-----Original Message-----<o:p></o:p></spa=
n></pre>
<pre><span style=3D"color:black">From: T2TRG [<a href=3D"mailto:t2trg-bounc=
es@irtf.org">mailto:t2trg-bounces@irtf.org</a>] On Behalf Of Hannes Tschofe=
nig<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Sent: Wednesday, March 8, 2017 3:13 PM<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">To: Eliot Lear <a href=3D"mailto:lear@cisc=
o.com">&lt;lear@cisco.com&gt;</a>; Kovatsch, Matthias <a href=3D"mailto:mat=
thias.kovatsch@siemens.com">&lt;matthias.kovatsch@siemens.com&gt;</a>; <a h=
ref=3D"mailto:mcr&#43;ietf@sandelman.ca">mcr&#43;ietf@sandelman.ca</a><o:p>=
</o:p></span></pre>
<pre><span style=3D"color:black">Cc: <a href=3D"mailto:T2TRG@irtf.org">T2TR=
G@irtf.org</a><o:p></o:p></span></pre>
<pre><span style=3D"color:black">Subject: Re: [T2TRG] RESTful Design &amp; =
Security<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Hi Eliot,<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">this would indeed be a good conversation t=
o have. I have tried to trigger it a couple of times in context of the IoT =
device classes but it is very hard to get people to state what their minimu=
m assumptions are.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">I believe it has to do with the type of st=
andardization approach we are exercising today and this gives us a hard tim=
e to describe the big picture of how the various building blocks are suppos=
ed to work together. In fact, the picture becomes extremely complex and fra=
gmented since there are just so many options while at the same time we envi=
sion super constrained devices. The T2TRG security document<o:p></o:p></spa=
n></pre>
<pre><span style=3D"color:black">(draft-irtf-t2trg-iot-seccons-01) confirms=
 this and happily talks about normal IPsec/IKE, diet IPsec, HIP, MIKEY, OSC=
OAP, JOSE, COSE, etc. etc.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ciao<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Hannes<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">On 03/08/2017 11:02 AM, Eliot Lear wrote:<=
o:p></o:p></span></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">Matthias,<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">I think the key question that everyone see=
ms to be dancing around is this:<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">What is an Internet host in the context of=
 IoT?&nbsp; What are the minimum<o:p></o:p></span></pre>
<pre><span style=3D"color:black">qualities it must possess?&nbsp; I don't m=
ean this to be a vote, but more<o:p></o:p></span></pre>
<pre><span style=3D"color:black">of a law of physics sort of thing.&nbsp; F=
or instance, does a host have a<o:p></o:p></span></pre>
<pre><span style=3D"color:black">secure unique identity?&nbsp; What capabil=
ities must it have?&nbsp; I would<o:p></o:p></span></pre>
<pre><span style=3D"color:black">expect them to be very few, but there are =
assuredly some...<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Eliot<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">On 3/7/17 8:36 PM, Kovatsch, Matthias wrot=
e:<o:p></o:p></span></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">Fair enough.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Yes, I am on this IoT Directorate. I would=
 say a large fraction of<o:p></o:p></span></pre>
<pre><span style=3D"color:black">the T2TRG participants has been arguing th=
at the Internet of Gateways<o:p></o:p></span></pre>
<pre><span style=3D"color:black">is not a good approach. Your security-rela=
ted summary proves this point.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">I personally don't see end-to-end security=
 happening if we keep<o:p></o:p></span></pre>
<pre><span style=3D"color:black">mixing application protocols, keep using b=
lack-magic middleboxes, and<o:p></o:p></span></pre>
<pre><span style=3D"color:black">keep using proprietary interfaces at the d=
evice level. We need<o:p></o:p></span></pre>
<pre><span style=3D"color:black">something end-to-end (or T2T) for end-to-e=
nd security.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Best wishes<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Matthias<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Sent from my phone, limitations might appl=
y.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">-----Original Message-----<o:p></o:p></spa=
n></pre>
<pre><span style=3D"color:black">*From:* Hannes Tschofenig [<a href=3D"mail=
to:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]<o:p></o:p></sp=
an></pre>
<pre><span style=3D"color:black">*Received:* Tuesday, 07 Mar 2017, 20:10<o:=
p></o:p></span></pre>
<pre><span style=3D"color:black">*To:* Kovatsch, Matthias (CT RDA NEC EMB-D=
E)<o:p></o:p></span></pre>
<pre><span style=3D"color:black">[<a href=3D"mailto:matthias.kovatsch@sieme=
ns.com">matthias.kovatsch@siemens.com</a>]; <a href=3D"mailto:mcr&#43;ietf@=
sandelman.ca">mcr&#43;ietf@sandelman.ca</a><o:p></o:p></span></pre>
<pre><span style=3D"color:black">[<a href=3D"mailto:mcr&#43;ietf@sandelman.=
ca">mcr&#43;ietf@sandelman.ca</a>]<o:p></o:p></span></pre>
<pre><span style=3D"color:black">*CC:* <a href=3D"mailto:T2TRG@irtf.org">T2=
TRG@irtf.org</a> [<a href=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>]<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">*Subject:* Re: [T2TRG] RESTful Design &amp=
; Security<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Hi Matthias,<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">I know that this is a research group and e=
veryone can create whatever<o:p></o:p></span></pre>
<pre><span style=3D"color:black">they want.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">We briefly talked about security at the Io=
T directorate conference<o:p></o:p></span></pre>
<pre><span style=3D"color:black">call and I would be interesting to hear wh=
at works and what does not<o:p></o:p></span></pre>
<pre><span style=3D"color:black">work for others.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ciao<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Hannes<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">On 03/07/2017 07:45 PM, Kovatsch, Matthias=
 wrote:<o:p></o:p></span></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">On big propaganda tour? :P<o:p></o:p></spa=
n></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Regards<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Matthias<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Sent from my phone, limitations might appl=
y.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">-----Original Message-----<o:p></o:p></spa=
n></pre>
<pre><span style=3D"color:black">*From:* Hannes Tschofenig [<a href=3D"mail=
to:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>]<o:p></o:p></sp=
an></pre>
<pre><span style=3D"color:black">*Received:* Tuesday, 07 Mar 2017, 19:39<o:=
p></o:p></span></pre>
<pre><span style=3D"color:black">*To:* Michael Richardson [<a href=3D"mailt=
o:mcr&#43;ietf@sandelman.ca">mcr&#43;ietf@sandelman.ca</a>]<o:p></o:p></spa=
n></pre>
<pre><span style=3D"color:black">*CC:* <a href=3D"mailto:t2trg@irtf.org">t2=
trg@irtf.org</a> [<a href=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>]<o:p=
></o:p></span></pre>
<pre><span style=3D"color:black">*Subject:* Re: [T2TRG] RESTful Design &amp=
; Security<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">OSCOAP does not work when<o:p></o:p></span=
></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">* you mix protocols,<o:p></o:p></span></pr=
e>
<pre><span style=3D"color:black">* use a middlebox for some processing inte=
ractions (such as data<o:p></o:p></span></pre>
<pre><span style=3D"color:black">aggregation), and<o:p></o:p></span></pre>
<pre><span style=3D"color:black">* when one of the protocols is a non-RESTf=
ul protocol, such as BLE<o:p></o:p></span></pre>
</blockquote>
<pre><span style=3D"color:black">or MQTT.<o:p></o:p></span></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">Unfortunately, these the use cases we are =
facing in current IoT<o:p></o:p></span></pre>
<pre><span style=3D"color:black">deployments. For similar reasons we cannot=
 use RFC 8075 either.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Maybe you are seeing different deployment =
environments.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">Ciao<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Hannes<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">On 03/07/2017 06:39 PM, Michael Richardson=
 wrote:<o:p></o:p></span></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">Hannes Tschofenig <a href=3D"mailto:hannes=
.tschofenig@gmx.net">&lt;hannes.tschofenig@gmx.net&gt;</a> wrote:<o:p></o:p=
></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp; &gt; Needless to say th=
at these challenges have also been<o:p></o:p></span></pre>
<pre><span style=3D"color:black">observed<o:p></o:p></span></pre>
</blockquote>
</blockquote>
<pre><span style=3D"color:black">in other<o:p></o:p></span></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp; &gt; protocols as well,=
 such as HTTP and even SIP.<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">&nbsp;&nbsp;&nbsp; &gt; What is the story =
for providing application layer security?<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">OSCOAP seems to be end-to-end to me.<o:p><=
/o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">--<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Michael Richardson <a href=3D"mailto:mcr&#=
43;IETF@sandelman.ca">&lt;mcr&#43;IETF@sandelman.ca&gt;</a>, Sandelman Soft=
ware<o:p></o:p></span></pre>
<pre><span style=3D"color:black">Works&nbsp; -=3D IPv6 IoT consulting =3D-<=
o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
</blockquote>
<pre><span style=3D"color:black">__________________________________________=
_____<o:p></o:p></span></pre>
<pre><span style=3D"color:black">T2TRG mailing list<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><a href=3D"mailto:T2TRG@irtf.org">T2TRG@ir=
tf.org</a><o:p></o:p></span></pre>
<pre><span style=3D"color:black"><a href=3D"https://www.irtf.org/mailman/li=
stinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a><o:p></o:p></s=
pan></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
</blockquote>
<pre><span style=3D"color:black">__________________________________________=
_____<o:p></o:p></span></pre>
<pre><span style=3D"color:black">T2TRG mailing list<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><a href=3D"mailto:T2TRG@irtf.org">T2TRG@ir=
tf.org</a><o:p></o:p></span></pre>
<pre><span style=3D"color:black"><a href=3D"https://www.irtf.org/mailman/li=
stinfo/t2trg">https://www.irtf.org/mailman/listinfo/t2trg</a><o:p></o:p></s=
pan></pre>
</blockquote>
</blockquote>
<pre><span style=3D"color:black">________________________________<o:p></o:p=
></span></pre>
<pre><span style=3D"color:black">The information contained in this message =
may be confidential and legally protected under applicable law. The message=
 is intended solely for the addressee(s). If you are not the intended recip=
ient, you are hereby notified that any use, forwarding, dissemination, or r=
eproduction of this message is strictly prohibited and may be unlawful. If =
you are not the intended recipient, please contact the sender by return e-m=
ail and destroy all copies of the original message.<o:p></o:p></span></pre>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_943f8c65ea1949d684e9f7af7b86f8a7ltuex1ltuadltuse_--


From nobody Thu Mar  9 07:00:26 2017
Return-Path: <lear@cisco.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 E779E129665 for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 07:00:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 6tuw5hTH2ysN for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 07:00:10 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 164DB12966F for <T2TRG@irtf.org>; Thu,  9 Mar 2017 07:00:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24323; q=dns/txt; s=iport; t=1489071607; x=1490281207; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=fH+DR7z4TOcyBxcHJ+cdEaS1IgyV+LML+0Mzxtyjo7A=; b=PqApHpnsedvVcQr5qUEodxdRPSGjPtE3QPS/8X424nyOvl3GDTR8GYX8 Jj0s9mD24DnARj3oK9deWzx2YTPREs/QRHZEXND4pDbzJ1dv6T3Liz9wD Yo9BnsZi+vFx4KZTQI+hKlFYqFmUUxZ/oC1byHbP78lVjaVHaApuqJSAs Q=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BSAQBKbcFY/xbLJq1UCRkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJuOYELgQqDYIoMc5A8H5U4gg4fAQqCQoM2AoJuGAECAQEBAQE?= =?us-ascii?q?BAWsohRUBAQEBAgEBASFFBgsFBwQLEQQBAQEnAwICJx8JCAYBDAYCAQGJZAMNC?= =?us-ascii?q?A6wToImK4pEAQEBAQEBAQEBAQEBAQEBAQEBAQEBDgoFiFMIgVmBCYJRgVwvLoJ?= =?us-ascii?q?Qgl8FiRqMYIY/g3iCCYQdiBqBe4UjgzGGUZM/HziBAyIVCBcVP4ZVPzWKKwEBA?= =?us-ascii?q?Q?=
X-IronPort-AV: E=Sophos;i="5.36,136,1486425600";  d="asc'?scan'208,217";a="692864373"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2017 15:00:04 +0000
Received: from [10.61.97.155] (dhcp-10-61-97-155.cisco.com [10.61.97.155]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v29F03an021123; Thu, 9 Mar 2017 15:00:03 GMT
To: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>, "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>, "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net> <10144.1488908366@obiwan.sandelman.ca> <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net> <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net> <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net> <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com> <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net> <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com> <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com> <03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.philips.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <88cc6f9b-9297-40cc-1a59-c4473784fd64@cisco.com>
Date: Thu, 9 Mar 2017 16:00:02 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.philips.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="H3j9Qu2oTwvkQ6qtGuaMXlM1CSqkPbU8T"
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/DGdXuv88JX6qQmPqrY1MICCkkuk>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Subject: Re: [T2TRG] RESTful Design & Security
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 09 Mar 2017 15:00:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--H3j9Qu2oTwvkQ6qtGuaMXlM1CSqkPbU8T
Content-Type: multipart/mixed; boundary="B9MTucvNmcQRPaqkgxGMTOt3xeQewXPRq";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>,
 Hannes Tschofenig <hannes.tschofenig@gmx.net>,
 "Kovatsch, Matthias" <matthias.kovatsch@siemens.com>,
 "mcr+ietf@sandelman.ca" <mcr+ietf@sandelman.ca>
Cc: "T2TRG@irtf.org" <T2TRG@irtf.org>
Message-ID: <88cc6f9b-9297-40cc-1a59-c4473784fd64@cisco.com>
Subject: Re: [T2TRG] RESTful Design & Security
References: <c15a387f-9dd3-987e-2901-b86fd8f60108@gmx.net>
 <10144.1488908366@obiwan.sandelman.ca>
 <952c4a16-174f-2457-1f11-8f733e738f90@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA2F98@DEFTHW99EL4MSX.ww902.siemens.net>
 <558bae1a-ff84-9fb3-c6bf-021f492e9a04@gmx.net>
 <4EBB3DDD0FBF694CA2A87838DF129B3C01AA313F@DEFTHW99EL4MSX.ww902.siemens.net>
 <c85cbfa5-083c-9159-3e01-001b353a3e35@cisco.com>
 <f33f30cc-9a6d-513d-f20f-620ac4b611e1@gmx.net>
 <d6c78126308c4f6c94ab4a827d0a8c2e@DB5PR9001MB0165.MGDPHG.emi.philips.com>
 <2669c38e-5a7e-e4a4-36d2-9fd9f7966d52@cisco.com>
 <03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.philips.com>
In-Reply-To: <03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.philips.com>

--B9MTucvNmcQRPaqkgxGMTOt3xeQewXPRq
Content-Type: multipart/alternative;
 boundary="------------1297F3471A32EDC0EF53C42E"

This is a multi-part message in MIME format.
--------------1297F3471A32EDC0EF53C42E
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Oskar,


I'm sorry I wasn't clear, but my point is that one needs to be able to
answer these sorts of questions in order to determine what the end is in
"end to end" security and shat the identity model for these things are.=20
There may be little if any networking available to the "end"  in some cas=
es.


Eliot


On 3/9/17 3:32 PM, Garcia-Morchon O, Oscar wrote:
>
> Hi Eliot,
>
>
> i believe that your two examples (fridge and car) describe a system
> (fridge and car) within a larger system (smart home or V2X). More
> complex scenarios exist.
>
>
> You could analyze such scenarios by decomposing the larger system into
> subsystems (domains) and applying the security considerations to each
> of the domains in which the "smart things or smart components" in that
> domain talk to each other.=20
>
>
> Does this help you further?Would you analyze this in a different way?
> Do you think that this explanation should be included in the our
> document?=20
>
>
> Cheers, Oscar.
>
>
> -----------------------------------------------------------------------=
-
> *From:* Eliot Lear <lear@cisco.com>
> *Sent:* Wednesday, March 8, 2017 4:46 PM
> *To:* Garcia-Morchon O, Oscar; Hannes Tschofenig; Kovatsch, Matthias;
> mcr+ietf@sandelman.ca
> *Cc:* T2TRG@irtf.org
> *Subject:* Re: [T2TRG] RESTful Design & Security
> =20
>
> Oscar,
>
> That's a great document.  In some ways, it's really several documents
> all rolled up into one.  But Let me ask some leading questions:
>
>   * Is my network-connected refrigerator a Thing or a component?
>   * Is the thermostat in my network-connected refrigerator a Thing or
>     a component?
>   * Is my network-connected car a Thing or a component?
>   * Is the engine that sits on the CAN bus a Thing or a component?
>
> What distinguishes a Thing from a component and when do your security
> considerations apply, and when do they not?
>
> Eliot
>
>
> On 3/8/17 4:31 PM, Garcia-Morchon O, Oscar wrote:
>> Hi Hannes,
>>
>> the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols. =
 But I do not think that we do this happily but seriously. Summarizing ex=
isting protocols/work is one of the goals of the document.
>>
>> The document also acknowledges that devices have different capabilitie=
s and requirements, also in terms of security. In my view, this fits with=
 the idea of minimum requirements. It would be great to have your input o=
n your use cases and your views on minimum assumptions in different deplo=
yment scenarios/security capabilities of different types of devices.
>>
>> Cheers, Oscar.
>>
>>
>> -----Original Message-----
>> From: T2TRG [mailto:t2trg-bounces@irtf.org] On Behalf Of Hannes Tschof=
enig
>> Sent: Wednesday, March 8, 2017 3:13 PM
>> To: Eliot Lear <lear@cisco.com>; Kovatsch, Matthias <matthias.kovatsch=
@siemens.com>; mcr+ietf@sandelman.ca
>> Cc: T2TRG@irtf.org
>> Subject: Re: [T2TRG] RESTful Design & Security
>>
>> Hi Eliot,
>>
>> this would indeed be a good conversation to have. I have tried to trig=
ger it a couple of times in context of the IoT device classes but it is v=
ery hard to get people to state what their minimum assumptions are.
>>
>> I believe it has to do with the type of standardization approach we ar=
e exercising today and this gives us a hard time to describe the big pict=
ure of how the various building blocks are supposed to work together. In =
fact, the picture becomes extremely complex and fragmented since there ar=
e just so many options while at the same time we envision super constrain=
ed devices. The T2TRG security document
>> (draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks abou=
t normal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.=

>>
>> Ciao
>> Hannes
>>
>> On 03/08/2017 11:02 AM, Eliot Lear wrote:
>>> Matthias,
>>>
>>> I think the key question that everyone seems to be dancing around is =
this:
>>>
>>> What is an Internet host in the context of IoT?  What are the minimum=

>>> qualities it must possess?  I don't mean this to be a vote, but more
>>> of a law of physics sort of thing.  For instance, does a host have a
>>> secure unique identity?  What capabilities must it have?  I would
>>> expect them to be very few, but there are assuredly some...
>>>
>>> Eliot
>>>
>>>
>>> On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
>>>> Fair enough.
>>>>
>>>> Yes, I am on this IoT Directorate. I would say a large fraction of
>>>> the T2TRG participants has been arguing that the Internet of Gateway=
s
>>>> is not a good approach. Your security-related summary proves this po=
int.
>>>>
>>>> I personally don't see end-to-end security happening if we keep
>>>> mixing application protocols, keep using black-magic middleboxes, an=
d
>>>> keep using proprietary interfaces at the device level. We need
>>>> something end-to-end (or T2T) for end-to-end security.
>>>>
>>>> Best wishes
>>>> Matthias
>>>>
>>>>
>>>>
>>>> Sent from my phone, limitations might apply.
>>>>
>>>> -----Original Message-----
>>>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>>> *Received:* Tuesday, 07 Mar 2017, 20:10
>>>> *To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
>>>> [matthias.kovatsch@siemens.com]; mcr+ietf@sandelman.ca
>>>> [mcr+ietf@sandelman.ca]
>>>> *CC:* T2TRG@irtf.org [T2TRG@irtf.org]
>>>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>>>
>>>> Hi Matthias,
>>>>
>>>> I know that this is a research group and everyone can create whateve=
r
>>>> they want.
>>>>
>>>> We briefly talked about security at the IoT directorate conference
>>>> call and I would be interesting to hear what works and what does not=

>>>> work for others.
>>>>
>>>> Ciao
>>>> Hannes
>>>>
>>>>
>>>> On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
>>>>> On big propaganda tour? :P
>>>>>
>>>>> Regards
>>>>> Matthias
>>>>>
>>>>>
>>>>> Sent from my phone, limitations might apply.
>>>>>
>>>>> -----Original Message-----
>>>>> *From:* Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>>>> *Received:* Tuesday, 07 Mar 2017, 19:39
>>>>> *To:* Michael Richardson [mcr+ietf@sandelman.ca]
>>>>> *CC:* t2trg@irtf.org [T2TRG@irtf.org]
>>>>> *Subject:* Re: [T2TRG] RESTful Design & Security
>>>>>
>>>>> OSCOAP does not work when
>>>>>
>>>>> * you mix protocols,
>>>>> * use a middlebox for some processing interactions (such as data
>>>>> aggregation), and
>>>>> * when one of the protocols is a non-RESTful protocol, such as BLE
>>>> or MQTT.
>>>>> Unfortunately, these the use cases we are facing in current IoT
>>>>> deployments. For similar reasons we cannot use RFC 8075 either.
>>>>>
>>>>> Maybe you are seeing different deployment environments.
>>>>>
>>>>> Ciao
>>>>> Hannes
>>>>>
>>>>> On 03/07/2017 06:39 PM, Michael Richardson wrote:
>>>>>> Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>>>>>>     > Needless to say that these challenges have also been
>>>>>> observed
>>>> in other
>>>>>>     > protocols as well, such as HTTP and even SIP.
>>>>>>
>>>>>>     > What is the story for providing application layer security?
>>>>>>
>>>>>> OSCOAP seems to be end-to-end to me.
>>>>>>
>>>>>> --
>>>>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software
>>>>>> Works  -=3D IPv6 IoT consulting =3D-
>>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> T2TRG mailing list
>>>>> T2TRG@irtf.org
>>>>> https://www.irtf.org/mailman/listinfo/t2trg
>>>>>
>>>> _______________________________________________
>>>> T2TRG mailing list
>>>> T2TRG@irtf.org
>>>> https://www.irtf.org/mailman/listinfo/t2trg
>> ________________________________
>> The information contained in this message may be confidential and lega=
lly protected under applicable law. The message is intended solely for th=
e addressee(s). If you are not the intended recipient, you are hereby not=
ified that any use, forwarding, dissemination, or reproduction of this me=
ssage is strictly prohibited and may be unlawful. If you are not the inte=
nded recipient, please contact the sender by return e-mail and destroy al=
l copies of the original message.
>


--------------1297F3471A32EDC0EF53C42E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Hi Oskar,</p>
    <p><br>
    </p>
    <p>I'm sorry I wasn't clear, but my point is that one needs to be
      able to answer these sorts of questions in order to determine what
      the end is in "end to end" security and shat the identity model
      for these things are.=C2=A0 There may be little if any networking
      available to the "end"=C2=A0 in some cases.</p>
    <p><br>
    </p>
    <p>Eliot<br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">On 3/9/17 3:32 PM, Garcia-Morchon O,
      Oscar wrote:<br>
    </div>
    <blockquote
cite=3D"mid:03443d82f2c94a5cad12978b4a3c54e4@DB5PR9001MB0165.MGDPHG.emi.p=
hilips.com"
      type=3D"cite">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8">
      <style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top=
:0;margin-bottom:0;} --></style>
      <div id=3D"divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size: 12=
pt;
        color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica,
        sans-serif, &quot;Apple Color Emoji&quot;, &quot;Segoe UI
        Emoji&quot;, NotoColorEmoji, &quot;Segoe UI Symbol&quot;,
        &quot;Android Emoji&quot;, EmojiSymbols, &quot;Apple Color
        Emoji&quot;, &quot;Segoe UI Emoji&quot;, NotoColorEmoji,
        &quot;Segoe UI Symbol&quot;, &quot;Android Emoji&quot;,
        EmojiSymbols;">
        <p>Hi Eliot,</p>
        <p><br>
        </p>
        <p>i believe that your two examples (fridge and car) describe a
          system (fridge and car) within a larger system (smart home or
          V2X). More complex scenarios exist.</p>
        <p><br>
        </p>
        <p>You could analyze such scenarios by decomposing the larger
          system into subsystems (domains) and=C2=A0applying the
          security=C2=A0considerations to each of the domains in which th=
e
          "smart=C2=A0things or smart=C2=A0components" in that domain tal=
k to each
          other.=C2=A0</p>
        <p><br>
        </p>
        <p>Does this help you further?Would you analyze this=C2=A0in a
          different way? Do you think that this explanation should be
          included in the our document?=C2=A0</p>
        <p><br>
        </p>
        <p>Cheers, Oscar.</p>
        <br>
        <div style=3D"color:rgb(0,0,0)">
          <hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
          <div id=3D"divRplyFwdMsg" dir=3D"ltr"><font style=3D"font-size:=
11pt"
              color=3D"#000000" face=3D"Calibri, sans-serif"><b>From:</b>=

              Eliot Lear <a class=3D"moz-txt-link-rfc2396E" href=3D"mailt=
o:lear@cisco.com">&lt;lear@cisco.com&gt;</a><br>
              <b>Sent:</b> Wednesday, March 8, 2017 4:46 PM<br>
              <b>To:</b> Garcia-Morchon O, Oscar; Hannes Tschofenig;
              Kovatsch, Matthias; <a class=3D"moz-txt-link-abbreviated" h=
ref=3D"mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a><br>
              <b>Cc:</b> <a class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:T2TRG@irtf.org">T2TRG@irtf.org</a><br>
              <b>Subject:</b> Re: [T2TRG] RESTful Design &amp; Security</=
font>
            <div>=C2=A0</div>
          </div>
          <div>
            <p>Oscar,</p>
            <p>That's a great document.=C2=A0 In some ways, it's really
              several documents all rolled up into one.=C2=A0 But Let me =
ask
              some leading questions:</p>
            <ul>
              <li>Is my network-connected refrigerator a Thing or a
                component? </li>
              <li>Is the thermostat in my network-connected refrigerator
                a Thing or a component?
              </li>
              <li>Is my network-connected car a Thing or a component? </l=
i>
              <li>Is the engine that sits on the CAN bus a Thing or a
                component? </li>
            </ul>
            <p>What distinguishes a Thing from a component and when do
              your security considerations apply, and when do they not?</=
p>
            <p>Eliot<br>
            </p>
            <br>
            <div class=3D"moz-cite-prefix">On 3/8/17 4:31 PM,
              Garcia-Morchon O, Oscar wrote:<br>
            </div>
            <blockquote type=3D"cite">
              <pre>Hi Hannes,

the document " draft-irtf-t2trg-iot-seccons-01" summarizes protocols.  Bu=
t I do not think that we do this happily but seriously. Summarizing exist=
ing protocols/work is one of the goals of the document.

The document also acknowledges that devices have different capabilities a=
nd requirements, also in terms of security. In my view, this fits with th=
e idea of minimum requirements. It would be great to have your input on y=
our use cases and your views on minimum assumptions in different deployme=
nt scenarios/security capabilities of different types of devices.

Cheers, Oscar.


-----Original Message-----
From: T2TRG [<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"mailto:t2trg-bounces@irtf.org">mailto:t2trg-bounces@irtf.org</a>]=
 On Behalf Of Hannes Tschofenig
Sent: Wednesday, March 8, 2017 3:13 PM
To: Eliot Lear <a moz-do-not-send=3D"true" class=3D"moz-txt-link-rfc2396E=
" href=3D"mailto:lear@cisco.com">&lt;lear@cisco.com&gt;</a>; Kovatsch, Ma=
tthias <a moz-do-not-send=3D"true" class=3D"moz-txt-link-rfc2396E" href=3D=
"mailto:matthias.kovatsch@siemens.com">&lt;matthias.kovatsch@siemens.com&=
gt;</a>; <a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" h=
ref=3D"mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>
Cc: <a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D=
"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a>
Subject: Re: [T2TRG] RESTful Design &amp; Security

Hi Eliot,

this would indeed be a good conversation to have. I have tried to trigger=
 it a couple of times in context of the IoT device classes but it is very=
 hard to get people to state what their minimum assumptions are.

I believe it has to do with the type of standardization approach we are e=
xercising today and this gives us a hard time to describe the big picture=
 of how the various building blocks are supposed to work together. In fac=
t, the picture becomes extremely complex and fragmented since there are j=
ust so many options while at the same time we envision super constrained =
devices. The T2TRG security document
(draft-irtf-t2trg-iot-seccons-01) confirms this and happily talks about n=
ormal IPsec/IKE, diet IPsec, HIP, MIKEY, OSCOAP, JOSE, COSE, etc. etc.

Ciao
Hannes

On 03/08/2017 11:02 AM, Eliot Lear wrote:
</pre>
              <blockquote type=3D"cite">
                <pre>Matthias,

I think the key question that everyone seems to be dancing around is this=
:

What is an Internet host in the context of IoT?  What are the minimum
qualities it must possess?  I don't mean this to be a vote, but more
of a law of physics sort of thing.  For instance, does a host have a
secure unique identity?  What capabilities must it have?  I would
expect them to be very few, but there are assuredly some...

Eliot


On 3/7/17 8:36 PM, Kovatsch, Matthias wrote:
</pre>
                <blockquote type=3D"cite">
                  <pre>Fair enough.

Yes, I am on this IoT Directorate. I would say a large fraction of
the T2TRG participants has been arguing that the Internet of Gateways
is not a good approach. Your security-related summary proves this point.

I personally don't see end-to-end security happening if we keep
mixing application protocols, keep using black-magic middleboxes, and
keep using proprietary interfaces at the device level. We need
something end-to-end (or T2T) for end-to-end security.

Best wishes
Matthias



Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [<a moz-do-not-send=3D"true" class=3D"moz-txt-l=
ink-abbreviated" href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofe=
nig@gmx.net</a>]
*Received:* Tuesday, 07 Mar 2017, 20:10
*To:* Kovatsch, Matthias (CT RDA NEC EMB-DE)
[<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"m=
ailto:matthias.kovatsch@siemens.com">matthias.kovatsch@siemens.com</a>]; =
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>
[<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"m=
ailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.ca</a>]
*CC:* <a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=
=3D"mailto:T2TRG@irtf.org">T2TRG@irtf.org</a> [<a moz-do-not-send=3D"true=
" class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2TRG=
@irtf.org</a>]
*Subject:* Re: [T2TRG] RESTful Design &amp; Security

Hi Matthias,

I know that this is a research group and everyone can create whatever
they want.

We briefly talked about security at the IoT directorate conference
call and I would be interesting to hear what works and what does not
work for others.

Ciao
Hannes


On 03/07/2017 07:45 PM, Kovatsch, Matthias wrote:
</pre>
                  <blockquote type=3D"cite">
                    <pre>On big propaganda tour? :P

Regards
Matthias


Sent from my phone, limitations might apply.

-----Original Message-----
*From:* Hannes Tschofenig [<a moz-do-not-send=3D"true" class=3D"moz-txt-l=
ink-abbreviated" href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofe=
nig@gmx.net</a>]
*Received:* Tuesday, 07 Mar 2017, 19:39
*To:* Michael Richardson [<a moz-do-not-send=3D"true" class=3D"moz-txt-li=
nk-abbreviated" href=3D"mailto:mcr+ietf@sandelman.ca">mcr+ietf@sandelman.=
ca</a>]
*CC:* <a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=
=3D"mailto:t2trg@irtf.org">t2trg@irtf.org</a> [<a moz-do-not-send=3D"true=
" class=3D"moz-txt-link-abbreviated" href=3D"mailto:T2TRG@irtf.org">T2TRG=
@irtf.org</a>]
*Subject:* Re: [T2TRG] RESTful Design &amp; Security

OSCOAP does not work when

* you mix protocols,
* use a middlebox for some processing interactions (such as data
aggregation), and
* when one of the protocols is a non-RESTful protocol, such as BLE
</pre>
                  </blockquote>
                  <pre>or MQTT.
</pre>
                  <blockquote type=3D"cite">
                    <pre>Unfortunately, these the use cases we are facing=
 in current IoT
deployments. For similar reasons we cannot use RFC 8075 either.

Maybe you are seeing different deployment environments.

Ciao
Hannes

On 03/07/2017 06:39 PM, Michael Richardson wrote:
</pre>
                    <blockquote type=3D"cite">
                      <pre>Hannes Tschofenig <a moz-do-not-send=3D"true" =
class=3D"moz-txt-link-rfc2396E" href=3D"mailto:hannes.tschofenig@gmx.net"=
>&lt;hannes.tschofenig@gmx.net&gt;</a> wrote:
    &gt; Needless to say that these challenges have also been
observed
</pre>
                    </blockquote>
                  </blockquote>
                  <pre>in other
</pre>
                  <blockquote type=3D"cite">
                    <blockquote type=3D"cite">
                      <pre>    &gt; protocols as well, such as HTTP and e=
ven SIP.

    &gt; What is the story for providing application layer security?

OSCOAP seems to be end-to-end to me.

--
Michael Richardson <a moz-do-not-send=3D"true" class=3D"moz-txt-link-rfc2=
396E" href=3D"mailto:mcr+IETF@sandelman.ca">&lt;mcr+IETF@sandelman.ca&gt;=
</a>, Sandelman Software
Works  -=3D IPv6 IoT consulting =3D-



</pre>
                    </blockquote>
                    <pre>_______________________________________________
T2TRG mailing list
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:T2TRG@irtf.org">T2TRG@irtf.org</a>
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" href=3D"https=
://www.irtf.org/mailman/listinfo/t2trg">https://www.irtf.org/mailman/list=
info/t2trg</a>

</pre>
                  </blockquote>
                  <pre>_______________________________________________
T2TRG mailing list
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"ma=
ilto:T2TRG@irtf.org">T2TRG@irtf.org</a>
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" href=3D"https=
://www.irtf.org/mailman/listinfo/t2trg">https://www.irtf.org/mailman/list=
info/t2trg</a>
</pre>
                </blockquote>
              </blockquote>
              <pre>________________________________
The information contained in this message may be confidential and legally=
 protected under applicable law. The message is intended solely for the a=
ddressee(s). If you are not the intended recipient, you are hereby notifi=
ed that any use, forwarding, dissemination, or reproduction of this messa=
ge is strictly prohibited and may be unlawful. If you are not the intende=
d recipient, please contact the sender by return e-mail and destroy all c=
opies of the original message.
</pre>
            </blockquote>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------1297F3471A32EDC0EF53C42E--

--B9MTucvNmcQRPaqkgxGMTOt3xeQewXPRq--

--H3j9Qu2oTwvkQ6qtGuaMXlM1CSqkPbU8T
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJYwW3zAAoJEIe2a0bZ0nozbFwIAJIClSeyYyPgEBoEl+xiyMlA
SSb8ocS4WYTJff4lm5lDXbcchWHHku6mceEZXnMASBPZP8UjTrw9xJlUab5yp8UH
3N+NbKQqpsLeODZwYldG+qRQ8fq+N+sLv5LyZlfbFFJeXuwEMAdoKn22QVXFKy0m
8tJUEiCjGLwe/FWFpPUljxbWRD8Hu+wCRr1mk7hNyfL1YouaALiDn+X48+CJvMRf
pgUU+KFfap2K+jGIUKtLo40H/otGo1y8m7fJAcwm6VW9O7xGG+xi1SjhmOh7o+n6
dNdOtZYimD6bDa5ME0QT185+rZOZTDuXdHVCMwbvhmTIOyerOihucI0eXwDTWJc=
=fcfS
-----END PGP SIGNATURE-----

--H3j9Qu2oTwvkQ6qtGuaMXlM1CSqkPbU8T--


From nobody Thu Mar  9 23:26:53 2017
Return-Path: <rashid.sangi@huawei.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 4DD2012940B for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 23:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 OwDwhSvy4_ls for <t2trg@ietfa.amsl.com>; Thu,  9 Mar 2017 23:26:51 -0800 (PST)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9DAF126D73 for <t2trg@irtf.org>; Thu,  9 Mar 2017 23:26:50 -0800 (PST)
Received: from 172.24.1.60 (EHLO SZXEMI415-HUB.china.huawei.com) ([172.24.1.60]) by szxrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DVH90168; Fri, 10 Mar 2017 15:26:12 +0800 (CST)
Received: from SZXEMI505-MBS.china.huawei.com ([169.254.4.125]) by SZXEMI415-HUB.china.huawei.com ([10.86.210.48]) with mapi id 14.03.0235.001; Fri, 10 Mar 2017 15:26:10 +0800
From: AbdurRashidSangi <rashid.sangi@huawei.com>
To: Carsten Bormann <cabo@tzi.org>, "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: [T2TRG] T2TRG Amsterdam work meeting remote participation
Thread-Index: AQHSmOFpZ/Q5ocQx0EmJkJfiav3rCqGNrKLA
Date: Fri, 10 Mar 2017 07:26:10 +0000
Message-ID: <C3DD54213F5261438F5CE46038658EE3209BFFF9@SZXEMI505-MBS.china.huawei.com>
References: <FF7415BD-E3F2-408F-9502-8B2BE1EE749F@ericsson.com> <B62713B9-ECB0-4132-AA06-2AF975938154@ericsson.com> <17088D06-F695-42D9-A502-9913B3C98AD0@ericsson.com> <0E254046-4FA7-4810-B4B6-DDD9D96F3C5E@tzi.org>
In-Reply-To: <0E254046-4FA7-4810-B4B6-DDD9D96F3C5E@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.151.40]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.58C25514.0225, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.125, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: b016e1dd1f6b29eb611bbd2cade19687
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/drGpKUbKfswvUC9tN2QPu8XMaOA>
Subject: Re: [T2TRG] T2TRG Amsterdam work meeting remote participation
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Fri, 10 Mar 2017 07:26:53 -0000

SXQgc2VlbXMgdG9kYXkncyBXZWJFeCBpcyBwYXNzd29yZCBwcm90ZWN0ZWQhIFRoZSBwYXNzd29y
ZCwgaXMgaXQgYXZhaWxhYmxlIHdpdGggc29tZW9uZT8NCg0KUmVnYXJkcywNClJhc2hpZCBTYW5n
aS4NCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBDYXJzdGVuIEJvcm1h
bm4gW21haWx0bzpjYWJvQHR6aS5vcmddDQo+IFNlbnQ6IDIwMTflubQz5pyIOeaXpSAyMTo0OQ0K
PiBUbzogdDJ0cmdAaXJ0Zi5vcmcNCj4gU3ViamVjdDogUmU6IFtUMlRSR10gVDJUUkcgQW1zdGVy
ZGFtIHdvcmsgbWVldGluZyByZW1vdGUgcGFydGljaXBhdGlvbg0KPiANCj4gV2UgZGlkIGdldCBh
IGZldyB3ZWlyZCBlZmZlY3RzIGhlcmUg4oCUIHBsZWFzZSB0cnkgYWdhaW4gaWYgcmUtam9pbmlu
Zw0KPiBmYWlsZWQuDQo+IA0KPiBHcsO8w59lLCBDYXJzdGVuDQo+IA0KPiA+IE9uIDkgTWFyIDIw
MTcsIGF0IDE0OjQwLCBBcmkgS2Vyw6RuZW4gPGFyaS5rZXJhbmVuQGVyaWNzc29uLmNvbT4gd3Jv
dGU6DQo+ID4NCj4gPiBTZWVtcyB0aGUgR29vZ2xlIGhhbmdvdXQgc2Vzc2lvbiBkaWVkIGR1cmlu
ZyBsdW5jaCBicmVhaywgYnV0IHdlIGFyZQ0KPiBub3cgYWJvdXQgdG8gY29udGludWUuIFRoZSBs
aW5rIGJlbG93IHNob3VsZCBzdGlsbCB3b3JrLg0KPiA+DQo+ID4NCj4gPiBDaGVlcnMsDQo+ID4g
QXJpDQo+ID4NCj4gPj4gT24gMDkgTWFyIDIwMTcsIGF0IDEwOjEwLCBBcmkgS2Vyw6RuZW4gPGFy
aS5rZXJhbmVuQGVyaWNzc29uLmNvbT4NCj4gd3JvdGU6DQo+ID4+DQo+ID4+IEFuZCBsaXZlIG1l
ZXRpbmcgbWludXRlczoNCj4gPj4gaHR0cHM6Ly9kb2NzLmdvb2dsZS5jb20vZG9jdW1lbnQvZC8x
T3dmYmEtDQo+IGJWX2lWaGpCbld5YTlSMzRqTThhaXhONThDQUhpck5JOHVRY1EvZWRpdD91c3A9
c2hhcmluZw0KPiA+Pg0KPiA+PiAoYWJvdXQgdG8gc3RhcnQgaW4gZmV3IG1pbnV0ZXMpDQo+ID4+
DQo+ID4+DQo+ID4+IENoZWVycywNCj4gPj4gQXJpDQo+ID4+DQo+ID4+PiBPbiAwOSBNYXIgMjAx
NywgYXQgMDk6NTMsIEFyaSBLZXLDpG5lbiA8YXJpLmtlcmFuZW5AZXJpY3Nzb24uY29tPg0KPiB3
cm90ZToNCj4gPj4+DQo+ID4+PiBIaSwNCj4gPj4+DQo+ID4+PiBIZXJlJ3MgYSBsaW5rIHRvIEdv
b2dsZSBoYW5nb3V0IGZvciByZW1vdGUgcGFydGljaXBhbnRzOg0KPiA+Pj4gaHR0cHM6Ly9oYW5n
b3V0cy5nb29nbGUuY29tL2NhbGwvaGlyZ3FzN25sNWFzaG94cXlmZWFrYWhlem1lDQo+ID4+Pg0K
PiA+Pj4gSG93ZXZlciwgdGhlIFdpLUZpIHNlZW1zIHRvIGJlIHF1aXRlIGZsYWt5IGFuZCBsaW1p
dGVkIGJhbmR3aWR0aCBzbw0KPiBxdWFsaXR5IG1heSB2YXJ5Lg0KPiA+Pj4NCj4gPj4+DQo+ID4+
Pg0KPiA+Pj4gQ2hlZXJzLA0KPiA+Pj4gQXJpDQo+ID4+DQo+ID4NCj4gPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IFQyVFJHIG1haWxpbmcgbGlz
dA0KPiA+IFQyVFJHQGlydGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaXJ0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby90MnRyZw0KPiA+DQo+ID4NCj4gDQoNCg==


From nobody Wed Mar 15 13:25:11 2017
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 99A9C131826 for <t2trg@ietfa.amsl.com>; Wed, 15 Mar 2017 13:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 1jiZpEnrLD2M for <t2trg@ietfa.amsl.com>; Wed, 15 Mar 2017 13:25:08 -0700 (PDT)
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 030EB1317F9 for <t2trg@irtf.org>; Wed, 15 Mar 2017 13:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2FKP4fJ006039 for <t2trg@irtf.org>; Wed, 15 Mar 2017 21:25:04 +0100 (CET)
Received: from [192.168.217.124] (p5DCCCDC2.dip0.t-ipconnect.de [93.204.205.194]) (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 3vk34c12RVzDJ1V; Wed, 15 Mar 2017 21:25:04 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
X-Mao-Original-Outgoing-Id: 511302303.408464-0744aba80b7c44b5527a38e75e83da6e
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 15 Mar 2017 21:25:03 +0100
Message-Id: <C921BE33-4B35-4981-9069-0814837AF89E@tzi.org>
To: t2trg@irtf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/1WD92bPy9kzbhAD3-gcJtSS_MA0>
Subject: [T2TRG] T2TRG@IETF98
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Wed, 15 Mar 2017 20:25:09 -0000

We have uploaded a draft of the T2TRG agenda for Chicago at:

https://datatracker.ietf.org/doc/agenda-98-t2trg/

This probably requires some explanation :-)

This time, instead of a summary meeting, where the RG reports to the =
IETF and everybody also gets to read their mail, we want to try =
something new.

We will have a =E2=80=9Cdiscovery meeting=E2=80=9D, where the IETF tells =
the RG what would be good subjects for work. =20

(Of course, we have a brief status at the beginning, and there will be =
some planning of further meetings.)

So, for the main body of the RG meeting, we want to structure the =
attendance into 3 or 4 breakouts (this is still a bit open depending on =
the room), where each breakout discusses a topic area and will try to =
capture the most pressing areas of work that would benefit the topic =
area.  In the end of each such breakout round (we plan to have two, with =
different topic structures), we want to have a quick roll call of the =
results.

For each of the breakouts, we=E2=80=99ll need a facilitator, that

* leads the discussion,
* makes sure there are good notes of the outcome (probably involving =
additional note takers).

If you think we could benefit from discussing a topic area, please come =
forward as a facilitator for it.

In the end, the result of the =E2=80=9Cdiscovery meeting" will be a bit =
more than the roll call: Each breakout will generate a page or two of =
notes that the RG can then take home and process, likely shaping the =
further work of the RG.  As importantly as that, the attendees of each =
breakout session will also take home the seeds of that work, as =
discussed.

An experiment =E2=80=94 I can=E2=80=99t wait to see how well it will =
work.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Wed Mar 15 17:29:11 2017
Return-Path: <ari.keranen@ericsson.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 3E14812E6D7 for <t2trg@ietfa.amsl.com>; Wed, 15 Mar 2017 17:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 DggvjB6ElPhn for <t2trg@ietfa.amsl.com>; Wed, 15 Mar 2017 17:29:08 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 5955312EE44 for <t2trg@irtf.org>; Wed, 15 Mar 2017 17:29:07 -0700 (PDT)
X-AuditID: c1b4fb25-ccfff70000002d78-02-58c9dc50718f
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by  (Symantec Mail Security) with SMTP id E2.F8.11640.05CD9C85; Thu, 16 Mar 2017 01:29:05 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.56]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0319.002; Thu, 16 Mar 2017 01:28:57 +0100
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>
CC: "t2trg-chairs@ietf.org" <t2trg-chairs@ietf.org>, "icnrg-chairs@ietf.org" <icnrg-chairs@ietf.org>
Thread-Topic: T2TRG related topics for the ICNRG meeting at Chicago
Thread-Index: AQHSnexMoTu5dSdhzEy23oiM5R17OA==
Date: Thu, 16 Mar 2017 00:28:56 +0000
Message-ID: <EC482CC9-7689-46F2-9F7A-D8ADA4548E8D@ericsson.com>
Reply-To: "t2trg-chairs@ietf.org" <t2trg-chairs@ietf.org>, "icnrg-chairs@ietf.org" <icnrg-chairs@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0575D73D6A08A4438D3ADBD9720B741C@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphkeLIzCtJLcpLzFFi42KZGbHdWDfwzskIg655Mha3tn9nsmi7+IHR 4v2DHhYHZo8lS34yeUzeeJgtgCmKyyYlNSezLLVI3y6BK2P5tZ0sBStZK7obvrA3MO5j6WLk 5JAQMJE4enMrYxcjF4eQwDpGibe7fzFDOIsZJT687WAEqWITsJeYvOYjmC0ioCqxceZGVhCb WSBN4t6Hx0wgtrCAncScPRtYIWqcJZ6/uA1l60n03ZzBDGKzAPX2PPnD3sXIzsELNPNVMkhU SCBH4t2y6WDTGQXEJL6fWsMEMV1c4taT+UwQdwpILNlznhnCFpV4+fgfK4StJNG45AnUNXoS N6ZOYYOwrSWWnP4DNUdbYtnC12C9vAKCEidnPmGZwCg6C8mKWUjaZyFpn4WkfRaS9gWMrKsY RYtTi5Ny042M9VKLMpOLi/Pz9PJSSzYxAuPo4JbfqjsYL79xPMQowMGoxMP7IexkhBBrYllx Ze4hRgkOZiUR3oOhQCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8ZivvhwsJpCeWpGanphakFsFk mTg4pRoYmaTzbrQdmHtl7f9w4eVbpr1ZzTi9SD743d1OroVVtieFeosO7dHnerk0YrU0T3ZI 7L6+mKubX++Z/Jj1Efu0CmGjBXveii/9Y18dp5hi5mYk9/tcqPM1YSbLyc8OlDQfO/hi4yd7 Nrdmv+aH86ZKn/7Urh1v9L3TtOHy8qXp8mw31a7e33L+uRJLcUaioRZzUXEiAFirQUefAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/MbCMBSGMDch-m-W9fJg2hJ2qNaI>
Subject: [T2TRG] T2TRG related topics for the ICNRG meeting at Chicago
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 16 Mar 2017 00:29:10 -0000

Hi all,

Since we will not have scheduled T2TRG activity for the weekend before the =
IETF, it's a good opportunity to take advantage of the ICNRG interim meetin=
g on Sunday [1] to continue our work together on IoT and ICN that we starte=
d at Seoul [2].

If you would like to propose discussion topics for the ICNRG interim, pleas=
e drop an e-mail to the chairs of both groups (icnrg-chairs@ietf.org, t2trg=
-chairs@ietf.org).


Thanks,
Ari

[1] https://trac.ietf.org/trac/irtf/wiki/icnrg#ICNRGInterimmeetingIETF-98Ch=
icagoILUSAMarch26th2017
[2] https://www.ietf.org/proceedings/interim-2016-icnrg-09/minutes/minutes-=
interim-2016-icnrg-09-201611130900-00=


From nobody Mon Mar 27 00:17:31 2017
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 26A39129411; Mon, 27 Mar 2017 00:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 9Sp3IUgdhnzW; Mon, 27 Mar 2017 00:17:09 -0700 (PDT)
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 A1E4C12943E; Mon, 27 Mar 2017 00:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v2R7H5CC000363; Mon, 27 Mar 2017 09:17:05 +0200 (CEST)
Received: from client-0161.vpn.uni-bremen.de (client-0161.vpn.uni-bremen.de [134.102.107.161]) (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 3vs51r3qGczDHZS; Mon, 27 Mar 2017 09:17:04 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 27 Mar 2017 02:17:02 -0500
Cc: lo <6lo@ietf.org>, core <core@ietf.org>, ace@ietf.org
X-Mao-Original-Outgoing-Id: 512291822.346343-47e2969abfd4b61dad48cd9e4a28d700
Reply-To: t2trg@irtf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <003A0EEA-EAC8-4C64-AFC1-174E8360AB63@tzi.org>
References: <149059838707.8031.8688478547594865185.idtracker@ietfa.amsl.com>
To: t2trg@irtf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/weGQHZQOPDTzfZrcdtiF2XOHIZ4>
Subject: [T2TRG] SWORN: Secure Wake on Radio Nudging
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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, 27 Mar 2017 07:17:12 -0000

I just submitted draft-bormann-t2trg-sworn-00.txt, which describes a =
secure way for applications to wake sleepy nodes.

For 6lo, it may be of interest as a way to expose a MAC layer feature to =
the application layer in a secure way.

For CoRE, it shows an unusual way to use the CoAP protocol.

For ACE, it is an example of properly authorizing network functions. =20
(It is also an example of using COSE =E2=80=94 it could even use CWT, =
but I didn=E2=80=99t specify that part.)

(I probably could add other WGs, but the IETF mail server will only =
allow so many destination addresses.)

I=E2=80=99m looking forward to discussion about this little note, and =
what kinds of standards possibly could be derived from it.

Gr=C3=BC=C3=9Fe, Carsten

> Htmlized:       =
https://tools.ietf.org/html/draft-bormann-t2trg-sworn-00
>=20
>=20
> Abstract:
>   Normally off devices (RFC7228) would need to expend considerable
>   energy resources to be reachable at all times.  Instead, MAC layer
>   mechanisms are often employed that allow the last hop router of the
>   device to "wake" the device via radio when needed.  Activating these
>   devices even for a short time still does expend energy and thus
>   should be available to authorized correspondents only.
>   Traditionally, this has been achieved by heavy firewalling, allowing
>   only authorized hosts to reach the device at all.  This may be too
>   inflexible for an Internet of Things.
>=20
>   The present report describes how to use a combination of currently
>   standardized (or in progress) technologies to securely effect this
>   authorization.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Mar 27 02:00:50 2017
Return-Path: <Niclas.Granqvist@polar.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 22A881294BF for <t2trg@ietfa.amsl.com>; Mon, 27 Mar 2017 02:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 SKmw9BqjqRi4 for <t2trg@ietfa.amsl.com>; Mon, 27 Mar 2017 02:00:46 -0700 (PDT)
Received: from secure.polar.fi (secure.polar.fi [62.61.73.19]) (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 71ECB1294BD for <t2trg@irtf.org>; Mon, 27 Mar 2017 02:00:44 -0700 (PDT)
Received: from niva.polar.grp (unknown [192.168.26.129]) by secure.polar.fi (Postfix) with ESMTP id D9E09E00119 for <t2trg@irtf.org>; Mon, 27 Mar 2017 12:00:40 +0300 (EEST)
Auto-Submitted: auto-generated
From: Niclas Granqvist <Niclas.Granqvist@polar.com>
To: t2trg@irtf.org
Message-ID: <OF206B6F29.7EE06EDA-ONC12580F0.00317FD7-C12580F0.00317FD7@polar.com>
Date: Mon, 27 Mar 2017 11:00:39 +0200
X-MIMETrack: Serialize by Router on PEFI1_NOTES10/PEG(Release 9.0.1FP7|August 17, 2016) at 03/27/2017 11:52:01
MIME-Version: 1.0
Content-type: multipart/alternative;  Boundary="0__=4EBB0A63DFA2F9478f9e8a93df938690918c4EBB0A63DFA2F947"
Content-Disposition: inline
X-Policy-Override: no
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/HyppL-J03zNPoDewuPDv9JGbP5c>
Subject: [T2TRG] AUTO: Niclas Granqvist/RD/PESW1/PEG is out of the office. (returning 03.04.2017)
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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, 27 Mar 2017 09:00:48 -0000

--0__=4EBB0A63DFA2F9478f9e8a93df938690918c4EBB0A63DFA2F947
Content-type: text/plain; charset=ISO-8859-2
Content-transfer-encoding: quoted-printable



I am out of the office until 03.04.2017.

Hi, you have reached my mail box.

If it=B4s an urgent matters please call +41 (0)79 814 9161
me on the cell phone or send a message to sami.karvonen@polar.com

I will respond to your message when I return.


Note: This is an automated response to your message  "[6lo] SWORN: Secu=
re
Wake on Radio Nudging" sent on 27.03.2017 09:17:02.

This is the only notification you will receive while this person is awa=
y.=

--0__=4EBB0A63DFA2F9478f9e8a93df938690918c4EBB0A63DFA2F947
Content-type: text/html; charset=ISO-8859-2
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
<p><font size=3D"1" face=3D"sans-serif">I am out of the office until 03=
.04.2017.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">Hi, you have reached my mai=
l box.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">If it=B4s an urgent matters=
 please call +41 (0)79 814 9161<br>
</font><font size=3D"1" face=3D"sans-serif">me on the cell phone or sen=
d a message to sami.karvonen@polar.com<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif">I will respond to your mess=
age when I return.<br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" face=3D"sans-serif"><br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif">Note: Thi=
s is an automated response to your message &nbsp;&quot;</font><font siz=
e=3D"1" face=3D"sans-serif"><b>[6lo] SWORN: Secure Wake on Radio Nudgin=
g&quot;</b></font><font size=3D"1" color=3D"#808080" face=3D"sans-serif=
">&nbsp;sent on </font><font size=3D"1" face=3D"sans-serif"><b>27.03.20=
17 09:17:02</b></font><font size=3D"1" color=3D"#808080" face=3D"sans-s=
erif">. <br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif"><br>
</font><font size=3D"1" color=3D"#808080" face=3D"sans-serif">This is t=
he only notification you will receive while this person is away.</font>=
</body></html>=

--0__=4EBB0A63DFA2F9478f9e8a93df938690918c4EBB0A63DFA2F947--


From nobody Thu Mar 30 11:29:08 2017
Return-Path: <kovatsch@inf.ethz.ch>
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 75881129453 for <t2trg@ietfa.amsl.com>; Thu, 30 Mar 2017 11:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 dArf7jJjZbEw for <t2trg@ietfa.amsl.com>; Thu, 30 Mar 2017 11:29:04 -0700 (PDT)
Received: from edge20.ethz.ch (edge20.ethz.ch [82.130.99.26]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEB92128616 for <t2trg@irtf.org>; Thu, 30 Mar 2017 11:29:02 -0700 (PDT)
Received: from CAS10.d.ethz.ch (172.31.38.210) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Mar 2017 20:28:53 +0200
Received: from MBX210.d.ethz.ch ([fe80::ed77:7d47:9467:69a9]) by CAS10.d.ethz.ch ([fe80::cce:fc66:7b56:a06a%10]) with mapi id 14.03.0319.002; Thu, 30 Mar 2017 20:29:00 +0200
From: "Kovatsch  Matthias" <kovatsch@inf.ethz.ch>
To: "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: Discovery session at IETF 98: Breakout 1 (Different kinds of data models)
Thread-Index: AQHSqYN/JdqqSNzn2kmlD7ScpEaxPQ==
Date: Thu, 30 Mar 2017 18:28:59 +0000
Message-ID: <55877B3AFB359744BA0F2140E36F52B558B20F4C@MBX210.d.ethz.ch>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.138.52]
Content-Type: multipart/alternative; boundary="_000_55877B3AFB359744BA0F2140E36F52B558B20F4CMBX210dethzch_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/w7IAl3bL7eJBrzJP7UBymdwm_xQ>
Subject: [T2TRG] Discovery session at IETF 98: Breakout 1 (Different kinds of data models)
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Thu, 30 Mar 2017 18:29:06 -0000

--_000_55877B3AFB359744BA0F2140E36F52B558B20F4CMBX210dethzch_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear group

I actually put the summary of breakout 1 onto GitHub:

https://github.com/t2trg/2017-ietf98/blob/master/breakout-datamodels.md

Please check it, correct it, amend it, etc. (pull request or response to th=
is thread). In particular, it would be nice to elaborate on the "Who wants =
to work on this" section! Please put your name and some pointers where or h=
ow you want to contribute.

Best wishes
Matthias

--_000_55877B3AFB359744BA0F2140E36F52B558B20F4CMBX210dethzch_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:=
0;}</style>
</head>
<body ocsi=3D"0" fpstyle=3D"1">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">Dear group<br>
<br>
I actually put the summary of breakout 1 onto GitHub:<br>
<br>
<a href=3D"https://github.com/t2trg/2017-ietf98/blob/master/breakout-datamo=
dels.md" target=3D"_blank">https://github.com/t2trg/2017-ietf98/blob/master=
/breakout-datamodels.md</a><br>
<br>
Please check it, correct it, amend it, etc. (pull request or response to th=
is thread). In particular, it would be nice to elaborate on the &quot;Who w=
ants to work on this&quot; section! Please put your name and some pointers =
where or how you want to contribute.<br>
<br>
Best wishes<br>
Matthias<br>
</div>
</body>
</html>

--_000_55877B3AFB359744BA0F2140E36F52B558B20F4CMBX210dethzch_--


From nobody Fri Mar 31 05:10:40 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: t2trg@irtf.org
Delivered-To: t2trg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CAE51242F5; Fri, 31 Mar 2017 05:10:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: t2trg@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149096223226.21673.18068659455067899990@ietfa.amsl.com>
Date: Fri, 31 Mar 2017 05:10:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/ST_PiIDoUaZpE-TIu_6yysPRh8Y>
Subject: [T2TRG] I-D Action: draft-irtf-t2trg-iot-seccons-02.txt
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Fri, 31 Mar 2017 12:10:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Thing-to-Thing of the IETF.

        Title           : State of the Art and Challenges for the Internet of Things
        Authors         : Oscar Garcia-Morchon
                          Sandeep S. Kumar
                          Mohit Sethi
	Filename        : draft-irtf-t2trg-iot-seccons-02.txt
	Pages           : 56
	Date            : 2017-03-31

Abstract:
   The Internet of Things concept refers to the usage of standard
   Internet protocols to allow for human-to-thing or thing-to-thing
   communication.  The security needs are well-recognized and and many
   standardization steps have been taken, for example, specification of
   CoAP over DTLS.  However, security challenges still exist and there
   are some use cases that lack a suitable solution.  This document
   first provides an overview of security architecture, its deployment
   model, security needs in the context of the lifecycle of a thing, as
   well as the state of the art on IoT security.  Then, we discuss the
   concept of security profiles for the successful roll-out of secure
   IoT applications and describe remaining security challenges in the
   IoT.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-t2trg-iot-seccons/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-02
https://datatracker.ietf.org/doc/html/draft-irtf-t2trg-iot-seccons-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-irtf-t2trg-iot-seccons-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Mar 31 06:47:40 2017
Return-Path: <georgios.karagiannis@huawei.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 6F81B12984C for <t2trg@ietfa.amsl.com>; Fri, 31 Mar 2017 06:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 k9y6_3QOCnQ8 for <t2trg@ietfa.amsl.com>; Fri, 31 Mar 2017 06:47:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17A71296B3 for <t2trg@irtf.org>; Fri, 31 Mar 2017 06:47:22 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DKA63693; Fri, 31 Mar 2017 13:47:19 +0000 (GMT)
Received: from LHREML502-MBS.china.huawei.com ([10.201.109.53]) by lhreml707-cah.china.huawei.com ([10.201.108.48]) with mapi id 14.03.0301.000;  Fri, 31 Mar 2017 14:47:13 +0100
From: Georgios Karagiannis <georgios.karagiannis@huawei.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: Survey on IoT Identifiers organised by AIOTI (Alliance for IoT Innovation)
Thread-Index: AQHSqiVMuzgS9RNFQ0iLImlFjhgwbQ==
Date: Fri, 31 Mar 2017 13:47:12 +0000
Message-ID: <C5034E44CD620A44971BAAEB372655DC2DCAC435@lhreml502-mbs>
References: <149096223226.21673.18068659455067899990@ietfa.amsl.com>
In-Reply-To: <149096223226.21673.18068659455067899990@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.147.216]
Content-Type: multipart/alternative; boundary="_000_C5034E44CD620A44971BAAEB372655DC2DCAC435lhreml502mbs_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.58DE5DE9.0048, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8fd3f6f053fe5905d32ca0c76fd0d3c7
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/MpHczpYyTzuehrcl8scZsWgiN4U>
Subject: [T2TRG] Survey on IoT Identifiers organised by AIOTI (Alliance for IoT Innovation)
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <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: Fri, 31 Mar 2017 13:47:38 -0000

--_000_C5034E44CD620A44971BAAEB372655DC2DCAC435lhreml502mbs_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear T2TRG members,

The Alliance for Internet of Things Innovation AIOTI (www.aioti.org<http://=
www.aioti.org>) was initiated by the European Commission in 2015, with the =
aim to strengthen the dialogue and interaction among Internet of Things (Io=
T) players in Europe, and to contribute to the creation of a dynamic Europe=
an IoT ecosystem to speed up the take up of IoT. Further objectives of the =
Alliance are fostering experimentation, replication, and deployment of IoT =
and supporting convergence and interoperability of IoT standards; gathering=
 evidence on market obstacles for IoT deployment; and mapping and bridging =
global, EU, and member states' IoT innovation activities.

AIOTI Working Group 03 is a focus of European engagement and steering in th=
e IoT standardization process:

-       Maintain a view on the landscape of IoT standards-relevant activiti=
es being driven by Standard Developing Organizations, Consortia, Alliances =
and Open Source Software projects

-       Provide a forum for analysis, discussion and alignment of strategic=
, cross-domain, technical themes and shared concerns across landscape activ=
ities

-       Develop recommendations and guidelines addressing those concerns

-       Engage the IoT community in disseminating and promoting the results=
 and steering emerging standards
Note that AIOTI will not develop standards itself but interact with standar=
dization development organizations and consortia in order to initiate stand=
ardization activities.

Identification plays an important role for IoT. In addition to the identifi=
cation of the Things identification of other entities will be needed. Vario=
us identification schemes already exist, are standardized and deployed. A t=
horough analysis of the identification needs and related standardization fo=
r IoT is therefore needed. The AIOTI WG03 IoT Identifier task force was set=
up specifically to

-       Evaluate identification needs for IoT and related requirements

-       Collect existing identification standards and ongoing standardizati=
on work and elaborate their applicability for IoT.
The results of these activities will be published in a public report on IoT=
 Identifiers.

The task force has setup a online survey in order to collect input for the =
above task.

IoT Identifier Survey<https://goo.gl/forms/vT22nR1ZEh13lfzi1> (https://goo.=
gl/forms/vT22nR1ZEh13lfzi1)

We are kindly asking T2TRG members to provide feedback to the survey until =
Friday April 7th 2017.

Please also feel free to distribute this survey request to the members of t=
he IoT related IETF WGs for their individual feedback to the survey.

Please note, that the information that you provide will be anonymized, i.e.=
 there will be no reference to your specific contribution to the survey in =
the public report. Still you can request to be listed in the report as a co=
ntributor to the survey without reference to your specific contribution.
A pdf file with the survey questions is attached for your information, but =
please use the only survey (see link above) for your feedback.

In case you have questions on the survey don't hesitate to contact the co-c=
hair of the AITOI WG3 IoT Identifier task force (juergen.heiles@siemens.com=
<mailto:juergen.heiles@siemens.com>, henri.barthel@gs1.org<mailto:henri.bar=
thel@gs1.org>).

Moreover, please note that I am attending the IETF'98 in Chicago USA.
If you would like to meet during this IETF meeting to discuss topics that a=
re related to this IoT Identifier survey, please let me know.

Best Regards
Georgios Karagiannis
AIOTI WG03 vice chair


--_000_C5034E44CD620A44971BAAEB372655DC2DCAC435lhreml502mbs_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:126750677;
	mso-list-type:hybrid;
	mso-list-template-ids:-1596445254 -957864004 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Arial","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Dear T2TRG members,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">The Alliance for Internet of Things Innov=
ation AIOTI (<a href=3D"http://www.aioti.org">www.aioti.org</a>) was initia=
ted by the European Commission in 2015, with the aim to strengthen
 the dialogue and interaction among Internet of Things (IoT) players in Eur=
ope, and to contribute to the creation of a dynamic European IoT ecosystem =
to speed up the take up of IoT. Further objectives of the Alliance are fost=
ering experimentation, replication,
 and deployment of IoT and supporting convergence and interoperability of I=
oT standards; gathering evidence on market obstacles for IoT deployment; an=
d mapping and bridging global, EU, and member states' IoT innovation activi=
ties.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">AIOTI Working Group 03 is a focus of Euro=
pean engagement and steering in the IoT standardization process:<o:p></o:p>=
</span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<s=
pan style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;">Maintain a view on the landscape =
of IoT standards-relevant activities being driven by Standard Developing Or=
ganizations, Consortia, Alliances and Open Source Software
 projects<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<s=
pan style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;">Provide a forum for analysis, dis=
cussion and alignment of strategic, cross-domain, technical themes and shar=
ed concerns across landscape activities<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<s=
pan style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;">Develop recommendations and guide=
lines addressing those concerns<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<s=
pan style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;">Engage the IoT community in disse=
minating and promoting the results and steering emerging standards<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Note that AIOTI will not develop standard=
s itself but interact with standardization development organizations and co=
nsortia in order to initiate standardization activities.<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Identification plays an important role fo=
r IoT. In addition to the identification of the Things identification of ot=
her entities will be needed. Various identification schemes
 already exist, are standardized and deployed. A thorough analysis of the i=
dentification needs and related standardization for IoT is therefore needed=
. The AIOTI WG03 IoT Identifier task force was setup specifically to<o:p></=
o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<s=
pan style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;">Evaluate identification needs for=
 IoT and related requirements<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">-<s=
pan style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;">Collect existing identification s=
tandards and ongoing standardization work and elaborate their applicability=
 for IoT.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">The results of these activities will be p=
ublished in a public report on IoT Identifiers.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">The task force has setup a online survey =
in order to collect input for the above task.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;"><a href=3D"https://goo.gl/forms/vT22nR=
1ZEh13lfzi1">IoT Identifier Survey</a> (<a href=3D"https://goo.gl/forms/vT2=
2nR1ZEh13lfzi1">https://goo.gl/forms/vT22nR1ZEh13lfzi1</a>)
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:black">We are kindly asking T2TRG=
 members to provide feedback to the survey until Friday April 7<sup>th</sup=
> 2017</span></b><span style=3D"font-size:10.0pt;font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;;color:black">.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;">Please also feel free to distribute th=
is survey request to the members of the IoT related IETF WGs for their indi=
vidual feedback to the survey.<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Please note, that the information that yo=
u provide will be anonymized, i.e. there will be no reference to your speci=
fic contribution to the survey in the public report. Still
 you can request to be listed in the report as a contributor to the survey =
without reference to your specific contribution.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">A pdf file with the survey questions is a=
ttached for your information, but please use the only survey (see link abov=
e) for your feedback.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">In case you have questions on the survey =
don&#8217;t hesitate to contact the co-chair of the AITOI WG3 IoT Identifie=
r task force (<a href=3D"mailto:juergen.heiles@siemens.com">juergen.heiles@=
siemens.com</a>,
<a href=3D"mailto:henri.barthel@gs1.org">henri.barthel@gs1.org</a><span sty=
le=3D"color:#1F497D">)</span>.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Moreover, please note that I am attending=
 the IETF&#8217;98 in Chicago USA.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">If you would like to meet during this IET=
F meeting to discuss topics that are related to this IoT Identifier survey,=
 please let me know.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Best Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal">Georgios Karagiannis<o:p></o:p></p>
<p class=3D"MsoNormal">AIOTI WG03 vice chair<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_C5034E44CD620A44971BAAEB372655DC2DCAC435lhreml502mbs_--

