[6tisch-security] security meeting schedule until IETF99

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 06 April 2017 21:55 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: 6tisch-security@ietfa.amsl.com
Delivered-To: 6tisch-security@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B60D129684 for <6tisch-security@ietfa.amsl.com>; Thu, 6 Apr 2017 14:55:42 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Qo4SELjM5Id for <6tisch-security@ietfa.amsl.com>; Thu, 6 Apr 2017 14:55:40 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ED8F128DF3 for <6tisch-security@ietf.org>; Thu, 6 Apr 2017 14:55:40 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [66.171.166.114]) by relay.sandelman.ca (Postfix) with ESMTPS id 54C561F8F5; Thu, 6 Apr 2017 21:55:38 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 3521F2918; Thu, 6 Apr 2017 16:55:37 -0500 (CDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 6tisch-security@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 06 Apr 2017 17:55:37 -0400
Message-ID: <27133.1491515737@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch-security/DD9If0O4345VnJ0tJYqH41wtcrw>
Subject: [6tisch-security] security meeting schedule until IETF99
X-BeenThere: 6tisch-security@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Extended Design Team for 6TiSCH security architecture <6tisch-security.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch-security>, <mailto:6tisch-security-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch-security/>
List-Post: <mailto:6tisch-security@ietf.org>
List-Help: <mailto:6tisch-security-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch-security>, <mailto:6tisch-security-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 21:55:42 -0000

The result of the doodle poll now favours Monday 2017-04-10 at 11am EDT.
That's 1500 UTC, I think.  There will be no time changes between now and
IETF99, so the choice of anchor should not matter.

I would like to use JITSI, using the URL:
  https://jitsi.tools.ietf.org/6tischsec

(because I'm totally annoyed at webex)

I encourage you to visit the site prior to Monday.
There is no PSTN dial-in provisions, but it does work on pretty much every
platform that has webrtc, even, I think, Microsoft Edge, but probably not
Opera, and maybe not Safari(?).

The series of meetings will be:
    2017-04-10
    2017-04-24
    2017-05-08
    2017-05-22  (a holiday in Canada, let's discuss)
    2017-06-05
    2017-06-19
    2017-07-10
IETF99 is 2017-07-15 through 2017-07-21

The overall agenda is:
    1) finish 6tisch-minimal-security, with hooks to zero-touch.
       Get this to WGLC by IETF99.
    2) finish sketch of zero-touch document indicating how it fills
       in the hooks.  Get this close to WGLC by IETF99.
    3) work on enhanced-beacon document, should WG adopt it.
    4) work on rekey document, should WG adopt it.

The agenda for Monday is:
    1) review of IETF99, make sure we have all actions collected.

    2) OSCOAP/EDHOC: learn what we need to do, and in which WGs to advance
       is such that we can use it.

    3) other business?

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