[6tisch-security] reminder of design team meeting today

[Michael Richardson <[e-mail]>]

etherpad:
https://etherpad.tools.ietf.org/p/6tisch-security?useMonospaceFont=true

Conference audio/video at https://appear.in/6tisch-coap-est-minimal

agenda:
        1) review of last time.
        2) what documents do we need to write?!?
        3) where will they be progressed?

See illustration of documents in next email.

DID WE HAVE A MEETING BEFORE 2017-11-27, or do I just have two sets of notes?

minutes from 2017-11-27:

Attendees
---------

- Michael Richardson (mcr)
- peter van der Stok (peter)
- Benjamin Damm (Time OK)
- max pritikin MP)
- Mališa Vučinić
- Thomas Watteyne
- Tengfei Chang

Agenda
------

The agenda is loose, but:

0) scheduling discussion
every 2 weeks proposed
this time slot
no dissent

1) recap of IETF100, things arising from meeting

EST-coap likely to get adoped by ACE WG, given removal of BRSKI hard references.
Jim had remarks about proxying.
LWM2M situation is other use for EST-coap.
EST server standalone is an important application.

Jim says to get the DTLS proxy correct, and that would sufficient to do an adoption call.
   -> figure https://tools.ietf.org/html/draft-vanderstok-ace-coap-est-02#section-6

2) frequency of these meetings

use of this meeting time, Panos + Peter are major authors.
MP: Panos indicates he couldn't join today but can join going forward. I've
    confirmed he has the invite.

3) state of 6tisch-minimal-security (briefly)
    MV: devoting all cycles to getting it out.
    * tagging of join traffic.  (AF43?)
    * MCR will send summary.

    Q: how well supported is DSCP/TOS setting for IPv6 socket API?
    MCR: I am pretty sure it's in the API, and can be done on a packet by packet basis even.


4) state of 6tisch-zerotouch-join (briefly)
  * CORE is getting to the point of being done with SID.
  * MCR to bring up question of assertion mapping
  * MCR how to we optimize the transmission of the client certificate?

MV: Jim has draft to encode certificate as CBOR, and option to have URL.
https://tools.ietf.org/html/draft-schaad-cose-x509-01
For (D)TLS this probably gets us into the realm of:
    https://datatracker.ietf.org/doc/draft-ietf-tokbind-negotiation/
or delayed authentication until post (D)TLS.

x5u:  This header parameter provides the ability to identify an X.509
      certificate by a URL.  The referenced resource can be any of the
      following media types:

5) plan for getting EST-COAPS to progress

we do not yet have a draft/presentation for zerotouch onboarding, except for 6tisch.


2017-11-27

present: mcr,

Minutes
-------

next meeting is Dec .11.
No meeting Dec. 25.
next meeting is January 8.




--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-