[MLS] MLS BoF has been scheduled

Richard Barnes <rlb@ipv.sx> Wed, 21 February 2018 16:52 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: mls@ietfa.amsl.com
Delivered-To: mls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652E61242F7 for <mls@ietfa.amsl.com>; Wed, 21 Feb 2018 08:52:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
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 doBJESrDNJbg for <mls@ietfa.amsl.com>; Wed, 21 Feb 2018 08:52:02 -0800 (PST)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C44E127010 for <mls@ietf.org>; Wed, 21 Feb 2018 08:52:01 -0800 (PST)
Received: by mail-wr0-x22f.google.com with SMTP id o76so6371866wrb.7 for <mls@ietf.org>; Wed, 21 Feb 2018 08:52:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=DFOSFX+USmvWsq97WKu0epHAJ4tcqBU0gJWXCIPNwu4=; b=ru2Cc7qf6z0BQiZOcYhQKjH6ER6WOkEVu2bOn29eR8RNyjGE7su4YS01hCHRpYBuWo 8TPIPiLCAgQM5/VtE0GJ3Xux/8BvrJ1xALy+c0yyrxjS7DE5gh9hXLei3KHn4MCohXlR 7syMykB1xXYk7YXUtvTlI+L/yfXL3yhw5FyRQuHdmxUETuIqGEyZdifEb/Lq5aNYdNSu HiOS9vPgb71Z4xA3lTsxpNHOVlIVslYQoPqRSeo0VSf5hjFMINZGXQ5SSBia4RSDCmZY E4EZurem9RUkbUeUxIcQlbea0n7RxOsf4icbJiFlezjUDF0+xSQTxxf1qGQCDOGSnw4t RBJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=DFOSFX+USmvWsq97WKu0epHAJ4tcqBU0gJWXCIPNwu4=; b=KCPRGbefqzs1PTyjOAXP3jhN7BPY6vLa8d//qXKI5jC0pzPf6wtMilMG0oYpmL9BTP trjKefiIHuzuK5H6Afpti0OREumywI/aGp77qKfdaShXSM0XpWzZEeULSDOrpLHqRgRX no28Xzw5220ZH1K4Yj10e1LjDWXsGnr5jhIrwgrNMh0vANQApEMTfVvlbZ5UDHBQqE5S 2GQzElaZI3zVEku9/hWlZg+WGae+5Po09wh7gFmEnYD/FPS7RV2mwdD0VAoy7iLN0Ck3 rc3VO7ip5JbjrKZMAowrKwxWNabNgFwOhQXP99gUtyimOwtndz0A+SM797o3plBBB4W4 WMoA==
X-Gm-Message-State: APf1xPCIGqUIAO4GPsMe5T/uwDZMvN7UC9ySqdZXS+wueoKg1e6Z68JX ySgqa4SjU9v+cPjhi+12vYbRiW+5FSFP7//ekuZY2qZLfLY=
X-Google-Smtp-Source: AH8x2265e8ChSJ+16xuhZnQ2rY/UPfVWkGfUOKEywb+ErCUX40/IjWHHky3CaGZ7TSDSTIHQECIFjJ6zeEpiD4lENn8=
X-Received: by 10.223.171.167 with SMTP id s36mr3478274wrc.52.1519231919872; Wed, 21 Feb 2018 08:51:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.20.66 with HTTP; Wed, 21 Feb 2018 08:51:59 -0800 (PST)
From: Richard Barnes <rlb@ipv.sx>
Date: Wed, 21 Feb 2018 11:51:59 -0500
Message-ID: <CAL02cgQ4BBdLooPPz8g9DiNyKorhxA5ceu0G_OTVOBKQQmGwUA@mail.gmail.com>
To: mls@ietf.org
Content-Type: multipart/alternative; boundary="001a113b37b6ea91d20565bbbe7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/oLBJOFtLYBnf5z8syJt_YXilUY0>
Subject: [MLS] MLS BoF has been scheduled
X-BeenThere: mls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Messaging Layer Security <mls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mls>, <mailto:mls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mls/>
List-Post: <mailto:mls@ietf.org>
List-Help: <mailto:mls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mls>, <mailto:mls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 16:52:03 -0000

FYI, the preliminary agenda for IETF 101 has been posted:

https://datatracker.ietf.org/meeting/agenda.html

The MLS BoF is scheduled for 15:50 - 17:50 on Thursday, March 22.

For anyone who won't be there in person, remote participation details
should be added at the above link as we get closer to the meeting.