From nobody Sun Jun  1 15:03:57 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87E3C1A00AA; Sun,  1 Jun 2014 15:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level: 
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 p0Ip3OL5IIGZ; Sun,  1 Jun 2014 15:02:50 -0700 (PDT)
Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3F531A0097; Sun,  1 Jun 2014 15:02:49 -0700 (PDT)
Received: by mail-ve0-f175.google.com with SMTP id jw12so4301715veb.6 for <multiple recipients>; Sun, 01 Jun 2014 15:02:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=ZLRO0/RIO56RwmstCmol+3YTYMXUG/RONLxBx3bLkC8=; b=gvpksA3lx30ZcAXoQXKmExES8VmFBK4rvsepd7bd+ljMI+9+ER4SDcpQHK09Yp5I+T JjVTDstoXyBfXch9NwOAHZN46R4JrpEssneQ+GOVL7WpW11OJP4Bz/9u081Va9nCpy7D ONv4nqSZ5+7dP1nkMLE5fWfkgCMRTnf6WiI2H4W0d23+DFy56Yt8ncBiN2c82dxZInXJ 1rNqGAoTalFgXJhkss8v3wawNasToxnXs7UGemYA1Rv9KNZ4rzKNPe2GlLkf4B2EgABC 1m1w8EAL8chaVIMzz2YRrPyVm4UDt8QnWeb0SX9Pc7Gc4prQML0gEXuWdbGJw25N2yhs 9Wzw==
MIME-Version: 1.0
X-Received: by 10.58.56.71 with SMTP id y7mr26717607vep.24.1401660164031; Sun, 01 Jun 2014 15:02:44 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Sun, 1 Jun 2014 15:02:43 -0700 (PDT)
Date: Mon, 2 Jun 2014 01:02:43 +0300
Message-ID: <CAP+sJUdPsh_DWdzuJK0GFEQhJO3rapK9VryNsV4uavyksDonnQ@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b3a9b742ce9d904facd703b
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/WI9gG3k_tO-BN4qzj2mCk8sW5VM
X-Mailman-Approved-At: Sun, 01 Jun 2014 15:03:56 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, 6tisch-security@ietf.org, lwip@ietf.org, roll <roll@ietf.org>, ace@ietf.org, dtls-iot@ietf.org, coman@ietf.org, core@ietf.org, 6lo@ietf.org, "6tisch@ietf.org" <6tisch@ietf.org>
Subject: [Roll] LLN Plugfest at IETF 90
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2014 22:02:53 -0000

--047d7b3a9b742ce9d904facd703b
Content-Type: text/plain; charset=UTF-8

Dear all,

We would like to announce the plugfest event at the 90th IETF Meeting in
Toronto.

We call for participants. The deadline to receive topics to present or
demonstrate in the event is 06/13/2014. Interested audience is also welcome
and we encourage audience to participate in the feedback session.

Please find next the plugfest information.

We hope to see you there!

Xavier and Ines.

-----------------------
Low Power and Lossy Networks plugfest at IETF90

The IETF 6TiSCH <https://datatracker.ietf.org/wg/6tisch/charter/>, IETF 6lo
<https://datatracker.ietf.org/wg/6lo/charter/> and IETF ROLL
<https://datatracker.ietf.org/wg/roll/charter/> working groups are hosting
an informal "plugfest" event at the IETF90 meeting, in Toronto, CA, during
the week of July 20-25 2014.
Goals

The goal of this event is to bring together people interested in hands-on
experience around the technology developed by the 6TiSCH, 6lo and ROLL
working groups, with a particular focus on the TSCH mode of IEEE802.15.4e,
6lowpan, RPL and new WG specifications.
When and where ?

   - *Date*: Sunday July 20 2014, 0900-1300 EDT.
   - *Location*: Meeting Room TBD, Fairmont Royal York Hotel 100 Front
   Street W, Toronto, CA.

*Early access: TBD if the plugfest room will be open starting 8am EDT on
Sunday 20 2014 to allow people to set up.*
Topology proposed - TBD

   - Star topology
   - IPv6

Complementary angles

This event will feature the following complementary angles:

   - Interoperation
   - Demonstration
   - Tools

Focus 1: Interoperation

Download the interoperation guidelines:

   - - TBD for Toronto - interoperation guidelines, version 1 (London)
   <https://bitbucket.org/6tisch/meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_guidelines_v01.pdf>

The goal is to achieve interoperation between different hardware and
software implementations on the different aspects addressed by 6lo, 6TiSCH
and ROLL WGs. This include 6TiSCH minimal draft implementation,
demonstrating TSCH synchronization and OF0 for RPL on a minimal network.
6lowpan to demostrate cross link layer inter-operability by means of
bridges or backbones routers. Storing and non-storing RPL implementation
including its coexistance in different sub-networks.

The focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH
drafts implementations, including but not limited to: e.g. - 6TiSCH minimal
draft: http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00. - TBD

Participants are encouraged to bring devices which implement parts or all
of the listed drafts.

Levels of interoperation are proposed:

   - *Level 1*, star topology. A single BBR devices acts as the time source
   neighbor for all other nodes. Nodes need to demonstrate frame-based and
   acknowledgement-based synchronization. The static TSCH schedule, as well as
   all slot timings are taken from draft-ietf-6tisch-minimal-00.
   - *Level 2*, multi-hop topology. This level builds upon level 1. The
   goal of this level is full compliance to draft-ietf-6tisch-minimal-00,
   including multi-hop routing (RPL).
   - *Level 3*, on-the-fly scheduling. [optional] Preliminary
   implementations of
   http://tools.ietf.org/html/draft-dujovne-6tisch-on-the-fly can be shown.
   - *Level 4*, drafts from ROLL, such as:
   draft-ietf-roll-mpl-parameter-configuration,
   draft-ko-roll-mix-network-pathology, Opportunistic routing, selective DIS,
   and others that participants want to show
   - *Level 5*, drafts from 6lo, such as: draft-ietf-6lo-btle,
   draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz, and others that participants
   want to show.
   - *Level 6* Other drafts, such as draft-thubert-6man-flow-label-for-rpl,
   etc.

Focus 2: Demonstration

Participants are encouraged to bring devices and technology based on
6TiSCH, 6lo and ROLL which they believe can be of interest for the other
participants. These devices may or may not participate in the
interoperation event. Demonstration of more complete systems are
encouraged, for example systems which show the interconnection of a 6TiSCH
based mesh to traditional networks.
Focus 3: Tools

Participants are encouraged to bring and present different tools developed
around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not
limited to:

   - acquisition devices (i.e. "sniffers")
   - packet analysis tools (e.g. Wireshark)
   - simulation/emulation platforms

Important Dates

The preparation of this event will be held during a portion of the
bi-weekly 6TiSCH call (*To Be Decided how and when!!!*). In particular:

   - *06/02/2014* Announcement of the plugfest event to the WG/ML related
   with constrained devices, such as: 6tisch, 6lo, roll, core, lwig, dtls-iot,
   coman, ace, etc.
   - *06/06/2014* Adoption of the plugfest call by the WGs, and call for
   participants at each group.
   - *06/02/2014-06/13/2014* Participants have contacted the plugfest
   chairs (Xavier or Ines) with a tentative description of what they wish to
   participate in.
   - *06/20/2014* Synchronization point 1. Participants can share the state
   of advancement of the implementation and raise blocking points.
   - *07/11/2014* Synchronization point 2. Participants can share the state
   of advancement of the implementation and raise blocking points.
   - *07/20/2014*. Plugfest at IETF90.

Tentative Agenda from 9:00 to 13:00

   - *[09.00]* Welcome and Initial Instructions
   - *[09.05]* Participants Pitch (5 min per Participant)
   - *[09.45]* Participants Pitch Tools (5 min per Participant)
   - *[10.15]* Interoperation (Islands)
   - *[11.50]* Feedback and open discussion.
   - *[12.40]* Acknowledgements and Plugfest End

For More Information

   - *Contact*: Xavi Vilajosana xvilajosana@eecs.berkeley.edu - Ines Robles
   mariainesrobles@gmail.com

Note Well

This event is organized as part of the IETF90 standardization meeting. You
need to register to the IETF90 conference to be able to participate. Daily
passes are available. The IETF Note Well applies to this plugfest, see
http://www.ietf.org/about/note-well.html.
About

The IETF 6TiSCH working group standardizes mechanisms focusing on enabling
IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the
charter at http://datatracker.ietf.org/wg/6tisch/charter/, which also
contains links to the mailing list and the Internet-Drafts published by the
group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is
open, and is subject to the IETF Note Well.

The IETF 6lo working group focuses on the work that facilitates IPv6
connectivity over constrained node networks with the characteristics of:
limited power, memory and processing resources;. You can access the charter
at https://datatracker.ietf.org/wg/6lo/charter/, which also contains links
to the mailing list and the I-D published by the group.

The IETF ROLL working group is focused on routing issues for LLN (Low Power
and Lossy Networks), in IPv6 routing architectural framework for the
industrial, connected home, building and urban sensor networks application
scenarios. You can access the charter at
https://datatracker.ietf.org/wg/roll/charter/, which also contains links to
the mailing list and the I-D published by the group.

--047d7b3a9b742ce9d904facd703b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><span style=3D"font-family:arial,helvetica,sans-=
serif;color:rgb(0,0,0)">Dear all,</span><br></div><font face=3D"arial, helv=
etica, sans-serif"><br style=3D"color:rgb(0,0,0)"><span style=3D"color:rgb(=
0,0,0)">We would like to announce the plugfest event at the 90th IETF Meeti=
ng in Toronto.</span></font><div>

<span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif=
"><br></font></span></div></div><div><span style=3D"color:rgb(0,0,0)"><font=
 face=3D"arial, helvetica, sans-serif">We call for participants. The deadli=
ne to receive topics to present or demonstrate in the event is 06/13/2014. =
Interested audience is also welcome and we encourage audience to participat=
e in the feedback session.</font></span></div>

<div><div><span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, =
sans-serif"><br></font></span></div><div><span style=3D"color:rgb(0,0,0)"><=
font face=3D"arial, helvetica, sans-serif">Please find next the plugfest in=
formation.=C2=A0</font></span><div>

<font face=3D"arial, helvetica, sans-serif"><br></font></div><div><span sty=
le=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif">We hope=
 to see you there!</font></span><div><font color=3D"#000000" face=3D"arial,=
 helvetica, sans-serif"><br>

</font></div><div><div style=3D"color:rgb(0,0,0)"><font face=3D"arial, helv=
etica, sans-serif">Xavier and Ines.</font></div></div></div></div><div styl=
e=3D"font-family:&#39;Times New Roman&#39;;font-size:13px;color:rgb(0,0,0)"=
>
<font size=3D"3"><br>
</font></div><div style=3D"font-family:&#39;Times New Roman&#39;;font-size:=
13px;color:rgb(0,0,0)"><font size=3D"3">-----------------------</font></div=
><div><h1 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-si=
ze:24px;margin:20px 0px 10px;padding:0px;font-weight:normal;line-height:1.2=
5">

Low Power and Lossy Networks plugfest at IETF90</h1><p style=3D"color:rgb(5=
1,51,51);font-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;pa=
dding:0px;word-wrap:break-word;line-height:20px">The=C2=A0<a href=3D"https:=
//datatracker.ietf.org/wg/6tisch/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6TiSCH</a>,=C2=A0<a href=3D"htt=
ps://datatracker.ietf.org/wg/6lo/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6lo</a>=C2=A0and=C2=A0<a href=
=3D"https://datatracker.ietf.org/wg/roll/charter/" style=3D"color:rgb(59,11=
5,175);text-decoration:none" target=3D"_blank">IETF ROLL</a>=C2=A0working g=
roups are hosting an informal &quot;plugfest&quot; event at the IETF90 meet=
ing, in Toronto, CA, during the week of July 20-25 2014.</p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Goals=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">

The goal of this event is to bring together people interested in hands-on e=
xperience around the technology developed by the 6TiSCH, 6lo and ROLL worki=
ng groups, with a particular focus on the TSCH mode of IEEE802.15.4e, 6lowp=
an, RPL and new WG specifications.</p>

<h3 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:18p=
x;margin:20px 0px 0px;padding:0px;line-height:1.3888888888888888;font-weigh=
t:normal">When and where ?</h3><ul style=3D"color:rgb(51,51,51);font-family=
:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word"><strong>Date</strong>: Sunday July 20 20=
14, 0900-1300 EDT.</li><li style=3D"word-wrap:break-word"><strong>Location<=
/strong>: Meeting Room TBD, Fairmont Royal York Hotel 100 Front Street W, T=
oronto, CA.</li>

</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
"><strong>Early access: TBD if the plugfest room will be open starting 8am =
EDT on Sunday 20 2014 to allow people to set up.</strong></p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Topol=
ogy proposed - TBD</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,s=
ans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word">Star topology</li><li style=3D"word-wrap=
:break-word">IPv6</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Ari=
al,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:no=
rmal;line-height:1.5">

Complementary angles</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,=
sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-w=
ord;line-height:20px">This event will feature the following complementary a=
ngles:</p>

<ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14p=
x;margin:10px 0px 0px;line-height:20px"><li style=3D"word-wrap:break-word">=
Interoperation</li><li style=3D"word-wrap:break-word">Demonstration</li><li=
 style=3D"word-wrap:break-word">

Tools</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-seri=
f;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-he=
ight:1.5">Focus 1: Interoperation</h2>
<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Dow=
nload the interoperation guidelines:</p><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px">

<li style=3D"word-wrap:break-word"><a href=3D"https://bitbucket.org/6tisch/=
meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_gui=
delines_v01.pdf" style=3D"color:rgb(59,115,175);text-decoration:none" targe=
t=3D"_blank"> - TBD for Toronto - interoperation guidelines, version 1 (Lon=
don)</a></li>

</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">The goal is to achieve interoperation between different hardware and soft=
ware implementations on the different aspects addressed by 6lo, 6TiSCH and =
ROLL WGs. This include 6TiSCH minimal draft implementation, demonstrating T=
SCH synchronization and OF0 for RPL on a minimal network. 6lowpan to demost=
rate cross link layer inter-operability by means of bridges or backbones ro=
uters. Storing and non-storing RPL implementation including its coexistance=
 in different sub-networks.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH draft=
s implementations, including but not limited to: e.g. - 6TiSCH minimal draf=
t:=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00"=
 rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00</a>. =
- TBD</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Par=
ticipants are encouraged to bring devices which implement parts or all of t=
he listed drafts.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Lev=
els of interoperation are proposed:</p><ul style=3D"color:rgb(51,51,51);fon=
t-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20=
px">

<li style=3D"word-wrap:break-word"><strong>Level 1</strong>, star topology.=
 A single BBR devices acts as the time source neighbor for all other nodes.=
 Nodes need to demonstrate frame-based and acknowledgement-based synchroniz=
ation. The static TSCH schedule, as well as all slot timings are taken from=
 draft-ietf-6tisch-minimal-00.</li>

<li style=3D"word-wrap:break-word"><strong>Level 2</strong>, multi-hop topo=
logy. This level builds upon level 1. The goal of this level is full compli=
ance to draft-ietf-6tisch-minimal-00, including multi-hop routing (RPL).</l=
i>

<li style=3D"word-wrap:break-word"><strong>Level 3</strong>, on-the-fly sch=
eduling. [optional] Preliminary implementations of=C2=A0<a href=3D"http://t=
ools.ietf.org/html/draft-dujovne-6tisch-on-the-fly" rel=3D"nofollow" style=
=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http://to=
ols.ietf.org/html/draft-dujovne-6tisch-on-the-fly</a>=C2=A0can be shown.</l=
i>

<li style=3D"word-wrap:break-word"><strong>Level 4</strong>, drafts from RO=
LL, such as: draft-ietf-roll-mpl-parameter-configuration, draft-ko-roll-mix=
-network-pathology, Opportunistic routing, selective DIS, and others that p=
articipants want to show</li>

<li style=3D"word-wrap:break-word"><strong>Level 5</strong>, drafts from 6l=
o, such as: draft-ietf-6lo-btle, draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz,=
 and others that participants want to show.</li><li style=3D"word-wrap:brea=
