[Lake] LAKE chartering discussion

[Michael Richardson <[e-mail]>]

Thank you Ben for the next steps on LAKE.
Are the BOF chairs on the hook to stick-handle the charter editing?
If not, then who?

Benjamin Kaduk <[e-mail]> wrote:
    bk> For the sake of facilitating discussion, we include draft charter
    bk> text for the OSCORE case, modified based on input from the BoF from
    bk> the version that was previously sent to secdispatch@ietf:

    > ==[ CHARTER ]==
    > Problem

    > Constrained environments using OSCORE in network environments such as
    > NB-IoT, 6TiSCH, and LoRaWAN need a ‘lightweight’ authenticated key
    > exchange (LAKE) that enables forward security.  'Lightweight' refers to:

    > * resource consumption, measured by bytes on the wire, wall-clock time to
    > complete, or power consumption
    > * the amount of new code required on end systems which already have an
    > OSCORE stack

    > Goals

    > This working group is intended to be a narrowly focused activity
    > intended to produce at most one LAKE for OSCORE usage and close.

    > The working group will collaborate and coordinate with other IETF WGs
    > such as ACE, CORE, 6TISCH, and LPWAN to understand and validate the
    > requirements and solution.  The WG will also evaluate work from
    > the TLS WG and derivatives thereof, and draft-selander-ace-cose-ecdhe.

Given that you said above:
      bk> bare-bones feature set.  On the balance, though, it seems that discussion
      bk> of a general-purpose-but-compact TLS would be most effectively done in the
      bk> TLS WG with additional input and collaboration as needed.  We plan to ask

It seems inappropriate to tell the new WG to look at the work from the TLS
WG, if the TLS WG will also be looking at a general-purpose-but-compact
thing.

We've already been down that road, finally getting to a BOF.
I'd like the IESG to please decide here.

    > Program of Work

    > The deliverables of this WG are:

    > 1. Design requirements of the lightweight authenticated key exchange
    > protocol for OSCORE (this draft will not be published as an RFC but will be
    > used to drive WG consensus on the deliverable (2)

    > 2. Specify a lightweight authenticated key exchange protocol suitable for
    > use in constrained environments using OSCORE
    > ==[ CHARTER ]==

This seems reasonable to me.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [


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