Re: [Moq] Encrypted Media Metadata

Ted Hardie <ted.ietf@gmail.com> Thu, 21 July 2022 09:16 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: moq@ietfa.amsl.com
Delivered-To: moq@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A7D2C157B53 for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 02:16:10 -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=unavailable 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 RW7XRPLzpgU3 for <moq@ietfa.amsl.com>; Thu, 21 Jul 2022 02:16:08 -0700 (PDT)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 BA8A5C157B39 for <MoQ@ietf.org>; Thu, 21 Jul 2022 02:16:02 -0700 (PDT)
Received: by mail-il1-x135.google.com with SMTP id v1so510453ilg.4 for <MoQ@ietf.org>; Thu, 21 Jul 2022 02:16:02 -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=1qaEhqctjw/+pdVcYCHdVB/NKcBriu1+Zaz0jGEoiuo=; b=AZmBO4W7XZ9tqsmi5g1NF0L+9swA26BySznw9MkYLiA6/HYGT81pv5O6to4Kavmlx4 AK62tOz9eoe4S9Kt1ffTt9GIrlQyU7e2x1MMW7GyQM5Cko5JhIz6Ur9lS8HGrJVW82Ba uSqLcqLXtbNY9h7VhivpjlEE8edFQZMaVWR0SMsEpoth76ff5nQzHCxYQ7Ml0xty1mZr BVHPWaanePSQF5yhexWeCiK5MPLFKw+wx/2LPjy616WX79H79hfUHU6YNqXjh6ilnHCz z+qhHWtQtvaokYRuHk2LWqoKwojgaP3VgAr/tAkNs95eIw2dmyn8xzK8n/w1466Zmmq6 syhQ==
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=1qaEhqctjw/+pdVcYCHdVB/NKcBriu1+Zaz0jGEoiuo=; b=b0p45uX/gXKPHoTEKbHvOKG8xdlquW7UCTHadi8ABtjaKl34XVAWmidb3gmk6rXAum IYSJgwNfBuP1Xt7qvaeDZoIMYZx62l3L6Mw80KnGSTpLQxKlxb2h/k3pMpqGQYhDWR2a +PZhQNkDJLrccmM76ltGfm+TJhJs8z7lRUkW3ywTNKwPm8poJZiqSmamyE0kvEKlakfT 44dhhPTuLbZ3cBFZBUaMu5up2UJl8fu03YzBr5Ah4POmf1kfOuB/yGcfQ1wk6k3vyGDl w7nxAwZg269YWIUC0JknrcRBCg5FT3ul3D6esXM70+jdVKB+SPps7JhRyryIA+NzImdS k0sw==
X-Gm-Message-State: AJIora8ylAShB8Sgm9dL60dkER2mXoGuy5WGWJVA3WLFbX6dH+rM/cEq qWUpJY24x9kprgKCLC4nU85akcSFko72icLVwZs=
X-Google-Smtp-Source: AGRyM1uSZtbSgFvSNs+WTeeA0JHmwJqvXBFfatE+xdLMbA9eTnLYkmEHLNriWs6ldy6Ukw3xMOI/ePvibdPPGw1dKVo=
X-Received: by 2002:a05:6e02:1be9:b0:2dc:68b5:4c55 with SMTP id y9-20020a056e021be900b002dc68b54c55mr20366678ilv.93.1658394962065; Thu, 21 Jul 2022 02:16:02 -0700 (PDT)
MIME-Version: 1.0
References: <LV2PR11MB604522717FFF34A5D066A9EEEA8D9@LV2PR11MB6045.namprd11.prod.outlook.com>
In-Reply-To: <LV2PR11MB604522717FFF34A5D066A9EEEA8D9@LV2PR11MB6045.namprd11.prod.outlook.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 21 Jul 2022 10:15:36 +0100
Message-ID: <CA+9kkMC+Zx-a=WLo+zQuw3f1=JnEGUKTR3pF2ONt94L_eZYVoA@mail.gmail.com>
To: "Deen, Glenn" <Glenn_Deen=40comcast.com@dmarc.ietf.org>
Cc: "MoQ@ietf.org" <MoQ@ietf.org>, "Deen, Glenn" <Glenn_Deen@comcast.com>
Content-Type: multipart/alternative; boundary="0000000000009c821205e44d2af3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/4FFthWvsqDFl8tArh-8-e3VEs8k>
Subject: Re: [Moq] Encrypted Media Metadata
X-BeenThere: moq@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Media over QUIC <moq.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/moq>, <mailto:moq-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/moq/>
List-Post: <mailto:moq@ietf.org>
List-Help: <mailto:moq-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/moq>, <mailto:moq-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2022 09:16:10 -0000

Hi Glenn,

I think I follow your core concern, but I'm a little confused about how to
reflect it in the charter in ways that don't start to assume the solution
space.  From your perspective are you looking for an elaboration to one of
these bullets:

The media publication protocol will be a push protocol for sending media
including audio, video, and timed metadata, such as closed captions and cue
points. The common protocol for publishing media over ingest and
distribution will support:

   - one or more media formats,
   - an interoperable way to request media and encodings,
   - rate adaption strategies based on changing codec rates, changing
   chosen media encoding/qualities,
   - cache friendly media mechanisms

So that they specifically mention the metadata in, for example, the bullet
about requesting media and encodings?  Or are you looking to add a bullet
here?

If you have charter text in mind, or can develop some, that would be most
helpful.

thanks,

Ted

On Sun, Jul 17, 2022 at 2:10 PM Deen, Glenn <Glenn_Deen=
40comcast.com@dmarc.ietf.org> wrote:

> I get the sense from the proposed charter Media Metadata is currently
> treated sort of monolithically in terms of access to it, its
> encryptability, and its use in different workflows.  Metadata is quite rich
> as a part of the media delivery workflow and is getting increasingly
> important and extensive as media transport and media types evolve.  I
> propose that it needs more specific focus in the group.
>
>
>
> Metadata data and access to it is something that maybe should be
> considered a distinct type of media content on its own along with having
> distinct from the transported media authenticated access and encryption
> considerations that are independent of the media being transported.
>
>
>
> This could possibly be part of the “coordinated or cooperative” middle
> boxes that Lucas has mentioned in his not on the thread “Re: [Moq] "MoQ
> Architecture" question from Spencer's mail”
>
>
>
> Metadata should be more distinctly mentioned in the charter along with
> perhaps a couple of documents that specifically cover Metadata
> authentication and encryption and Metadata Use Cases by both end points and
> middle boxes.
>
>
>
> -glenn
> --
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq
>