k-word">

<strong>Level 6</strong>=C2=A0Other drafts, such as draft-thubert-6man-flow=
-label-for-rpl, etc.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:=
Arial,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight=
:normal;line-height:1.5">

Focus 2: Demonstration</h2><p style=3D"color:rgb(51,51,51);font-family:Aria=
l,sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break=
-word;line-height:20px">Participants are encouraged to bring devices and te=
chnology based on 6TiSCH, 6lo and ROLL which they believe can be of interes=
t for the other participants. These devices may or may not participate in t=
he interoperation event. Demonstration of more complete systems are encoura=
ged, for example systems which show the interconnection of a 6TiSCH based m=
esh to traditional networks.</p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Focus=
 3: Tools</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">

Participants are encouraged to bring and present different tools developed =
around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not limite=
d to:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font=
-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word">acquisition devices (i.e. &quot;sniffers=
&quot;)</li><li style=3D"word-wrap:break-word">packet analysis tools (e.g. =
Wireshark)</li><li style=3D"word-wrap:break-word">simulation/emulation plat=
forms</li>

</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Important Dates</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-=
serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;l=
ine-height:20px">

The preparation of this event will be held during a portion of the bi-weekl=
y 6TiSCH call (<strong>To Be Decided how and when!!!</strong>). In particul=
ar:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-s=
ize:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word"><strong>06/02/2014</strong>=C2=A0Announc=
ement of the plugfest event to the WG/ML related with constrained devices, =
such as: 6tisch, 6lo, roll, core, lwig, dtls-iot, coman, ace, etc.</li><li =
style=3D"word-wrap:break-word">

<strong>06/06/2014</strong>=C2=A0Adoption of the plugfest call by the WGs, =
and call for participants at each group.</li><li style=3D"word-wrap:break-w=
ord"><strong>06/02/2014-06/13/2014</strong>=C2=A0Participants have contacte=
d the plugfest chairs (Xavier or Ines) with a tentative description of what=
 they wish to participate in.</li>

<li style=3D"word-wrap:break-word"><strong>06/20/2014</strong>=C2=A0Synchro=
nization point 1. Participants can share the state of advancement of the im=
plementation and raise blocking points.</li><li style=3D"word-wrap:break-wo=
rd">
<strong>07/11/2014</strong>=C2=A0Synchronization point 2. Participants can =
share the state of advancement of the implementation and raise blocking poi=
nts.</li>
<li style=3D"word-wrap:break-word"><strong>07/20/2014</strong>. Plugfest at=
 IETF90.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-s=
erif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line=
-height:1.5">

Tentative Agenda from 9:00 to 13:00</h2><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px"><li style=3D"word-wrap:break-word"><em>[09.00]</em>=C2=A0Welcome and I=
nitial Instructions</li>

<li style=3D"word-wrap:break-word"><em>[09.05]</em>=C2=A0Participants Pitch=
 (5 min per Participant)</li><li style=3D"word-wrap:break-word"><em>[09.45]=
</em>=C2=A0Participants Pitch Tools (5 min per Participant)</li><li style=
=3D"word-wrap:break-word">

<em>[10.15]</em>=C2=A0Interoperation (Islands)</li><li style=3D"word-wrap:b=
reak-word"><em>[11.50]</em>=C2=A0Feedback and open discussion.</li><li styl=
e=3D"word-wrap:break-word"><em>[12.40]</em>=C2=A0Acknowledgements and Plugf=
est End</li></ul>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">For M=
ore Information</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans=
-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">

<li style=3D"word-wrap:break-word"><strong>Contact</strong>: Xavi Vilajosan=
a=C2=A0<a href=3D"mailto:xvilajosana@eecs.berkeley.edu" style=3D"color:rgb(=
59,115,175);text-decoration:none" target=3D"_blank">xvilajosana@eecs.berkel=
ey.edu</a>=C2=A0- Ines Robles=C2=A0<a href=3D"mailto:mariainesrobles@gmail.=
com" style=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank"=
>mariainesrobles@gmail.com</a></li>

</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Note Well</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">

This event is organized as part of the IETF90 standardization meeting. You =
need to register to the IETF90 conference to be able to participate. Daily =
passes are available. The IETF Note Well applies to this plugfest, see=C2=
=A0<a href=3D"http://www.ietf.org/about/note-well.html" rel=3D"nofollow" st=
yle=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http:/=
/www.ietf.org/about/note-well.html</a>.</p>

<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">About=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">

The IETF 6TiSCH working group standardizes mechanisms focusing on enabling =
IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the c=
harter at=C2=A0<a href=3D"http://datatracker.ietf.org/wg/6tisch/charter/" r=
el=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" target=
=3D"_blank">http://datatracker.ietf.org/wg/6tisch/charter/</a>, which also =
contains links to the mailing list and the Internet-Drafts published by the=
 group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is=
 open, and is subject to the IETF Note Well.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF 6lo working group focuses on the work that facilitates IPv6 connectiv=
ity over constrained node networks with the characteristics of: limited pow=
er, memory and processing resources;. You can access the charter at=C2=A0<a=
 href=3D"https://datatracker.ietf.org/wg/6lo/charter/" rel=3D"nofollow" sty=
le=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">https:/=
/datatracker.ietf.org/wg/6lo/charter/</a>, which also contains links to the=
 mailing list and the I-D published by the group.</p>

<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF ROLL working group is focused on routing issues for LLN (Low Power an=
d Lossy Networks), in IPv6 routing architectural framework for the industri=
al, connected home, building and urban sensor networks application scenario=
s. You can access the charter at=C2=A0<a href=3D"https://datatracker.ietf.o=
rg/wg/roll/charter/" rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-d=
ecoration:none" target=3D"_blank">https://datatracker.ietf.org/wg/roll/char=
ter/</a>, which also contains links to the mailing list and the I-D publish=
ed by the group.</p>

</div></div></div>

--047d7b3a9b742ce9d904facd703b--


From nobody Tue Jun  3 14:17:21 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B6D1A036A for <roll@ietfa.amsl.com>; Tue,  3 Jun 2014 14:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 dAITY9PkaBVu for <roll@ietfa.amsl.com>; Tue,  3 Jun 2014 14:17:18 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F14C1A02F7 for <roll@ietf.org>; Tue,  3 Jun 2014 14:17:18 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id jz11so7603490veb.7 for <roll@ietf.org>; Tue, 03 Jun 2014 14:17:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=1BBiMwNhR99aAatVMkWtc9d4T2hnsWGnrKVm3thU1CY=; b=xW19ahPpXkzjHJ1O0Sidh5lZJAwDVqA5xsiPfkVDbOUUF58njd/DBzPzn1Xkjq692L yvNU8O0aTPk4qy478uXDIeRG49JkN0V3/e7sMSlYBAab4vQKZRZ7U+eu32KVQf6nEUBm i04ycfqciazD6GrfPhoXiQ4uvwew+nT7fOjsytYqVgMXVM0Pv26PupwhTEirstUe0fya dWV0WqJ8G+e46OVnMIt3Hm4t/LnpiNzS9p2bI2PWuKlcZN2HbQ1DTL8rJw+imGtNY3Qb AvlHY/xPsrRmFhNsFXNSBejCDsNBpeZx7gvKqhTeR7fbHFZ6+c1HjW3VdHracQd8/JmY J8nQ==
MIME-Version: 1.0
X-Received: by 10.58.123.71 with SMTP id ly7mr38429964veb.11.1401830231724; Tue, 03 Jun 2014 14:17:11 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Tue, 3 Jun 2014 14:17:11 -0700 (PDT)
Date: Wed, 4 Jun 2014 00:17:11 +0300
Message-ID: <CAP+sJUe5X5pdMZtyStVQGibS2CZ-R-32yQhj8wLAPePqSCq_3g@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: roll <roll@ietf.org>
Content-Type: multipart/alternative; boundary=089e0115f0a2ff58fe04faf5081f
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/wYOG7ZaZeOQ8Oa4DXY14D3FvZZE
Cc: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: [Roll] IETF 90 - Toronto - Draft to be presented - Slides in advance
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 21:17:19 -0000

--089e0115f0a2ff58fe04faf5081f
Content-Type: text/plain; charset=UTF-8

Hello,

This is a kindly reminder,

Due to the limited duration of the meeting (1 hour more or less), we
require please the slides in advance, to decide if the drafts will be
presented or not. Please, we require the slides before 06/06/2014.

Please let us know if you desire present remotely.

Thanks and Regards,

Michael & Ines.


2014-05-08 16:28 GMT+03:00 Ines Robles <mariainesrobles@googlemail.com>:

>
> Hello,
>
> We would like to know please, which drafts desire be presented in the Next
> Meeting: IETF 90, July 20-25, 2014
>
> Due to the limited duration of the meeting (1 hour more or less), we
> require please the slides in advance, to decide if the drafts will be
> presented or not. Please, we require the slides before 06/06/2014.
>
> After the decision (based on the slides obtained), we will let you know
> about which  drafts will be included in the meeting.
>
> Thank you very much in advance,
>
> Michael & Ines.
>

--089e0115f0a2ff58fe04faf5081f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:13px=
">Hello,</span><div style=3D"font-family:arial,sans-serif;font-size:13px"><=
br></div><div style=3D"font-family:arial,sans-serif;font-size:13px">This is=
 a kindly reminder,</div>
<div class=3D"im" style=3D"font-family:arial,sans-serif;font-size:13px"><di=
v><br></div><div><span style=3D"font-family:Arial;line-height:14.9499998092=
65137px;white-space:pre-wrap">Due to the limited duration of the meeting (1=
 hour more or less), we require please the </span><span style=3D"font-famil=
y:Arial;line-height:14.949999809265137px;white-space:pre-wrap">slides</span=
><span style=3D"font-family:Arial;line-height:14.949999809265137px;white-sp=
ace:pre-wrap"> in </span><span style=3D"font-family:Arial;line-height:14.94=
9999809265137px;white-space:pre-wrap">advance</span><span style=3D"font-fam=
ily:Arial;line-height:14.949999809265137px;white-space:pre-wrap">, to decid=
e if the drafts will be </span><span style=3D"font-family:Arial;line-height=
:14.949999809265137px;white-space:pre-wrap">presented</span><span style=3D"=
font-family:Arial;line-height:14.949999809265137px;white-space:pre-wrap"> o=
r not. Please, we require the </span><span style=3D"font-family:Arial;line-=
height:14.949999809265137px;white-space:pre-wrap">slides</span><span style=
=3D"font-family:Arial;line-height:14.949999809265137px;white-space:pre-wrap=
"> before 06/06/2014.</span><br>
</div><div><span style=3D"font-family:Arial;line-height:14.949999809265137p=
x;white-space:pre-wrap"><br></span></div><div><span style=3D"font-family:Ar=
ial;line-height:14.949999809265137px;white-space:pre-wrap">Please let us kn=
ow if you desire present remotely.</span></div>
<div><span style=3D"font-family:Arial;line-height:14.949999809265137px;whit=
e-space:pre-wrap"><br></span></div><div><span style=3D"color:rgb(34,34,34)"=
>Thanks and Regards,</span><br></div></div><div style=3D"font-family:arial,=
sans-serif;font-size:13px">
<br></div><div style=3D"font-family:arial,sans-serif;font-size:13px">Michae=
l &amp; Ines.</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_q=
uote">2014-05-08 16:28 GMT+03:00 Ines  Robles <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mariainesrobles@googlemail.com" target=3D"_blank">mariainesroble=
s@googlemail.com</a>&gt;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><span><br><p dir=3D"ltr" st=
yle=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt;margin-right:1pt">=
<span style=3D"font-size:13px;font-family:Arial;vertical-align:baseline;whi=
te-space:pre-wrap">Hello,</span></p>

<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt;margin-right:1pt"><span style=3D"font-size:13px;font-family:Arial;vertic=
al-align:baseline;white-space:pre-wrap">We would like to know please, which=
 drafts desire be presented in the Next Meeting: </span><span style=3D"font=
-size:13px;font-family:Arial;background-color:rgb(255,255,204);vertical-ali=
gn:baseline;white-space:pre-wrap">IETF 90, July 20-25, 2014</span></p>

<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt;margin-right:1pt"><span style=3D"font-size:13px;font-family:Arial;vertic=
al-align:baseline;white-space:pre-wrap">Due to the limited duration of the =
meeting (1 hour more or less), we require please the slides in advance, to =
decide if the drafts will be presented or not. Please, we require the slide=
s before 06/06/2014.</span></p>

<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt;margin-right:1pt"><span style=3D"font-size:13px;font-family:Arial;vertic=
al-align:baseline;white-space:pre-wrap">After the decision (based on the sl=
ides obtained), we will let you know about which =C2=A0drafts will be inclu=
ded in the meeting.</span></p>

<br><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0=
pt;margin-right:1pt"><span style=3D"font-size:13px;font-family:Arial;vertic=
al-align:baseline;white-space:pre-wrap">Thank you very much in advance,</sp=
an></p>

<br><span style=3D"font-size:13px;font-family:Arial;vertical-align:baseline=
;white-space:pre-wrap">Michael &amp; Ines.</span></span><br></div>
</blockquote></div><br></div></div>

--089e0115f0a2ff58fe04faf5081f--


From nobody Tue Jun 10 13:24:29 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 724E11A02FB for <roll@ietfa.amsl.com>; Tue, 10 Jun 2014 13:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 1mWxl58VSRez for <roll@ietfa.amsl.com>; Tue, 10 Jun 2014 13:24:06 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 571121A02D0 for <roll@ietf.org>; Tue, 10 Jun 2014 13:24:06 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id oz11so4224086veb.8 for <roll@ietf.org>; Tue, 10 Jun 2014 13:24:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=RNLzNlWkcOf95FXmzae2DHTOl4RABOGRc1lFGQtPPzM=; b=hzAKiTLj4FWX1ex/0BFS4vMttkWGiRVX4Z1CTIW9u7Qmx0AbNDExkOqEtdsi8cAuAC iimWWlRQmmMfZ58kv1Zm5eG22u8XqEYZGLsq9eOjDKa3FN+MQSogmkLAZhxiMxgRncoO PyZnXgVG12CTrBle1n4XBD6MiNWbbJ9dzJEDQTHS+GIbZh1jBma51LQ+/oFQah7UD46R VvLq8Fl6C2mj6HIGG54Sdxxjg3/BBldxzQSTuUJ71SEat1RJE8nLlm02TxVyziiW99gB iGB6SUVjkbujRM25KbPflK2Zq2elqfEsx3daDy6namhoIHiMvHx40jCyriZTIBrBo9Fs IaVQ==
MIME-Version: 1.0
X-Received: by 10.58.30.1 with SMTP id o1mr33575680veh.37.1402431845099; Tue, 10 Jun 2014 13:24:05 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Tue, 10 Jun 2014 13:24:05 -0700 (PDT)
Date: Tue, 10 Jun 2014 23:24:05 +0300
Message-ID: <CAP+sJUcNDZ81ZjEYYEhdt6O9ZG6AV19s=akTuf2LE8aA-pooAQ@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: roll <roll@ietf.org>
Content-Type: multipart/alternative; boundary=089e013cbe5ef2f11c04fb811be5
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/QNq0LX4sq-Qg_-NmOC1VcjxEUCk
Cc: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: [Roll] Fwd: Improving and Restructuring the Routing Area
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 20:24:08 -0000

--089e013cbe5ef2f11c04fb811be5
Content-Type: text/plain; charset=UTF-8

Hi,

It would be great if you can give your ideas of this topic in the
routing-discussion ML.

Thanks in advance,

Michael and Ines.

---------- Forwarded message ----------
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, Jun 10, 2014 at 3:57 PM
Subject: Improving and Restructuring the Routing Area
To: routing-discussion@ietf.org


To all participants in the Routing Area,

Adrian and I are working on improving the quality, speed, and
experience of getting work done in the IETF Routing Area.  There are
three initiatives that we are working: WG Draft QA, Routing Area
specific WG chair training, and reorganizing the working groups in the
area.

