Re: [Moq] Call for Adoption: Use Cases and Requirements for Media Transport Protocol Design

Cullen Jennings <fluffy@iii.ca> Sat, 03 June 2023 14:43 UTC

Return-Path: <fluffy@iii.ca>
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 98F9BC151095 for <moq@ietfa.amsl.com>; Sat, 3 Jun 2023 07:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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
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 YiLBhULlqy9T for <moq@ietfa.amsl.com>; Sat, 3 Jun 2023 07:43:36 -0700 (PDT)
Received: from smtp112.iad3a.emailsrvr.com (smtp112.iad3a.emailsrvr.com [173.203.187.112]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7652C151099 for <moq@ietf.org>; Sat, 3 Jun 2023 07:43:36 -0700 (PDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp31.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 6C8F821F6E; Sat, 3 Jun 2023 10:43:35 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CA+9kkMBCA9+WNYu+Mi6Vkq-T3GeDHWdGo+4vK8dbAy_cF1hXCA@mail.gmail.com>
Date: Sat, 03 Jun 2023 08:43:24 -0600
Cc: moq-chairs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C7457D7-CDCC-4585-A361-1D75DBA0762C@iii.ca>
References: <CA+9kkMBCA9+WNYu+Mi6Vkq-T3GeDHWdGo+4vK8dbAy_cF1hXCA@mail.gmail.com>
To: MOQ Mailing List <moq@ietf.org>
X-Mailer: Apple Mail (2.3731.500.231)
X-Classification-ID: 73ef6e13-2676-40de-95e7-10e35ed77305-1-1
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/0hG6MYz4PWwPEsEqd4JyyVlMgvI>
Subject: Re: [Moq] Call for Adoption: Use Cases and Requirements for Media Transport Protocol Design
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: Sat, 03 Jun 2023 14:43:40 -0000

I realize that it is a bit past April 14 but this thread never seemed to reach consensus. 

I think the -05 draft ( draft-gruessing-moq-requirements-05 ) looks ready for WG adoption of me. 

Not really related to the draft but more about the WG milestones …  There is one part I strongly disagree with and that is not requesting publication as an RFC. I feel this is a huge amounted of work to do a document like this, and if we are doing it, it should be finished in the sense we know it represents the IETF consensus on this work and should be published as an RFC. It is unreasonable to ask people to do this much and not provide them with concrete recognition of completing it.  I think if the WG is going to bother to do this work, we should expect it to be published. 

I would like to propose that the WG should ask the AD to add a milestone for:
* Forward Protocol Specification for Use Cases and Requirements document for Media over QUIC draft to IESG



> On Mar 25, 2023, at 4:09 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
> 
> Dear colleagues,
> 
> This is a call for working group adoption for "Media Over QUIC - Use Cases and Requirements for Media Transport Protocol Design" (https://datatracker.ietf.org/doc/draft-gruessing-moq-requirements/).  Because it is being issued during the IETF week, we will allocate a slightly longer period than normal, and the call for adoption will conclude on April 14, 2023.
> 
> Given that the working group has a number of participants who are new to the IETF, the chairs would like to remind folks that a call for adoption represents a decision by the working group that the input document is a reasonable basis upon which to build one of the chartered deliverables of the working group.  Further changes are expected; the difference is that change control moves to the working group.
> 
> Please send comments on the adoption to the list.
> 
> regards,
> 
> Ted and Alan
> -- 
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq