Re: [Moq] New Version Notification for draft-gruessing-moq-requirements-04.txt
James <james.ietf@gmail.com> Mon, 13 March 2023 17:19 UTC
Return-Path: <james.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 F2247C1524D3; Mon, 13 Mar 2023 10:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 SQmECASKdbDC; Mon, 13 Mar 2023 10:19:55 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 6501AC152565; Mon, 13 Mar 2023 10:19:55 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id cn21so21504919edb.0; Mon, 13 Mar 2023 10:19:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678727994; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=/oJ6zuo6Hq4NDp3SWypB/+2fQHxwusF6Yp//D8+atzQ=; b=iEwiUyW8kpd7BgBrekI9h3eVd/DCZZADq/VO0xWQkzBncGDURGuFwKoqCDv6QiSAkd gR+TsxRlKp9ZosrdvRlHJ+faOgw2LuQNwrbX+5M1wIuY80lHb0TDyJxsXvLXVGnxKmIn zYPZmvGXPvaV12l1Rq7Mdgux1+F2TQzHiFfRhhClHLytvp3N0LL6VCpkW588mgCUvPiJ L7hvggiSUoL9GlwmblB1syrMDUzpZB2suF9Czi1imbRMZGK/q5OfzEmMNVRkaxgu4jPZ YerNr8mPpqedrjKCejl5Aie5KTSn1lic0DsVQEdJ4AJKjGOc09zfda2fuU4sBI/7gOqi ghHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678727994; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=/oJ6zuo6Hq4NDp3SWypB/+2fQHxwusF6Yp//D8+atzQ=; b=vZJXM8ZbORhTnEuZCGAuKwbwq+qxzJhDSZqKk3ViFS1h3E8A4Jslno7viQGdKrZsge C3S1546FtbhSES/cnyCXMelXjdGo74ME2gplUIl+z1J6P4S8Ofk6A4JUKgwiO5ppXOO7 LD6CrlL4LrqbnOOVPeLbyPvQvd5rpJd7yj9VbXKilC7oLwExRCY/nLtEwF35+8EpYgyw 1g+DvwxsC48Ios3AfLW/tCDAk9kLnabG2Zdv3+X23ZSBNRnvsanWtGpDculBpufWyXPY vHLfqAOfU+GUuIcmdMaWzALnzxukpdlSnM6Yq1O0o7xhL6v0yud8R2izjluTK8pajoFe k/EQ==
X-Gm-Message-State: AO0yUKUHoi63wy6eDM6OPtT+Qxg3M9aeTb+82F4PW7aTNWH2bzRuh3/F pieZ4OlNkoiAh/retXTB6JxUNFwr8Rk=
X-Google-Smtp-Source: AK7set9JswnopTi91JJv4mhkmJYcP7XMtMRtwP6SGE4dGxTsTmEuL9ApKhrnh9VRzKQtufzIvszHeA==
X-Received: by 2002:aa7:c9c9:0:b0:4fa:8aa4:8d8b with SMTP id i9-20020aa7c9c9000000b004fa8aa48d8bmr6553216edt.7.1678727993678; Mon, 13 Mar 2023 10:19:53 -0700 (PDT)
Received: from smtpclient.apple (2a02-a468-ca02-2-1021-3c15-a2a8-9f2e.fixed6.kpn.net. [2a02:a468:ca02:2:1021:3c15:a2a8:9f2e]) by smtp.gmail.com with ESMTPSA id z4-20020a170906714400b008e53874f8d8sm37313ejj.180.2023.03.13.10.19.52 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Mar 2023 10:19:53 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: James <james.ietf@gmail.com>
In-Reply-To: <167872749284.24423.10467174102919502134@ietfa.amsl.com>
Date: Mon, 13 Mar 2023 18:19:42 +0100
Cc: moq@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <72FD9DA7-63F0-4553-98C7-CFEE9A9D5AD9@gmail.com>
References: <167872749284.24423.10467174102919502134@ietfa.amsl.com>
To: moq-chairs@ietf.org
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/K3vUxyofJteGec20_WgB89-c-8A>
Subject: Re: [Moq] New Version Notification for draft-gruessing-moq-requirements-04.txt
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: Mon, 13 Mar 2023 17:19:57 -0000
Hi Alan and Ted, Spencer and myself have just before deadline pushed out a new version of our requirements draft (see below). The focus of this version is around the inclusion of requirements based on interim meeting discussions and mailing list activity. We've kept it light on normative language and it's by far complete but believe it should be sufficient enough to start a call for adoption, noting that adopting it does not necessarily mean agreeing with everything contained within and anything can be adjusted pending working group consensus. If you agree that it's ready for adoption call, can you please start the process, and if not let Spencer and myself know what needs to be addressed to get it in the right state? - J > On 13 Mar 2023, at 18:11, internet-drafts@ietf.org wrote: > > > A new version of I-D, draft-gruessing-moq-requirements-04.txt > has been successfully submitted by James Gruessing and posted to the > IETF repository. > > Name: draft-gruessing-moq-requirements > Revision: 04 > Title: Media Over QUIC - Use Cases and Requirements for Media Transport Protocol Design > Document date: 2023-03-13 > Group: Individual Submission > Pages: 14 > URL: https://www.ietf.org/archive/id/draft-gruessing-moq-requirements-04.txt > Status: https://datatracker.ietf.org/doc/draft-gruessing-moq-requirements/ > Html: https://www.ietf.org/archive/id/draft-gruessing-moq-requirements-04.html > Htmlized: https://datatracker.ietf.org/doc/html/draft-gruessing-moq-requirements > Diff: https://author-tools.ietf.org/iddiff?url2=draft-gruessing-moq-requirements-04 > > Abstract: > This document describes use cases and requirements that guide the > specification of a simple, low-latency media delivery solution for > ingest and distribution, using either the QUIC protocol or > WebTransport. > > > > > The IETF Secretariat > >