First, we intend to use our Routing Directorate more proactively by
introducing a Working Group Draft Quality Assurance (WG Draft QA)
process where the same selected routing directorate member will review
a draft during WG draft adoption and during WG last call.  The process
will be documented on the Routing Area wiki
(http://trac.tools.ietf.org/area/rtg/trac/wiki).  This should allow
directorate reviews to report technical issues that can actually get
fixed early in the process (equivalent of bug reports) as opposed to
just noting the concerns in the drafts (equivalent of release notes).

Second, as was discussed during the recent IESG retreat, in addition
to the IETF-wide WG chair training, we intend to have a series of
training sessions for WG Chairs in the Routing Area addressing topics
such as judging consensus, project management, motivating volunteers,
using the datatracker (via a sandbox version that can be played
with safely), and sharing experiences between WG chairs.

Third, we intend to reorganize the working groups in the Routing area.
We feel that it is important to focus on areas where there is active
interest in standardization and to be open and able to accept new work
into the area.  As you know, we have had several new working groups
(nvo3, i2rs, sfc, spring) created in the last few years and we need to
be open and able to handle more new work as it comes in.  We would
also like to improve the signal-to-noise ratio experienced by
participants in the different working groups and improve the quantity
and quality of discussion and reviews.  It is likely that not all WGs
in the Routing Area will be directly affected.

Here is the time-line for reorganizing the WGs.

   NOW: public discussion on routing-discussion@ietf.org about how to
   reorganize the working groups to best meet our motivations.
   Additional focused discussions are expected on the
   rtg-chairs@ietf.org and rtg-dir@ietf.org mailing lists.

   In Toronto: There will be meetings with the WG chairs and the
   Routing Directorate to get the ideas described and agreed upon.

   At the Routing Area Meeting in Toronto: Discuss the set of
   reorganized WGs and general charter content in the Routing Area
   meeting.

   September 2014: Based upon the feedback, suggestions, and
   discussion, Adrian and I finalize the reorganized WG charters.  We
   start the internal IESG discussion and public reviews.

   October 2014: Formal rechartering process completes.

   In Honolulu: The new set of WGs meet.

   After Honolulu: Adrian and I deal with any issues and charter
   updates based upon a few months of experience.

Here are the motivations that Adrian and I would like to be considered
when coming up with ideas for how the WGs should be reorganized.

   1) Move towards organizing working groups on functional
   responsibilities rather than scoping them to specific protocols.

   2) Split giant working groups so relevant work is done in one place
   and there is an improved signal-to-noise ratio for participants who
   are only interested in a slice of the current working group's work.

   3) Create synergies for scattered functionality (example ideas:
   OAM, FRR, traffic-engineering)

   4) Create a DISPATCH working group for clear new idea discussion;
   rtgwg serves some of this purpose but doesn't have a clear process
   and isn't drawing in the new ideas.

   5) Focus Routing Area time on design centers rather than on far
   corner cases.

   6) Each working group should have clear, well defined, and achievable
goals.

Noting that the Routing Area has inherited some of its WG structure
from the sub-IP area, it is not a goal to force IP routing and MPLS
routing to remain separated.

The goal of this reorganization is not closing working groups.  Adrian
and Alia are perfectly capable of closing working groups without going
through restructuring.

For those of you that have read this far, thank you.  Getting this 80%
right is going to take some serious discussion and thought.  We all
work in the Routing Area together with different perspectives.  Please
think carefully and help us have a highly focused discussion.

Thanks,
Alia and Adrian

--089e013cbe5ef2f11c04fb811be5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>It would be great if you can give y=
our ideas of this topic in the routing-discussion ML.</div><div><br></div><=
div>Thanks in advance,</div><div><br></div><div>Michael and Ines.</div><div=
>
<div class=3D"gmail_quote"><div dir=3D"ltr"><div><br><div class=3D"gmail_qu=
ote">---------- Forwarded message ----------<br>From: <b class=3D"gmail_sen=
dername">Alia Atlas</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:akatlas@gma=
il.com" target=3D"_blank">akatlas@gmail.com</a>&gt;</span><br>

Date: Tue, Jun 10, 2014 at 3:57 PM<br>Subject: Improving and Restructuring =
the Routing Area<br>To: <a href=3D"mailto:routing-discussion@ietf.org" targ=
et=3D"_blank">routing-discussion@ietf.org</a><br><br><br><div dir=3D"ltr"><=
div>
To all participants in the Routing Area,</div>
<div><br></div><div>Adrian and I are working on improving the quality, spee=
d, and</div><div>experience of getting work done in the IETF Routing Area. =
=C2=A0There are</div>
<div>three initiatives that we are working: WG Draft QA, Routing Area</div>=
<div>specific WG chair training, and reorganizing the working groups in the=
</div><div>area.</div><div><br></div><div>First, we intend to use our Routi=
ng Directorate more proactively by</div>


<div>introducing a Working Group Draft Quality Assurance (WG Draft QA)</div=
><div>process where the same selected routing directorate member will revie=
w</div><div>a draft during WG draft adoption and during WG last call. =C2=
=A0The process</div>


<div>will be documented on the Routing Area wiki</div><div>(<a href=3D"http=
://trac.tools.ietf.org/area/rtg/trac/wiki" target=3D"_blank">http://trac.to=
ols.ietf.org/area/rtg/trac/wiki</a>). =C2=A0This should allow</div><div>dir=
ectorate reviews to report technical issues that can actually get</div>


<div>fixed early in the process (equivalent of bug reports) as opposed to</=
div><div>just noting the concerns in the drafts (equivalent of release note=
s).</div><div><br></div><div>Second, as was discussed during the recent IES=
G retreat, in addition</div>


<div>to the IETF-wide WG chair training, we intend to have a series of</div=
><div>training sessions for WG Chairs in the Routing Area addressing topics=
</div><div>such as judging consensus, project management, motivating volunt=
eers,</div>


<div>using the datatracker (via a sandbox version that can be played</div><=
div>with safely), and sharing experiences between WG chairs.</div><div><br>=
</div><div>Third, we intend to reorganize the working groups in the Routing=
 area.</div>


<div>We feel that it is important to focus on areas where there is active</=
div><div>interest in standardization and to be open and able to accept new =
work</div><div>into the area. =C2=A0As you know, we have had several new wo=
rking groups</div>


<div>(nvo3, i2rs, sfc, spring) created in the last few years and we need to=
</div><div>be open and able to handle more new work as it comes in. =C2=A0W=
e would</div><div>also like to improve the signal-to-noise ratio experience=
d by</div>


<div>participants in the different working groups and improve the quantity<=
/div><div>and quality of discussion and reviews. =C2=A0It is likely that no=
t all WGs</div><div>in the Routing Area will be directly affected.</div><di=
v>


<br></div><div>Here is the time-line for reorganizing the WGs.</div><div><b=
r></div><div>=C2=A0 =C2=A0NOW: public discussion on <a href=3D"mailto:routi=
ng-discussion@ietf.org" target=3D"_blank">routing-discussion@ietf.org</a> a=
bout how to</div>

<div>=C2=A0 =C2=A0reorganize the working groups to best meet our motivation=
s.</div>
<div>=C2=A0 =C2=A0Additional focused discussions are expected on the</div><=
div>=C2=A0 =C2=A0<a href=3D"mailto:rtg-chairs@ietf.org" target=3D"_blank">r=
tg-chairs@ietf.org</a> and <a href=3D"mailto:rtg-dir@ietf.org" target=3D"_b=
lank">rtg-dir@ietf.org</a> mailing lists.</div>

<div><br>
</div><div>=C2=A0 =C2=A0In Toronto: There will be meetings with the WG chai=
rs and the</div><div>=C2=A0 =C2=A0Routing Directorate to get the ideas desc=
ribed and agreed upon.</div><div><br></div><div>=C2=A0 =C2=A0At the Routing=
 Area Meeting in Toronto: Discuss the set of</div>


<div>=C2=A0 =C2=A0reorganized WGs and general charter content in the Routin=
g Area</div><div>=C2=A0 =C2=A0meeting.</div><div><br></div><div>=C2=A0 =C2=
=A0September 2014: Based upon the feedback, suggestions, and</div><div>=C2=
=A0 =C2=A0discussion, Adrian and I finalize the reorganized WG charters. =
=C2=A0We</div>


<div>=C2=A0 =C2=A0start the internal IESG discussion and public reviews.</d=
iv><div><br></div><div>=C2=A0 =C2=A0October 2014: Formal rechartering proce=
ss completes.</div><div><br></div><div>=C2=A0 =C2=A0In Honolulu: The new se=
t of WGs meet.</div><div>

<br>
</div><div>=C2=A0 =C2=A0After Honolulu: Adrian and I deal with any issues a=
nd charter</div><div>=C2=A0 =C2=A0updates based upon a few months of experi=
ence.</div><div><br></div><div>Here are the motivations that Adrian and I w=
ould like to be considered</div>


<div>when coming up with ideas for how the WGs should be reorganized.</div>=
<div><br></div><div>=C2=A0 =C2=A01) Move towards organizing working groups =
on functional</div><div>=C2=A0 =C2=A0responsibilities rather than scoping t=
hem to specific protocols.</div>


<div><br></div><div>=C2=A0 =C2=A02) Split giant working groups so relevant =
work is done in one place</div><div>=C2=A0 =C2=A0and there is an improved s=
ignal-to-noise ratio for participants who</div><div>=C2=A0 =C2=A0are only i=
nterested in a slice of the current working group&#39;s work.</div>


<div><br></div><div>=C2=A0 =C2=A03) Create synergies for scattered function=
ality (example ideas:</div><div>=C2=A0 =C2=A0OAM, FRR, traffic-engineering)=
</div><div><br></div><div>=C2=A0 =C2=A04) Create a DISPATCH working group f=
or clear new idea discussion;</div>


<div>=C2=A0 =C2=A0rtgwg serves some of this purpose but doesn&#39;t have a =
clear process</div><div>=C2=A0 =C2=A0and isn&#39;t drawing in the new ideas=
.</div><div><br></div><div>=C2=A0 =C2=A05) Focus Routing Area time on desig=
n centers rather than on far</div>


<div>=C2=A0 =C2=A0corner cases.</div><div><br></div><div>=C2=A0 =C2=A06) Ea=
ch working group should have clear, well defined, and achievable goals.</di=
v><div><br></div><div>Noting that the Routing Area has inherited some of it=
s WG structure</div>


<div>from the sub-IP area, it is not a goal to force IP routing and MPLS</d=
iv><div>routing to remain separated.</div><div><br></div><div>The goal of t=
his reorganization is not closing working groups. =C2=A0Adrian</div><div>an=
d Alia are perfectly capable of closing working groups without going</div>


<div>through restructuring.</div><div><br></div><div>For those of you that =
have read this far, thank you. =C2=A0Getting this 80%</div><div>right is go=
ing to take some serious discussion and thought. =C2=A0We all</div><div>wor=
k in the Routing Area together with different perspectives. =C2=A0Please</d=
iv>


<div>think carefully and help us have a highly focused discussion.</div><di=
v><br></div><div>Thanks,</div><div>Alia and Adrian</div><div><br></div></di=
v>
</div><br></div></div>
</div><br></div></div>

--089e013cbe5ef2f11c04fb811be5--


From nobody Tue Jun 10 14:22:07 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4B31A02C7; Tue, 10 Jun 2014 14:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.522
X-Spam-Level: *
X-Spam-Status: No, score=1.522 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 zw3BLi_mTpUE; Tue, 10 Jun 2014 14:21:22 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C39BF1A02C6; Tue, 10 Jun 2014 14:21:21 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id db12so6053079veb.7 for <multiple recipients>; Tue, 10 Jun 2014 14:21:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MIncnq8sQIs7wApfWhyJ1pDH3g44HBtTe1VPntgmmIY=; b=RmQ163Kb1LdwnqbGkLCTHOT5nEJK5pSKnyvSe7gUlIHdaUsfIzYbgNvlAk9qJTuMrm kvMPZJS5K8fot0mmIQTPcLrPuMfUiCc+txP21GjjiqjgB4xy7el0jFXsDkLsB6i25m49 EHelGRsh9+YUfGKdUn1Cg/OtuMvFGgs7uAXLiLI1UQ4hcq9Nv0s9UL9LgU2GZgs9Lz2r 3Wb8hbhync1NgyIC5xgFmmLYFZQy7GN/azrII2s1buskHWEsnavoL5cTV6B2YLSy1M/y UVbXyOBIVEAZolR95qeskC4QFtPiR1uVHHYUp3CfrBbKIlt71foPRIB0r7EcjXgT4mRT DgmA==
MIME-Version: 1.0
X-Received: by 10.221.20.199 with SMTP id qp7mr35108377vcb.24.1402435280720; Tue, 10 Jun 2014 14:21:20 -0700 (PDT)
Received: by 10.221.16.3 with HTTP; Tue, 10 Jun 2014 14:21:20 -0700 (PDT)
In-Reply-To: <CAP+sJUdPsh_DWdzuJK0GFEQhJO3rapK9VryNsV4uavyksDonnQ@mail.gmail.com>
References: <CAP+sJUdPsh_DWdzuJK0GFEQhJO3rapK9VryNsV4uavyksDonnQ@mail.gmail.com>
Date: Wed, 11 Jun 2014 00:21:20 +0300
Message-ID: <CAP+sJUcFC_-mJfTBaR=SZ28LbyzYmEc_WK3hSDsBhsiXqws10g@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11339e2eba82fc04fb81e825
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/nsOk5qDi47U4x5DMQQhg0nmYz6k
X-Mailman-Approved-At: Tue, 10 Jun 2014 14:22:05 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, 6tisch-security@ietf.org, lwip@ietf.org, roll <roll@ietf.org>, ace@ietf.org, dtls-iot@ietf.org, coman@ietf.org, core@ietf.org, 6lo@ietf.org, "6tisch@ietf.org" <6tisch@ietf.org>
Subject: Re: [Roll] LLN Plugfest at IETF 90
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jun 2014 21:21:25 -0000

--001a11339e2eba82fc04fb81e825
Content-Type: text/plain; charset=UTF-8

Dear all,

This is a kindly reminder :-) .

We call for participants. The deadline to receive topics to present or
demonstrate in the event is 06/20/2014 :-). Interested audience is also
welcome and we encourage audience to participate in the feedback session.

More information:
https://bitbucket.org/6tisch/meetings/wiki/140720a_ietf90_toronto_plugfest

We hope to see you there!

Xavier and Ines.


2014-06-02 1:02 GMT+03:00 Ines Robles <mariainesrobles@googlemail.com>:

