From nobody Fri Jul 2 15:05:07 2021 Return-Path: X-Original-To: mls@ietf.org Delivered-To: mls@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 467683A09E9; Fri, 2 Jul 2021 15:02:55 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: kaduk@mit.edu, mls@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.34.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <162526337527.26814.12088070916491856430@ietfa.amsl.com> Date: Fri, 02 Jul 2021 15:02:55 -0700 Archived-At: Subject: [MLS] mls - Requested session has been scheduled for IETF 111 X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2021 22:03:04 -0000 Dear Sean Turner, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. mls Session 1 (1:00 requested) Thursday, 29 July 2021, Session II 1330-1430 Room Name: Room 7 size: 507 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/111/sessions/mls.ics Request Information: --------------------------------------------------------- Working Group Name: Messaging Layer Security Area Name: Security Area Session Requester: Sean Turner Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 25 Conflicts to Avoid: People who must be present: Benjamin Kaduk Nick Sullivan Richard Barnes Sean Turner Resources Requested: Special Requests: --------------------------------------------------------- From nobody Sun Jul 4 00:51:16 2021 Return-Path: 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 802123A3BEF for ; Sun, 4 Jul 2021 00:51:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=PKoi8rNb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=q9a14abw 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 f_o3o1epj1aN for ; Sun, 4 Jul 2021 00:51:08 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAB373A3BEC for ; Sun, 4 Jul 2021 00:51:08 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 931C85C00BC for ; Sun, 4 Jul 2021 03:34:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 04 Jul 2021 03:34:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm3; bh=LXIbugNu9bT deTFNh3cWVHmzcrpLLRe+WweeZYcg1nU=; b=PKoi8rNbC3qsO0S2QjrixRQ4Ys4 5w5L69DrcIFtyMvwBGUVBWuU2n6km18UHfnyNanblK1yp1JNAB+vUpnegUgO5Dni v2P7tO1wXA/rWKNcdVUVYhL5jdJ/TYCcIi3vvVCExZKB79BqHaMoUopaOy0MVG+O 22YVhfuxJssTRuy6aU4qO/Ekv/TeDe0XcOiWPDZN7CPke3dopcfhwQ5ZZxr9/VSJ 1ArCujeCaIHhhMcPsItZHxIM7Q4YLALcQqIQvXrHJUH7gONvk5db7+62+79ub046 aOmNHOilwSlaXgEhjJYAoH68amOAsr/6YJxUEYbJYqPcyrlzCpiJwCqvsbw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=LXIbugNu9bTdeTFNh3cWVHmzcrpLLRe+WweeZYcg1nU=; b=q9a14abw E0TIkOhZoUfj8ysYDHsoGt53maONoLwVk4jy8/vBS4S7UeJIBkTf9Zkg2pvsHIHx emUtPETJR423W2J0bjEMmGs/SGVC4w4oOZyZhle65yt03xUPCPu1RKBdgww9ztEb 20JkCon81rMaoGD2EQAEJWJfWIj+A/eGIMjOCrIU/UcCxlsUbAexLUVpl0bRAhpS Yed2yFIUT3Vl305xm4nm/kDY54ew5DBK0VthCS3q/1ABYNBpdFCtim01R1DRxX/v RY2HQGlb2q3k1ZB0sHwmGOvIgJok1UTdb0O0RILkhPcoo2IOBWu4OrQhnZ+r0+Fd urDX1RyDhNK0lA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeejuddguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgepvdenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 4 Jul 2021 03:34:15 -0400 (EDT) Content-Type: multipart/alternative; boundary="===============2541030111203950758==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: mls@ietf.org Message-Id: <20210704075108.BAB373A3BEC@ietfa.amsl.com> Date: Sun, 4 Jul 2021 00:51:08 -0700 (PDT) Archived-At: Subject: [MLS] Weekly github digest (MLS Working Group summary) X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2021 07:51:14 -0000 --===============2541030111203950758== MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; format="flowed" Issues ------ * mlswg/mls-protocol (+0/-0/=F0=9F=92=AC4) 1 issues received 4 new comments: - #468 Clarify relationship between Ratchet Tree Evolution, Group Creatio= n, and Key Schedule (4 by kkohbrok, knightcode) https://github.com/mlswg/mls-protocol/issues/468=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/mlswg/mls-architecture * https://github.com/mlswg/mls-protocol * https://github.com/mlswg/mls-federation --===============2541030111203950758== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (MLS Working Group summary)

Sunday July 04, 2021

Issues

mlswg/mls-protocol (+0/-0/=F0=9F=92=AC4)

1 issues received 4 new comments:

Repositories tracked by this digest:

