Re: [6tisch] Comments on draft-ietf-6tisch-minimal-security-06

2018-07-17 Thread Tengfei Chang
Hi Malisa and Tero, Thanks for answering my question! It is clear to me! I don't fully understand. Do you mean in which case would a node send > another Join Request, if it has already completed the join process sometime > before and obtained the L2 encryption keys? > My question is exactly what

Re: [6tisch] Comments on draft-ietf-6tisch-minimal-security-06

2018-07-17 Thread Tero Kivinen
Mališa Vučinić writes: > Hence I have two questions:  > 1. in what case JRC or some entity will send such packet? > > For example if a JRC detects that some node in the network > misbehaves, generates large amount of traffic, is misconfigured or > similar. The JRC would then simply need to

Re: [6tisch] My comments to the draft-ietf-6tisch-minimal-security-06

2018-07-17 Thread Tero Kivinen
Mališa Vučinić writes: > Would a following resolution work for you: > > OLD: > > Typically, this is the 16-bit Personal Area Network Identifier (PAN ID) > > defined in [IEEE802.15.4]. > Companion documents can specify the use of a different network identifier for > join purposes, but > this is o

Re: [6tisch] Review draft-ietf-6tisch-minimal-security

2018-07-17 Thread Mališa Vučinić
Hi Jim, It seems we have two use cases where this is relevant: 1) Change of ownership without reprovisioning the pledge (and using symmetric keys) 2) Failure of JRC Case (1): reuse of PIV can be avoided by mandating the exchange of OSCORE mutable parameters. Case (2): the context is lost and wi

Re: [6tisch] Comments on draft-ietf-6tisch-minimal-security-06

2018-07-17 Thread Mališa Vučinić
Hi Tengfei, Thanks for your review! See my responses and proposed resolutions inline. Mališa On Mon, Jul 9, 2018 at 3:44 PM Tengfei Chang wrote: > Hi Malisa, > > I just reviewed the draft and have several comments below. > > *Comment 1: * > *--* > In section 9.3.2 when desc

Re: [6tisch] comments to the “Minimal Security Framework for 6TiSCH” document

2018-07-17 Thread Mališa Vučinić
Hi Xavi, Many thanks for sending this review. See my responses inline. Mališa On Fri, Jun 29, 2018 at 5:37 PM Xavi Vilajosana Guillen wrote: > Hi, > > I reviewed the ”Minimal Security Framework for 6TiSCH” document. > > Here some comments that have not been mentioned by others. > > 1) I miss s

Re: [6tisch] My comments to the draft-ietf-6tisch-minimal-security-06

2018-07-17 Thread Mališa Vučinić
Hi Tero, Thank you for this extensive review! See my responses inline. Mališa On Thu, Jun 28, 2018 at 12:24 AM Tero Kivinen wrote: > In section 3 there is text saying: > >The "network identifier" uniquely identifies the 6TiSCH network in >the namespace managed by a JRC. Typically, thi

Re: [6tisch] 6TiSCH@IETF102 slides

2018-07-17 Thread Pascal Thubert (pthubert)
Super Ceci dit ce serait pas mal de montrer le charter. Je peux ouvrir un browser préférerais une Slide Regards, Pascal Le 17 juil. 2018 à 09:13, Thomas Watteyne mailto:thomas.watte...@inria.fr>> a écrit : All, Slides for the 6TiSCH WG meetingof tomorrow are now at https://datatracker.ietf

[6tisch] 6TiSCH@IETF102 slides

2018-07-17 Thread Thomas Watteyne
All, Slides for the 6TiSCH WG meetingof tomorrow are now at https://datatracker.ietf.org/meeting/102/materials.html/#6tisch. @presenters, please verify (all of) your slides are there, and with correct formatting. Looking forward to discussing those! Thomas -- _