> Dear all,
>
> We would like to announce the plugfest event at the 90th IETF Meeting in
> Toronto.
>
> We call for participants. The deadline to receive topics to present or
> demonstrate in the event is 06/13/2014. Interested audience is also welcome
> and we encourage audience to participate in the feedback session.
>
> Please find next the plugfest information.
>
> We hope to see you there!
>
> Xavier and Ines.
>
> -----------------------
> Low Power and Lossy Networks plugfest at IETF90
>
> The IETF 6TiSCH <https://datatracker.ietf.org/wg/6tisch/charter/>, IETF
> 6lo <https://datatracker.ietf.org/wg/6lo/charter/> and IETF ROLL
> <https://datatracker.ietf.org/wg/roll/charter/> working groups are
> hosting an informal "plugfest" event at the IETF90 meeting, in Toronto, CA,
> during the week of July 20-25 2014.
> Goals
>
> The goal of this event is to bring together people interested in hands-on
> experience around the technology developed by the 6TiSCH, 6lo and ROLL
> working groups, with a particular focus on the TSCH mode of IEEE802.15.4e,
> 6lowpan, RPL and new WG specifications.
> When and where ?
>
>    - *Date*: Sunday July 20 2014, 0900-1300 EDT.
>    - *Location*: Meeting Room TBD, Fairmont Royal York Hotel 100 Front
>    Street W, Toronto, CA.
>
> *Early access: TBD if the plugfest room will be open starting 8am EDT on
> Sunday 20 2014 to allow people to set up.*
> Topology proposed - TBD
>
>    - Star topology
>    - IPv6
>
> Complementary angles
>
> This event will feature the following complementary angles:
>
>    - Interoperation
>    - Demonstration
>    - Tools
>
> Focus 1: Interoperation
>
> Download the interoperation guidelines:
>
>    - - TBD for Toronto - interoperation guidelines, version 1 (London)
>    <https://bitbucket.org/6tisch/meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_guidelines_v01.pdf>
>
> The goal is to achieve interoperation between different hardware and
> software implementations on the different aspects addressed by 6lo, 6TiSCH
> and ROLL WGs. This include 6TiSCH minimal draft implementation,
> demonstrating TSCH synchronization and OF0 for RPL on a minimal network.
> 6lowpan to demostrate cross link layer inter-operability by means of
> bridges or backbones routers. Storing and non-storing RPL implementation
> including its coexistance in different sub-networks.
>
> The focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH
> drafts implementations, including but not limited to: e.g. - 6TiSCH minimal
> draft: http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00. - TBD
>
> Participants are encouraged to bring devices which implement parts or all
> of the listed drafts.
>
> Levels of interoperation are proposed:
>
>    - *Level 1*, star topology. A single BBR devices acts as the time
>    source neighbor for all other nodes. Nodes need to demonstrate frame-based
>    and acknowledgement-based synchronization. The static TSCH schedule, as
>    well as all slot timings are taken from draft-ietf-6tisch-minimal-00.
>    - *Level 2*, multi-hop topology. This level builds upon level 1. The
>    goal of this level is full compliance to draft-ietf-6tisch-minimal-00,
>    including multi-hop routing (RPL).
>    - *Level 3*, on-the-fly scheduling. [optional] Preliminary
>    implementations of
>    http://tools.ietf.org/html/draft-dujovne-6tisch-on-the-fly can be
>    shown.
>    - *Level 4*, drafts from ROLL, such as:
>    draft-ietf-roll-mpl-parameter-configuration,
>    draft-ko-roll-mix-network-pathology, Opportunistic routing, selective DIS,
>    and others that participants want to show
>    - *Level 5*, drafts from 6lo, such as: draft-ietf-6lo-btle,
>    draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz, and others that participants
>    want to show.
>    - *Level 6* Other drafts, such as
>    draft-thubert-6man-flow-label-for-rpl, etc.
>
> Focus 2: Demonstration
>
> Participants are encouraged to bring devices and technology based on
> 6TiSCH, 6lo and ROLL which they believe can be of interest for the other
> participants. These devices may or may not participate in the
> interoperation event. Demonstration of more complete systems are
> encouraged, for example systems which show the interconnection of a 6TiSCH
> based mesh to traditional networks.
> Focus 3: Tools
>
> Participants are encouraged to bring and present different tools developed
> around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not
> limited to:
>
>    - acquisition devices (i.e. "sniffers")
>    - packet analysis tools (e.g. Wireshark)
>    - simulation/emulation platforms
>
> Important Dates
>
> The preparation of this event will be held during a portion of the
> bi-weekly 6TiSCH call (*To Be Decided how and when!!!*). In particular:
>
>    - *06/02/2014* Announcement of the plugfest event to the WG/ML related
>    with constrained devices, such as: 6tisch, 6lo, roll, core, lwig, dtls-iot,
>    coman, ace, etc.
>    - *06/06/2014* Adoption of the plugfest call by the WGs, and call for
>    participants at each group.
>    - *06/02/2014-06/13/2014* Participants have contacted the plugfest
>    chairs (Xavier or Ines) with a tentative description of what they wish to
>    participate in.
>    - *06/20/2014* Synchronization point 1. Participants can share the
>    state of advancement of the implementation and raise blocking points.
>    - *07/11/2014* Synchronization point 2. Participants can share the
>    state of advancement of the implementation and raise blocking points.
>    - *07/20/2014*. Plugfest at IETF90.
>
> Tentative Agenda from 9:00 to 13:00
>
>    - *[09.00]* Welcome and Initial Instructions
>    - *[09.05]* Participants Pitch (5 min per Participant)
>    - *[09.45]* Participants Pitch Tools (5 min per Participant)
>    - *[10.15]* Interoperation (Islands)
>    - *[11.50]* Feedback and open discussion.
>    - *[12.40]* Acknowledgements and Plugfest End
>
> For More Information
>
>    - *Contact*: Xavi Vilajosana xvilajosana@eecs.berkeley.edu - Ines
>    Robles mariainesrobles@gmail.com
>
> Note Well
>
> This event is organized as part of the IETF90 standardization meeting. You
> need to register to the IETF90 conference to be able to participate. Daily
> passes are available. The IETF Note Well applies to this plugfest, see
> http://www.ietf.org/about/note-well.html.
> About
>
> The IETF 6TiSCH working group standardizes mechanisms focusing on enabling
> IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the
> charter at http://datatracker.ietf.org/wg/6tisch/charter/, which also
> contains links to the mailing list and the Internet-Drafts published by the
> group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is
> open, and is subject to the IETF Note Well.
>
> The IETF 6lo working group focuses on the work that facilitates IPv6
> connectivity over constrained node networks with the characteristics of:
> limited power, memory and processing resources;. You can access the charter
> at https://datatracker.ietf.org/wg/6lo/charter/, which also contains
> links to the mailing list and the I-D published by the group.
>
> The IETF ROLL working group is focused on routing issues for LLN (Low
> Power and Lossy Networks), in IPv6 routing architectural framework for the
> industrial, connected home, building and urban sensor networks application
> scenarios. You can access the charter at
> https://datatracker.ietf.org/wg/roll/charter/, which also contains links
> to the mailing list and the I-D published by the group.
>

--001a11339e2eba82fc04fb81e825
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear all,<div><br></div><div>This is a kindly reminder :-)=
 .</div><div><br></div><div><span style=3D"color:rgb(0,0,0);font-family:ari=
al,helvetica,sans-serif">We call for participants. The deadline to receive =
topics to present or demonstrate in the event is 06/20/2014 :-). Interested=
 audience is also welcome and we encourage audience to participate in the f=
eedback session.</span></div>

<div><span style=3D"color:rgb(0,0,0);font-family:arial,helvetica,sans-serif=
"><br></span></div><div><span style=3D"color:rgb(0,0,0);font-family:arial,h=
elvetica,sans-serif">More information:=C2=A0</span><font color=3D"#000000" =
face=3D"arial, helvetica, sans-serif"><a href=3D"https://bitbucket.org/6tis=
ch/meetings/wiki/140720a_ietf90_toronto_plugfest" target=3D"_blank">https:/=
/bitbucket.org/6tisch/meetings/wiki/140720a_ietf90_toronto_plugfest</a></fo=
nt></div>

<div><br></div><div><span style=3D"color:rgb(0,0,0);font-family:arial,helve=
tica,sans-serif">We hope to see you there!</span><br></div><div><span style=
=3D"color:rgb(0,0,0);font-family:arial,helvetica,sans-serif"><br></span></d=
iv>

<div><font color=3D"#000000" face=3D"arial, helvetica, sans-serif">Xavier a=
nd Ines.</font></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">2014-06-02 1:02 GMT+03:00 Ines  Robles <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mariainesrobles@googlemail.com" target=3D"_blank">mariainesrobl=
es@googlemail.com</a>&gt;</span>:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div><div><span style=3D"font-family:aria=
l,helvetica,sans-serif;color:rgb(0,0,0)">Dear all,</span><br>

</div><font face=3D"arial, helvetica, sans-serif"><br style=3D"color:rgb(0,=
0,0)"><span style=3D"color:rgb(0,0,0)">We would like to announce the plugfe=
st event at the 90th IETF Meeting in Toronto.</span></font><div>

<span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif=
"><br></font></span></div></div><div><span style=3D"color:rgb(0,0,0)"><font=
 face=3D"arial, helvetica, sans-serif">We call for participants. The deadli=
ne to receive topics to present or demonstrate in the event is 06/13/2014. =
Interested audience is also welcome and we encourage audience to participat=
e in the feedback session.</font></span></div>



<div><div><span style=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, =
sans-serif"><br></font></span></div><div><span style=3D"color:rgb(0,0,0)"><=
font face=3D"arial, helvetica, sans-serif">Please find next the plugfest in=
formation.=C2=A0</font></span><div>



<font face=3D"arial, helvetica, sans-serif"><br></font></div><div><span sty=
le=3D"color:rgb(0,0,0)"><font face=3D"arial, helvetica, sans-serif">We hope=
 to see you there!</font></span><div><font color=3D"#000000" face=3D"arial,=
 helvetica, sans-serif"><br>



</font></div><div><div style=3D"color:rgb(0,0,0)"><font face=3D"arial, helv=
etica, sans-serif">Xavier and Ines.</font></div></div></div></div><div styl=
e=3D"font-family:&#39;Times New Roman&#39;;font-size:13px;color:rgb(0,0,0)"=
>


<font size=3D"3"><br>
</font></div><div style=3D"font-family:&#39;Times New Roman&#39;;font-size:=
13px;color:rgb(0,0,0)"><font size=3D"3">-----------------------</font></div=
><div><h1 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-si=
ze:24px;margin:20px 0px 10px;padding:0px;font-weight:normal;line-height:1.2=
5">



Low Power and Lossy Networks plugfest at IETF90</h1><p style=3D"color:rgb(5=
1,51,51);font-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;pa=
dding:0px;word-wrap:break-word;line-height:20px">The=C2=A0<a href=3D"https:=
//datatracker.ietf.org/wg/6tisch/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6TiSCH</a>,=C2=A0<a href=3D"htt=
ps://datatracker.ietf.org/wg/6lo/charter/" style=3D"color:rgb(59,115,175);t=
ext-decoration:none" target=3D"_blank">IETF 6lo</a>=C2=A0and=C2=A0<a href=
=3D"https://datatracker.ietf.org/wg/roll/charter/" style=3D"color:rgb(59,11=
5,175);text-decoration:none" target=3D"_blank">IETF ROLL</a>=C2=A0working g=
roups are hosting an informal &quot;plugfest&quot; event at the IETF90 meet=
ing, in Toronto, CA, during the week of July 20-25 2014.</p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Goals=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">



The goal of this event is to bring together people interested in hands-on e=
xperience around the technology developed by the 6TiSCH, 6lo and ROLL worki=
ng groups, with a particular focus on the TSCH mode of IEEE802.15.4e, 6lowp=
an, RPL and new WG specifications.</p>



<h3 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:18p=
x;margin:20px 0px 0px;padding:0px;line-height:1.3888888888888888;font-weigh=
t:normal">When and where ?</h3><ul style=3D"color:rgb(51,51,51);font-family=
:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word"><strong>Date</strong>: Sunday July 20 20=
14, 0900-1300 EDT.</li><li style=3D"word-wrap:break-word"><strong>Location<=
/strong>: Meeting Room TBD, Fairmont Royal York Hotel 100 Front Street W, T=
oronto, CA.</li>



</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
"><strong>Early access: TBD if the plugfest room will be open starting 8am =
EDT on Sunday 20 2014 to allow people to set up.</strong></p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Topol=
ogy proposed - TBD</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,s=
ans-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word">Star topology</li><li style=3D"word-wrap=
:break-word">IPv6</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Ari=
al,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:no=
rmal;line-height:1.5">



Complementary angles</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,=
sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-w=
ord;line-height:20px">This event will feature the following complementary a=
ngles:</p>



<ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14p=
x;margin:10px 0px 0px;line-height:20px"><li style=3D"word-wrap:break-word">=
Interoperation</li><li style=3D"word-wrap:break-word">Demonstration</li><li=
 style=3D"word-wrap:break-word">



Tools</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-seri=
f;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-he=
ight:1.5">Focus 1: Interoperation</h2>
<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Dow=
nload the interoperation guidelines:</p><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px">



<li style=3D"word-wrap:break-word"><a href=3D"https://bitbucket.org/6tisch/=
meetings/src/master/140306_ietf89_plugfest_london/ietf89_6tisch_interop_gui=
delines_v01.pdf" style=3D"color:rgb(59,115,175);text-decoration:none" targe=
t=3D"_blank"> - TBD for Toronto - interoperation guidelines, version 1 (Lon=
don)</a></li>



</ul><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">The goal is to achieve interoperation between different hardware and soft=
ware implementations on the different aspects addressed by 6lo, 6TiSCH and =
ROLL WGs. This include 6TiSCH minimal draft implementation, demonstrating T=
SCH synchronization and OF0 for RPL on a minimal network. 6lowpan to demost=
rate cross link layer inter-operability by means of bridges or backbones ro=
uters. Storing and non-storing RPL implementation including its coexistance=
 in different sub-networks.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 focus during this event is open to demonstrating 6lo, ROLL or 6TiSCH draft=
s implementations, including but not limited to: e.g. - 6TiSCH minimal draf=
t:=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00"=
 rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-6tisch-minimal-00</a>. =
- TBD</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Par=
ticipants are encouraged to bring devices which implement parts or all of t=
he listed drafts.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">Lev=
els of interoperation are proposed:</p><ul style=3D"color:rgb(51,51,51);fon=
t-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:20=
px">



<li style=3D"word-wrap:break-word"><strong>Level 1</strong>, star topology.=
 A single BBR devices acts as the time source neighbor for all other nodes.=
 Nodes need to demonstrate frame-based and acknowledgement-based synchroniz=
ation. The static TSCH schedule, as well as all slot timings are taken from=
 draft-ietf-6tisch-minimal-00.</li>



<li style=3D"word-wrap:break-word"><strong>Level 2</strong>, multi-hop topo=
logy. This level builds upon level 1. The goal of this level is full compli=
ance to draft-ietf-6tisch-minimal-00, including multi-hop routing (RPL).</l=
i>



<li style=3D"word-wrap:break-word"><strong>Level 3</strong>, on-the-fly sch=
eduling. [optional] Preliminary implementations of=C2=A0<a href=3D"http://t=
ools.ietf.org/html/draft-dujovne-6tisch-on-the-fly" rel=3D"nofollow" style=
=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http://to=
ols.ietf.org/html/draft-dujovne-6tisch-on-the-fly</a>=C2=A0can be shown.</l=
i>



<li style=3D"word-wrap:break-word"><strong>Level 4</strong>, drafts from RO=
LL, such as: draft-ietf-roll-mpl-parameter-configuration, draft-ko-roll-mix=
-network-pathology, Opportunistic routing, selective DIS, and others that p=
articipants want to show</li>



<li style=3D"word-wrap:break-word"><strong>Level 5</strong>, drafts from 6l=
o, such as: draft-ietf-6lo-btle, draft-ietf-6lo-ghc,draft-ietf-6lo-lowpanz,=
 and others that participants want to show.</li><li style=3D"word-wrap:brea=
k-word">



<strong>Level 6</strong>=C2=A0Other drafts, such as draft-thubert-6man-flow=
-label-for-rpl, etc.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:=
Arial,sans-serif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight=
:normal;line-height:1.5">



Focus 2: Demonstration</h2><p style=3D"color:rgb(51,51,51);font-family:Aria=
l,sans-serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break=
-word;line-height:20px">Participants are encouraged to bring devices and te=
chnology based on 6TiSCH, 6lo and ROLL which they believe can be of interes=
t for the other participants. These devices may or may not participate in t=
he interoperation event. Demonstration of more complete systems are encoura=
ged, for example systems which show the interconnection of a 6TiSCH based m=
esh to traditional networks.</p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">Focus=
 3: Tools</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">



Participants are encouraged to bring and present different tools developed =
around 6TiSCH/6lo/ROLL networks. Possible tools include, but are not limite=
d to:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font=
-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word">acquisition devices (i.e. &quot;sniffers=
&quot;)</li><li style=3D"word-wrap:break-word">packet analysis tools (e.g. =
Wireshark)</li><li style=3D"word-wrap:break-word">simulation/emulation plat=
forms</li>



</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Important Dates</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-=
serif;font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;l=
ine-height:20px">