--===============2541030111203950758==-- From nobody Thu Jul 8 11:08:49 2021 Return-Path: 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 C0E2C3A1190 for ; Thu, 8 Jul 2021 11:08:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 JHX1m5gNCZc0 for ; Thu, 8 Jul 2021 11:08:43 -0700 (PDT) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 194A23A1188 for ; Thu, 8 Jul 2021 11:08:42 -0700 (PDT) Received: by mail-qk1-x72c.google.com with SMTP id q190so6586134qkd.2 for ; Thu, 08 Jul 2021 11:08:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=frlMmpAp9BGBq7/hnrkH/0X01YrpRJetLhEIr9IESdI=; b=MKxBa0sxWFrQmwuwmVu+KAcqBpRQZtemK+B6NpOQO8KWgHqK5iVHvldqBaaXfb9hAB uXRPwZ06/3IMgvQZsNuLup8SQW7Q6NfQ2XhCq478Bu/13O6RNCpYs7QBMAwMFS2iFhm2 zr/ONcT0od8Z32LM9A/jQccbITTTRMhI8IxIo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=frlMmpAp9BGBq7/hnrkH/0X01YrpRJetLhEIr9IESdI=; b=mDtQ808WXUGZTblnIdXpQe7aT8aaI6AyiTz1StsAxkzopSDzS3ZDNpi70uzZl0qkAp rXGHsreuRn5tUD3w7icfHFpVYry8zLcfeCg03mOPs3qAVO9qaFioTepxeI0gwgBH3H2r K3jTU/sxwzh6NlBDvW66QVyPYum9y6flM4U3bYENu4AuZM287r9E67qg5Fk2uf6mpIum C17WhPbL2C5z5D1PljbrlCACaW85sVQiNbUuTvsT7y24SQGAJl3CpJj2YY7UoHbM/kvT nvCFA/4g9LHiXuv5dbvMgbXriQc6wN2AIUsE6vGECEQBwUXmGnSahFLLDhXcQ7+gHifV 1hMQ== X-Gm-Message-State: AOAM531seorLCiUDbvd8O5TH7ozSy7Xnp8SSPETRzbFS7yzDX5wzas0a GoCFGansexNsYavCs/aeTrlwasFRUt6uRw== X-Google-Smtp-Source: ABdhPJyPfLVyIKn6NsC0p3KKSX6RpUdlc5cjQWNlsDaVpU4a9y8oh7D7jRbkC4MUQOSTW6zssbDiww== X-Received: by 2002:a37:4d8:: with SMTP id 207mr7712037qke.8.1625767720927; Thu, 08 Jul 2021 11:08:40 -0700 (PDT) Received: from smtpclient.apple (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id x28sm1278987qtm.71.2021.07.08.11.08.39 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jul 2021 11:08:40 -0700 (PDT) From: Sean Turner Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) Message-Id: <11F70F23-9288-42B0-8F10-A49F87E8D22F@sn3rd.com> Date: Thu, 8 Jul 2021 14:08:38 -0400 To: MLS List X-Mailer: Apple Mail (2.3654.100.0.2.22) Archived-At: Subject: [MLS] mls@ietf11: agenda topics X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2021 18:08:48 -0000 Hi! We currently have a meeting time scheduled for Thursday, 29 July = 2021 from 2030-2130 (UTC). That=E2=80=99s one hour to review outstanding = issues/PRs on the protocol and architecture I-Ds as well as any updates = on any security analysis (and potential changes as a result). I suspect = that we will do as we have done in the past and walk through the GitHub = repos for the two I-Ds. Are there any other topics that need to be addressed? spt= From nobody Mon Jul 19 08:56:24 2021 Return-Path: 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 C45053A3862 for ; Mon, 19 Jul 2021 08:56:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.887 X-Spam-Level: X-Spam-Status: No, score=-1.887 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 cu9nrjRqTTKp for ; Mon, 19 Jul 2021 08:56:14 -0700 (PDT) Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 710D33A3865 for ; Mon, 19 Jul 2021 08:56:14 -0700 (PDT) Received: by mail-qk1-x72f.google.com with SMTP id m3so17131173qkm.10 for ; Mon, 19 Jul 2021 08:56:14 -0700 (PDT) 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=5jeFxriZD+TmBj4+kFttODc6GKIK3lZuKouVONtdvZY=; b=lJMqab8Zzt7EwH6BWp17y3cSay8YV7QBhoWs7VBukKaQ8wCms4QRMPj+byhVtmn9mV j6V6KcL6YDZcbCvh74DNRbxkhJpKlaAMpfo4qbe01BI0A/g6kApuAeIcDUGk6DPBpkgD yd8ilkguPoZDaRmlGuOXziYlqrPuUe8LT+PJPOSBuBOuYJ73G7NOZnNe5/l97WGduqCk nwbvB+honCxD92th5KKtb8flM1ts40yIpg7Pvfp/npFRd7Ug/Tyui+IETADQEIpiq9om i8RrEiv7nrVUB+m7m9EgJicv7oHpStKrj7O3pGxcg62zwIFH96AmhsHvsDd6nbDEwgir JPEQ== 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=5jeFxriZD+TmBj4+kFttODc6GKIK3lZuKouVONtdvZY=; b=UdrNWAvsby44jl8eYAgHpg5ZnQyt1XerkY4QEEfpzDEL/hcjBt6vUhP5Ezro3ACO7B JSJsAy5l4dzcRmza2WfNz5zdRz5K6jpn//+2tAgPZQjjHIgFQ/yAM09rQghyTLj1x9MR J3vrXSzYITsZ1ISykZl+h9czLORSB3XFnnBptQ+eiGTql73mHDTNcDH1hDP+rA6CQA5H xz6OQNC1iVKKAx08J7Ojcr63UXMQl1to8zQXB21SBGJ3SqF/9uJo6mM4G/MKnJp6mX1P eB/obRBti70Fl8Qr/io+xLXcrCMBAewhqJkvvsDII5K7hIC0yic9w+NXgLTdK32doI72 6KCQ== X-Gm-Message-State: AOAM530OcxCdrWTXmZmd7l/8HTC1GxkEE+1oP/GjYibQiDVUtkyd7GkS 57yY4TMN7o9zB7t9ekw47Y6Nxwbv/uwByAChNv5u/YGfW/lrrA== X-Google-Smtp-Source: ABdhPJxGwSe+ShTZaRBN0a89ic34loysBx1BhVClI9U3XlE9zHka3SCvlRCHOyx+gW5H/DJegBEWqoooPdXNyj6/tq4= X-Received: by 2002:a05:620a:982:: with SMTP id x2mr13787050qkx.347.1626710172370; Mon, 19 Jul 2021 08:56:12 -0700 (PDT) MIME-Version: 1.0 From: Richard Barnes Date: Mon, 19 Jul 2021 11:56:01 -0400 Message-ID: To: Messaging Layer Security WG Content-Type: multipart/alternative; boundary="000000000000fa1b1605c77bf95f" Archived-At: Subject: [MLS] Progress update; cancel MLS meeting at IETF 111? X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2021 15:56:19 -0000 --000000000000fa1b1605c77bf95f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, We MLS protocol spec editors wanted to provide an update on plans and progress as we approach the IETF meeting. The short version here is: We should probably cancel the MLS meeting at IETF in favor of a meeting about a month later. On the interop front: The MLSpp and OpenMLS teams have been having periodic interop calls, and are getting close to interop. As of this writing, the two stacks are interoperating on all test vectors except the TreeKEM test vector. The next phase is to verify compatibility on protocol operations, which we plan to ramp up work on in August, with a goal of getting verified interop by the end of the month. Other implementations are of course welcome to join in! We are coordinating on Wire; please let me know if we should add you to the channel. On the spec front: The last interim flagged several issues we had where the authors were going to propose a way forward, and we haven=E2=80=99t made pr= ogress on any of them. We are planning to accelerate work on this in August, with a goal of having most of the outstanding PRs and issues done by about the same time as the interop work. Obviously, please file any remaining PRs/issues ASAP. With all that, it looks like we=E2=80=99ll be in a good position to issue W= GLC in ~September. Instead of meeting in a couple of weeks at the IETF, it would probably be more effective to meet at the end of August / early September to look at any last lessons learned from interop testing, and any non-trivial PR/issue resolutions that need WG attention. Cheers, Richard and Raphael --000000000000fa1b1605c77bf95f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi all,


