
From nobody Tue Mar  8 15:52:42 2022
Return-Path: <rlb@ipv.sx>
X-Original-To: sframe@ietfa.amsl.com
Delivered-To: sframe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 874103A1BE1 for <sframe@ietfa.amsl.com>; Tue,  8 Mar 2022 15:52:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20210112.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 U3jIIbWCbMNh for <sframe@ietfa.amsl.com>; Tue,  8 Mar 2022 15:52:38 -0800 (PST)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 1184B3A1BDE for <sframe@ietf.org>; Tue,  8 Mar 2022 15:52:37 -0800 (PST)
Received: by mail-qt1-x82d.google.com with SMTP id c4so610380qtx.1 for <sframe@ietf.org>; Tue, 08 Mar 2022 15:52:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20210112.gappssmtp.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=2N1riklOU+GQmkmih2Ny8+d4t2DW8rZoiaQanNVH4NE=; b=lEsjuQ43UxOSZ1Tkz8Da3wV4i9dbE8AIn3KNP+EwUt9SDMEBlndq9EVXHV91iGWgEX iqcRRVm+zpBCTFTiA9nvm2OUeoKuuirERRWZiISWwlx9rxjwDVv/ZB/VbQE3dslzLEXC 4oCmRuhnjdmvuGy0saWit2tvcM2xmFsJ8u/gXX0Ptnyutt/759iZ7oWB3nxo/xGcAiTO 1ECa25uNzkcJUy51TwbCHQFJ+2nXfbcfGWOm3ezMoyrvk3LheoI1yfrtlF8Ipe/G7Zpu qyAnTYKPBP5qDpu9kVrQ4iuWVt7KHxoDjdgcK2giTM8HiyxRwARzgmDjkqcDZAhKoU4W Pbpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2N1riklOU+GQmkmih2Ny8+d4t2DW8rZoiaQanNVH4NE=; b=GK+Sxo3Ui/B/ENAFz/T4KQeWv379N066tnFMdu112BnBHjVcncm3jff1/XsZBA1yeT W9Kv8L7lijr3Etp5w/DsFGgOIY5SVqpVmIC+waWL4WikgqVjwje/ZMdNFVkWvAnzgYQg OpiOwrkpViEatX+/juPLJQ/iYUaBhZMepWimtKIMeEtfZsxCjorRP5eVQGgVRKmrzCDI XjfEM7TCB4n2tcLg7KxDceb08QcWaupyRUmY9hdLpxztuuBTq8tBwPJcqW83cnWVYGNu 80Yr4LnIJcbA4ERoQwrZYGdJk4MKYumfCDJiS5xaQSMG2NSltHqjkHke3kafjHyeLfKd xiuQ==
X-Gm-Message-State: AOAM530IofW+LmGM3V0KgUQQBs09KA7E/43n1CEtNDE6L+iMsP/9qlwd kO+5MJDFcGzoME/vhNUVsNhgWjALc3zAnIO3/mZmSNE0az8S4g==
X-Google-Smtp-Source: ABdhPJw03V9eiDdHwquORoIC8vL36HO5IK9OGoMIfioex8Blbxl6Pv3qRbsCmCq2Cm76+eBZbTGCNZ4nzH1lualilnE=
X-Received: by 2002:ac8:4e82:0:b0:2e1:a1e1:b5c with SMTP id 2-20020ac84e82000000b002e1a1e10b5cmr41780qtp.122.1646783556356; Tue, 08 Mar 2022 15:52:36 -0800 (PST)
MIME-Version: 1.0
From: Richard Barnes <rlb@ipv.sx>
Date: Tue, 8 Mar 2022 18:52:25 -0500
Message-ID: <CAL02cgQM58vEfm2hRnedjaZSLd1rT1vboE+HGxA_LoUBtDLDRQ@mail.gmail.com>
To: sframe@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e61f9b05d9bdaccc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sframe/r_RwaUjC7ZOiY1h9tqQaoTNxFDA>
Subject: [Sframe] PRs!
X-BeenThere: sframe@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Media Frames <sframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sframe>, <mailto:sframe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sframe/>
List-Post: <mailto:sframe@ietf.org>
List-Help: <mailto:sframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sframe>, <mailto:sframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2022 23:52:41 -0000

--000000000000e61f9b05d9bdaccc
Content-Type: text/plain; charset="UTF-8"

Hey all,

It doesn't look like we have a slot at IETF 113, but this still seemed like
a propitious time to re-energize this group.  I've started doing a review
of the spec, and just posted PRs on the first two, non-normative sections:

https://github.com/eomara/sframe/pull/72
https://github.com/eomara/sframe/pull/73

Feedback welcome!  There should obviously be more as I continue working
through the spec.

It seems like we should probably have a virtual interim at some point to
discuss these.

Also, I think we agreed to adopt the draft, so should the authors resubmit
as draft-ietf-sframe-protocol?

Cheers,
--Richard

--000000000000e61f9b05d9bdaccc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hey all,</div><div><br></div><div>It doesn&#39;t look=
 like we have a slot at IETF 113, but this still seemed like a propitious t=
ime to re-energize this group.=C2=A0 I&#39;ve started doing a review of the=
 spec, and just posted PRs on the first two, non-normative sections:</div><=
div><br></div><div><a href=3D"https://github.com/eomara/sframe/pull/72">htt=
ps://github.com/eomara/sframe/pull/72</a></div><div><a href=3D"https://gith=
ub.com/eomara/sframe/pull/73">https://github.com/eomara/sframe/pull/73</a><=
/div><div><br></div><div>Feedback welcome!=C2=A0 There should obviously be =
more as I continue working through the spec.<br></div><div><br></div><div>I=
t seems like we should probably have a virtual interim at some point to dis=
cuss these.</div><div><br></div><div>Also, I think we agreed to adopt the d=
raft, so should the authors resubmit as draft-ietf-sframe-protocol?</div><d=
iv><br></div><div>Cheers,</div><div>--Richard<br></div></div>

--000000000000e61f9b05d9bdaccc--


From nobody Thu Mar 10 00:43:16 2022
Return-Path: <sergio.garcia.murillo@cosmosoftware.io>
X-Original-To: sframe@ietfa.amsl.com
Delivered-To: sframe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA2D33A0AA3 for <sframe@ietfa.amsl.com>; Thu, 10 Mar 2022 00:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level: 
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cosmosoftware-io.20210112.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 5PD5SvJgmXzl for <sframe@ietfa.amsl.com>; Thu, 10 Mar 2022 00:43:10 -0800 (PST)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 85C2C3A02BC for <sframe@ietf.org>; Thu, 10 Mar 2022 00:43:10 -0800 (PST)
Received: by mail-pg1-x530.google.com with SMTP id o26so4148841pgb.8 for <sframe@ietf.org>; Thu, 10 Mar 2022 00:43:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cosmosoftware-io.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Oak0tPNVMGEGb3WGi8lgTdFvzDUcgIAlmlwt26gv3mc=; b=ojnrLnYSu6/rNQ4G2TuuiDrgD2XcLYzuMT0wDv3JtVdHyd0FJkRGAR6iOe1KbgKFPr 7jbPRTKL36Jfb8NXtog2x7i/lcxwEgmm3APL2pBhxSveUtQzPPzZk2lDp+DA7USZNmAp WdTSvQJ3v7TVEnQ2Dp65PVdk1RF4rcuJX4x9RJ6p0mwcgWSQE//3fjI1Sef4B0E7tTH5 n39iAQ/9+zz7AdFm+jgbPPhXm55NFdl9bjjPwj4Bdi5n939atOaeU1et7Stt7LVOZIgH 0WjrAXpp7jGSfUyMs2oYp48wVfF1O/zgZheHfrLpPkOgoOVeIIy3lQwfecKfYGgZ7KTf gEBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Oak0tPNVMGEGb3WGi8lgTdFvzDUcgIAlmlwt26gv3mc=; b=SwMn2/OIGbRsR68A/LH6qrCaUc52cMd7IVRIDSCDXiTY62dGW4B0BSVnBklVd5ozdP VupkWaJDMGFi3NhduDp8JlTHRVfEVg/njALZjs0XQaIKFP1dFkAEQLzJJBUi5yXjazi+ mBrmP/Lu4/8JBQaCxLfFBnZsyFMCFDe7uKkcHc58r/oV0bGtgC+g6jtsRP+iyb7Jk1OM t7bxMoQ5H04slnpCANVLvLkALaicVhJyBtO9WmQzp1cgtCaH2RmjeEcleDhYweRQIlB5 FYTRR6Vo5Pa/zaUNAGBGng9RG/aGvZgDJq+YYgu+t6IvH83YhZmUQHUH4BK2vM+lTuag Cwew==
X-Gm-Message-State: AOAM530esGsaoTWurKw6UbqfSKe3EIQSNkDE+e06KT3Hdv+gyeS2ul84 VOxiWULirzzfzgs3m2hu7v+mzWXrkRubNP2hJ4MXR7dBwXk=
X-Google-Smtp-Source: ABdhPJyWUan/MA3UOrsvwmif7V3dm4PUiYAUlPmD9Lu93KHWcqCGHm/Rncs8jERlMlxFRfM0FxlOErcKSFtMHrJSPMQ=
X-Received: by 2002:a05:6a00:15d5:b0:4f0:fbeb:6007 with SMTP id o21-20020a056a0015d500b004f0fbeb6007mr3939795pfu.17.1646901789320; Thu, 10 Mar 2022 00:43:09 -0800 (PST)
MIME-Version: 1.0
References: <CAL02cgQM58vEfm2hRnedjaZSLd1rT1vboE+HGxA_LoUBtDLDRQ@mail.gmail.com>
In-Reply-To: <CAL02cgQM58vEfm2hRnedjaZSLd1rT1vboE+HGxA_LoUBtDLDRQ@mail.gmail.com>
From: Sergio Garcia Murillo <sergio.garcia.murillo@cosmosoftware.io>
Date: Thu, 10 Mar 2022 09:42:58 +0100
Message-ID: <CANRTqcMASJfyZKOnAiOySmX0mo2bc_0gxuHrDpiUFOGGue4hoA@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Cc: sframe@ietf.org
Content-Type: multipart/alternative; boundary="00000000000022093205d9d93445"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sframe/_pVkq6TFyBp1f_rOFUJvASGl-68>
Subject: Re: [Sframe] PRs!
X-BeenThere: sframe@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Media Frames <sframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sframe>, <mailto:sframe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sframe/>
List-Post: <mailto:sframe@ietf.org>
List-Help: <mailto:sframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sframe>, <mailto:sframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2022 08:43:15 -0000