The preparation of this event will be held during a portion of the bi-weekl=
y 6TiSCH call (<strong>To Be Decided how and when!!!</strong>). In particul=
ar:</p><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-s=
ize:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word"><strong>06/02/2014</strong>=C2=A0Announc=
ement of the plugfest event to the WG/ML related with constrained devices, =
such as: 6tisch, 6lo, roll, core, lwig, dtls-iot, coman, ace, etc.</li><li =
style=3D"word-wrap:break-word">



<strong>06/06/2014</strong>=C2=A0Adoption of the plugfest call by the WGs, =
and call for participants at each group.</li><li style=3D"word-wrap:break-w=
ord"><strong>06/02/2014-06/13/2014</strong>=C2=A0Participants have contacte=
d the plugfest chairs (Xavier or Ines) with a tentative description of what=
 they wish to participate in.</li>



<li style=3D"word-wrap:break-word"><strong>06/20/2014</strong>=C2=A0Synchro=
nization point 1. Participants can share the state of advancement of the im=
plementation and raise blocking points.</li><li style=3D"word-wrap:break-wo=
rd">


<strong>07/11/2014</strong>=C2=A0Synchronization point 2. Participants can =
share the state of advancement of the implementation and raise blocking poi=
nts.</li>
<li style=3D"word-wrap:break-word"><strong>07/20/2014</strong>. Plugfest at=
 IETF90.</li></ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-s=
erif;font-size:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line=
-height:1.5">



Tentative Agenda from 9:00 to 13:00</h2><ul style=3D"color:rgb(51,51,51);fo=
nt-family:Arial,sans-serif;font-size:14px;margin:10px 0px 0px;line-height:2=
0px"><li style=3D"word-wrap:break-word"><em>[09.00]</em>=C2=A0Welcome and I=
nitial Instructions</li>



<li style=3D"word-wrap:break-word"><em>[09.05]</em>=C2=A0Participants Pitch=
 (5 min per Participant)</li><li style=3D"word-wrap:break-word"><em>[09.45]=
</em>=C2=A0Participants Pitch Tools (5 min per Participant)</li><li style=
=3D"word-wrap:break-word">



<em>[10.15]</em>=C2=A0Interoperation (Islands)</li><li style=3D"word-wrap:b=
reak-word"><em>[11.50]</em>=C2=A0Feedback and open discussion.</li><li styl=
e=3D"word-wrap:break-word"><em>[12.40]</em>=C2=A0Acknowledgements and Plugf=
est End</li></ul>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">For M=
ore Information</h2><ul style=3D"color:rgb(51,51,51);font-family:Arial,sans=
-serif;font-size:14px;margin:10px 0px 0px;line-height:20px">



<li style=3D"word-wrap:break-word"><strong>Contact</strong>: Xavi Vilajosan=
a=C2=A0<a href=3D"mailto:xvilajosana@eecs.berkeley.edu" style=3D"color:rgb(=
59,115,175);text-decoration:none" target=3D"_blank">xvilajosana@eecs.berkel=
ey.edu</a>=C2=A0- Ines Robles=C2=A0<a href=3D"mailto:mariainesrobles@gmail.=
com" style=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank"=
>mariainesrobles@gmail.com</a></li>



</ul><h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-siz=
e:20px;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">=
Note Well</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;=
font-size:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-he=
ight:20px">



This event is organized as part of the IETF90 standardization meeting. You =
need to register to the IETF90 conference to be able to participate. Daily =
passes are available. The IETF Note Well applies to this plugfest, see=C2=
=A0<a href=3D"http://www.ietf.org/about/note-well.html" rel=3D"nofollow" st=
yle=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">http:/=
/www.ietf.org/about/note-well.html</a>.</p>



<h2 style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:20p=
x;margin:20px 0px 0px;padding:0px;font-weight:normal;line-height:1.5">About=
</h2><p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size=
:14px;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px=
">



The IETF 6TiSCH working group standardizes mechanisms focusing on enabling =
IPv6 over the TSCH mode of the IEEE802.15.4e standard. You can access the c=
harter at=C2=A0<a href=3D"http://datatracker.ietf.org/wg/6tisch/charter/" r=
el=3D"nofollow" style=3D"color:rgb(59,115,175);text-decoration:none" target=
=3D"_blank">http://datatracker.ietf.org/wg/6tisch/charter/</a>, which also =
contains links to the mailing list and the Internet-Drafts published by the=
 group. 6TiSCH holds weekly phone calls on Friday 8am PST. Participation is=
 open, and is subject to the IETF Note Well.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF 6lo working group focuses on the work that facilitates IPv6 connectiv=
ity over constrained node networks with the characteristics of: limited pow=
er, memory and processing resources;. You can access the charter at=C2=A0<a=
 href=3D"https://datatracker.ietf.org/wg/6lo/charter/" rel=3D"nofollow" sty=
le=3D"color:rgb(59,115,175);text-decoration:none" target=3D"_blank">https:/=
/datatracker.ietf.org/wg/6lo/charter/</a>, which also contains links to the=
 mailing list and the I-D published by the group.</p>



<p style=3D"color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px=
;margin:10px 0px 0px;padding:0px;word-wrap:break-word;line-height:20px">The=
 IETF ROLL working group is focused on routing issues for LLN (Low Power an=
d Lossy Networks), in IPv6 routing architectural framework for the industri=
al, connected home, building and urban sensor networks application scenario=
s. You can access the charter at=C2=A0<a href=3D"https://datatracker.ietf.o=
rg/wg/roll/charter/" rel=3D"nofollow" style=3D"color:rgb(59,115,175);text-d=
ecoration:none" target=3D"_blank">https://datatracker.ietf.org/wg/roll/char=
ter/</a>, which also contains links to the mailing list and the I-D publish=
ed by the group.</p>



</div></div></div>
</blockquote></div><br></div></div>

--001a11339e2eba82fc04fb81e825--


From nobody Tue Jun 10 19:01:27 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C17F21A02EF; Tue, 10 Jun 2014 19:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 P9fMqw-2gEpC; Tue, 10 Jun 2014 19:01:18 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 596A41A030B; Tue, 10 Jun 2014 19:01:14 -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
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140611020114.15734.18330.idtracker@ietfa.amsl.com>
Date: Tue, 10 Jun 2014 19:01:14 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/9e0hOnKxRpwsBi-e9e5y4WCW5Vs
Cc: roll@ietf.org
Subject: [Roll] I-D Action: draft-ietf-roll-security-threats-07.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jun 2014 02:01:21 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Routing Over Low power and Lossy networks Working Group of the IETF.

        Title           : A Security Threat Analysis for Routing Protocol for Low-power and lossy networks (RPL)
        Authors         : Tzeta Tsao
                          Roger K. Alexander
                          Mischa Dohler
                          Vanesa Daza
                          Angel Lozano
                          Michael Richardson
	Filename        : draft-ietf-roll-security-threats-07.txt
	Pages           : 40
	Date            : 2014-06-10

Abstract:
   This document presents a security threat analysis for the Routing
   Protocol for Low-power and lossy networks (RPL, ROLL).  The
   development builds upon previous work on routing security and adapts
   the assessments to the issues and constraints specific to low-power
   and lossy networks.  A systematic approach is used in defining and
   evaluating the security threats.  Applicable countermeasures are
   application specific and are addressed in relevant applicability
   statements.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-roll-security-threats/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-roll-security-threats-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-roll-security-threats-07


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 10 19:03:54 2014
Return-Path: <trac+roll@trac.tools.ietf.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF551A02EF for <roll@ietfa.amsl.com>; Tue, 10 Jun 2014 19:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 oZrzD52JsjOX for <roll@ietfa.amsl.com>; Tue, 10 Jun 2014 19:03:50 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 DF4A41A02FB for <roll@ietf.org>; Tue, 10 Jun 2014 19:03:50 -0700 (PDT)
Received: from localhost ([::1]:58504 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1WuXtD-0003XP-Bz; Tue, 10 Jun 2014 19:03:47 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "roll issue tracker" <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: mcr@sandelman.ca, mariainesrobles@gmail.com
X-Trac-Project: roll
Date: Wed, 11 Jun 2014 02:03:47 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/roll/trac/ticket/153#comment:3
Message-ID: <082.f01c18511ca1b5ce3ce760c26fb8ca01@trac.tools.ietf.org>
References: <067.cc7b7ee9b48456369af4633c53403c40@trac.tools.ietf.org>
X-Trac-Ticket-ID: 153
In-Reply-To: <067.cc7b7ee9b48456369af4633c53403c40@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: mcr@sandelman.ca, mariainesrobles@gmail.com, robert.cragie@gridmerge.com, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/HPNWXlCjkbeTaeCQSkHo4XoFypY
Cc: roll@ietf.org
Subject: Re: [Roll] [roll] #153 (security-threats): draft-ietf-roll-security-threats - Add further clarification/information - Section 6
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: roll@ietf.org
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jun 2014 02:03:53 -0000

#153: draft-ietf-roll-security-threats - Add further clarification/information -
Section 6

Changes (by mcr@sandelman.ca):

 * status:  assigned => closed
 * resolution:   => wontfix


-- 
---------------------------------------+-------------------------------
 Reporter:  mariainesrobles@gmail.com  |       Owner:  mcr@sandelman.ca
     Type:  defect                     |      Status:  closed
 Priority:  major                      |   Milestone:
Component:  security-threats           |     Version:
 Severity:  In WG Last Call            |  Resolution:  wontfix
 Keywords:                             |
---------------------------------------+-------------------------------

Ticket URL: <https://svn.tools.ietf.org/wg/roll/trac/ticket/153#comment:3>
roll <http://tools.ietf.org/wg/roll/>


From nobody Tue Jun 10 19:05:15 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D98D1A02EF for <roll@ietfa.amsl.com>; Tue, 10 Jun 2014 19:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_MIME_NO_TEXT=0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 XMwbPsZ_tn_b for <roll@ietfa.amsl.com>; Tue, 10 Jun 2014 19:05:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBC791A0313 for <roll@ietf.org>; Tue, 10 Jun 2014 19:05:11 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6AA0420011; Tue, 10 Jun 2014 22:08:43 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 5BA9F63B0E; Tue, 10 Jun 2014 22:05:08 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4361C63B0B; Tue, 10 Jun 2014 22:05:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: roll@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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-sha1; protocol="application/pgp-signature"
Date: Tue, 10 Jun 2014 22:05:08 -0400
Message-ID: <27411.1402452308@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/0ny9NQjNygqy5SubHKc0ID1vUtI
Subject: [Roll] draft-ietf-roll-security-threats -07 posted
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jun 2014 02:05:13 -0000

--=-=-=


<HAT OFF>
Please have a read.
       http://www.ietf.org/rfcdiff?url1=draft-ietf-roll-security-threats-06&difftype=--html&submit=Go%21&url2=draft-ietf-roll-security-threats-07

If you have some comments on the changes, *PLEASE* contribute text to fix it.
Otherwise, I really think we are done.

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU5e5UYCLcPvd0N1lAQIU5Qf/f6M08Jne7aIM9ev6qYqYeivlETGjmWXO
qqQiqtOCKfdWgqdEdU/P9cLJ0/2yfZBOw9Mf4xrHA439JjBf/1jvG2WSulB7wzOP
Tw36CTJ/WwCG3ftBpOT+FF43xdJH6qjTqmiZ1feE8pozDlOhFIc87XyIHW41qyh0
tiRojkM9D++NL8SZbNJCqsNe9F57v5iUBfLzDe2ovh5AsFjDkUR1VZ4DAcXjsol1
4SVMgcJv1rHOFfYjfNfWkgSz6LlWzQ1vvfTn65MlIv5jPT2q2eWUxgntY722dQVP
NneHb//tKFvc76mLZ6U6ZeOB8oK0WiaUxR1LWvKPa1/VKhGKy5fQiQ==
=6We6
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Jun 15 22:18:43 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D59B71B29FF for <roll@ietfa.amsl.com>; Sun, 15 Jun 2014 22:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 V8QCV1kAmiNb for <roll@ietfa.amsl.com>; Sun, 15 Jun 2014 22:18:39 -0700 (PDT)
Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1B4B1B2A1C for <roll@ietf.org>; Sun, 15 Jun 2014 22:18:39 -0700 (PDT)
Received: by mail-ve0-f169.google.com with SMTP id pa12so5692379veb.0 for <roll@ietf.org>; Sun, 15 Jun 2014 22:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=jYXPqac9xr2AyPVhQb4fXy1rjZsnTFWgAdsau+6moxw=; b=t71NxCGCn2MhP12YaIZoWPUSLZAjnefvsywWpaXy49fo6b/NjQplIYDiHygWR3Zw0n +ljU9N5Jyx1fB1kZ+6zS1Vv+ZsqW4KEwhtjtAqGIhF3cHJ8ooIMD3X4ZrT52jlZWSg21 NIiSQEI0uCRPac7cJGWPyymZ4GiXjxswNRCJWeO4hEVV/9PHvJrsOLyrH1pqjqKYR2mY SMVSDXeIAK/nR38cs+8ed4m+rJo8taPFnJVxEGxMZl6RIY9Tql9qPsxoZgMNUIbyWmR+ KO5R3Y+nN2fpc5L+aCvAPGnPwQHk7tuoqAOxSaUbrdo2z0TF11271cRmTphzJ925VV7U Di0A==
MIME-Version: 1.0
X-Received: by 10.58.243.1 with SMTP id wu1mr1763513vec.27.1402895917710; Sun, 15 Jun 2014 22:18:37 -0700 (PDT)
Received: by 10.220.79.19 with HTTP; Sun, 15 Jun 2014 22:18:37 -0700 (PDT)
Date: Mon, 16 Jun 2014 08:18:37 +0300
Message-ID: <CAP+sJUd3nT+H4vva=LMwC7ZtiOSVhBayU6LHkbOK8r3sfYWkAQ@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: roll <roll@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bacc6dad503fa04fbed28d3
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/_wKxIXINOYEZYAiU8VJRwufS6uM
Cc: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: [Roll] Slides - IETF 90 - available to download
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2014 05:18:41 -0000

--047d7bacc6dad503fa04fbed28d3
Content-Type: text/plain; charset=UTF-8

Hi,

Please find the slides for the meeting in this link, we think it is better
have a single doc with all the slides:

http://www.ietf.org/proceedings/90/slides/slides-90-roll-0.pdf

These slides are not definitive, please let us know if you find something
that should be corrected before the meeting in Toronto.

We will keep you posted about the last version.

Thank you and Kind Regards,

Michael & Ines.

--047d7bacc6dad503fa04fbed28d3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div style>Please find the slides for th=
e meeting in this link, we think it is better have a single doc with all th=
e slides:</div><div style><br></div><div style><a href=3D"http://www.ietf.o=
rg/proceedings/90/slides/slides-90-roll-0.pdf">http://www.ietf.org/proceedi=
ngs/90/slides/slides-90-roll-0.pdf</a><br>

</div><div style><br></div><div style>These slides are not definitive, plea=
se let us know if you find something that should be corrected before the me=
eting in Toronto.</div><div style><br></div><div style>We will keep you pos=
ted about the last version.</div>

<div style><br></div><div style>Thank you and Kind Regards,<br></div><div s=
tyle><br></div><div style>Michael &amp; Ines.</div></div>

--047d7bacc6dad503fa04fbed28d3--


From nobody Tue Jun 17 02:05:09 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D428A1A032B for <roll@ietfa.amsl.com>; Tue, 17 Jun 2014 02:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.023
X-Spam-Level: 
X-Spam-Status: No, score=0.023 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Y0xyM-R-kGnY for <roll@ietfa.amsl.com>; Tue, 17 Jun 2014 02:05:06 -0700 (PDT)
Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4C271A0327 for <roll@ietf.org>; Tue, 17 Jun 2014 02:05:06 -0700 (PDT)
Received: by mail-vc0-f178.google.com with SMTP id ij19so6054060vcb.23 for <roll@ietf.org>; Tue, 17 Jun 2014 02:05:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=6T0QCLfyutyd/2IhKbJ3aFxQRjz8a1VPtOK8KE3qCoU=; b=fSy4ul4/KEA/S2n4OFN3wDhSf4TL32VriLlxnUiCiGNaZGpPpuyj53XinWMPD+GOBH FreLZjG7gu1OzL0arprZNMspZDXHeye3vN8xctkC0dHD+lBJpbBM1j+PqneI/x0ZMiTF xI5n/dRAgWRCRoj9EFuap4X2zx/CDnN54v74iz8Fzi0VrfYJbb+D5yOPhggtwKDeo14N oK+H/9ir9meFkyrM+OMsaLei8YUW+4SEkpoKjK55C5EdUVC1tyZZDM0/9RwPHuo5hk+D 2hrUjjajcNgBVUwzhSbErjnCcP3EWgayR+PaW6NdavpEPyGRMLZvCJ0Kg9MRroqSd2Ga jE0A==
MIME-Version: 1.0
X-Received: by 10.58.236.170 with SMTP id uv10mr6192866vec.31.1402995905913; Tue, 17 Jun 2014 02:05:05 -0700 (PDT)
Received: by 10.220.79.19 with HTTP; Tue, 17 Jun 2014 02:05:05 -0700 (PDT)
Date: Tue, 17 Jun 2014 12:05:05 +0300
Message-ID: <CAP+sJUcEBj5F1b06xjcmBdrH30_4503PdUc3a+YBtTZ65G9pPg@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: roll <roll@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bdc1a9c97ec6604fc047016
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/nP1PNG7x5RAS5BahYYrKvylC6T0
Cc: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: [Roll] I-D Submission Cut-Off --- 07-04-2014
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2014 09:05:08 -0000

--047d7bdc1a9c97ec6604fc047016
Content-Type: text/plain; charset=UTF-8

Hi,

This is a kindly reminder,

*2014-07-04 (Friday):* Internet Draft submission cut-off (for all drafts,
including -00) by UTC 23:59, upload using IETF ID Submission Tool
<https://datatracker.ietf.org/submit/>.

Thanks,

Michael & Ines

--047d7bdc1a9c97ec6604fc047016
Content-Type: text/html; charset=UTF-8

<div dir="ltr"><div><div><div>Hi,<br><br></div>This is a kindly reminder,<br><br><strong>2014-07-04 (Friday):</strong> Internet Draft submission cut-off (for all drafts, including -00) by
              UTC 23:59, upload using <a href="https://datatracker.ietf.org/submit/">IETF ID Submission Tool</a>.<br><br></div>Thanks,<br><br></div>Michael &amp; Ines<br></div>

--047d7bdc1a9c97ec6604fc047016--


From nobody Thu Jun 19 02:18:20 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104A61A00B6; Thu, 19 Jun 2014 02:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 PUuxkkrwhZfg; Thu, 19 Jun 2014 02:18:17 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88FF81A008C; Thu, 19 Jun 2014 02:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2369; q=dns/txt; s=iport; t=1403169497; x=1404379097; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=1aFcbYV/9XACWqqd9HvK2nt3EF9W/2Uvkzw2lXvH9u8=; b=dqkgBB9J4cCDF9zqBZuS3Z20YtuOxgWCKny38GAhYI6/PK0b9VCFM4gE E84Frj77pFqcFqtMjvACyorkDMLVoB///7mTKTI+lX60IsKn6eLgqr5I+ aQc9H9OC01c6o+SBygHi7uZAQAG+i7OgrVfnXcjXAyImbUFTAsspdhk24 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUFACaqolOtJA2M/2dsb2JhbABagw1SWqoVAQIBAQUBkWiHPwGBCxZ1hAMBAQEEAQEBNzQJDgQCAQgRBAEBCxQJBycLFAcBAQUDAgQBEggBiDkNzhUXhWKIQCM4BoMngRYEnAaSFYNCbIFE
X-IronPort-AV: E=Sophos;i="5.01,506,1400025600"; d="scan'208";a="331123194"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP; 19 Jun 2014 09:18:16 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s5J9IGXb025664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 19 Jun 2014 09:18:16 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.126]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Thu, 19 Jun 2014 04:18:16 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6tisch@ietf.org" <6tisch@ietf.org>, roll <roll@ietf.org>
Thread-Topic: New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-00.txt
Thread-Index: AQHPi5y88O696LSvcUm4Be3uzHbJWZt4I5YQgAADaPA=
Date: Thu, 19 Jun 2014 09:18:15 +0000
Deferred-Delivery: Thu, 19 Jun 2014 09:18:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842C43C2B@xmb-rcd-x01.cisco.com>
References: <20140619085905.10564.60750.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD842C43B7E@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD842C43B7E@xmb-rcd-x01.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.52]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/et9EXrLlQLofAI_fyq1Rn5ClQjM
Subject: [Roll] FW: New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-00.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jun 2014 09:18:19 -0000

