
From nobody Thu Jun  1 14:51:25 2017
Return-Path: <m.waehlisch@fu-berlin.de>
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 C0196124B0A; Thu,  1 Jun 2017 14:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level: 
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, 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 K-JxUD_X24SY; Thu,  1 Jun 2017 14:51:22 -0700 (PDT)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 3ABDD1241FC; Thu,  1 Jun 2017 14:51:22 -0700 (PDT)
Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from <m.waehlisch@fu-berlin.de>) id <1dGY00-001u3t-5W>; Thu, 01 Jun 2017 23:51:20 +0200
Received: from x5ce76966.dyn.telefonica.de ([92.231.105.102] helo=mw-PC.fritz.box) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1:AES256-SHA:256) (envelope-from <m.waehlisch@fu-berlin.de>) id <1dGXzz-002nx8-Re>; Thu, 01 Jun 2017 23:51:20 +0200
Date: Thu, 1 Jun 2017 23:50:35 +0200
From: Matthias Waehlisch <m.waehlisch@fu-berlin.de>
To: icnrg <icnrg@irtf.org>, T2TRG@irtf.org
Message-ID: <alpine.WNT.2.00.1706012347510.8164@mw-PC>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
X-X-Sender: waehl@mail.zedat.fu-berlin.de
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Originating-IP: 92.231.105.102
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/FbQENzbo_DKIUr3DKoT3izGb9gI>
Subject: [T2TRG] GI-Dagstuhl IoT Hackathon from July 23-28, 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: Thu, 01 Jun 2017 21:51:24 -0000

Folks,

  if you or your students are interested in IoT or ICN ;) and like to 
code, please distribute the Call for Participation for the first 
GI-Dagstuhl Hackathon.


Thanks
  matthias



*************************************************************
Call for Participation
GI-Dagstuhl IoT Hackathon: From Research to Practice

July 23-28, 2017

https://dagstuhl-hackathon17.github.io/
http://www.dagstuhl.de/de/programm/kalender/evhp/?semnr=17303
*************************************************************


The objective of the first GI-Dagstuhl Hackathon is to explore 
challenging problems in the Internet of Things (IoT) by both design 
discussions and practical prototyping of technical solutions. A special 
focus will be on potentials of information-centric networking for the 
IoT.

The hackathon will bring together advanced students and early career 
researchers with senior scientists from academia and industry. The 
hackathon will consist of some technical background sessions and mostly 
hands-on hacking.

The topics of interest for this GI-Dagstuhl Hackathon include but are 
not limited to

* application of ICN concepts to IoT.
* extending, enhancing, unifying existing ICN codebases for well-known IoT operating systems such as RIOT.
* exploring data-centric security in IoT, trying out various security methods, evaluating feasibility, etc.
* other non-ICN topics for IoT.


