Apologies for cross-posting, but it seems some people not following the 
Secdispatch list have missed the connection between EDHOC and the new LAKE 
mailing list and BoF.

ACE, CoRE, 6TiSCH and LPWAN are identified as stakeholders in the draft charter 
for the LAKE WG (see [1] below).

If you are interested in a handshake protocol for OSCORE, join the LAKE mailing 
list now and attend the LAKE BoF at IETF 105.

Göran


On 2019-06-14, 21:32, "Secdispatch on behalf of Stephen Farrell" 
<[email protected] on behalf of [email protected]> wrote:

    
    Hiya,
    
    There's a new mailing list for discussion of lightweight
    authenticated key exchange, which has previously been
    discussed here in various edhoc threads. There's a BoF
    on this topic planned for IETF 105 as well. [1] Yoav and
    I are down to chair that at the moment.
    
    So if you're interested in that topic please sign up.
    We'll try kick off some pre-BoF discussion once people
    have had a chance to get onto the new list and Yoav
    and I have had a chance to chat about it all.
    
    Cheers,
    S.
    
    [1] https://trac.tools.ietf.org/bof/trac/wiki#LAKE

    
    
    -------- Forwarded Message --------
    Subject: New Non-WG Mailing List: lake
    Date: Fri, 14 Jun 2019 10:10:34 -0700
    From: IETF Secretariat <[email protected]>
    Reply-To: [email protected]
    To: IETF Announcement List <[email protected]>
    CC: [email protected], [email protected]
    
    A new IETF non-working group email list has been created.
    
    List address: [email protected]
    Archive: https://mailarchive.ietf.org/arch/browse/lake/
    To subscribe: https://www.ietf.org/mailman/listinfo/lake

    
    Purpose:
    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; and the amount of new code required on
    end systems which already have an OSCORE stack.
    This list belong IETF area: SEC
    
    For additional information, please contact the list administrators.
    
    

_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch

Reply via email to