Dear all;

I published a draft at 6Lo to ask for the changes we discussed in London at=
 the plugfest and the WG meeting.
This particular work discusses the adaptation for 6LowPAN ND and RPL to co-=
operate, allowing in particular a 6LoWPAn node to become a RPL leaf.

Cheers,

Pascal


-----Original Message-----
From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Pascal Thubert (pthube=
rt)
Sent: jeudi 19 juin 2014 11:07
To: 6lo@ietf.org
Subject: [6lo] FW: New Version Notification for draft-thubert-6lo-rfc6775-u=
pdate-reqs-00.txt

Dear all:

Samita suggested that I prepare a draft to discuss proposed updates to 6LoW=
PAN ND (RFC 6775) in the light of work at 6MAN and 6TiSCH.
I put the reference draft together, please read on.=20

Dear chairs:

I'd wish to have a slot in Toronto to introduce the matter if time permits.

Cheers,

Pascal


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
Sent: jeudi 19 juin 2014 10:59
To: Pascal Thubert (pthubert); Pascal Thubert (pthubert)
Subject: New Version Notification for draft-thubert-6lo-rfc6775-update-reqs=
-00.txt


A new version of I-D, draft-thubert-6lo-rfc6775-update-reqs-00.txt
has been successfully submitted by Pascal Thubert and posted to the IETF re=
pository.

Name:		draft-thubert-6lo-rfc6775-update-reqs
Revision:	00
Title:		Requirements for an update to 6LoWPAN ND
Document date:	2014-06-19
Group:		Individual Submission
Pages:		11
URL:            http://www.ietf.org/internet-drafts/draft-thubert-6lo-rfc67=
75-update-reqs-00.txt
Status:         https://datatracker.ietf.org/doc/draft-thubert-6lo-rfc6775-=
update-reqs/
Htmlized:       http://tools.ietf.org/html/draft-thubert-6lo-rfc6775-update=
-reqs-00


Abstract:
   Work presented at the 6TiSCH and 6MAN working groups suggest a number
   of enhancements to the 6LoWPAN ND mechanism.  This document
   elaborates on such requirements.

                                                                           =
      =20


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

The IETF Secretariat

_______________________________________________
6lo mailing list
6lo@ietf.org
https://www.ietf.org/mailman/listinfo/6lo


From nobody Fri Jun 20 11:42:16 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0786F1A02BA; Fri, 20 Jun 2014 11:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.777
X-Spam-Level: 
X-Spam-Status: No, score=0.777 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FRT_BELOW2=2.154, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 1XpLZXu-lJvP; Fri, 20 Jun 2014 11:42:11 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C893F1A0291; Fri, 20 Jun 2014 11:42:10 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id hy4so3764872vcb.6 for <multiple recipients>; Fri, 20 Jun 2014 11:42:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=JkTNSEvIXYaNlXRRFTMvzcLMlTtK+VEPTg0MPASExEk=; b=tPLH6JOsmx2SIIsFp6cRdXs3kq+AyrUn9XORABk7GWW8KY4IkZ44OReZktz68INkSv 9svSz/XP9z1yvkvjLTwhpfgpBIExccD047kFH6hppA6EfrCf0J2iurf2Zg5UJDV+lR8L IWjtXrTsEUh3aZ6iuGAvDYlA6N5tJpZ87HSQrXW8rTM6VVetLsoS2GyLZjxCIWO9w53S NV7z/8aOwGp2ZdhIlxwhOt/XzCk3Emg6ljD13ncSjxjsK+vP30eO1AVJIDpoGA/qUQ7e wm94U+AeOL8JSO3PKJkwkcAUUpuNAvmoZuL6izhtFj7mr3VB58F9uj6D1bfOQpQvQK8/ hgeQ==
MIME-Version: 1.0
X-Received: by 10.220.94.146 with SMTP id z18mr2234075vcm.40.1403289729900; Fri, 20 Jun 2014 11:42:09 -0700 (PDT)
Received: by 10.220.79.19 with HTTP; Fri, 20 Jun 2014 11:42:09 -0700 (PDT)
Date: Fri, 20 Jun 2014 21:42:09 +0300
Message-ID: <CAP+sJUfN+ktQrnEtV8tfA7Hsxi4ae_DGZ2YpD6P23rd94SK7Rw@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: "6tisch@ietf.org" <6tisch@ietf.org>, 6lo@ietf.org, roll <roll@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c1e9d0de261d04fc48d927
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/D4xWttB8fC9ysUloELwdDENOQTc
Subject: [Roll] Link to Minute of Plugfest IETF 90
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2014 18:42:12 -0000

--001a11c1e9d0de261d04fc48d927
Content-Type: text/plain; charset=UTF-8

Dear all,

Please find bellow the link to the minute of the meeting today about the
plugfest IETF 90.

https://bitbucket.org/6tisch/meetings/wiki/140620_webex_plugfest

Please any comments are very welcome.

Cheers,

Xavier and Ines.

--001a11c1e9d0de261d04fc48d927
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear all,<div><br></div><div>Please find bellow the link t=
o the minute of the meeting today about the plugfest IETF 90.</div><div><br=
></div><div><a href=3D"https://bitbucket.org/6tisch/meetings/wiki/140620_we=
bex_plugfest">https://bitbucket.org/6tisch/meetings/wiki/140620_webex_plugf=
est</a><br>
</div><div><br></div><div>Please any comments are very welcome.</div><div><=
br></div><div>Cheers,</div><div><br></div><div>Xavier and Ines.</div></div>

--001a11c1e9d0de261d04fc48d927--


From nobody Mon Jun 23 13:09:02 2014
Return-Path: <cabo@tzi.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4AB71B2C01; Mon, 23 Jun 2014 13:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 s5FxYKaX46Ib; Mon, 23 Jun 2014 13:08:52 -0700 (PDT)
Received: from 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 C35481B2C1F; Mon, 23 Jun 2014 13:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s5NK8mX3011258; Mon, 23 Jun 2014 22:08:48 +0200 (CEST)
Received: from [192.168.217.145] (p54891060.dip0.t-ipconnect.de [84.137.16.96]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E6AD115A1; Mon, 23 Jun 2014 22:08:47 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 23 Jun 2014 22:08:46 +0200
X-Mao-Original-Outgoing-Id: 425246857.799132-8d342d9386cf261c93e883303d18d67f
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B2BA53C-BCEE-4CD5-B6A2-566CCD95E351@tzi.org>
References: <63722FD9-BA11-48E6-951A-7A3823F5EFD5@tzi.org>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, 6tisch@ietf.org
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/4TyULUOGCMi-efe0BIp3C_CIoms
Subject: [Roll] Fwd: Constrained Node/Network Cluster @ IETF90, early draft version
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 20:08:53 -0000

Sorry for the separate message, but there are too many WGs in this =
cluster now for a single cross posting...

Begin forwarded message:

> From: Carsten Bormann <cabo@tzi.org>
> Subject: Constrained Node/Network Cluster @ IETF90, early draft =
version
> Date: 23 Jun 2014 22:05:54 +0200
> To: dtls-iot@ietf.org, core <core@ietf.org>, ace@ietf.org, =
"6lo@ietf.org WG" <6lo@ietf.org>, lwip@ietf.org
>=20
> A first draft version of the IETF90 agenda is out.
> ** THIS IS GOING TO CHANGE ** for conflict resolution,
> so please don't make travel arrangements based on it.
>=20
> Here is my usual eclectic condensed agenda built from that. =20
> The Constrained Node/Network group meetings are nicely spread out over =
the week.
>=20
> All times are EDT (UTC-0400) (use =
https://datatracker.ietf.org/meeting/agenda-utc and press the button to =
get your local time in case you want to listen in from remote).
>=20
> Gr=FC=DFe, Carsten
>=20
>=20
> MONDAY, July 21, 2014
>=20
> 0900-1130  Morning Session I
> Ontario 	APP	appsawg	Applications Area Working Group WG - =
Combined with APPAREA
> Canadian	OPS	v6ops	IPv6 Operations WG
>=20
> 1300-1500  Afternoon Session I
> Ontario 	APP	httpbis	Hypertext Transfer Protocol WG
> Ballroom	INT	intarea	Internet Area Working Group WG
> Salon A 	SEC	jose	Javascript Object Signing and Encryption =
WG
>=20
> 1520-1650  Afternoon Session II
> Territories	INT ***	6tisch	IPv6 over the TSCH mode of IEEE =
802.15.4e WG
> Ontario 	SEC	tls	Transport Layer Security WG
> Ballroom	TSV	taps	Transport Services WG
>=20
> TUESDAY, July 22, 2014
>=20
> 0900-1130  Morning Session I
> Ontario 	APP	uta	Using TLS in Applications WG
> Territories	TSV	tsvwg	Transport Area Working Group WG
>=20
> 1300-1400  Afternoon Session I
> Ontario 	INT ***	lwig	Light-Weight Implementation Guidance WG
> Canadian	TSV	tsvwg	Transport Area Working Group WG
>=20
> 1420-1620  Afternoon Session II
> Territories	APP	httpbis	Hypertext Transfer Protocol WG
> Ontario 	OPS	v6ops	IPv6 Operations WG
>=20
> 1640-1840  Afternoon Session III
> Tudor 7/8	RTG ***	roll	Routing Over Low power and Lossy =
networks WG
>=20
> WEDNESDAY, July 23, 2014
>=20
> 0900-1130  Morning Session I
> Tudor 7/8	SEC ***	ace	Authentication and Authorization for =
Constrained Environments WG
>=20
> 1300-1500  Afternoon Session I
> Ballroom	OPS	ucan	Use Cases for Autonomic Networking BOF
> Tudor 7/8	TSV	tcpinc	TCP Increased Security WG
>=20
> 1520-1650  Afternoon Session II
> Territories	APP ***	core	Constrained RESTful Environments WG
>=20
> THURSDAY, July 24, 2014
>=20
> 0900-1130  Morning Session I
> Tudor 7/8	INT ***	6lo	IPv6 over Networks of =
Resource-constrained Nodes WG
> Salon B 	SEC	httpauth	Hypertext Transfer Protocol =
Authentication WG - 1000-1130
>=20
> 1300-1500  Afternoon Session I
> Canadian	SEC	saag	Security Area Open Meeting
> Ballroom	TSV	rmcat	RTP Media Congestion Avoidance =
Techniques WG
>=20
> 1520-1720  Afternoon Session II
> Canadian	INT	dnssd	Extensions for Scalable DNS Service =
Discovery  WG
> Salon A 	OPS	eman	Energy Management WG
> Ontario 	RTG	rtgarea	Routing Area Open Meeting
> Manitoba	SEC	oauth	Web Authorization Protocol WG
>=20
> 1730-1830  Afternoon Session III
> Salon B 	APP ***	core	Constrained RESTful Environments WG
> Ontario 	SEC	tls	Transport Layer Security WG
> Ballroom	TSV	rmcat	RTP Media Congestion Avoidance =
Techniques WG
>=20
> FRIDAY, July 25, 2014
>=20
> 0900-1130  Morning Session I
> Canadian	INT	homenet	Home Networking WG
>=20
> 1150-1320  Afternoon Session I
> Salon B 	SEC ***	dice	DTLS In Constrained Environments WG
>=20
>=20
>=20
>=20


From nobody Mon Jun 23 13:22:09 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2373A1B2BD0; Mon, 23 Jun 2014 13:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 7Wh5cje82BXJ; Mon, 23 Jun 2014 13:22:05 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2EFB1A0308; Mon, 23 Jun 2014 13:22:04 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id db11so6466821veb.26 for <multiple recipients>; Mon, 23 Jun 2014 13:22:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XomSv2zmMDWxFhJU8L7rTtIN2hvP5x9pTyR+G39EFYs=; b=leT0EljwW9SmYybwuPt9QdB9gIgah974gLr8xB+3hqb6b3x3hT+FvIyIECp67EDjx0 cNgRhKEsBOdsjw0zsB99kGfC9qESpRjtogJi7XlypiHrJRT4MqD2b4ak7Ey2I+vILDHn hndFQN6tpqv81gAwWReod4Jr4N841oeDEdKDhq4Ec23HFCSkvXKZ9m5Qou2hHH3kCOqA +L0xlmnz77SZt5Bx1EN0TaS4t/AeuEVuG8EROcBLUmArAxlYQtKlm2nrz/TifOlyxOCo Xcv25dNP+pOXtu906hWTe8id87Z1JSrH5Qa0ue3xSEWK+7FWQeKmthnN24VtCNxKc8dr dP0A==
MIME-Version: 1.0
X-Received: by 10.52.252.226 with SMTP id zv2mr17767652vdc.19.1403554923997; Mon, 23 Jun 2014 13:22:03 -0700 (PDT)
Received: by 10.220.79.19 with HTTP; Mon, 23 Jun 2014 13:22:03 -0700 (PDT)
In-Reply-To: <4B2BA53C-BCEE-4CD5-B6A2-566CCD95E351@tzi.org>
References: <63722FD9-BA11-48E6-951A-7A3823F5EFD5@tzi.org> <4B2BA53C-BCEE-4CD5-B6A2-566CCD95E351@tzi.org>
Date: Mon, 23 Jun 2014 23:22:03 +0300
Message-ID: <CAP+sJUfUbob1jLtzMySCOeTQqKpZdX=Vn0bXK_ZWqs4-NTsfKQ@mail.gmail.com>
From: Ines  Robles <mariainesrobles@googlemail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=001a1135ed22ab0f6204fc86987a
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/s3oAg2Twjo7k3IWAlIW4g9ZYdF4
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] Fwd: Constrained Node/Network Cluster @ IETF90, early draft version
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 20:22:07 -0000

