Re: [Sframe] Concluding SFRAME

Bernard Aboba <bernard.aboba@gmail.com> Wed, 27 July 2022 15:53 UTC

Return-Path: <bernard.aboba@gmail.com>
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 8EFACC13633B for <sframe@ietfa.amsl.com>; Wed, 27 Jul 2022 08:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, 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=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZTSFjNcMPWi for <sframe@ietfa.amsl.com>; Wed, 27 Jul 2022 08:53:39 -0700 (PDT)
Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB3E4C136333 for <sframe@ietf.org>; Wed, 27 Jul 2022 08:53:39 -0700 (PDT)
Received: by mail-ej1-x62e.google.com with SMTP id sz17so32256725ejc.9 for <sframe@ietf.org>; Wed, 27 Jul 2022 08:53:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zwfI8JgiH5LST9YQxJ6RfoK9kC3eTlyf7pTnvQGqEFA=; b=S15goNCAdKa5CZj6Fhhuv0H1tFjRUJQFh4C9gNbZSgcF61oV0qddORD0YyOQ0dGMK1 I6+XT3s85VYOiyAQr/gJb7cmJGh4qg5YkaUu8IDw/qQ2kSUeG/liZBX9DzV2kqrGBgNX bjsFhdNgzn5G2iiOQX6dafDBrIT7mVrfXLbpLNmO4Ju/zzsY5UxNjC7vSZufuYJHThR1 jOdnt4Gko8ebdqspsB/gJXzy7vrou0rScOQeRa8o2dFK14qtdCeetsrJM3WpzY/otqAS QA9KNa3trPsSX4HcGncQRfckHdGATML9fA7XAHFZo9IN4/ebKbPkibsuGCM8z2rw1GHn LMOQ==
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=zwfI8JgiH5LST9YQxJ6RfoK9kC3eTlyf7pTnvQGqEFA=; b=Q40yexetw3TxcAlgKTR1KmOb5ltzMvzKUq65Hgxt4uiX6tKqj6LuhqVlFVpwaXRLGM ds2gBlQ91z5LM55Xuq4t5RmyOOkbOYl6C+udXAE4I/Lez/MP6Ip/xGQE1jVYRtEqyOwU cH9dU32DQpp4XQrW3tWu0PcsCuHmiNz8azYd3OM8iz5xNRp0t4cSYPwOBhC1lODg3c10 vSRuif+3EhvXg/vM3h5Z5OlUwNecnosqltuCr3hf0PQKV7t7PKOFbzFbZLZEH04CADnZ tRpqOA86EfYGfxJyTyM4Ota/AvKWi8qIXPl2rLmVvgO3Fd3AkCULzUYT1mw/8fq6TX+y otCA==
X-Gm-Message-State: AJIora/FmWTnM0G021Qi6i+m1vIUJN2pCEMMdsmQhutUvG27Vc/CmJMd JTgZJmauEm0tA1oNUrpYEwi4GTSM53nYrqtHjPaWL/OcvfA=
X-Google-Smtp-Source: AGRyM1u7kBlHlPA4gp+LhH5euYp6UuQnRH9gXjheVhEs6qUsvAqOPalKHPpUYwZstp45pUYif+Ly1f/WhOIKS4/ptk8=
X-Received: by 2002:a17:907:2c75:b0:72b:3431:2a0a with SMTP id ib21-20020a1709072c7500b0072b34312a0amr18830576ejc.234.1658937218042; Wed, 27 Jul 2022 08:53:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwYJz930r+P=5bO8UZYHYuBDuW69MwWCE67BEQTOFnXw4g@mail.gmail.com> <BYAPR06MB4037B9AD4403A8ECA6FB090291979@BYAPR06MB4037.namprd06.prod.outlook.com> <81CC8365-A73B-4E06-BB4F-0846E721B675@apple.com> <CAL0qLwa8UMYanaK70etDAs33yFMGn7Pd85mWAFw0mZKumR7iQQ@mail.gmail.com> <FC861097-3B4F-405B-A662-74AF544623FF@apple.com>
In-Reply-To: <FC861097-3B4F-405B-A662-74AF544623FF@apple.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 27 Jul 2022 08:53:26 -0700
Message-ID: <CAOW+2dvzdh_=hrXKQQtJ+3B-J+Bpt+=0n3w+mjFOTb72+PNVXA@mail.gmail.com>
To: Youenn Fablet <youenn=40apple.com@dmarc.ietf.org>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, "Sergio Murillo (CosmoSoftware)" <sergio.garcia.murillo@cosmosoftware.io>, "sframe@ietf.org" <sframe@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000960ebe05e4cb6be1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sframe/DcjeWZG38JBpQh0U9u5sS0RBXbE>
Subject: Re: [Sframe] Concluding SFRAME
X-BeenThere: sframe@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 27 Jul 2022 15:53:43 -0000

Youen said:

"This would mean splitting the current document in two, one which is
format-only specific and another one that would be explainer/architecture
related. This follows suggestions made during the review of the current
document.
The format document would then be referred directly from other specs like
https://w3c.github.io/webrtc-encoded-transform/#sframe.
The plan is to make this happen after the current draft is published as a
WG draft."

[BA] Getting a format-only document out quickly would be very helpful, even
if it can't be published as a WG draft right away.  At this point, the
other WGs (inside and outside of IETF) which depend on SFRAME are looking
for "proof of life".

On Wed, Jul 27, 2022 at 8:46 AM Youenn Fablet <youenn=
40apple.com@dmarc.ietf.org> wrote:

>
> On 27 Jul 2022, at 17:37, Murray S. Kucherawy <superuser@gmail.com> wrote:
>
> On Wed, Jul 27, 2022 at 11:11 AM Youenn Fablet <youenn@apple.com> wrote:
>
>> +1 to what Sergio said.
>>
>> Also, there has been some progress on GitHub, admittedly very slow, to
>> be able to finalise the first WG draft.
>> The latest commit was made 5 days ago.
>> I would expect a first WG draft to happen before the end of this summer.
>>
>
> Youenn,
>
> The change made five days ago appears to be a merge of a bunch of
> automated and other miscellaneous metadata changes, not draft development.
> The last change to the actual draft work I can see was in March, matching
> the last time there was any non-automatic list traffic.
>
> What I don't see much evidence of is that there's likely to be sustained
> working group energy should this draft appear by the end of the summer.
> The working group was chartered in November of 2020 but hasn't adopted
> anything yet.  I believe the chairs are feeling deflated, and I sympathize.
>
> Do you believe we're going to see an active working group here in the near
> future?
>
>
> Sergio and I discussed about this a few weeks ago and we think we will be
> able to contribute actively in a near future.
>
> One area where I think we can make quick and good progress is in
> finalising the format itself.
> We would leave the application level, key management and network
> interaction as follow-up steps.
>
> This would mean splitting the current document in two, one which is
> format-only specific and another one that would be explainer/architecture
> related. This follows suggestions made during the review of the current
> document.
> The format document would then be referred directly from other specs like
> https://w3c.github.io/webrtc-encoded-transform/#sframe.
> The plan is to make this happen after the current draft is published as a
> WG draft.
>
>
> -MSK
>
>
> --
> Sframe mailing list
> Sframe@ietf.org
> https://www.ietf.org/mailman/listinfo/sframe
>