If you are intersted in participation, please submit the following 
details in a single PDF file to the organizers (see 
https://dagstuhl-hackathon17.github.io/call)

* brief CV.
* brief motivation statement.
* topics that you are interested in.
* link to your code repository (e.g., GitHub), if available.
* indication if you plan to attend IETF 99 as well.

Feel free to already sketch a concrete project that you want to work on.

Note that all code contributions of the GI-Dagstuhl Hackathon will be 
open source and made publicly available via GitHub.


Application deadline
* June 30, 2017

Acceptance Notification
* July 2, 2017 



--
Prof. Dr. Matthias Waehlisch
.  Freie Universitaet Berlin, Computer Science
.. http://www.cs.fu-berlin.de/~waehl


From nobody Fri Jun  2 00:18:50 2017
Return-Path: <session-request@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 3267612441E; Fri,  2 Jun 2017 00:18:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: cabo@tzi.org, t2trg@irtf.org, irtf-chair@irtf.org, t2trg-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149638792915.31851.1078700246301775809.idtracker@ietfa.amsl.com>
Date: Fri, 02 Jun 2017 00:18:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/OLuImMPrfFwFIz6wRiMtOhSaVAU>
Subject: [T2TRG] t2trg - New Meeting Session Request for IETF 99
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, 02 Jun 2017 07:18:49 -0000

A new meeting session request has just been submitted by Carsten Bormann, a Chair of the t2trg working group.


---------------------------------------------------------
Working Group Name: Thing-to-Thing
Area Name: IRTF
Session Requester: Carsten Bormann

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 120
Conflicts to Avoid: 
 First Priority: cbor httpbis core ace lpwan 6lo roll teep ice
 Second Priority: dnssd saag irtfopen 6tisch netconf netmod sacm artarea
 Third Priority: lwig detnet quic v6ops opsarea cfrg icnrg intarea


People who must be present:
  Carsten Bormann
  Ari Keranen

Resources Requested:

Special Requests:
  Early in the week would help so participants from the Saturday/Sunday
workshop can hang around.
Please also avoid any IoT related BOFs that might come up.
---------------------------------------------------------


From nobody Tue Jun  6 22:57:41 2017
Return-Path: <simonmayer@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 5CCEE12E043; Tue,  6 Jun 2017 22:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-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 s2XmcmivQVJw; Tue,  6 Jun 2017 22:38:42 -0700 (PDT)
Received: from goliath.siemens.com (goliath.siemens.com [136.157.241.27]) (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 250F2129B16; Tue,  6 Jun 2017 22:38:42 -0700 (PDT)
Received: from mail4.usa.siemens.com (mail4.usa.siemens.com [136.157.7.59]) by goliath.siemens.com (8.14.7/8.14.7) with ESMTP id v575cete017735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 7 Jun 2017 01:38:40 -0400
Received: from USMLVA0EC01MSX.ww017.siemens.net ([161.134.243.153]) by mail4.usa.siemens.com (8.14.7/8.14.7) with ESMTP id v575cd0A031293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 7 Jun 2017 01:38:40 -0400
Received: from USLZUA0EM21MSX.ww017.siemens.net ([169.254.3.41]) by USMLVA0EC01MSX.ww017.siemens.net ([161.134.243.153]) with mapi id 14.03.0339.000; Wed, 7 Jun 2017 01:38:38 -0400
From: "Mayer, Simon" <simonmayer@siemens.com>
To: "stefan.schneegass@uni-due.de" <stefan.schneegass@uni-due.de>
Thread-Topic: IoT 2017: Deadline Extension until June 20
Thread-Index: AdLfUEtn0H71OcpdSNO9Ge5v7CzCWg==
Date: Wed, 7 Jun 2017 05:38:38 +0000
Message-ID: <0BF6298221F34E48B14697AF143FEF0F26B501ED@USLZUA0EM21MSX.ww017.siemens.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.134.175.67]
Content-Type: multipart/alternative; boundary="_000_0BF6298221F34E48B14697AF143FEF0F26B501EDUSLZUA0EM21MSXw_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/P_z-p4iirhaq6rsL_-MNIj9S4iE>
X-Mailman-Approved-At: Tue, 06 Jun 2017 22:57:39 -0700
Subject: [T2TRG] IoT 2017: Deadline Extension until June 20
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, 07 Jun 2017 05:38:44 -0000

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

Dear colleagues,

we have decided to extend the full paper deadline of IoT 2017 by 2 weeks, u=
ntil June 20, to attract more submissions and give authors of submitted man=
uscripts more time for polishing their contributions.

Please help us spread this information and the IoT 2017 call for papers (ht=
tp://iot-conference.org/iot2017/iot2017/call-for-papers/) to everyone you t=
hink might be interested in attending the conference and contributing to it=
s technical program.

Thank you and best wishes,
Simon Mayer and Stefan Schneegass

---

IoT 2017 Resources:
- Conference Website (will be updated shortly): http://iot-conference.org/
- Submission website: https://easychair.org/conferences/?conf=3Diot2017
- IoT 2017 Poster: https://www.pervasive.jku.at/iot2017/IOT2017-Plakat-DINA=
2-final.pdf
- PDF Call for Papers: http://iot-conference.org/iot2017/wp-content/uploads=
/2017/01/IoT-2017-CFP-4.pdf


This message and any attachments are solely for the use of intended recipie=
nts. The information contained herein may include trade secrets, protected =
health or personal information, privileged or otherwise confidential inform=
ation. Unauthorized review, forwarding, printing, copying, distributing, or=
 using such information is strictly prohibited and may be unlawful. If you =
are not an intended recipient, you are hereby notified that you received th=
is email in error, and that any review, dissemination, distribution or copy=
ing of this email and any attachment is strictly prohibited. If you have re=
ceived this email in error, please contact the sender and delete the messag=
e and any attachment from your system. Thank you for your cooperation

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial" size=3D"2"><span style=3D"font-size:11pt;">
<div><font color=3D"#222222">Dear colleagues,<br>

<br>

we have decided to extend the full paper deadline of IoT 2017 by 2 weeks, u=
ntil June 20, to attract more submissions and give authors of submitted man=
uscripts more time for polishing their contributions.<br>

<br>

Please help us spread this information and the IoT 2017 call for papers (<a=
 href=3D"http://iot-conference.org/iot2017/iot2017/call-for-papers/"><font =
color=3D"blue"><u>http://iot-conference.org/iot2017/iot2017/call-for-papers=
/</u></font></a>) to everyone you think
might be interested in attending the conference and contributing to its tec=
hnical program.<br>

<br>

Thank you and best wishes,<br>

Simon Mayer and Stefan Schneegass<br>

<br>

---<br>

<br>

IoT 2017 Resources:<br>

- Conference Website (will be updated shortly): <a href=3D"http://iot-confe=
rence.org/"><font color=3D"blue"><u>http://iot-conference.org/</u></font></=
a></font></div>
<div><font color=3D"#222222">- Submission website: <a href=3D"https://easyc=
hair.org/conferences/?conf=3Diot2017"><font color=3D"blue"><u>https://easyc=
hair.org/conferences/?conf=3Diot2017</u></font></a></font></div>
<div><font color=3D"#222222">- IoT 2017 Poster: <a href=3D"https://www.perv=
asive.jku.at/iot2017/IOT2017-Plakat-DINA2-final.pdf"><font color=3D"blue"><=
u>https://www.pervasive.jku.at/iot2017/IOT2017-Plakat-DINA2-final.pdf</u></=
font></a></font></div>
<div><font color=3D"#222222">- PDF Call for Papers: <a href=3D"http://iot-c=
onference.org/iot2017/wp-content/uploads/2017/01/IoT-2017-CFP-4.pdf"><font =
color=3D"blue"><u>http://iot-conference.org/iot2017/wp-content/uploads/2017=
/01/IoT-2017-CFP-4.pdf</u></font></a></font></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Times New Roman" size=3D"2"><span style=3D"font-size:9pt=
;">This message and any attachments are solely for the use of intended reci=
pients. The information contained herein may include trade secrets, protect=
ed health or personal information, privileged
or otherwise confidential information. Unauthorized review, forwarding, pri=
nting, copying, distributing, or using such information is strictly prohibi=
ted and may be unlawful. If you are not an intended recipient, you are here=
by notified that you received this
email in error, and that any review, dissemination, distribution or copying=
 of this email and any attachment is strictly prohibited. If you have recei=
ved this email in error, please contact the sender and delete the message a=
nd any attachment from your system.
Thank you for your cooperation</span></font></div>
</span></font>
</body>
</html>

--_000_0BF6298221F34E48B14697AF143FEF0F26B501EDUSLZUA0EM21MSXw_--


From nobody Tue Jun  6 23:36:22 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 111DD127077 for <t2trg@ietfa.amsl.com>; Tue,  6 Jun 2017 23:36:21 -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 VNb8EhynGOWD for <t2trg@ietfa.amsl.com>; Tue,  6 Jun 2017 23:36:18 -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 ADDFA120725 for <t2trg@irtf.org>; Tue,  6 Jun 2017 23:36:17 -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 v576aCLp029203 for <t2trg@irtf.org>; Wed, 7 Jun 2017 08:36:12 +0200 (CEST)
Received: from client-0084.vpn.uni-bremen.de (client-0084.vpn.uni-bremen.de [134.102.107.84]) (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 3wjJjS45NWzDKdR; Wed,  7 Jun 2017 08:36:12 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0BF6298221F34E48B14697AF143FEF0F26B501ED@USLZUA0EM21MSX.ww017.siemens.net>
Date: Wed, 7 Jun 2017 08:36:11 +0200
X-Mao-Original-Outgoing-Id: 518510171.811394-661a460e5cb6be21a565363ee344548a
Content-Transfer-Encoding: quoted-printable
Message-Id: <A00FA44B-B7B0-47D8-961E-758D5FD0C165@tzi.org>
References: <0BF6298221F34E48B14697AF143FEF0F26B501ED@USLZUA0EM21MSX.ww017.siemens.net>
To: t2trg@irtf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/F6KD4Vu0KxqtJ39BROLK8_h8hsg>
Subject: Re: [T2TRG] IoT 2017: Deadline Extension until June 20
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, 07 Jun 2017 06:36:21 -0000

(Just to reiterate on the policy here:
We don=E2=80=99t want the RG list to be a CFP list =E2=80=94 you all =
know where to find CFPs.
We do make occasional exceptions, for conferences that have deep =
personal or topical ties to the WG work.)

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


> On Jun 7, 2017, at 07:38, Mayer, Simon <simonmayer@siemens.com> wrote:
>=20
> Dear colleagues,
>=20
> we have decided to extend the full paper deadline of IoT 2017 by 2 =
weeks, until June 20, to attract more submissions and give authors of =
submitted manuscripts more time for polishing their contributions.
>=20
> Please help us spread this information and the IoT 2017 call for =
papers (http://iot-conference.org/iot2017/iot2017/call-for-papers/) to =
everyone you think might be interested in attending the conference and =
contributing to its technical program.
>=20
> Thank you and best wishes,
> Simon Mayer and Stefan Schneegass
>=20
> ---
>=20
> IoT 2017 Resources:
> - Conference Website (will be updated shortly): =
http://iot-conference.org/
> - Submission website: https://easychair.org/conferences/?conf=3Diot2017
> - IoT 2017 Poster: =
https://www.pervasive.jku.at/iot2017/IOT2017-Plakat-DINA2-final.pdf
> - PDF Call for Papers: =
http://iot-conference.org/iot2017/wp-content/uploads/2017/01/IoT-2017-CFP-=
4.pdf
> =20
> =20
> This message and any attachments are solely for the use of intended =
recipients. The information contained herein may include trade secrets, =
protected health or personal information, privileged or otherwise =
confidential information. Unauthorized review, forwarding, printing, =
copying, distributing, or using such information is strictly prohibited =
and may be unlawful. If you are not an intended recipient, you are =
hereby notified that you received this email in error, and that any =
review, dissemination, distribution or copying of this email and any =
attachment is strictly prohibited. If you have received this email in =
error, please contact the sender and delete the message and any =
attachment from your system. Thank you for your cooperation
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg


From nobody Wed Jun  7 14:58:35 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 EBE1813148B for <t2trg@ietfa.amsl.com>; Wed,  7 Jun 2017 14:58:33 -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, 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=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 R8v4-IZE7fwn for <t2trg@ietfa.amsl.com>; Wed,  7 Jun 2017 14:58:30 -0700 (PDT)
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 3C4161293EC for <t2trg@irtf.org>; Wed,  7 Jun 2017 14:58:30 -0700 (PDT)
X-AuditID: c1b4fb30-874f69a000003fda-c1-5938770449e7
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 4C.00.16346.40778395; Wed,  7 Jun 2017 23:58:28 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.30]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0339.000; Wed, 7 Jun 2017 23:58:22 +0200
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: "draft-irtf-t2trg-iot-seccons@ietf.org" <draft-irtf-t2trg-iot-seccons@ietf.org>
CC: "t2trg@irtf.org" <t2trg@irtf.org>
Thread-Topic: draft-irtf-t2trg-iot-seccons review comments
Thread-Index: AQHS39ktBLo3SZaPZkumeLfTIDRdSQ==
Date: Wed, 7 Jun 2017 21:58:21 +0000
Message-ID: <D3E7BBCB-E59E-4A10-AC25-D95B0A1958DC@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C67875331FA5ED40992E4D48B2FCC15E@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2K7hC5LuUWkQWOTvMXB3k3MFu8f9LA4 MHksWfKTyWPyxsNsAUxRXDYpqTmZZalF+nYJXBn7d+9gKuj1qFjYPZ2tgfG0VRcjJ4eEgInE rTXPmLsYuTiEBI4wSmz51swG4SxilLh36jYjSBWbgL3E5DUfwWwRgVCJ42/XsILYzAKqEps/ TQXq5uAQFjCVOH5GFKLESuLMwdXMELaexIfre8HKWQRUJL6e7WMCKecFGnnzUBhImFFATOL7 qTVMEBPFJW49mc8EcZuAxJI955khbFGJl4//sULYShIrtl9ihKjXk7gxdQobhG0tsalvNjOE rS2xbOFrMJtXQFDi5MwnLBMYRWYhWTELSfssJO2zkLTPQtK+gJF1FaNocWpxUm66kZFealFm cnFxfp5eXmrJJkZglBzc8ttgB+PL546HGAU4GJV4eKckWEQKsSaWFVfmHmKU4GBWEuHNiwAK 8aYkVlalFuXHF5XmpBYfYpTmYFES53XcdyFCSCA9sSQ1OzW1ILUIJsvEwSnVwJizKkdWxiDa Wbmro1WGx6Oxa+OT+PAvHC+X/y15dvfLBuOvVWtDpzrEXc1/8kByxwGNrp2zRGpLXNM9TCPj N5f8/bf8m6p/y6R9bWy/3vg/4w3gvuF7/dsDy6V9atU3Hn6/U3W7Pvi29MuwfRlf6j/sFhPT kmhLWBnzaG2U6ErnfL6Ne4N6HZRYijMSDbWYi4oTAYA8u0KOAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/1Jm9AucdZMKwkr8V-xT4SrhR27k>
Subject: [T2TRG] draft-irtf-t2trg-iot-seccons review comments
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, 07 Jun 2017 21:58:34 -0000

Hi Authors,

Here's my review comments for the T2TRG IoT Security Considerations draft. =
I tried to do a thorough "final" review so some of the comments are rather =
detailed. I used the 269603a commit version in Github.

Overall I think the draft is in pretty good shape and there's lots of good =
material worth publishing. However there are some issues I'd consider havin=
g a second look; see details below. Additionally I'll send you another mail=
 with suggested editorial nits and tweaks. Those shouldn't require mail lis=
t discussion (but feel free to disagree).


Cheers,
Ari

---

Section 1:

I don't think a full history of the document (second to last paragraph) is =
needed in the final version. RFC5743 calls for description of level of supp=
ort, but probably few sentences less is enough.

Section 3.1:
> The thing is later installed and commissioned within a network by an inst=
aller during the bootstrapping phase. Specifically, the device identity and=
 the secret keys used during normal operation are provided to the device du=
ring this phase.=20

The device ID and keys could also be provided before install/commission, du=
ring manufacturing.=20

Section 4: I'm not sure SIP is worth listing as "related IP protocol".

> Privacy threat: The tracking of a thing's location and usage may pose a p=
rivacy risk to its users. An attacker can infer information based on the in=
formation gathered about individual things, thus deducing behavioral patter=
ns of the user of interest to him. Such information can subsequently be sol=
d to interested parties for marketing purposes and targeted advertising.

Probably targeted advertising is not the biggest problem here, albeit proba=
bly most common today. I'd recommend making clear that advertising is just =
one example and perhaps mention other/bigger risks too, such as tracking of=
 dissidents in oppressive regimes.=20

This is probably(?) only editorial issue, but there are many instance of "I=
oTs". Since the acronym is already plural ("Internet of Things"), the s in =
the end doesn't sound right. I'd recommend "s/IoTs/IoT/g" and occasional re=
phrasing where needed.

> DoS attack can be launched by physically jamming the communication channe=
l, thus breaking down the T2T communication channel

Jamming breaks also other channels than T2T.

Fig 3: "Thing's model" sounds ambiguous. What does it actually mean?

Section 5.1:
> The CoRE working group {{WG-CoRE}} provides a framework for resource-orie=
nted applications intended to run on constrained IP network (6LoWPAN). One =
of its main tasks is the definition of a lightweight version of the HTTP pr=
otocol, the Constrained Application Protocol (CoAP) {{RFC7252}}, that runs =
over UDP and enables efficient application-level communication for things.

Actually CoRE applies beyond 6LoWPAN, so maybe just drop that part in paren=
thesis and say "constrained IP networks".

And CoAP is not just "lightweight version of HTTP". I've been using "RESTfu=
l protocol for constrained devices, modelled after HTTP".

> Additionally industry alliances and other standardization bodies are crea=
ting constrained IP protocol stacks based on the IETF work. Some important =
examples of this include:

Makes sense to add OMA with LwM2M to the list since that's heavily re-using=
 IETF CoRE and IP infra.

Section 5.4:
> Despite the acknowledgement that security in the Internet is needed and m=
ultiple guidelines exist, the fact is that many IoT devices and systems are=
 not fully secure.=20

"fully secure" is something we may never achieve, but with many current IoT=
 devices and systems it's even much worse. So maybe say here "are not very =
secure".

Section 6.1.1:
> The IoT is a resource-constrained network that relies on lossy and low-ba=
ndwidth channels for communication between small nodes, regarding CPU, memo=
ry, and energy budget

IoT networks are not always low-bandwidth nor nodes constrained. For exampl=
e critical MTC cases are usually quite the opposite. It's OK to focus on th=
at part of IoT here but we shouldn't generalize that too far. And "IoT" is =
not a "network", so could say here e.g., "IoT devices are often using resou=
rce-constrained networks...".

Section 6.1.3:
> The term end-to-end security often has multiple interpretations.

We actually discussed this in lengths in the Amsterdam T2TRG meeting. See t=
he end of notes in: https://www.ietf.org/proceedings/interim-2017-t2trg-01/=
minutes/minutes-interim-2017-t2trg-01-201703091000-00

Perhaps we could finally have a documented definition of this we can agree =
on?

> Even though 6LoWPAN and CoAP progress towards reducing the gap between In=
ternet protocols and the IoT, they do not target protocol specifications th=
at are identical to their Internet counterparts due to performance reasons.

IoT protocols such as CoAP and 6LoWPAN are Internet protocols. There are al=
so non Internet protocols (esp. non-IP protocols) that are used for buildin=
g "IoT", or rather M2M systems, but that's a different story.

Perhaps better wording here is "constrained Internet protocols".

> There are essentially five approaches to handle such end-to-end confident=
iality and integrity protection while letting middleboxes access/modify dat=
a for different purposes:
[...]
> 2. Reusing the Internet wire format in the IoT makes conversion between I=
oT and Internet protocols unnecessary. However, it can lead to poor perform=
ance in some use cases because IoT specific optimizations (e.g., stateful o=
r stateless compression) are not possible.

These two parts don't seem to be aligned; e2e security with middle boxes an=
d not needing protocol conversion? And also issue with "IoT protocols" and =
"Internet protocols" (see my comment above).

And how about homomorphic crypto?

> Moreover, it cannot be used with encrypted data because the lack of clear=
text prevents gateways from transforming packets.

I'm not sure if I follow the line of thought there.

> Currently the IoT based object security format based on COSE {{ID-cose}} =
is different from the Internet based JOSE or CMS.=20

Again "IoT vs. Internet". Also in following sentence.=20

> To the best of our knowledge, none of the mentioned security approaches t=
hat focus on the confidentiality and integrity of the communication exchang=
e between two IP end-points provides a fully customizable solution in this =
problem space.

What is "a fully customizable solution"?

Section 6.3.1:
> Moreover, end-to-end security associations are an important measure to br=
idge the gap between the IoT and the Internet.

Again "IoT vs. Internet".

Section 6.3.2:
> All discussed protocols only cover unicast communication and therefore do=
 not focus on group-key establishment.=20

Here good to be more explicit which protocols. I assume (D)TLS and IKEv2 (E=
SP)?

Section 6.4:
> IoT devices have a reputation for being insecure at the time of manufactu=
re.

What do you mean by this? Is that "already insecure when they are manufactu=
red" or "to be secured after manufacturing", or something else?

Section 6.5:
> An IoT device user/owner would like to monitor and know if the device is =
calling home (i.e. verify its operational behavior).=20

Not everyone will be familiar with "calling home" feature. I'd suggest re-p=
hrasing or explaining that.

> For example, the user should be ensured that his/her TV is not sending da=
ta when he/she inserts a new USB stick.

In some cases this could be legitimate thing to do (right?).

Section 6.8:
> First, functionalities enabled by means of RSA/ECC - namely key exchange,=
 public-key encryption and signature - would not be secure anymore due to S=
hor's algorithm. Second, the security level of symmetric algorithms will de=
crease, e.g., the security of a block cipher with a key size of b bits will=
 only offer b/2 bits of security due to Grover's algorithm.

If there's an easy (like sentence or two) way to explain Shor's and Grover'=
s algorithms, that might be useful here. Otherwise it's probably better to =
actually shorten this and just say that the crypto operations are not secur=
e anymore and give references.

Section 6.9 ("Privacy protection"):
> When IoT systems are deployed, the above issues should be considered to e=
nsure that private data remains private. How to achieve this in practice is=
 still an area of ongoing research.

Could refer to RFC6973 here and e.g., RFC7221 too for recent IETF work on t=
he topic.

Section 6.11:
> The idea behind MUD files is simple: devices would disclose the location =
of its MUD file to the network during installation. The network can then (i=
) retrieve those files, (ii) learn from the manufacturers the intended usag=
e of the devices, e.g., which services they require to access, and then (ii=
i) create suitable filters.

I think you can go beyond "suitable filters" with MUD. For example using an=
omaly detection algorithms. And would be good to clarify what kind of filte=
rs you mean (firewall rules?).


From nobody Mon Jun 12 12:41:21 2017
Return-Path: <session-request@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 82B19127077; Mon, 12 Jun 2017 12:41:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: cabo@tzi.org, t2trg@irtf.org, irtf-chair@irtf.org, t2trg-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149729647944.10266.16492489078667989483.idtracker@ietfa.amsl.com>
Date: Mon, 12 Jun 2017 12:41:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/xGqbFQYKfCXyu9ByFCf7QYdD5ns>
Subject: [T2TRG] t2trg - New Interim Meeting Request
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: Mon, 12 Jun 2017 19:41:19 -0000

A new interim meeting request has just been submitted by Carsten Bormann.

This request requires approval by the IRTF Chair

The meeting can be approved here: 
https://datatracker.ietf.org/meeting/interim/request/interim-2017-t2trg-02



---------------------------------------------------------
Research Group Name: Thing-to-Thing
Session Requester: Carsten Bormann

City: Prague
Country: CZ


Session 1:

Date: 2017-07-15
Start Time: 09:00 Europe/Berlin
Duration: 09:00
Remote Participation Information: As usual for T2TRG interims, feeble attempts will be made to enable some remote participation
Agenda Note: 
Session 2:

Date: 2017-07-16
Start Time: 09:00 Europe/Berlin
Duration: 07:00
Remote Participation Information: As usual for T2TRG interims, feeble attempts will be made to enable some remote participation
Agenda Note: 

---------------------------------------------------------


From nobody Mon Jun 12 12:44:17 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 B4DF9127077 for <t2trg@ietfa.amsl.com>; Mon, 12 Jun 2017 12:44:15 -0700 (PDT)
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 m95zHbOE70P9 for <t2trg@ietfa.amsl.com>; Mon, 12 Jun 2017 12:44:13 -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 D30B1127735 for <t2trg@irtf.org>; Mon, 12 Jun 2017 12:44:12 -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 v5CJi9O5008707 for <t2trg@irtf.org>; Mon, 12 Jun 2017 21:44:09 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (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 3wmjyK5T5Cz3Z3J; Mon, 12 Jun 2017 21:44:09 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149729647944.10266.16492489078667989483.idtracker@ietfa.amsl.com>
Date: Mon, 12 Jun 2017 21:44:09 +0200
X-Mao-Original-Outgoing-Id: 518989448.990098-0aceff10365a18f46a23304e4ee99b13
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FC77A28-2A8E-4E08-9E2A-81892518EAD4@tzi.org>
References: <149729647944.10266.16492489078667989483.idtracker@ietfa.amsl.com>
To: t2trg@irtf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/WJvTKiQOJCRkkDEMjNIR7Ol2YrY>
Subject: Re: [T2TRG] t2trg - New Interim Meeting Request
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, 12 Jun 2017 19:44:16 -0000

(In case you wonder:
The below was an automatic message that results from the chairs =
following the formal process of establishing the meeting as a T2TRG =
interim.  But you know about WISHI already=E2=80=A6)

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


> On Jun 12, 2017, at 21:41, IETF Meeting Session Request Tool =
<session-request@ietf.org> wrote:
>=20
>=20
> A new interim meeting request has just been submitted by Carsten =
Bormann.
>=20
> This request requires approval by the IRTF Chair
>=20
> The meeting can be approved here:=20
> =
https://datatracker.ietf.org/meeting/interim/request/interim-2017-t2trg-02=

>=20
>=20
>=20
> ---------------------------------------------------------
> Research Group Name: Thing-to-Thing
> Session Requester: Carsten Bormann
>=20
> City: Prague
> Country: CZ
>=20
>=20
> Session 1:
>=20
> Date: 2017-07-15
> Start Time: 09:00 Europe/Berlin
> Duration: 09:00
> Remote Participation Information: As usual for T2TRG interims, feeble =
attempts will be made to enable some remote participation
> Agenda Note:=20
> Session 2:
>=20
> Date: 2017-07-16
> Start Time: 09:00 Europe/Berlin
> Duration: 07:00
> Remote Participation Information: As usual for T2TRG interims, feeble =
attempts will be made to enable some remote participation
> Agenda Note:=20
>=20
> ---------------------------------------------------------
>=20
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg
>=20


From nobody Tue Jun 13 07:36:36 2017
Return-Path: <iesg-secretary@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 96F941318B4; Tue, 13 Jun 2017 07:36:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>, "IRTF-Announce" <irtf-announce@irtf.org>
Cc: t2trg@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149736458236.7440.6135055320635970858@ietfa.amsl.com>
Date: Tue, 13 Jun 2017 07:36:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/P0KNWoXhCjo80Gd1OhjFEvNmHaE>
Subject: [T2TRG] Thing-to-Thing (t2trg) RG Interim Meeting: 2017-07-15
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: Tue, 13 Jun 2017 14:36:23 -0000

The Thing-to-Thing (t2trg) Research Group will hold
a multi-day interim meeting.

Session 1:
2017-07-15     09:00 to 18:00  Europe/Berlin
Session 2:
2017-07-16     09:00 to 16:00  Europe/Berlin

Meeting Location:
Prague, CZ

Agenda:
Please see https://github.com/t2trg/2017-07-wishi/blob/master/AGENDA.md

Information about remote participation:
As usual for T2TRG interims, feeble attempts will be made to enable some remote participation


From nobody Tue Jun 13 13:04:45 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 0F238129A8D for <t2trg@ietfa.amsl.com>; Tue, 13 Jun 2017 13:04:44 -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, 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 U9CXTlk_NYsH for <t2trg@ietfa.amsl.com>; Tue, 13 Jun 2017 13:04:42 -0700 (PDT)
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 251C1129AB5 for <t2trg@irtf.org>; Tue, 13 Jun 2017 13:04:41 -0700 (PDT)
X-AuditID: c1b4fb3a-31fff70000004a6a-3c-59404557688f
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 2A.DA.19050.75540495; Tue, 13 Jun 2017 22:04:40 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.30]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0339.000; Tue, 13 Jun 2017 22:04:39 +0200
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: "t2trg@irtf.org" <t2trg@irtf.org>, "public-wot-ig@w3.org" <public-wot-ig@w3.org>, "iotsi@iab.org" <iotsi@iab.org>
CC: "t2trg-chairs@ietf.org" <t2trg-chairs@ietf.org>
Thread-Topic: Draft agenda and registration for the Workshop on IoT Semantic/Hypermedia Interoperability (WISHI)
Thread-Index: AQHS5IBJtTNvJlRyZkOXxCofgACB0A==
Date: Tue, 13 Jun 2017 20:04:38 +0000
Message-ID: <D03BDAC8-BE42-4541-A564-319B342EA57B@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5862F85FF3737C458973A31E68DBCF72@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyM2K7hG6Eq0OkwcJjohaHr+5gtpj7tpXN ou3iB0aL9w96WBxYPG5dfcnssWTJTyaPyRsPs3kcnbefNYAlissmJTUnsyy1SN8ugSvjRdM7 toKtzBXTpq5gbGB8wdTFyMkhIWAice5rA1sXIxeHkMARRokj5+6wQziLGSXuvLvAAlLFJmAv MXnNR0YQW0SgXGJj631WEJtZwFiif3cjG4gtLJArsebodxaImiKJ/m2T2CBsPYnOE/PZQWwW AVWJQ6+/gPXyAs18Ov8hWD2jgJjE91NrmCBmikvcejIf6joBiSV7zjND2KISLx//Y4WwFSWu Tl8OVa8ncWPqFDYI21riVcMcZghbW2LZwtfMELsEJU7OfMIygVFkFpIVs5C0z0LSPgtJ+ywk 7QsYWVcxihanFhfnphsZ6aUWZSYXF+fn6eWllmxiBEbUwS2/rXYwHnzueIhRgINRiYe3w94h Uog1say4MvcQowQHs5II72eQEG9KYmVValF+fFFpTmrxIUZpDhYlcV6HfRcihATSE0tSs1NT C1KLYLJMHJxSDYzprSdlphx4lnFv24qglwbiX7P01Y9ty596MSciPGyhqdThTXOD+vk9RCdE OHhaJz84sL2s8ZTsFpUj82svnpwqOGfNtMV1+ndC2Yts371ZNXd65ByJOfHrNTymL2Hqe999 +lKUi/yxj9tSNsekPftxQJCfLd3FRJv7Ns8URlaHLe0i/+e66b9QYinOSDTUYi4qTgQAQIXS EKQCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/nJz3dzEAExui_vXdITCcC6taL80>
Subject: [T2TRG] Draft agenda and registration for the Workshop on IoT Semantic/Hypermedia Interoperability (WISHI)
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: Tue, 13 Jun 2017 20:04:44 -0000

Hi all,

We have now published first draft agenda for the WISHI workshop:
https://github.com/t2trg/2017-07-wishi/blob/master/AGENDA.md

Also we would like to remind you to register for the workshop by Friday Jun=
e 23rd. The registration (and meeting) is free of cost but we need to know =
amount of participants for meeting logistics.

Registration is available here: https://goo.gl/forms/yUTebqK9C84Ef01i2


Thanks,
Ari=


From nobody Fri Jun 16 16:57:06 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 AB520129540; Fri, 16 Jun 2017 16:56:36 -0700 (PDT)
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 nM8JdYlIWS9x; Fri, 16 Jun 2017 16:56:35 -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 CB18F12953F; Fri, 16 Jun 2017 16:56:34 -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 v5GNuUVG003810; Sat, 17 Jun 2017 01:56:30 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (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 3wqHMd617KzDK04; Sat, 17 Jun 2017 01:56:29 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=utf-8
X-Mao-Original-Outgoing-Id: 519350189.453979-e3b2d906e8bab442948f66a848a5cc63
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sat, 17 Jun 2017 01:56:29 +0200
Message-Id: <2DB0474F-900D-42FD-B2C5-F61F396B751C@tzi.org>
To: ace <ace@ietf.org>, core <core@ietf.org>, cose <cose@ietf.org>, cbor@ietf.org, t2trg@irtf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/yT0tiLvNF4eY4BH3G7woTXt2jmM>
Subject: [T2TRG] Constrained Node/Network Cluster @ IETF99: DRAFT AGENDA
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, 16 Jun 2017 23:56:37 -0000

Here is my usual eclectic condensed agenda based on the DRAFT AGENDA
for IETF99.  Remember that there is still quite some potential for
changes.

ACE people are going to miss DISPATCH (ARTAREA) again -- not sure if
there would have been be any discussions relevant to Constrained
Nodes/Networks in ARTAREA, but it doesn't make sense with this
scheduling.  CORE people will miss both ANIMA and (in-week) ICNRG.
ROLL people will miss SAAG, ouch.  And LPWAN is on the second half of
QUIC.  All no disasters, AFAICS, but not pain-free.

All times are CEST (UTC+0200).  (You can get pure UTC times on
https://datatracker.ietf.org/meeting/agenda-utc, for those who want to
listen from remote.)

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


SATURDAY/SUNDAY
-- T2TRG
-- ICNRG
-- Hackathon (including various interops)

MONDAY, July 17, 2017

0930-1200  Morning Session I
Congress H III	ART	dispatch	Dispatch WG - 09:30-11:30
Grand Hilton BR	INT	6man	IPv6 Maintenance WG
Congress H I	SEC ***	ace	Authentication and Authorization for =
Constrained Environments WG
Congress H III	SEC	curdle	CURves, Deprecating and a Little more =
Encryption WG - 11:30-12:00

1330-1530  Afternoon Session I
Karlin I/II	INT ***	6tisch	IPv6 over the TSCH mode of IEEE =
802.15.4e WG
Grand Hilton BR	INT	homenet	Home Networking WG

1550-1720  Afternoon Session II
Karlin I/II	ART ***	cbor	Concise Binary Object Representation =
Maintenance and Extensions WG
Berlin/Brussels	SEC	tokbind	Token Binding WG

1740-1840  Afternoon Session III
Athens/Barcel.	RTG	babel	Babel routing protocol WG
Grand Hilton BR	TSV	tsvarea	Transport Area Open Meeting

TUESDAY, July 18, 2017

0930-1200  Morning Session I
Congress H II	OPS	v6ops	IPv6 Operations WG
Congress H I	TSV	taps	Transport Services WG

1330-1530  Afternoon Session I
Grand Hilton BR	IRTF***	t2trg	Thing-to-Thing
Berlin/Brussels	SEC	oauth	Web Authorization Protocol WG
Congress H I	TSV	tsvwg	Transport Area Working Group WG

1550-1750  Afternoon Session II
Karlin I/II	INT ***	6lo	IPv6 over Networks of =
Resource-constrained Nodes WG
Congress H I	IRTF	cfrg	Crypto Forum

WEDNESDAY, July 19, 2017

0930-1200  Morning Session I
Congress H I	ART ***	core	Constrained RESTful Environments WG
Karlin I/II	IRTF	icnrg	Information-Centric Networking
Congress H III	OPS	anima	Autonomic Networking Integrated Model =
and Approach WG
Congress H II	RTG	rtgarea	Routing Area Open Meeting
Grand Hilton BR	SEC	tls	Transport Layer Security WG
Karlin III	TSV	rmcat	RTP Media Congestion Avoidance =
Techniques WG

1330-1500  Afternoon Session I
Grand Hilton BR	ART	httpbis	Hypertext Transfer Protocol WG
Congress H III	IRTF	panrg	Proposed Path Aware Networking
Congress H II	RTG	ideas	IDentity Enabled Networks BOF

1520-1650  Afternoon Session II
Grand Hilton BR	ART	httpbis	Hypertext Transfer Protocol WG

THURSDAY, July 20, 2017

0930-1200  Morning Session I
Grand Hilton BR	INT	intarea	Internet Area Working Group WG
Congress H II	IRTF	maprg	Measurement and Analysis for Protocols
Congress H I	RTG	detnet	Deterministic Networking WG

1330-1530  Afternoon Session I
Berlin/Brussels	ART	ice	Interactive Connectivity Establishment =
WG
Grand Hilton BR	OPS	v6ops	IPv6 Operations WG
Karlin I/II	RTG ***	roll	Routing Over Low power and Lossy =
networks WG
Congress H III	SEC	saag	Security Area Open Meeting

1550-1750  Afternoon Session II
Athens/Barcel.	INT	ipwave	IP Wireless Access in Vehicular =
Environments WG
Grand Hilton BR	TSV	quic	QUIC WG

1810-1910  Afternoon Session III
Berlin/Brussels	ART	uta	Using TLS in Applications WG
Athens/Barcel.	INT ***	lwig	Light-Weight Implementation Guidance WG
Karlin I/II	RTG	bier	Bit Indexed Explicit Replication WG
Congress H III	TSV	tsvwg	Transport Area Working Group WG

FRIDAY, July 21, 2017

0930-1130  Morning Session I
Berlin/Brussels	INT	dnssd	Extensions for Scalable DNS Service =
Discovery  WG
Karlin I/II	INT ***	lpwan	IPv6 over Low Power Wide-Area Networks =
WG
Karlin III	SEC	oauth	Web Authorization Protocol WG
Grand Hilton BR	TSV	quic	QUIC WG

1150-1320  Afternoon Session II
Congress H III	ART ***	core	Constrained RESTful Environments WG
Grand Hilton BR	SEC	acme	Automated Certificate Management =
Environment WG



From nobody Tue Jun 20 06:26:27 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 4353C12EB7A; Tue, 20 Jun 2017 06:26:26 -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.55.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149796518623.23807.13157236360711022116@ietfa.amsl.com>
Date: Tue, 20 Jun 2017 06:26:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/w0-R0k7VpinHCucOVZIbstTt-o0>
Subject: [T2TRG] I-D Action: draft-irtf-t2trg-iot-seccons-04.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: Tue, 20 Jun 2017 13:26:26 -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 Security
        Authors         : Oscar Garcia-Morchon
                          Sandeep S. Kumar
                          Mohit Sethi
	Filename        : draft-irtf-t2trg-iot-seccons-04.txt
	Pages           : 44
	Date            : 2017-06-20

Abstract:
   The Internet of Things (IoT) concept refers to the usage of standard
   Internet protocols to allow for human-to-thing and thing-to-thing
   communication.  The security needs for IoT are well-recognized and
   many standardization steps for providing security have been taken,
   for example, the specification of Constrained Application Protocol
   (CoAP) over Datagram Transport Layer Security (DTLS).  However,
   security challenges still exist and there are some use cases that
   lack a suitable solution.  In this document, we first discuss the
   various stages in the lifecycle of a thing.  Next, we document the
   various security threats to a thing and the challenges that one might
   face to protect against these threats.  Lastly, we discuss the next
   steps needed to ensure roll out of secure IoT services.

   This document is a product of the IRTF Thing-to-Thing Research Group
   (T2TRG).


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-04
https://datatracker.ietf.org/doc/html/draft-irtf-t2trg-iot-seccons-04

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


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 Tue Jun 20 06:34:33 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 DD99B12EBFF for <t2trg@ietfa.amsl.com>; Tue, 20 Jun 2017 06:34:31 -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, 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 f0lJoaP3guJt for <t2trg@ietfa.amsl.com>; Tue, 20 Jun 2017 06:34:26 -0700 (PDT)
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 2F5B412EC03 for <T2TRG@irtf.org>; Tue, 20 Jun 2017 06:34:26 -0700 (PDT)
X-AuditID: c1b4fb3a-307ff70000004a6a-ce-5949245e6ea5
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id AB.14.19050.E5429495; Tue, 20 Jun 2017 15:34:24 +0200 (CEST)
Received: from nomadiclab.fi.eu.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.3.339.0; Tue, 20 Jun 2017 15:34:22 +0200
Received: from nomadiclab.fi.eu.ericsson.se (localhost [127.0.0.1])	by nomadiclab.fi.eu.ericsson.se (Postfix) with ESMTP id BCBA34F9CE;	Tue, 20 Jun 2017 16:38:29 +0300 (EEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])	by nomadiclab.fi.eu.ericsson.se (Postfix) with ESMTP id 2F8F04E6D8;	Tue, 20 Jun 2017 16:38:29 +0300 (EEST)
References: <149796518623.23807.13157236360711022116@ietfa.amsl.com>
To: "t2trg@irtf.org" <T2TRG@irtf.org>
CC: "Garcia-Morchon O, Oscar" <oscar.garcia-morchon@philips.com>, "Kumar, Sandeep" <sandeep.kumar@philips.com>
From: Mohit Sethi <mohit.m.sethi@ericsson.com>
X-Forwarded-Message-Id: <149796518623.23807.13157236360711022116@ietfa.amsl.com>
Message-ID: <2b8450e1-a8bd-dc09-c72f-17b43049b184@ericsson.com>
Date: Tue, 20 Jun 2017 16:34:21 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <149796518623.23807.13157236360711022116@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------63810E55AF2DF8E9EF668234"
Content-Language: en-US
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBIsWRmVeSWpSXmKPExsUyM2J7oG6CimekwfTlQhYNdy6wWCw5vIjR 4v2DHhYHZo/JGw+zeRw4sJspgCmKyyYlNSezLLVI3y6BK2PW1BVsBROdK3Z/+cjYwPjfpIuR k0NCwESi/9xPpi5GLg4hgSOMEjsvbWCHcHYwSqxZ8YoNpEpIYBOjxPUZYhCJhYwS50+2MYEk hAVcJc7uWMrcxcgBlHCR2Pc2DSQsIqAq0TDnOitImFmgQOJMkxJImE1AT6Lz3HFmiMUBEo82 rgWzeQXsJZZ8uMwKYrMAtV5//BBsrahAhMSu6wdYIWoEJU7OfMICYnMCbT1+8zlYL7NAmMTm WV9ZIWxxiVtP5jNBzFeTuHpuEzPE+eoSWzsOME5gFJmFZNQsJO2zkLTPArvaXuLB1jKIsLxE 89bZzBC2vsT1O/dZkcUXMLKvYhQtTi0uzk03MtJLLcpMLi7Oz9PLSy3ZxAiMr4NbflvtYDz4 3PEQowAHoxIPb7KEZ6QQa2JZcWXuIUYJDmYlEd57ICHelMTKqtSi/Pii0pzU4kOM0hwsSuK8 DvsuRAgJpCeWpGanphakFsFkmTg4pRoYnTbrW2dPmGd0Z/K1hONv94qrT5QzmaL6Ifn2q/9F 65Tv+4je7HYo2CcYIO+4oIE5fqpesY6Dn2GZ5bRYT9dDK57f/fb2+fl9/EKvPt9IXWm6XvFD /7pv3uXiFTtYy7ZzsvcHazxXkPx5WPabQXj4IvcYlpxEt5tnpCN2zlH99iz699HVxs9ilFiK MxINtZiLihMBuLGGS6sCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/z4rbfs3YZ_h7lgg1WN50em2aiKA>
Subject: [T2TRG] Fwd:  I-D Action: draft-irtf-t2trg-iot-seccons-04.txt
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: Tue, 20 Jun 2017 13:34:32 -0000

--------------63810E55AF2DF8E9EF668234
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit

Hi folks,

Thanks to Fred Baker, Thorsten Dahm, Göran Selander, Laurent Ciavaglia, 
Ari Keränen and Carsten Bormann for providing us with extensive comments 
on and off the list. We have submitted another version to address the 
comments received. Hopefully the draft is now also shorter and easier to 
read. The current version of the draft can be found here:

https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-04

The authors believe that the document to be ready and your feedback and 
comments are appreciated as always.

Oscar, Sandeep and Mohit


-------- Forwarded Message --------
Subject: 	[T2TRG] I-D Action: draft-irtf-t2trg-iot-seccons-04.txt
Date: 	Tue, 20 Jun 2017 06:26:26 -0700
From: 	internet-drafts@ietf.org
To: 	i-d-announce@ietf.org
CC: 	t2trg@irtf.org



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 Security
         Authors         : Oscar Garcia-Morchon
                           Sandeep S. Kumar
                           Mohit Sethi
	Filename        : draft-irtf-t2trg-iot-seccons-04.txt
	Pages           : 44
	Date            : 2017-06-20

Abstract:
    The Internet of Things (IoT) concept refers to the usage of standard
    Internet protocols to allow for human-to-thing and thing-to-thing
    communication.  The security needs for IoT are well-recognized and
    many standardization steps for providing security have been taken,
    for example, the specification of Constrained Application Protocol
    (CoAP) over Datagram Transport Layer Security (DTLS).  However,
    security challenges still exist and there are some use cases that
    lack a suitable solution.  In this document, we first discuss the
    various stages in the lifecycle of a thing.  Next, we document the
    various security threats to a thing and the challenges that one might
    face to protect against these threats.  Lastly, we discuss the next
    steps needed to ensure roll out of secure IoT services.

    This document is a product of the IRTF Thing-to-Thing Research Group
    (T2TRG).


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-04
https://datatracker.ietf.org/doc/html/draft-irtf-t2trg-iot-seccons-04

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


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/

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


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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi folks,<br>
      <br>
      Thanks to Fred Baker, Thorsten Dahm, Göran Selander, Laurent
      Ciavaglia, Ari Keränen and Carsten Bormann for providing us with
      extensive comments on and off the list. We have submitted another
      version to address the comments received. Hopefully the draft is
      now also shorter and easier to read. The current version of the
      draft can be found here:<br>
    </p>
    <p><a moz-do-not-send="true"
        href="https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-04">https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-04</a><br>
    </p>
    <p>The authors believe that the document to be ready and your
      feedback and comments are appreciated as always. <br>
    </p>
    <p> </p>
    Oscar, Sandeep and Mohit
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
            </th>
            <td>[T2TRG] I-D Action: draft-irtf-t2trg-iot-seccons-04.txt</td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
            <td>Tue, 20 Jun 2017 06:26:26 -0700</td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" align="RIGHT" nowrap="nowrap">CC: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:t2trg@irtf.org">t2trg@irtf.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>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 Security
        Authors         : Oscar Garcia-Morchon
                          Sandeep S. Kumar
                          Mohit Sethi
	Filename        : draft-irtf-t2trg-iot-seccons-04.txt
	Pages           : 44
	Date            : 2017-06-20

Abstract:
   The Internet of Things (IoT) concept refers to the usage of standard
   Internet protocols to allow for human-to-thing and thing-to-thing
   communication.  The security needs for IoT are well-recognized and
   many standardization steps for providing security have been taken,
   for example, the specification of Constrained Application Protocol
   (CoAP) over Datagram Transport Layer Security (DTLS).  However,
   security challenges still exist and there are some use cases that
   lack a suitable solution.  In this document, we first discuss the
   various stages in the lifecycle of a thing.  Next, we document the
   various security threats to a thing and the challenges that one might
   face to protect against these threats.  Lastly, we discuss the next
   steps needed to ensure roll out of secure IoT services.

   This document is a product of the IRTF Thing-to-Thing Research Group
   (T2TRG).


The IETF datatracker status page for this draft is:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-irtf-t2trg-iot-seccons/">https://datatracker.ietf.org/doc/draft-irtf-t2trg-iot-seccons/</a>

There are also htmlized versions available at:
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-04">https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-04</a>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-irtf-t2trg-iot-seccons-04">https://datatracker.ietf.org/doc/html/draft-irtf-t2trg-iot-seccons-04</a>

A diff from the previous version is available at:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-irtf-t2trg-iot-seccons-04">https://www.ietf.org/rfcdiff?url2=draft-irtf-t2trg-iot-seccons-04</a>


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:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>

_______________________________________________
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>
    </div>
  </body>
</html>

--------------63810E55AF2DF8E9EF668234--


From nobody Fri Jun 23 11:34: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 6BF4B1289C3; Fri, 23 Jun 2017 11:34:15 -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 4LIhTV3NyAj7; Fri, 23 Jun 2017 11:34:12 -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 7AB431286B1; Fri, 23 Jun 2017 11:34:12 -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 v5NIY9nj026681; Fri, 23 Jun 2017 20:34:09 +0200 (CEST)
Received: from [192.168.217.113] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (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 3wvRtS6YWQz3YtG; Fri, 23 Jun 2017 20:34:08 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
Date: Fri, 23 Jun 2017 20:34:08 +0200
Cc: t2trg-chairs@ietf.org
X-Mao-Original-Outgoing-Id: 519935648.045704-d43190ac33347bfb3f163bbc7554b280
Content-Transfer-Encoding: quoted-printable
Message-Id: <39F54EE8-F06D-4416-A85F-E360AE58FD37@tzi.org>
To: t2trg@irtf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/ajeEhA_x5065APTWA4v53_orNrI>
Subject: [T2TRG] Reminder: Please register for WISHI workshop
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, 23 Jun 2017 18:34:15 -0000

For the Workshop on IoT Semantic/Hypermedia Interoperability (WISHI)
July 15/16 in Prague, registration is closing.

Please register now at:
  https://goo.gl/forms/yUTebqK9C84Ef01i2

A general overview of the workshop is at:
  https://github.com/t2trg/2017-07-wishi
and the draft agenda is at:
  https://github.com/t2trg/2017-07-wishi/blob/master/AGENDA.md


The agenda has space for topic-based breakout sessions; we have
started a collection of candidate topics at:
  https://github.com/t2trg/2017-07-wishi/wiki/Candidate-Breakout-Topics

(This is a wiki so you can go ahead and suggest your own topics; you
can also pencil yourself in as a breakout leader for one of the
topics.  Actual topics will be decided on the workshop Saturday.)


We need your registration to plan food/drink, T-Shirts (yes! :-) and
an evening event.  We are also getting close to the capacity of the
room and need to know whether we'll have to look for a larger one.


While we have your attention (but please register first before reading
the rest of the message):

* The next OCF-T2TRG joint session is materializing on November 10 at
  the Sheraton Towers Singapore, the Friday before IETF100 in
  Singapore (OCF was kind enough to choose Singapore as their main
  meeting location based on IETF's choice).

* We do plan to meet as part of the RIOT/ICN cluster of meetings and
  workshops in Berlin in Week 39, but haven't nailed down the details
  yet.

Gr=C3=BC=C3=9Fe, Carsten (also for Ari, who is busy celebrating =
Juhannus)


From nobody Fri Jun 23 17:17:05 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 D327F12EB95; Fri, 23 Jun 2017 17:07:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <cabo@tzi.org>, <t2trg-chairs@ietf.org>
Cc: t2trg@irtf.org, irtf-chair@irtf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149826283786.7840.15530277731552232392.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 17:07:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/kWb2U3a8vXzeRGjJ5wySAilHNXc>
Subject: [T2TRG] t2trg - Requested session has been scheduled for IETF 99
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: Sat, 24 Jun 2017 00:07:18 -0000

Dear Carsten Bormann,

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

t2trg Session 1 (2:00:00)
    Tuesday, Afternoon Session I 1330-1530
    Room Name: Grand Hilton Ballroom size: 250
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: Thing-to-Thing
Area Name: IRTF
Session Requester: Carsten Bormann

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 120
Conflicts to Avoid: 
 First Priority: cbor httpbis core ace lpwan 6lo roll teep ice
 Second Priority: dnssd saag irtfopen 6tisch netconf netmod sacm artarea
 Third Priority: lwig detnet quic v6ops opsarea cfrg icnrg intarea


People who must be present:
  Carsten Bormann
  Ari Keranen

Resources Requested:

Special Requests:
  Early in the week would help so participants from the Saturday/Sunday
workshop can hang around.
Please also avoid any IoT related BOFs that might come up.
---------------------------------------------------------


From nobody Sat Jun 24 01:58:22 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 9EA86129413; Sat, 24 Jun 2017 01:58:20 -0700 (PDT)
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 rCkuqw2dVVni; Sat, 24 Jun 2017 01:58:18 -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 76C331242F5; Sat, 24 Jun 2017 01:58:18 -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 v5O8wFiL024355; Sat, 24 Jun 2017 10:58:15 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (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 3wvq3V5hTTz3Z2D; Sat, 24 Jun 2017 10:58:14 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2DB0474F-900D-42FD-B2C5-F61F396B751C@tzi.org>
Date: Sat, 24 Jun 2017 10:58:14 +0200
X-Mao-Original-Outgoing-Id: 519987494.231328-86f3961023977340577980ee6f18d1af
Content-Transfer-Encoding: quoted-printable
Message-Id: <26509597-910C-48F9-B004-86322AD123F3@tzi.org>
References: <2DB0474F-900D-42FD-B2C5-F61F396B751C@tzi.org>
To: ace <ace@ietf.org>, core <core@ietf.org>, cose <cose@ietf.org>, cbor@ietf.org, t2trg@irtf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/gTCC_Lj06x0T2SfM4h1sbDmCFng>
Subject: [T2TRG] Constrained Node/Network Cluster @ IETF99: "FINAL" AGENDA
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: Sat, 24 Jun 2017 08:58:21 -0000

Here is my usual eclectic condensed agenda, now based on the "FINAL"
AGENDA for IETF99.  Compared to the last week's draft agenda, dnssd
and acme were moved.  (It is likely that there still will be some more
changes after this "FINAL" agenda.)

ACE people are going to miss DISPATCH (ARTAREA) again -- not sure if
there would have been be any discussions relevant to Constrained
Nodes/Networks in ARTAREA, but it doesn't make sense with this
scheduling.  CORE people will miss both ANIMA and (in-week) ICNRG.
ROLL people will miss SAAG, ouch.  And LPWAN is on the second half of
QUIC.  All no disasters, AFAICS, but not pain-free.

All times are CEST (UTC+0200).  (You can get pure UTC times on
https://datatracker.ietf.org/meeting/agenda-utc, for those who want to
listen from remote.)


SATURDAY, July 15, 2017

0900-1700  ACM, IRTF & ISOC Applied Networking Research Workshop 2017 =
(Registration Required) - Athens/Barcelona
0900-1800  T2TRG Interim Meeting - Berlin/Brussels
0900-2100  IETF Hackathon - Chez Louis

SUNDAY, July 16, 2017

0900-1600  T2TRG Interim Meeting - Berlin/Brussels
0900-1600  IETF Hackathon - Chez Louis
1345-1445  IEEE 802.1 Time-Sensitive Networking - Congress Hall III
1345-1445  IRTF Overview - Congress Hall I
1345-1445  TEEP Tutorial - Karlin I/II
1600-1700  Newcomers' Meet and Greet (open to Newcomers, WG chairs and =
Mentors only) - Garden Terrace
1700-1900  Welcome Reception - Grand Hilton Ballroom & Foyer

MONDAY, July 17, 2017

0930-1200  Morning Session I
Congress H III	ART	dispatch	Dispatch WG - 09:30-11:30
Grand Hilton BR	INT	6man	IPv6 Maintenance WG
Congress H I	SEC ***	ace	Authentication and Authorization for =
Constrained Environments WG
Congress H III	SEC	curdle	CURves, Deprecating and a Little more =
Encryption WG - 11:30-12:00

1330-1530  Afternoon Session I
Karlin I/II	INT ***	6tisch	IPv6 over the TSCH mode of IEEE =
802.15.4e WG
Grand Hilton BR	INT	homenet	Home Networking WG

1550-1720  Afternoon Session II
Karlin I/II	ART ***	cbor	Concise Binary Object Representation =
Maintenance and Extensions WG
Berlin/Brussels	SEC	tokbind	Token Binding WG

1740-1840  Afternoon Session III
Athens/Barcel.	RTG	babel	Babel routing protocol WG
Grand Hilton BR	TSV	tsvarea	Transport Area Open Meeting

TUESDAY, July 18, 2017

0930-1200  Morning Session I
Congress H II	OPS	v6ops	IPv6 Operations WG
Congress H I	TSV	taps	Transport Services WG

1330-1530  Afternoon Session I
Grand Hilton BR	IRTF***	t2trg	Thing-to-Thing
Berlin/Brussels	SEC	oauth	Web Authorization Protocol WG
Congress H I	TSV	tsvwg	Transport Area Working Group WG

1550-1750  Afternoon Session II
Karlin I/II	INT ***	6lo	IPv6 over Networks of =
Resource-constrained Nodes WG
Congress H I	IRTF	cfrg	Crypto Forum

WEDNESDAY, July 19, 2017

0930-1200  Morning Session I
Congress H I	ART ***	core	Constrained RESTful Environments WG
Karlin I/II	IRTF	icnrg	Information-Centric Networking
Congress H III	OPS	anima	Autonomic Networking Integrated Model =
and Approach WG
Congress H II	RTG	rtgarea	Routing Area Open Meeting
Grand Hilton BR	SEC	tls	Transport Layer Security WG
Karlin III	TSV	rmcat	RTP Media Congestion Avoidance =
Techniques WG

1330-1500  Afternoon Session I
Grand Hilton BR	ART	httpbis	Hypertext Transfer Protocol WG
Congress H III	IRTF	panrg	Proposed Path Aware Networking
Congress H II	RTG	ideas	IDentity Enabled Networks BOF

1520-1650  Afternoon Session II
Grand Hilton BR	ART	httpbis	Hypertext Transfer Protocol WG
Athens/Barcel.	INT	dnssd	Extensions for Scalable DNS Service =
Discovery  WG

THURSDAY, July 20, 2017

0930-1200  Morning Session I
Grand Hilton BR	INT	intarea	Internet Area Working Group WG
Congress H II	IRTF	maprg	Measurement and Analysis for Protocols
Congress H I	RTG	detnet	Deterministic Networking WG

1330-1530  Afternoon Session I
Berlin/Brussels	ART	ice	Interactive Connectivity Establishment =
WG
Grand Hilton BR	OPS	v6ops	IPv6 Operations WG
Karlin I/II	RTG ***	roll	Routing Over Low power and Lossy =
networks WG
Congress H III	SEC	saag	Security Area Open Meeting

1550-1750  Afternoon Session II
Athens/Barcel.	INT	ipwave	IP Wireless Access in Vehicular =
Environments WG
Grand Hilton BR	TSV	quic	QUIC WG

1810-1910  Afternoon Session III
Berlin/Brussels	ART	uta	Using TLS in Applications WG
Athens/Barcel.	INT ***	lwig	Light-Weight Implementation Guidance WG
Karlin I/II	RTG	bier	Bit Indexed Explicit Replication WG
Congress H III	TSV	tsvwg	Transport Area Working Group WG

FRIDAY, July 21, 2017

0930-1130  Morning Session I
Karlin I/II	INT ***	lpwan	IPv6 over Low Power Wide-Area Networks =
WG
Athens/Barcel.	SEC	acme	Automated Certificate Management =
Environment WG
Karlin III	SEC	oauth	Web Authorization Protocol WG
Grand Hilton BR	TSV	quic	QUIC WG

1150-1320  Afternoon Session II
Congress H III	ART ***	core	Constrained RESTful Environments WG