--001a1135ed22ab0f6204fc86987a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thank you very much Carsten for the agenda.

Best,


2014-06-23 23:08 GMT+03:00 Carsten Bormann <cabo@tzi.org>:

> Sorry for the separate message, but there are too many WGs in this cluste=
r
> now for a single cross posting...
>
> Begin forwarded message:
>
> > From: Carsten Bormann <cabo@tzi.org>
> > Subject: Constrained Node/Network Cluster @ IETF90, early draft version
> > Date: 23 Jun 2014 22:05:54 +0200
> > To: dtls-iot@ietf.org, core <core@ietf.org>, ace@ietf.org, "6lo@ietf.or=
g
> WG" <6lo@ietf.org>, lwip@ietf.org
> >
> > A first draft version of the IETF90 agenda is out.
> > ** THIS IS GOING TO CHANGE ** for conflict resolution,
> > so please don't make travel arrangements based on it.
> >
> > Here is my usual eclectic condensed agenda built from that.
> > The Constrained Node/Network group meetings are nicely spread out over
> the week.
> >
> > All times are EDT (UTC-0400) (use
> https://datatracker.ietf.org/meeting/agenda-utc and press the button to
> get your local time in case you want to listen in from remote).
> >
> > Gr=C3=BC=C3=9Fe, Carsten
> >
> >
> > MONDAY, July 21, 2014
> >
> > 0900-1130  Morning Session I
> > Ontario       APP     appsawg Applications Area Working Group WG -
> Combined with APPAREA
> > Canadian      OPS     v6ops   IPv6 Operations WG
> >
> > 1300-1500  Afternoon Session I
> > Ontario       APP     httpbis Hypertext Transfer Protocol WG
> > Ballroom      INT     intarea Internet Area Working Group WG
> > Salon A       SEC     jose    Javascript Object Signing and Encryption =
WG
> >
> > 1520-1650  Afternoon Session II
> > Territories   INT *** 6tisch  IPv6 over the TSCH mode of IEEE 802.15.4e
> WG
> > Ontario       SEC     tls     Transport Layer Security WG
> > Ballroom      TSV     taps    Transport Services WG
> >
> > TUESDAY, July 22, 2014
> >
> > 0900-1130  Morning Session I
> > Ontario       APP     uta     Using TLS in Applications WG
> > Territories   TSV     tsvwg   Transport Area Working Group WG
> >
> > 1300-1400  Afternoon Session I
> > Ontario       INT *** lwig    Light-Weight Implementation Guidance WG
> > Canadian      TSV     tsvwg   Transport Area Working Group WG
> >
> > 1420-1620  Afternoon Session II
> > Territories   APP     httpbis Hypertext Transfer Protocol WG
> > Ontario       OPS     v6ops   IPv6 Operations WG
> >
> > 1640-1840  Afternoon Session III
> > Tudor 7/8     RTG *** roll    Routing Over Low power and Lossy networks
> WG
> >
> > WEDNESDAY, July 23, 2014
> >
> > 0900-1130  Morning Session I
> > Tudor 7/8     SEC *** ace     Authentication and Authorization for
> Constrained Environments WG
> >
> > 1300-1500  Afternoon Session I
> > Ballroom      OPS     ucan    Use Cases for Autonomic Networking BOF
> > Tudor 7/8     TSV     tcpinc  TCP Increased Security WG
> >
> > 1520-1650  Afternoon Session II
> > Territories   APP *** core    Constrained RESTful Environments WG
> >
> > THURSDAY, July 24, 2014
> >
> > 0900-1130  Morning Session I
> > Tudor 7/8     INT *** 6lo     IPv6 over Networks of Resource-constraine=
d
> Nodes WG
> > Salon B       SEC     httpauth        Hypertext Transfer Protocol
> Authentication WG - 1000-1130
> >
> > 1300-1500  Afternoon Session I
> > Canadian      SEC     saag    Security Area Open Meeting
> > Ballroom      TSV     rmcat   RTP Media Congestion Avoidance Techniques
> WG
> >
> > 1520-1720  Afternoon Session II
> > Canadian      INT     dnssd   Extensions for Scalable DNS Service
> Discovery  WG
> > Salon A       OPS     eman    Energy Management WG
> > Ontario       RTG     rtgarea Routing Area Open Meeting
> > Manitoba      SEC     oauth   Web Authorization Protocol WG
> >
> > 1730-1830  Afternoon Session III
> > Salon B       APP *** core    Constrained RESTful Environments WG
> > Ontario       SEC     tls     Transport Layer Security WG
> > Ballroom      TSV     rmcat   RTP Media Congestion Avoidance Techniques
> WG
> >
> > FRIDAY, July 25, 2014
> >
> > 0900-1130  Morning Session I
> > Canadian      INT     homenet Home Networking WG
> >
> > 1150-1320  Afternoon Session I
> > Salon B       SEC *** dice    DTLS In Constrained Environments WG
> >
> >
> >
> >
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

--001a1135ed22ab0f6204fc86987a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you very much Carsten for the agenda.<div><br></div>=
<div>Best,<br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote"=
>2014-06-23 23:08 GMT+03:00 Carsten Bormann <span dir=3D"ltr">&lt;<a href=
=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Sorry for the separate message, but there ar=
e too many WGs in this cluster now for a single cross posting...<br>
<br>
Begin forwarded message:<br>
<br>
&gt; From: Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tzi.org=
</a>&gt;<br>
&gt; Subject: Constrained Node/Network Cluster @ IETF90, early draft versio=
n<br>
&gt; Date: 23 Jun 2014 22:05:54 +0200<br>
&gt; To: <a href=3D"mailto:dtls-iot@ietf.org">dtls-iot@ietf.org</a>, core &=
lt;<a href=3D"mailto:core@ietf.org">core@ietf.org</a>&gt;, <a href=3D"mailt=
o:ace@ietf.org">ace@ietf.org</a>, &quot;<a href=3D"mailto:6lo@ietf.org">6lo=
@ietf.org</a> WG&quot; &lt;<a href=3D"mailto:6lo@ietf.org">6lo@ietf.org</a>=
&gt;, <a href=3D"mailto:lwip@ietf.org">lwip@ietf.org</a><br>

&gt;<br>
&gt; A first draft version of the IETF90 agenda is out.<br>
&gt; ** THIS IS GOING TO CHANGE ** for conflict resolution,<br>
&gt; so please don&#39;t make travel arrangements based on it.<br>
&gt;<br>
&gt; Here is my usual eclectic condensed agenda built from that.<br>
&gt; The Constrained Node/Network group meetings are nicely spread out over=
 the week.<br>
&gt;<br>
&gt; All times are EDT (UTC-0400) (use <a href=3D"https://datatracker.ietf.=
org/meeting/agenda-utc" target=3D"_blank">https://datatracker.ietf.org/meet=
ing/agenda-utc</a> and press the button to get your local time in case you =
want to listen in from remote).<br>

&gt;<br>
&gt; Gr=C3=BC=C3=9Fe, Carsten<br>
&gt;<br>
&gt;<br>
&gt; MONDAY, July 21, 2014<br>
&gt;<br>
&gt; 0900-1130 =C2=A0Morning Session I<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 APP =C2=A0 =C2=A0 appsawg Applications Ar=
ea Working Group WG - Combined with APPAREA<br>
&gt; Canadian =C2=A0 =C2=A0 =C2=A0OPS =C2=A0 =C2=A0 v6ops =C2=A0 IPv6 Opera=
tions WG<br>
&gt;<br>
&gt; 1300-1500 =C2=A0Afternoon Session I<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 APP =C2=A0 =C2=A0 httpbis Hypertext Trans=
fer Protocol WG<br>
&gt; Ballroom =C2=A0 =C2=A0 =C2=A0INT =C2=A0 =C2=A0 intarea Internet Area W=
orking Group WG<br>
&gt; Salon A =C2=A0 =C2=A0 =C2=A0 SEC =C2=A0 =C2=A0 jose =C2=A0 =C2=A0Javas=
cript Object Signing and Encryption WG<br>
&gt;<br>
&gt; 1520-1650 =C2=A0Afternoon Session II<br>
&gt; Territories =C2=A0 INT *** 6tisch =C2=A0IPv6 over the TSCH mode of IEE=
E 802.15.4e WG<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 SEC =C2=A0 =C2=A0 tls =C2=A0 =C2=A0 Trans=
port Layer Security WG<br>
&gt; Ballroom =C2=A0 =C2=A0 =C2=A0TSV =C2=A0 =C2=A0 taps =C2=A0 =C2=A0Trans=
port Services WG<br>
&gt;<br>
&gt; TUESDAY, July 22, 2014<br>
&gt;<br>
&gt; 0900-1130 =C2=A0Morning Session I<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 APP =C2=A0 =C2=A0 uta =C2=A0 =C2=A0 Using=
 TLS in Applications WG<br>
&gt; Territories =C2=A0 TSV =C2=A0 =C2=A0 tsvwg =C2=A0 Transport Area Worki=
ng Group WG<br>
&gt;<br>
&gt; 1300-1400 =C2=A0Afternoon Session I<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 INT *** lwig =C2=A0 =C2=A0Light-Weight Im=
plementation Guidance WG<br>
&gt; Canadian =C2=A0 =C2=A0 =C2=A0TSV =C2=A0 =C2=A0 tsvwg =C2=A0 Transport =
Area Working Group WG<br>
&gt;<br>
&gt; 1420-1620 =C2=A0Afternoon Session II<br>
&gt; Territories =C2=A0 APP =C2=A0 =C2=A0 httpbis Hypertext Transfer Protoc=
ol WG<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 OPS =C2=A0 =C2=A0 v6ops =C2=A0 IPv6 Opera=
tions WG<br>
&gt;<br>
&gt; 1640-1840 =C2=A0Afternoon Session III<br>
&gt; Tudor 7/8 =C2=A0 =C2=A0 RTG *** roll =C2=A0 =C2=A0Routing Over Low pow=
er and Lossy networks WG<br>
&gt;<br>
&gt; WEDNESDAY, July 23, 2014<br>
&gt;<br>
&gt; 0900-1130 =C2=A0Morning Session I<br>
&gt; Tudor 7/8 =C2=A0 =C2=A0 SEC *** ace =C2=A0 =C2=A0 Authentication and A=
uthorization for Constrained Environments WG<br>
&gt;<br>
&gt; 1300-1500 =C2=A0Afternoon Session I<br>
&gt; Ballroom =C2=A0 =C2=A0 =C2=A0OPS =C2=A0 =C2=A0 ucan =C2=A0 =C2=A0Use C=
ases for Autonomic Networking BOF<br>
&gt; Tudor 7/8 =C2=A0 =C2=A0 TSV =C2=A0 =C2=A0 tcpinc =C2=A0TCP Increased S=
ecurity WG<br>
&gt;<br>
&gt; 1520-1650 =C2=A0Afternoon Session II<br>
&gt; Territories =C2=A0 APP *** core =C2=A0 =C2=A0Constrained RESTful Envir=
onments WG<br>
&gt;<br>
&gt; THURSDAY, July 24, 2014<br>
&gt;<br>
&gt; 0900-1130 =C2=A0Morning Session I<br>
&gt; Tudor 7/8 =C2=A0 =C2=A0 INT *** 6lo =C2=A0 =C2=A0 IPv6 over Networks o=
f Resource-constrained Nodes WG<br>
&gt; Salon B =C2=A0 =C2=A0 =C2=A0 SEC =C2=A0 =C2=A0 httpauth =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Hypertext Transfer Protocol Authentication WG - 1000-1130<br>
&gt;<br>
&gt; 1300-1500 =C2=A0Afternoon Session I<br>
&gt; Canadian =C2=A0 =C2=A0 =C2=A0SEC =C2=A0 =C2=A0 saag =C2=A0 =C2=A0Secur=
ity Area Open Meeting<br>
&gt; Ballroom =C2=A0 =C2=A0 =C2=A0TSV =C2=A0 =C2=A0 rmcat =C2=A0 RTP Media =
Congestion Avoidance Techniques WG<br>
&gt;<br>
&gt; 1520-1720 =C2=A0Afternoon Session II<br>
&gt; Canadian =C2=A0 =C2=A0 =C2=A0INT =C2=A0 =C2=A0 dnssd =C2=A0 Extensions=
 for Scalable DNS Service Discovery =C2=A0WG<br>
&gt; Salon A =C2=A0 =C2=A0 =C2=A0 OPS =C2=A0 =C2=A0 eman =C2=A0 =C2=A0Energ=
y Management WG<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 RTG =C2=A0 =C2=A0 rtgarea Routing Area Op=
en Meeting<br>
&gt; Manitoba =C2=A0 =C2=A0 =C2=A0SEC =C2=A0 =C2=A0 oauth =C2=A0 Web Author=
ization Protocol WG<br>
&gt;<br>
&gt; 1730-1830 =C2=A0Afternoon Session III<br>
&gt; Salon B =C2=A0 =C2=A0 =C2=A0 APP *** core =C2=A0 =C2=A0Constrained RES=
Tful Environments WG<br>
&gt; Ontario =C2=A0 =C2=A0 =C2=A0 SEC =C2=A0 =C2=A0 tls =C2=A0 =C2=A0 Trans=
port Layer Security WG<br>
&gt; Ballroom =C2=A0 =C2=A0 =C2=A0TSV =C2=A0 =C2=A0 rmcat =C2=A0 RTP Media =
Congestion Avoidance Techniques WG<br>
&gt;<br>
&gt; FRIDAY, July 25, 2014<br>
&gt;<br>
&gt; 0900-1130 =C2=A0Morning Session I<br>
&gt; Canadian =C2=A0 =C2=A0 =C2=A0INT =C2=A0 =C2=A0 homenet Home Networking=
 WG<br>