--00000000000022093205d9d93445
Content-Type: text/plain; charset="UTF-8"

Hi Richard,

Thanks for the PR, I think that the editorial changes are ok, but I have a
concern regarding if we should try first to split the draft, one containing
the SFrame/SPacket description and usage, and another one to only specify
how the encryption process works for  a given blob regardless it is SFrame
or SPacket. Although I guess we can just merge the PRs and then do the
split too.

Best regards
Sergio

On Wed, Mar 9, 2022 at 12:52 AM Richard Barnes <rlb@ipv.sx> wrote:

> Hey all,
>
> It doesn't look like we have a slot at IETF 113, but this still seemed
> like a propitious time to re-energize this group.  I've started doing a
> review of the spec, and just posted PRs on the first two, non-normative
> sections:
>
> https://github.com/eomara/sframe/pull/72
> https://github.com/eomara/sframe/pull/73
>
> Feedback welcome!  There should obviously be more as I continue working
> through the spec.
>
> It seems like we should probably have a virtual interim at some point to
> discuss these.
>
> Also, I think we agreed to adopt the draft, so should the authors resubmit
> as draft-ietf-sframe-protocol?
>
> Cheers,
> --Richard
> --
> Sframe mailing list
> Sframe@ietf.org
> https://www.ietf.org/mailman/listinfo/sframe
>

--00000000000022093205d9d93445
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Richard,<div><br></div><div>Thanks=C2=A0for the PR, I t=
hink that the editorial changes are ok, but I have a concern regarding if w=
e should try first to split the draft, one containing the SFrame/SPacket de=
scription=C2=A0and usage, and another one to only specify how the encryptio=
n process=C2=A0works for=C2=A0 a given blob regardless=C2=A0it is SFrame or=
 SPacket. Although I guess we can just merge the PRs and then do the split =
too.=C2=A0</div><div><br></div><div>Best regards</div><div>Sergio</div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On W=
ed, Mar 9, 2022 at 12:52 AM Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx=
">rlb@ipv.sx</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div>Hey all,</div><div><br></div><div>It does=
n&#39;t look like we have a slot at IETF 113, but this still seemed like a =
propitious time to re-energize this group.=C2=A0 I&#39;ve started doing a r=
eview of the spec, and just posted PRs on the first two, non-normative sect=
ions:</div><div><br></div><div><a href=3D"https://github.com/eomara/sframe/=
pull/72" target=3D"_blank">https://github.com/eomara/sframe/pull/72</a></di=
v><div><a href=3D"https://github.com/eomara/sframe/pull/73" target=3D"_blan=
k">https://github.com/eomara/sframe/pull/73</a></div><div><br></div><div>Fe=
edback welcome!=C2=A0 There should obviously be more as I continue working =
through the spec.<br></div><div><br></div><div>It seems like we should prob=
ably have a virtual interim at some point to discuss these.</div><div><br><=
/div><div>Also, I think we agreed to adopt the draft, so should the authors=
 resubmit as draft-ietf-sframe-protocol?</div><div><br></div><div>Cheers,</=
div><div>--Richard<br></div></div>
-- <br>
Sframe mailing list<br>
<a href=3D"mailto:Sframe@ietf.org" target=3D"_blank">Sframe@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/sframe" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/sframe</a><br>
</blockquote></div>

--00000000000022093205d9d93445--