We MLS protocol spec editors wanted to provide an update on pl= ans and progress as we approach the IETF meeting.=C2=A0 The short version h= ere is: We should probably cancel the MLS meeting at IETF in favor of a mee= ting about a month later.


On the interop front: The MLSpp and OpenMLS t= eams have been having periodic interop calls, and are getting close to inte= rop.=C2=A0 As of this writing, the two stacks are interoperating on all tes= t vectors except the TreeKEM test vector.=C2=A0 The next phase is to verify= compatibility on protocol operations, which we plan to ramp up work on in = August, with a goal of getting verified interop by the end of the month.=C2= =A0 Other implementations are of course welcome to join in!=C2=A0 We are co= ordinating on Wire; please let me know if we should add you to the channel.=


On the spec front: The last interim flagged several issues we had wher= e the authors were going to propose a way forward, and we haven=E2=80=99t m= ade progress on any of them.=C2=A0 We are planning to accelerate work on th= is in August, with a goal of having most of the outstanding PRs and issues = done by about the same time as the interop work. Obviously, please file an= y remaining PRs/issues ASAP.


With all that, it looks like we=E2=80=99ll= be in a good position to issue WGLC in ~September.=C2=A0 Instead of meetin= g in a couple of weeks at the IETF, it would probably be more effective to = meet at the end of August / early September to look at any last lessons lea= rned from interop testing, and any non-trivial PR/issue resolutions that ne= ed WG attention.


Cheers,

Richard and Raphael

--000000000000fa1b1605c77bf95f-- From nobody Thu Jul 22 02:58:24 2021 Return-Path: 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 D510B3A4040 for ; Thu, 22 Jul 2021 02:58:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mBE8BYAaqeRX for ; Thu, 22 Jul 2021 02:58:19 -0700 (PDT) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 630F13A4041 for ; Thu, 22 Jul 2021 02:58:19 -0700 (PDT) Received: by mail-wm1-x332.google.com with SMTP id 14-20020a05600c028eb0290228f19cb433so1223161wmk.0 for ; Thu, 22 Jul 2021 02:58:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=TVOXhCbJa8vPJ5gTb3kXESqAb+Q464upzP/zDc+CYU8=; b=Itkn+yNZtA7Md86LvTlRMz98pvB1sj+MwVX4V6lWMz6kmbuBUDcKkx5B1t0/KLFQjB 6VMw1EanN8zMgA5X1sbrkCAXj5h8qngKbl8QzKtEYze+G13dVQtn/b/oNpgN+D22RJy9 2pqDzskrwlOtAsIicAGW9DlG3kFRF7Elx60S8aV6eLO3OBiYovenR5DTtgLT/yK8/v5P f2OWVE6s0fFQ+KVCjS1qJ99bq/r4qpt2EJTxgEofCe4XuzLqIBITCFA59+8fCNT5bpLx jXvX4lzZs7u2cXoAjB1d7nHvqommksDEuZs/zC+xJ7PosyYiXjosWMS+tKdwxm49gQmO Np1w== 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=TVOXhCbJa8vPJ5gTb3kXESqAb+Q464upzP/zDc+CYU8=; b=B1PuUqKtJH3XcSEw/PoXhTvI7bLkFANViDw6OoEIEIAH75+JZjzexEwKaV1R5k5swx JuhZbr9ngbeah76EWMK3EDPe2KnUqfguqlhrJuLOOiXYm+atTP7GFBWiMgcOGGaM4ZMD va1leIiiyL9h4gsg1B/oQ/O5XFESwQODqSNj18cjUdt5J1pXWsZQzmC37Elq37hwbi83 8iF/7eVkq2HB3CZIDUExzyVHUBy3Xjir9uwNt5OBaWPiuMxdTJ0SP2yk/1r2BFv/hdoY 5nA90QzvMm2YQqcE7VwHtdJ1UhZAGc8jMmF9y7j9pNPIpRyERlM4HCOCAOFQeu6XKAC7 Gxag== X-Gm-Message-State: AOAM532U5rXg3VXLP245TU+oR5rACUWqD0AAOxxl3WCzRhssRIXf3hCy BtAjhRIYWiC+X9zi5rvsKtTL0QD0MAwqPcpvB47d6Q99qTg= X-Google-Smtp-Source: ABdhPJxR3UGXMzJCj6bcfmSusUP+brDGPqbgYT4wpmOo1Ngsoix21zUNxMcLtcP7o+Hc6NJ5o+TAukri2vuE/3fuMZs= X-Received: by 2002:a1c:7c08:: with SMTP id x8mr42438288wmc.2.1626947892135; Thu, 22 Jul 2021 02:58:12 -0700 (PDT) MIME-Version: 1.0 From: Tijana Klimovic Date: Thu, 22 Jul 2021 11:58:00 +0200 Message-ID: To: mls@ietf.org Content-Type: multipart/alternative; boundary="0000000000002dca5705c7b353ea" Archived-At: Subject: [MLS] Reuse guard in Framing X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2021 09:58:22 -0000 --0000000000002dca5705c7b353ea Content-Type: text/plain; charset="UTF-8" Hello, I have a question regarding the reuse guard used in the framing. The specification motivates its use in the following way: "Before use in the encryption operation, the nonce is XORed with a fresh random value to guard against reuse. Because the key schedule generates nonces deterministically, a client must keep a persistent state as to where in the key schedule it is; if this persistent state is lost or corrupted, a client might reuse a generation that has already been used, causing reuse of a key/nonce pair." When would losing one's state be a realisitic possibility? Many thanks. Tijana --0000000000002dca5705c7b353ea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

I have a question regarding = the reuse guard used in the framing. The specification motivates its use in= the following way:

"Before use in the encryp= tion operation, the nonce is XORed with a fresh random value to guard again= st reuse. Because the key schedule generates nonces deterministically, a cl= ient must keep a persistent state as to where in the key schedule it is; if= this persistent state is lost or corrupted, a client might reuse a generat= ion that has already been used, causing reuse of a key/nonce pair."

When would losing one's state be a realisitic po= ssibility?=C2=A0

Many thanks.
Tijana
--0000000000002dca5705c7b353ea-- From nobody Thu Jul 22 04:23:34 2021 Return-Path: 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 DB49D3A42B8 for ; Thu, 22 Jul 2021 04:23:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 DjGi0ESTvA18 for ; Thu, 22 Jul 2021 04:23:28 -0700 (PDT) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 0FC913A42B7 for ; Thu, 22 Jul 2021 04:23:17 -0700 (PDT) Received: by mail-lf1-x133.google.com with SMTP id b26so7974652lfo.4 for ; Thu, 22 Jul 2021 04:23:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DOj+CZziYeBIjP5h9Jyz4d+8ohZ7/EF+C0KktuTIqaw=; b=cGjZ40Cs14UPCapB1DnAccVxLmQ/OrxQjaD/SDN3702BZPqFBIJGCOfO1ZZ7l3S5Ea x3LPC/KzqGXUyjYBX1TZsutv965hQcEsPURmIZUOMqIs6qY7QgVL0BWcXMLMDtMY/Stj vIBExbf2N/jz6xJ+vltcSjV8PxxGE2zI2ZeLFVmHZax9jIDXgyLkexjNCrxf+8DI33Yb xpj+3xPFrWhw8QkgB3+rWt2OnqSyo1vJpKmqW56RjergCq0oXaOW6r7iPGuCYLkp8IOt HvxKJxm1dzXyIjEHZn1AXOVVItc3sXiamG0EiX+BpGr5inRKvAgkKa6b8pG/ctoPiW4c DKBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DOj+CZziYeBIjP5h9Jyz4d+8ohZ7/EF+C0KktuTIqaw=; b=Hl7wR1K6qv6gosQn79D/jW7IXNbVxZBpdtXeUEl/gymu4sTfnqzfh0gYA+V8UlKHRm FuTj7OtdZR8YcroThn/SoxMeEhFGMJSXExgUdDvfLc2VM1WJ0GwhiieblpPHr6dVTtHs X5ZjZ/fq1y+mHXYXelO21buaJL5G0TK9K0gh69182RtHM+saO0OripI0WpJG7amHbDZ4 2w/fO3tMxsKGaA79zbGYXsNIWB+D2Ooc2LKRONlwHXSz1tH3Db+7eXI0Wt4tCXIW3doS 41AOnFdK3ykkjRULEsVLZyjGSBHFYMSCgoWqRAEdgXvV+XsqGS8YhSp56KaRJ2+Tz3Zj AyxQ== X-Gm-Message-State: AOAM530HzfVYPb/5U0vRRSlejtu4Ml6czH4cHMejWwJ1krUzt6wcNrDq yMTCKoS0MJyhL8mx6FWE/2kXklEdN6+DectnBKc= X-Google-Smtp-Source: ABdhPJx/R2HBCt/n3IHhpKzIkKXU5WgrpcSDklLI11BllHOeHsw7TgWN8D+No0uc2JcOJTTqHKkBwXtjkV8dYgnplto= X-Received: by 2002:a05:6512:3316:: with SMTP id k22mr28592594lfe.472.1626952995567; Thu, 22 Jul 2021 04:23:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Natanael Date: Thu, 22 Jul 2021 13:23:01 +0200 Message-ID: To: Tijana Klimovic Cc: mls@ietf.org Content-Type: multipart/alternative; boundary="0000000000005dfd9605c7b48377" Archived-At: Subject: Re: [MLS] Reuse guard in Framing X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2021 11:23:33 -0000 --0000000000005dfd9605c7b48377 Content-Type: text/plain; charset="UTF-8" Den tors 22 juli 2021 11:58Tijana Klimovic skrev: > Hello, > > I have a question regarding the reuse guard used in the framing. The > specification motivates its use in the following way: > > "Before use in the encryption operation, the nonce is XORed with a fresh > random value to guard against reuse. Because the key schedule generates > nonces deterministically, a client must keep a persistent state as to where > in the key schedule it is; if this persistent state is lost or corrupted, a > client might reuse a generation that has already been used, causing reuse > of a key/nonce pair." > > When would losing one's state be a realisitic possibility? > Via a recent thread on the metzdowd cryptography mailing list; https://www.metzdowd.com/pipermail/cryptography/2021-July/037258.html The TLDR is we've seen it break so many times that we have to assume it will fail again. See for example the Sony PS3 signing key leak, via ECDSA k value reuse. Anything from a power loss, to a logic bug, to application state being replicated into new instances, or even restore from a backup, or a weak RNG, etc, can cause it. Note that in certain situations where nonce reuse happens due to lost state, it may be because you're in a virtualized environment where the RNG has also broken for the exact same reason. If you're concerned nonce reuse may happen in a given environment, an MRAE ciphersuite is the best option (misuse resistant authenticated encryption, including most SIV modes). Looks like the draft currently only have plain stream cipher modes defined (which would unfortunately fail catastrophically in the case a nonce and key is reused for different messages), but perhaps AES-GCM-SIV can be added in addition to the regular AES-GCM mode which is currently defined? --0000000000005dfd9605c7b48377 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


Den tors 22 juli 2021 11:58Tijana Klimovic <tijana.klimovic97@gmail.com> skrev:
Hello,

I have a question = regarding the reuse guard used in the framing. The specification motivates = its use in the following way:

"Before use in = the encryption operation, the nonce is XORed with a fresh random value to g= uard against reuse. Because the key schedule generates nonces deterministic= ally, a client must keep a persistent state as to where in the key schedule= it is; if this persistent state is lost or corrupted, a client might reuse= a generation that has already been used, causing reuse of a key/nonce pair= ."

When would losing one's state be a rea= lisitic possibility?=C2=A0

Via a recent thread on the metzdowd crypt= ography mailing list;

https://www.metzdowd.com/pipermai= l/cryptography/2021-July/037258.html

The TLDR is we've seen it break so many times that= we have to assume it will fail again. See for example the Sony PS3 signing= key leak, via ECDSA k value reuse.

Anything from a power loss, to a logic bug, to application stat= e being replicated into new instances, or even restore from a backup, or a = weak RNG, etc, can cause it.

Note that in certain situations where nonce reuse happens due to lost = state, it may be because you're in a virtualized environment where the = RNG has also broken for the exact same reason. If you're concerned nonc= e reuse may happen in a given environment, an MRAE ciphersuite is the best = option (misuse resistant authenticated encryption, including most SIV modes= ).

Looks like the draft = currently only have plain stream cipher modes defined (which would unfortun= ately fail catastrophically in the case a nonce and key is reused for diffe= rent messages), but perhaps AES-GCM-SIV can be added in addition to the reg= ular AES-GCM mode which is currently defined?
=
--0000000000005dfd9605c7b48377-- From nobody Thu Jul 22 10:41:25 2021 Return-Path: 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 841FB3A0AF3 for ; Thu, 22 Jul 2021 10:41:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.586 X-Spam-Level: X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 ne9kjtDTgMhO for ; Thu, 22 Jul 2021 10:41:19 -0700 (PDT) Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (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 039763A0AE7 for ; Thu, 22 Jul 2021 10:41:18 -0700 (PDT) Received: by mail-vk1-xa2f.google.com with SMTP id k9so1437670vki.5 for ; Thu, 22 Jul 2021 10:41:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VIQ1nRUAUSGfAnaad69YOZvdGTTKvyd1PvGq96qvIGw=; b=DVyXs5cXOSpSR22VG2VHMfJQWZrzDRwwz5SXeKlJHu3Iy8LCHNf2GkhkAJ5qXOdoCZ kCLnDI9GDhoOvoVR7rklrfb/m+Vq8H3F8iXu7Ym4zTmilCaBQ7Ys6VzKo74ExL1PQL28 c966kERM+vhvEDEMwZKetRfvzOutAhvVS9nyo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VIQ1nRUAUSGfAnaad69YOZvdGTTKvyd1PvGq96qvIGw=; b=kcgQ/scKD3MZieb++/2K13PgEyUfHSgAq7BRX7t4WwsA6JgPZbEpGtKAPYqfom0Gdv /1ozQadZmz7Qzp23eUMHJ2nWswV00RNPr3ckOCU94TidTsx1z4fKcvmUF3X6BuM5WKcc FOX5Eme2wQMM1yFdpFzj/gCqfXTs3N/PeHE6dtNqloelN+OBVu058WvXXa0skj1A93dl kC2ENEV5yJ+BqCpaprzkJHgET5CC8EHONpl+6SkNcXV/nQ9aLydrq+MqAhmi6fJRv8II HKKwdmDcNpr0YYgAVCdYApoTEVTNn0iWw6tc1vWUCFH8gnIrA2XOcUaF5lB+834/0Xyo 1lJQ== X-Gm-Message-State: AOAM532lU5MMtkg958SKUkTDl6vv69tuqw9h8SLN9/JjA4yfdgP21igg gkz1ymMrzA9eDiRmZ3ow8/usjRkdmt4x4cHiqKiQ3DhuCWc= X-Google-Smtp-Source: ABdhPJx3qw8zQsBXQcKP2JGls2iFwYgT5s85nFCzVjdgTtIB5HF1Hbw8OZd7yjZDsmyqinGi8aKleeH1NXr21CvmLZU= X-Received: by 2002:a1f:2bd4:: with SMTP id r203mr1171518vkr.8.1626975677158; Thu, 22 Jul 2021 10:41:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nick Sullivan Date: Thu, 22 Jul 2021 13:41:01 -0400 Message-ID: To: Richard Barnes Cc: Messaging Layer Security WG Content-Type: multipart/alternative; boundary="0000000000004bf7c705c7b9cb46" Archived-At: Subject: Re: [MLS] Progress update; cancel MLS meeting at IETF 111? X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2021 17:41:25 -0000 --0000000000004bf7c705c7b9cb46 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MLS group, We're going to cancel the IETF meeting next week and look into setting up an interim in the near future. Best Nick & Sean On Mon, Jul 19, 2021 at 11:56 AM Richard Barnes wrote: > Hi all, > > We MLS protocol spec editors wanted to provide an update on plans and > progress as we approach the IETF meeting. The short version here is: We > should probably cancel the MLS meeting at IETF in favor of a meeting abou= t > a month later. > > On the interop front: The MLSpp and OpenMLS teams have been having > periodic interop calls, and are getting close to interop. As of this > writing, the two stacks are interoperating on all test vectors except the > TreeKEM test vector. The next phase is to verify compatibility on protoc= ol > operations, which we plan to ramp up work on in August, with a goal of > getting verified interop by the end of the month. Other implementations > are of course welcome to join in! We are coordinating on Wire; please le= t > me know if we should add you to the channel. > > On the spec front: The last interim flagged several issues we had where > the authors were going to propose a way forward, and we haven=E2=80=99t m= ade > progress on any of them. We are planning to accelerate work on this in > August, with a goal of having most of the outstanding PRs and issues done > by about the same time as the interop work. Obviously, please file any > remaining PRs/issues ASAP. > > With all that, it looks like we=E2=80=99ll be in a good position to issue= WGLC in > ~September. Instead of meeting in a couple of weeks at the IETF, it woul= d > probably be more effective to meet at the end of August / early September > to look at any last lessons learned from interop testing, and any > non-trivial PR/issue resolutions that need WG attention. > > Cheers, > > Richard and Raphael > _______________________________________________ > MLS mailing list > MLS@ietf.org > https://www.ietf.org/mailman/listinfo/mls > --0000000000004bf7c705c7b9cb46 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
MLS group,

We're going to cancel th= e IETF meeting next=C2=A0week and look into setting up an interim in the ne= ar future.

Best
Nick & Sean

On = Mon, Jul 19, 2021 at 11:56 AM Richard Barnes <rlb@ipv.sx> wrote:

Hi all,


We MLS protocol spec= editors wanted to provide an update on plans and progress as we approach t= he IETF meeting.=C2=A0 The short version here is: We should probably cancel= the MLS meeting at IETF in favor of a meeting about a month later.<= /p>

On = the interop front: The MLSpp and OpenMLS teams have been having periodic in= terop calls, and are getting close to interop.=C2=A0 As of this writing, th= e two stacks are interoperating on all test vectors except the TreeKEM test= vector.=C2=A0 The next phase is to verify compatibility on protocol operat= ions, which we plan to ramp up work on in August, with a goal of getting ve= rified interop by the end of the month.=C2=A0 Other implementations are of = course welcome to join in!=C2=A0 We are coordinating on Wire; please let me= know if we should add you to the channel.


On the spec front: The last = interim flagged several issues we had where the authors were going to propo= se a way forward, and we haven=E2=80=99t made progress on any of them.=C2= =A0 We are planning to accelerate work on this in August, with a goal of ha= ving most of the outstanding PRs and issues done by about the same time as = the interop work. Obviously, please file any remaining PRs/issues ASAP.


With all that, it looks like we=E2=80=99ll be in a good position to issue= WGLC in ~September.=C2=A0 Instead of meeting in a couple of weeks at the I= ETF, it would probably be more effective to meet at the end of August / ear= ly September to look at any last lessons learned from interop testing, and = any non-trivial PR/issue resolutions that need WG attention.


=

= Cheers,

Ri= chard and Raphael

_______________________________________________
MLS mailing list
MLS@ietf.org
https://www.ietf.org/mailman/listinfo/mls
--0000000000004bf7c705c7b9cb46-- From nobody Sun Jul 25 01:31:07 2021 Return-Path: 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 3BA8E3A1C74 for ; Sun, 25 Jul 2021 01:31:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=E+QF9klz; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PITX5HI/ 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 xwTFCi0j-ISa for ; Sun, 25 Jul 2021 01:30:59 -0700 (PDT) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73FE53A1C70 for ; Sun, 25 Jul 2021 01:30:59 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 705F95C00D9 for ; Sun, 25 Jul 2021 03:34:10 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 25 Jul 2021 03:34:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm3; bh=He5hF+u4nVf FDxdC+1ftc/gNf7izwUjIqIs8ArbD3U8=; b=E+QF9klzsLheqINpuZ2TP5hpwCG 7Jwc6pLBIT1C91pI3Q2mrQVvIN3kkKz3q2wkzC8EG8OUDhDxnXhYAkqicdSeA7y4 8HWdCNq6FW76JKOSMSp8gOVaamWNPr7UVJt0oYmH0NEbENLtLeN2YJwrhWViRcLn LhIxMhgmM9ToD0G1qTcnN8JxWC7NCWDWN/pdlMik/XEuPCuetzXCcrRpe3dP1UrR nThaG9o4DpNkIOPXZCH8O11HujhbFJG8HBtL0uCwwibreGECAbqtQvS3fvaS75aH 0RHYiR16NGw+BvwlQv/oyn2Ghbo7T8FXxtyqYq3jRRwC/0KZjFFCPzl8r3w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=He5hF+u4nVfFDxdC+1ftc/gNf7izwUjIqIs8ArbD3U8=; b=PITX5HI/ 7jrBnbEX/tLGbjM1150OvRMmxxQC1xG16QL6/9PHtRIqhcW4euGka8p2qUqcJS6K o/ny01frZlXRrfBSLti3ZwBsDRelfyl+99e4pnlQVtfzDusvWJdp/fpshsehkmtp IJwiMnaaUrNKN5wY5Duk38WeR+5AAHRLCwD/t8IB/vbH+yeceoH9gZ3EXji0bFii dvT/InSTNvL6Lxet6+qX7gqu5/xEB3roJhExqZw8i6Bc+/5IiaxAAk1qsCirVhF3 fFSIldwIbI6h9TcAjTK8BVahGxJkx7qVqkRHiayeUv5jDvfK1RsjE/L/wiRKWzRU QXbDlOFhr1jc9Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrgedugdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenuc fjughrpegtggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicu tegtthhivhhithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihse hmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeefvdduteejvdefkeehieevuefg fefhteetveegffekffefteffvdelheduieetnecuffhomhgrihhnpehgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpedvnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 25 Jul 2021 03:34:10 -0400 (EDT) Content-Type: multipart/alternative; boundary="===============8644529234402072539==" MIME-Version: 1.0 From: Repository Activity Summary Bot To: mls@ietf.org Message-Id: <20210725083059.73FE53A1C70@ietfa.amsl.com> Date: Sun, 25 Jul 2021 01:30:59 -0700 (PDT) Archived-At: Subject: [MLS] Weekly github digest (MLS Working Group summary) X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2021 08:31:04 -0000 --===============8644529234402072539== MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; format="flowed" Pull requests ------------- * mlswg/mls-protocol (+2/-1/=F0=9F=92=AC0) 2 pull requests submitted: - Clarify signature encoding (by franziskuskiefer) https://github.com/mlswg/mls-protocol/pull/475=20 - Explicit blank cases in MLSPlaintextTBS (by eiqo) https://github.com/mlswg/mls-protocol/pull/474=20 1 pull requests merged: - Explicit blank cases in MLSPlaintextTBS https://github.com/mlswg/mls-protocol/pull/474=20 Repositories tracked by this digest: ----------------------------------- * https://github.com/mlswg/mls-architecture * https://github.com/mlswg/mls-protocol * https://github.com/mlswg/mls-federation --===============8644529234402072539== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Weekly github digest (MLS Working Group summary)

Sunday July 25, 2021

Pull requests

mlswg/mls-protocol (+2/-1/=F0=9F=92=AC0)

2 pull requests submitted:

1 pull requests merged:

Repositories tracked by this digest:

--===============8644529234402072539==-- From nobody Tue Jul 27 14:29:04 2021 Return-Path: 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 DA0753A087F for ; Tue, 27 Jul 2021 14:29:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 KglbkP2wKeN8 for ; Tue, 27 Jul 2021 14:28:58 -0700 (PDT) Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 7D1293A0875 for ; Tue, 27 Jul 2021 14:28:58 -0700 (PDT) Received: by mail-qk1-x732.google.com with SMTP id z24so206260qkz.7 for ; Tue, 27 Jul 2021 14:28:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :cc:to; bh=TsbhyQanzhR1jnNk5ME44qAQVhoBnwdF2qgGoPWPErE=; b=QUxvHLRhFw0E9X1HO4M/kb+3okF9/y7RBEMgP30AOeZjW+VwnhaiJR+TQk82pSfguQ XmSKUHaBqELYvFXNqFMGJN+y+6JwayDyhlxuYOnUB6KbEMeLdcmGRxJ7lquB1/zr0AXG 9DfjAqZFUyyEoXFmoCr9Pu3GtVWypF9EEsMMs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:cc:to; bh=TsbhyQanzhR1jnNk5ME44qAQVhoBnwdF2qgGoPWPErE=; b=XVVKcma2am5oXtc/gM+GeTNsqLqBOBbko5LJ4CKbuoBB5Fm3yng4lfWaDi+4lxViSM uoxD0eJ2/ejtPnhhZ6i1yTRFC45952Z/Id9V6MQuSu0Y8XjbG7cErq7eepv4J+gm9MFX HOdWbYiq0BZU7ICV8Ea9V/cx585inPlx7CD6Kwm9JyD5X2dSIX51HRIRK6lE2b+sSk82 RKyVNrZY6ZRPNvO94wp7t72P+/LQPgoiz/VvksdaRpL2v6h+e7mWz54b7SEeQdBAGxpw 58x2mEKOoBITfbIkOzND7ClvHVfidFQ3gNbulxel/KvuqicrIW2l3RshlEQdvKr51VWf x+RA== X-Gm-Message-State: AOAM533eMwU6C7EEf95I3oiey8qYWeMTon5XXovBZyantY7T6YqKSfbq D2mxVlPfAdUSMgiRYgvqaAwxEw== X-Google-Smtp-Source: ABdhPJzFJfJzv6cTVjvFNlihV3yTFXQESYTNLG1M6hModeXeqCUy5MNk8jfhAHmk2MMdCx/v5hzBbw== X-Received: by 2002:ae9:e311:: with SMTP id v17mr24700328qkf.283.1627421336941; Tue, 27 Jul 2021 14:28:56 -0700 (PDT) Received: from smtpclient.apple (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id v5sm2298444qkh.39.2021.07.27.14.28.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Jul 2021 14:28:56 -0700 (PDT) From: Sean Turner Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Message-Id: <43837BDF-7D19-4FDA-B914-CE4902900D47@sn3rd.com> Date: Tue, 27 Jul 2021 17:28:55 -0400 Cc: MLS List To: IETF SAAG X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: [MLS] mls@ietf11: saag report X-BeenThere: mls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Messaging Layer Security List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jul 2021 21:29:03 -0000 MLS meeting canceled. Planning and interim sometime late August. spt (for the chairs)