&gt;<br>
&gt; 1150-1320 =C2=A0Afternoon Session I<br>
&gt; Salon B =C2=A0 =C2=A0 =C2=A0 SEC *** dice =C2=A0 =C2=A0DTLS In Constra=
ined Environments WG<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><br>
</blockquote></div><br></div></div></div>

--001a1135ed22ab0f6204fc86987a--


From nobody Tue Jun 24 23:15:15 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 502281B2AE0; Tue, 24 Jun 2014 23:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ZW0ZOvllGLhl; Tue, 24 Jun 2014 23:15:12 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CFC71B2ADE; Tue, 24 Jun 2014 23:15:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3564; q=dns/txt; s=iport; t=1403676912; x=1404886512; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Xs5AiIY1AegBCxRhp2ztzNoZbFytv+voSJW5NOmT0+I=; b=efwfxhZfAjzAaP6tcjc+MwhS/Zv0SdJ9p289ZQgWj16PeCqM2hPC+gG6 X112cteX1xTBsHTF22emvg2keuOEnOjPuNqBZDOuRcZoN3jSJ5t3l/to2 WA7N3/16QsyAg0KEZ68qztN0D44KRpeCYgg+qTkLBYfY/+DZ+e4EqKSsh U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIFADVoqlOtJA2B/2dsb2JhbABQCoMNUlqqSgUBkXqHQAGBEhZ1hAMBAQEEAQEBNzQJAgwEAgEIEQEDAQELFAkHJwsUAwQBAQUDAgQOBQgBiDkNyEkXhWOIPSsxBwaDJ4EWBZY9hVqSJYNCbIFE
X-IronPort-AV: E=Sophos;i="5.01,543,1400025600"; d="scan'208";a="55729722"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-6.cisco.com with ESMTP; 25 Jun 2014 06:15:11 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s5P6FBmw005105 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Jun 2014 06:15:11 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.12]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Wed, 25 Jun 2014 01:15:11 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-00.txt
Thread-Index: AQHPi5y88O696LSvcUm4Be3uzHbJWZt4I5YQgAddbDCAAd+NEA==
Date: Wed, 25 Jun 2014 06:15:10 +0000
Deferred-Delivery: Wed, 25 Jun 2014 06:15:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842C52B6A@xmb-rcd-x01.cisco.com>
References: <20140619085905.10564.60750.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD842C43B7E@xmb-rcd-x01.cisco.com> <ECA43DA70480A3498E43C3471FB2E1F01C1EBD71@eusaamb103.ericsson.se>
In-Reply-To: <ECA43DA70480A3498E43C3471FB2E1F01C1EBD71@eusaamb103.ericsson.se>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.205.235]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/x6imXl_0-pVswk6aeLlM8AlByhw
Cc: roll <roll@ietf.org>
Subject: [Roll] FW: New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-00.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 06:15:14 -0000

Dear all:

This work is an important step for 6TiSCH (and probably ROLL) and I do enco=
urage you to participate to the thread on the 6lo mailing list.

Abstract:
   "Work presented at the 6TiSCH and 6MAN working groups suggest a number
   of enhancements to the 6LoWPAN ND mechanism.  This document
   elaborates on such requirements."

As you know, 6TiSCH is only chartered to define the architecture that ties =
RPL, 6LoWPAN and other IETF protocols together.
At some point, we identify issues and need to go to the relevant groups and=
 trigger the incremental standardization work.

This particular draft lists the issues that we have found and the requireme=
nts we have discussed in order to get a 6LoWPAN ND node act as a RPL leaf.

We need activity and support on these requirements to trigger work at 6lo (=
and eventually ROLL) to perform the necessary adaptations.

Cheers,

Pascal


-----Original Message-----
From: Samita Chakrabarti [mailto:samita.chakrabarti@ericsson.com]=20
Sent: mardi 24 juin 2014 03:34
To: Pascal Thubert (pthubert); 6lo@ietf.org
Subject: RE: New Version Notification for draft-thubert-6lo-rfc6775-update-=
reqs-00.txt


Thank you Pascal for putting together this draft.

I'll read and provide comments if any. I'll encourage the WG to please read=
 this draft and comment/add any more ideas/suggestions  that you might have=
 experienced with RFC 6775 implementations or usage scenarios.

Thanks,
-Samita

-----Original Message-----
From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Pascal Thubert (pthube=
rt)
Sent: Thursday, June 19, 2014 2:07 AM
To: 6lo@ietf.org
Subject: [6lo] FW: New Version Notification for draft-thubert-6lo-rfc6775-u=
pdate-reqs-00.txt

Dear all:

Samita suggested that I prepare a draft to discuss proposed updates to 6LoW=
PAN ND (RFC 6775) in the light of work at 6MAN and 6TiSCH.
I put the reference draft together, please read on.=20

Dear chairs:

I'd wish to have a slot in Toronto to introduce the matter if time permits.

Cheers,

Pascal


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
Sent: jeudi 19 juin 2014 10:59
To: Pascal Thubert (pthubert); Pascal Thubert (pthubert)
Subject: New Version Notification for draft-thubert-6lo-rfc6775-update-reqs=
-00.txt


A new version of I-D, draft-thubert-6lo-rfc6775-update-reqs-00.txt
has been successfully submitted by Pascal Thubert and posted to the IETF re=
pository.

Name:		draft-thubert-6lo-rfc6775-update-reqs
Revision:	00
Title:		Requirements for an update to 6LoWPAN ND
Document date:	2014-06-19
Group:		Individual Submission
Pages:		11
URL:            http://www.ietf.org/internet-drafts/draft-thubert-6lo-rfc67=
75-update-reqs-00.txt
Status:         https://datatracker.ietf.org/doc/draft-thubert-6lo-rfc6775-=
update-reqs/
Htmlized:       http://tools.ietf.org/html/draft-thubert-6lo-rfc6775-update=
-reqs-00


Abstract:
   Work presented at the 6TiSCH and 6MAN working groups suggest a number
   of enhancements to the 6LoWPAN ND mechanism.  This document
   elaborates on such requirements.

                                                                           =
      =20


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

The IETF Secretariat

_______________________________________________
6lo mailing list
6lo@ietf.org
https://www.ietf.org/mailman/listinfo/6lo


From nobody Fri Jun 27 11:02:43 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 155421A03B4 for <roll@ietfa.amsl.com>; Fri, 27 Jun 2014 11:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_MIME_NO_TEXT=0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 sd3Wdouehfgc for <roll@ietfa.amsl.com>; Fri, 27 Jun 2014 11:02:39 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B043C1ABB90 for <roll@ietf.org>; Fri, 27 Jun 2014 11:02:39 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3AE37200F7 for <roll@ietf.org>; Fri, 27 Jun 2014 13:56:52 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 1B0F264630; Wed, 25 Jun 2014 12:03:27 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 056EF63AED for <roll@ietf.org>; Wed, 25 Jun 2014 12:03:27 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: roll@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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-sha1; protocol="application/pgp-signature"
Date: Wed, 25 Jun 2014 12:03:27 -0400
Message-ID: <24486.1403712207@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/pvPofpC5J_hbU3RDhXPfKpkaZbE
Subject: [Roll] STRONG NUDGE: review draft-ietf-roll-mpl-parameter-configuration
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2014 18:02:41 -0000

--=-=-=


The WG adopted:
    http://datatracker.ietf.org/doc/draft-ietf-roll-mpl-parameter-configuration/

in march.  There has been only minor discussion on this document, despite
there being a reasonable number of people who said they thought this was a
valuable addition to LLNs, and MPL.

The authors posted a few comments about a question I had: what happens to MPL
if the parameters are changed, and I think that I'm satisfied.

At this point, it's the WG job to read the document and post questions.
Even if the protocol is no interest to you, but you've read it, you could say
so. Clearly if you have an interest in the protocol, and in MPL, please review.

The chairs think that this document may be read for a WGLC, but we do not
think that there has been enough discussion for us to believe that the
document has been sufficiently read.

Please comment before IETF90 so we don't have to abandon the work!

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBU6ryzoCLcPvd0N1lAQItCgf/WBfB6SExiAa6s7BNA7YuO/BjiRH7hn06
ftl05pOitcEg9RzyRwSf33baLzrPAEdDamrHnAVxRPfH3fn9IQksqybVTe/hc3Zg
BCog9UYWhGjt5JXRWGyed1lTt+LPxG0IkzZ29o6iThW+2up+GQNzIZXQvkx9JcMH
pUdxPq+flxmIyUFpiHYfzTuqrS42/Dfb8vK/Rjg8I74qoOQ84Q5i38PkHcmGugRH
vU8EvEQBtSEIfKuhynqgeclQvSiKMhm3kUVsY5VvkIY+CYwklb3JeRUfSYtgYrn4
7ePIMGSwFeWnezqkf+bPOdpIklS9ReBZlVInDYqws4BhAmWp7kB2Ow==
=Om1e
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Jun 29 18:59:04 2014
Return-Path: <yusuke.doi@toshiba.co.jp>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE92A1A00B6 for <roll@ietfa.amsl.com>; Sun, 29 Jun 2014 18:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level: 
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 g7psUpAn3cDa for <roll@ietfa.amsl.com>; Sun, 29 Jun 2014 18:59:00 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA1EE1A00B2 for <roll@ietf.org>; Sun, 29 Jun 2014 18:58:59 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id s5U1wsdU002678 for <roll@ietf.org>; Mon, 30 Jun 2014 10:58:54 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id s5U1wsm5004434 for roll@ietf.org; Mon, 30 Jun 2014 10:58:54 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id LAA04432; Mon, 30 Jun 2014 10:58:54 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id s5U1ws4H009695 for <roll@ietf.org>; Mon, 30 Jun 2014 10:58:54 +0900 (JST)
Received: from spiffy21.isl.rdc.toshiba.co.jp by toshiba.co.jp id s5U1wr5r010579; Mon, 30 Jun 2014 10:58:53 +0900 (JST)
Received: from [133.196.16.134] (ncg-dhcp134.isl.rdc.toshiba.co.jp [133.196.16.134]) by spiffy21.isl.rdc.toshiba.co.jp (Postfix) with ESMTPS id 91AC597D14 for <roll@ietf.org>; Mon, 30 Jun 2014 10:58:53 +0900 (JST)
Message-ID: <53B0C45C.8000705@toshiba.co.jp>
Date: Mon, 30 Jun 2014 10:58:52 +0900
From: Yusuke DOI <yusuke.doi@toshiba.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Routing Over Low power and Lossy networks <roll@ietf.org>
References: <24486.1403712207@sandelman.ca>
In-Reply-To: <24486.1403712207@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/GZAF5vlqUIqZ_rgFmO8vY_zTVco
Subject: Re: [Roll] STRONG NUDGE: review draft-ietf-roll-mpl-parameter-configuration
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 01:59:03 -0000

Michael, all WG members,

Thanks for attention. I'll update the draft by tomorrow to include minor edits. Anyway core idea will be unchanged. I believe we need to have a control for MPL parameters because it means control over network usage, redundancy/reliability, and end-to-end latency. I really appreciate your comments.

Thanks,

Yusuke



(2014-06-26 01:03), Michael Richardson wrote:
>
> The WG adopted:
>      http://datatracker.ietf.org/doc/draft-ietf-roll-mpl-parameter-configuration/
>
> in march.  There has been only minor discussion on this document, despite
> there being a reasonable number of people who said they thought this was a
> valuable addition to LLNs, and MPL.
>
> The authors posted a few comments about a question I had: what happens to MPL
> if the parameters are changed, and I think that I'm satisfied.
>
> At this point, it's the WG job to read the document and post questions.
> Even if the protocol is no interest to you, but you've read it, you could say
> so. Clearly if you have an interest in the protocol, and in MPL, please review.
>
> The chairs think that this document may be read for a WGLC, but we do not
> think that there has been enough discussion for us to believe that the
> document has been sufficiently read.
>
> Please comment before IETF90 so we don't have to abandon the work!
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>


From nobody Mon Jun 30 05:07:46 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D69B51A0292; Mon, 30 Jun 2014 05:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 F3I93369xM0Q; Mon, 30 Jun 2014 05:07:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B93601A029D; Mon, 30 Jun 2014 05:07:35 -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
X-Test-IDTracker: no
X-IETF-IDTracker: 5.5.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140630120735.10385.12981.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jun 2014 05:07:35 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/DLWB7nVmMNv5mTrIhqtsit6QKlA
Cc: roll@ietf.org
Subject: [Roll] I-D Action: draft-ietf-roll-applicability-home-building-04.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 12:07:39 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Routing Over Low power and Lossy networks Working Group of the IETF.

        Title           : Applicability Statement: The use of the RPL protocol suite in Home Automation and Building Control
        Authors         : Anders Brandt
                          Emmanuel Baccelli
                          Robert Cragie
                          Peter van der Stok
	Filename        : draft-ietf-roll-applicability-home-building-04.txt
	Pages           : 29
	Date            : 2014-06-30

Abstract:
   The purpose of this document is to provide guidance in the selection
   and use of protocols from the RPL protocol suite to implement the
   features required for control in building and home environments.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-roll-applicability-home-building/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-roll-applicability-home-building-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-roll-applicability-home-building-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 Mon Jun 30 05:11:48 2014
Return-Path: <stokcons@xs4all.nl>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 070291A0275 for <roll@ietfa.amsl.com>; Mon, 30 Jun 2014 05:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.106
X-Spam-Level: 
X-Spam-Status: No, score=-0.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651] autolearn=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 f7MpUoLgbjUX for <roll@ietfa.amsl.com>; Mon, 30 Jun 2014 05:11:45 -0700 (PDT)
Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34B721A026E for <roll@ietf.org>; Mon, 30 Jun 2014 05:11:44 -0700 (PDT)
Received: from roundcube.xs4all.nl (roundcube5.xs4all.net [194.109.20.203]) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id s5UCBejx014538; Mon, 30 Jun 2014 14:11:40 +0200 (CEST) (envelope-from stokcons@xs4all.nl)
Received: from AMontpellier-654-1-230-241.w92-145.abo.wanadoo.fr ([92.145.113.241]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Mon, 30 Jun 2014 14:11:39 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 30 Jun 2014 14:11:39 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: roll@ietf.org
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <20140630120735.10385.32739.idtracker@ietfa.amsl.com>
References: <20140630120735.10385.32739.idtracker@ietfa.amsl.com>
Message-ID: <78f848c8d65580816f68ad0bbfb1db18@xs4all.nl>
X-Sender: stokcons@xs4all.nl (xD/of9P6GewqOzJqPFSAqVP59aqmH3nM)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/38fXj390yHZgahAeuznSWF9qsPY
Cc: Anders Brandt <abr@sdesigns.dk>
Subject: Re: [Roll] New Version Notification for draft-ietf-roll-applicability-home-building-04.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: consultancy@vanderstok.org, Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jun 2014 12:11:47 -0000

Dear all.

A new applicability draft for home and buildings, version 4, has been 
submitted.

Changes from version 3 to version 4
<t> Renumbered sections and moved text to conform to applicability 
template</t>
<t> Extended MPL parameter value text </t>
<t> Added references to building control products </t>

Peter


internet-drafts@ietf.org schreef op 2014-06-30 14:07:
> A new version of I-D, 
> draft-ietf-roll-applicability-home-building-04.txt
> has been successfully submitted by Peter van der Stok and posted to the
> IETF repository.
> 
> Name:		draft-ietf-roll-applicability-home-building
> Revision:	04
> Title:		Applicability Statement: The use of the RPL protocol suite in
> Home Automation and Building Control
> Document date:	2014-06-30
> Group:		roll
> Pages:		29
> URL:
> http://www.ietf.org/internet-drafts/draft-ietf-roll-applicability-home-building-04.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-roll-applicability-home-building/
> Htmlized:
> http://tools.ietf.org/html/draft-ietf-roll-applicability-home-building-04
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-roll-applicability-home-building-04
> 
> Abstract:
>    The purpose of this document is to provide guidance in the selection
>    and use of protocols from the RPL protocol suite to implement the
>    features required for control in building and home environments.
> 
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat