IETF Logo Mail Archive

Re: [Sframe] Concluding SFRAME

Youenn Fablet <youenn@apple.com> Wed, 27 July 2022 15:46 UTC

Return-Path: <youenn@apple.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 ECB7BC13CCF8 for <sframe@ietfa.amsl.com>; Wed, 27 Jul 2022 08:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.69
X-Spam-Level:
X-Spam-Status: No, score=-7.69 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.582, 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_HI=-5, 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=apple.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 uTR_mfC4saln for <sframe@ietfa.amsl.com>; Wed, 27 Jul 2022 08:46:05 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp24.apple.com (rn-mailsvcp-ppex-lapp24.rno.apple.com [17.179.253.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32404C16ECC9 for <sframe@ietf.org>; Wed, 27 Jul 2022 08:45:57 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp24.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp24.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 26RFdZ9x030775; Wed, 27 Jul 2022 08:45:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=dr+q99Pce27jn2yBG56vUiivBm00elWj/x7NU6mnJVw=; b=KyVUnhF10yKqrPW0iScmtCdXqoqzQIJj/ujT6MHJqQg3F6axL7fYhVIXj3MEYTi7SAYc /uaFO0D8gFaFBQxO1A7aQ3NUw1S4g2QN821+KGS3O4GWRoqPZ9S74cCapNPy6sk9SlP7 U+jrIR8JSrfoJgXqOus2Xr+51Q3P2QqXy6E9yqjpq+gRYonvMPR7GniU+UPFDkr8LJEK PfeD5hYmTvMJFXklqZ32HWf/G9vD8TQjXShqASmTDG5219gTTUgVAOdYAZdoMYJ6YKbh LoZ//JrfMJy+HW7bZ30Tg8GE5MB8uVt1Sqo0LG+nTzOWBr/dWIEYf+GfObFUtQZ3EcYl yg==
Received: from crk-mailsvcp-mta-lapp03.euro.apple.com (crk-mailsvcp-mta-lapp03.euro.apple.com [17.66.55.16]) by rn-mailsvcp-ppex-lapp24.rno.apple.com with ESMTP id 3hgek9m3dc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 27 Jul 2022 08:45:55 -0700
Received: from crk-mailsvcp-mmp-lapp03.euro.apple.com (crk-mailsvcp-mmp-lapp03.euro.apple.com [17.72.136.17]) by crk-mailsvcp-mta-lapp03.euro.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPS id <0RFO004GWRSHTT10@crk-mailsvcp-mta-lapp03.euro.apple.com>; Wed, 27 Jul 2022 16:45:53 +0100 (IST)
Received: from process_milters-daemon.crk-mailsvcp-mmp-lapp03.euro.apple.com by crk-mailsvcp-mmp-lapp03.euro.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) id <0RFO00A00RP0M600@crk-mailsvcp-mmp-lapp03.euro.apple.com>; Wed, 27 Jul 2022 16:45:53 +0100 (IST)
X-Va-A:
X-Va-T-CD: 9af4f3cab97292f02d929d3c7735f3b4
X-Va-E-CD: d277504602a7f612b6062ec869a6b50e
X-Va-R-CD: 4667316b123c8b26a7859467bdbad792
X-Va-CD: 0
X-Va-ID: f6e5eaec-2f62-4266-b91f-b4becdad7e03
X-V-A:
X-V-T-CD: 9af4f3cab97292f02d929d3c7735f3b4
X-V-E-CD: d277504602a7f612b6062ec869a6b50e
X-V-R-CD: 4667316b123c8b26a7859467bdbad792
X-V-CD: 0
X-V-ID: ca3493ba-d96a-4037-b782-c2b5e0e51c0d
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-07-27_06:2022-07-27, 2022-07-27 signatures=0
Received: from smtpclient.apple (unknown [17.235.198.227]) by crk-mailsvcp-mmp-lapp03.euro.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPSA id <0RFO00B3XRSGOY00@crk-mailsvcp-mmp-lapp03.euro.apple.com>; Wed, 27 Jul 2022 16:45:53 +0100 (IST)
From: Youenn Fablet <youenn@apple.com>
Message-id: <FC861097-3B4F-405B-A662-74AF544623FF@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_495AC850-5D42-4923-AF6C-AB3F2058EA5D"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Date: Wed, 27 Jul 2022 17:45:51 +0200
In-reply-to: <CAL0qLwa8UMYanaK70etDAs33yFMGn7Pd85mWAFw0mZKumR7iQQ@mail.gmail.com>
Cc: "Sergio Murillo (CosmoSoftware)" <sergio.garcia.murillo@cosmosoftware.io>, "sframe@ietf.org" <sframe@ietf.org>
To: "Murray S. Kucherawy" <superuser@gmail.com>
References: <CAL0qLwYJz930r+P=5bO8UZYHYuBDuW69MwWCE67BEQTOFnXw4g@mail.gmail.com> <BYAPR06MB4037B9AD4403A8ECA6FB090291979@BYAPR06MB4037.namprd06.prod.outlook.com> <81CC8365-A73B-4E06-BB4F-0846E721B675@apple.com> <CAL0qLwa8UMYanaK70etDAs33yFMGn7Pd85mWAFw0mZKumR7iQQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3696.100.31)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-07-27_06:2022-07-27, 2022-07-27 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sframe/f5j0Jp0H4-YRH0vIzy57TFzj7As>
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:46:09 -0000

> 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 <mailto: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 <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

v2.23.0 | Report a Bug | By Email