[6tisch-security] (minutes of Wed Jan 14, 2015, 11am EST call) reminder -- 6tisch security call *tomorrow*, Wed Jan 14, 2015, 11am EST (dial-in info at bottom)

[Rene Struik <[e-mail]>]

Dear colleagues:

Please find below the minutes of the 6TiSCH Security conf call as of 
January 14, 2015, 11am-12pm EST.

Minutes 6TiSCH Security conf call, Wed January 14, 2015, 11am-12pm EST
{note taker: Rene Struik}
{recording: see 6tisch bitbucket list}
{slides discussed (and referenced in minutes): no slides this time}

1. Attendance:
Michael Richardson, Malisa Vucinic, Mike Seewald, Thomas Watteyne, Rene 
Struik

2. Agenda
The suggested agenda was approved.
Agenda:
1) administrativia {agenda bashing/minutes}
2) (brief update) feedback on posted security draft
3) input 6tisch security to the 6tisch architecture draft
4) AOB

3. Minutes
The minutes of the previous 6TiSCH security conference calls will be 
first item of agenda for approval at the next 6tTiSCH security 
conference call. {Please review.}

4. Feedback on posted security considerations draft 
(draft-struik-6tisch-security-architectural-considerations-01)
RS mentioned that he posted (on Fri January 9, 2015) a write-up on 
security considerations for 6tisch that provides lots of footnotes on 
behavior and security and implementation considerations re MAC, 
networking, and join protocol behavior. He also posted a slightly 
updated version (#01) that includes a high-level overview of the join 
protocol, including phases (authentication, authorization, 
configuration), device roles, and diagrams. He suggested that the draft 
tried to take into account technical discussions on 6TiSCH security 
calls since early December 2014, as well as offline feedback on 
pre-draft versions from several participants. While he acknowledged the 
draft still had some rough edges that needed polishing, he would welcome 
feedback from the group that would help in making the draft better. Kris 
Pister already kindly provided some preliminary feedback on the 6TiSCH 
mailing list, but more feedback would be much appreciated.

TW volunteered to provide feedback to the list.

5. Input 6tisch security to the architecture draft 
(draft-ietf-6tisch-architecture-04)
TW mentioned that there were currently three text proposals that could 
be used for inclusion with the architecture draft:
http://www.ietf.org/mail-archive/web/6tisch/current/msg02690.html
http://www.ietf.org/mail-archive/web/6tisch-security/current/msg00328.html
https://tools.ietf.org/html/draft-struik-6tisch-security-considerations-01

MV suggested that the verbiage of the three text proposals differed in 
level of detail provided, which made it hard to compare. RS suggested 
that at the previous 6TiSCH security conference call (Tue January 5, 
2015), everyone agreed that "the the level of detail would reflect 
consensus as reached to-date, so as to remove roadblocks by end of week" 
and that snippets that do (as yet) not carry this consensus would, 
therefore, have to be trimmed out. MR suggested that some of the 
language in section 1.3.1 of 
draft-struik-6tisch-security-considerations-01 was too high level and 
"does not align with what we were told". RS reminded the group that he 
simply provided text suitable for inclusion with the architecture draft 
that was known to reflect consensus to-date. Moreover, he suggested that 
the architecture draft does not have to carry all detailed information, 
if only because lots of work is still required to iron this out.

MR suggested that he would like to see inclusion of, e.g., details re 
trust relationships, certificate detail, and scalability properties. RS 
suggested that those could indeed be considered, but since some aspects 
hereof are still highly controversial at this time, this should be left 
out for now.

TW summarized some areas of consensus, including (a) identifying three 
device roles in the join process (joining node, join assistant, "JCE"); 
(b) aiming at minimization of long-haul communications between join 
assistant and JCE (ideally, only comprising one communication flow to 
and from the JCE, as, e.g., w/HART does).

MR suggested that it would be useful to add some verbiage re privacy 
aspects of addressing (e.g., that joined nodes would use short 
addresses). He further suggested that it would be useful to 
cross-reference some actual protocols that could be considered. As to 
the latter, RS suggested that it would certainly be possible to add some 
verbiage along the lines "the join protocol would consider authenticated 
key agreement protocols, such as, e.g., DTLS, and certificate schemes, 
such as, e.g., X509", etc., if referring to these acronyms would make 
people happy.

TW asked whether RS could review the three text proposals currently on 
the table and suggest a way forward that takes into account consensus 
and what was discussed during the call. RS agreed to take this on as 
homework assignment, with target to report back on this to the group by 
the end of Monday next week (January 19, 2015).

6. AOB
RS mentioned that there is no conference call schedule for next calls 
yet, but he would poll people re time preferences.

Best regards, Rene

-------- Forwarded Message --------
Subject: 	reminder -- 6tisch security call *tomorrow*, Wed Jan 14, 2015, 
11am EST (dial-in info at bottom)
Date: 	Tue, 13 Jan 2015 19:37:04 -0500
From: 	Rene Struik <[e-mail]>
To: 	tisch-security <[e-mail]>



Dear colleagues:

Just a quick reminder that we *do* have a conf call tomorrow, Wed Jan 
14, 2015, 11am EST.

Currently, the main agenda item is item #4b of last week: input to the 
6tisch architecture draft. It would also be good to have some more 
comments on the draft I posted.

Minutes of calls later tonight (sorry - extremely busy). For conf call 
dial-in info, see bottom of email.

Best regards, Rene

==
Note: next week's call is on Wed Jan 14, 2015, 11am EST.

On 1/6/2015 11:48 AM, Rene Struik wrote:
> Dear colleagues:
>
> Happy New Year!
>
> According to the agreed-upon 6tisch security conf call schedule, we 
> will resume the conference call series today, Tue Jan 6, 2015, 5pm EST.
>
> I propose we continue the discussion where we left off prior to 
> Christmas (essentially, item 3c below), except that we may have a 
> short presentation first (item #2).
>
> Agenda:
> 1) administrativia {agenda bashing/minutes}
> 2) {still to be confirmed} presentation Giuseppe Piro
> 3) join protocol details
> -- a) (done) status update MAC behavior
> -- b) (brief!) recap of routing/communication flow aspects
> -- c) incremental deployment aspects
> 4) input 6tisch security to other 6tisch documents
> -- a) terminology draft
> -- b) architecture draft
>
> Conf call time: 5pm EST = 7am Japan = 2pm PST = 11pm Paris time. {The 
> next call, on January 6, 2014) is also at 5pm EST (see schedule till 
> half of January 2015)}.
> Note: next week's call is on Wed Jan 14, 2015, 11am EST.
>
> Dial-in info at end of this email.
>
> Best regards,
>
> Rene
>
> -------- Forwarded Message --------
> Subject: 	Suggested agenda for 6tisch security call of *today*, Tue 
> December 16, 2014, 5pm EST (dial-in info at bottom)
> Date: 	Tue, 16 Dec 2014 09:21:20 -0500
> From: 	Rene Struik <[e-mail]>
> To: 	tisch-security <[e-mail]>
>
>
>
> Dear colleagues:
>
> I propose we continue the discussion where we left off last week.
>
> Agenda:
> 1) administrativia {agenda bashing/minutes}
> 2) join protocol details
> -- a) (brief!) status update MAC behavior
> -- b) continuation of routing/communication flow aspects {last week, 
> we did not finish the only two slides on this
> 3) input 6tisch security to other 6tisch documents
>
> Conf call time: 5pm EST = 7am Japan = 2pm PST = 11pm Paris time. {The 
> next call, on January 6, 2014) is also at 5pm EST (see schedule till 
> half of January 2015)}.
>
> Dial-in info at end of this email.
>
> Best regards,
>
> Rene
>
> -------- Forwarded Message --------
> Subject: 	suggested agenda for 6tisch security call of tomorrow, Tue 
> December 9, 2014, 9am EST (dial-in info at bottom)
> Date: 	Mon, 08 Dec 2014 17:16:40 -0500
> From: 	Rene Struik <[e-mail]>
> To: 	tisch-security <[e-mail]>
>
>
>
> Dear colleagues:
>
> For last week's Tue Dec 2, 2014, 9am EST conf call I prepared some 
> material and posted prior to the call. During the call, we discussed 
> all MAC-related aspects relevant for the join protocol and did not 
> discuss higher-layer aspects I prepared material for yet. I suggest we 
> continue the systematic discussion of last week and take that topic on 
> now.
>
> This leads to the following suggested agenda for this week 
> (essentially a continuation of last week's one):
>
> Same as last week's, except with
> #1a-b) focus on routing/communication flow related aspects join protocol;
> #2a): confirm concensus on MAC (as discussed last week) and 
> routing/communication flow aspects
> #2c) {as consequence of two items above} what to squeeze into 
> architecture draft
>
> The detailed agenda and dial-in info is below (#A, resp. #B).
>
> Best regards, Rene
>
> _A) Suggested agenda Tue Dec 9, 2014, 9am EST call_
>
> Proposed agenda:
>
> 0) Agenda bashing
>
> 1) Join protocol details
>
>     a) desired properties
>     b) realizable properties
>
>     #1a-b) focus on routing/communication flow related aspects join
>     protocol (we discussed MAC-related join-relevant aspects during
>     the conf call of Tue Dec 2, 2014, 9am EST).
>     For slides, see
>     https://drive.google.com/folderview?id=0B2a6Ilxu1XfCNF9JaXR1ZXlzZlU&usp=sharing
>     (same slides as sent out prior to Dec 2, 2014, 9am EST call)
>     Relevant slides: Slides 23-25 (contained in entire slide deck
>     (ppt), but also in excerpt (pdf))
>
> 2) Next steps:
>         a) consensus on 1#a and 1#b
>
>     #2a): confirm consensus on MAC (as discussed last week) and
>     routing/communication flow aspects
>     #2c) {as consequence of two items above} what to squeeze into
>     architecture draft
>
>         b) form tiger team to work out details
>             - project phases
>             - communication of sub-results
>         c) what to squeeze into architecture draft, etc.
>
> I will prepare material to facilitate discussion on 1) and 2), to be 
> discussed during the call.
>
> _B) Dial-in information:_
> English : New York Time 6tisch security
> Tuesday, December 9, 2014 | 9:00 am Eastern Standard Time (GMT-05:00)
> Meeting number:   641 709 118
> Meeting password: joinjoin
> Audio connection:
>        1-877-668-4493 Call-in toll free number (US/Canada)
>        1-650-479-3208 Call-in toll number (US/Canada)
>
> Access code: 641 709 118
> Meeting link:
>          https://ietf.webex.com/ietf/j.php?MTID=m1aa12258a83109b4ae291fb0c2bd92d6
>
> The etherpad we have used is at:
>         http://etherpad.tools.ietf.org:9000/p/6tisch-security-6top-xml.txt
>
>
> -- 
> email:[e-mail]  | Skype: rstruik
> cell: [phone] | US: [phone]
>
>
>
>


-- 
email:[e-mail]  | Skype: rstruik
cell: [phone] | US: [phone]