Re: [dispatch] Request for agenda time for Game Moves over RTP

Cullen Jennings <fluffy@iii.ca> Tue, 08 March 2022 01:15 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39583A0115 for <dispatch@ietfa.amsl.com>; Mon, 7 Mar 2022 17:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWJqkH5goXX9 for <dispatch@ietfa.amsl.com>; Mon, 7 Mar 2022 17:15:07 -0800 (PST)
Received: from smtp111.iad3a.emailsrvr.com (smtp111.iad3a.emailsrvr.com [173.203.187.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8CE13A00E3 for <dispatch@ietf.org>; Mon, 7 Mar 2022 17:15:07 -0800 (PST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp22.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 7F6BD188F; Mon, 7 Mar 2022 20:15:05 -0500 (EST)
Message-ID: <5942a407-7db4-4667-da63-692a1c0d842e@iii.ca>
Date: Mon, 07 Mar 2022 18:15:06 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "dispatch@ietf.org" <dispatch@ietf.org>, Avt@ietf.org
References: <d2022786-737f-7a8b-c735-3a90f5b304e7@iii.ca> <bf4ab3ae9a7c91af51088041c1da16d5d6877e24.camel@ericsson.com>
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <bf4ab3ae9a7c91af51088041c1da16d5d6877e24.camel@ericsson.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Classification-ID: a60aa920-e64f-4578-9cf5-c397611a6687-1-1
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/FZAEDVKxbibNS6BAFbJN3aQueHs>
Subject: Re: [dispatch] Request for agenda time for Game Moves over RTP
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2022 01:15:11 -0000

Perhaps AVTCORE is the right place but I'm not sure. ( Adding Avt@ietf 
to thread  )

This draft is more about defining the encoding of the position of 
objects and players than defining RTP Payload Format. It's more like the 
MIDI 1.0 specification, which I think of as a Media Format, plus the 
stuff in RFC 6295 that defined the Payload Format for MIDI.

This game state draft also needs the RTP Payload Format and clearly the 
expertise for Payload Format is in AVTCORE, but it was less clear to me 
that the other parts of actually defining the data and encoding of what 
goes in the Payload Format is in scope for AVTCORE.

I would be fine with doing this all in AVTCORE if that is all in the 
scope of AVTCORE. I can also imagine some scheme where it got split into 
two drafts (one for payload format and one for media format) but I am 
less keen on that as it just spreads stuff around too much for something 
that is pretty basic.

You have pretty solid history on all groups AVT and what is in scope so 
if you thought this fits in AVTCORE, I would glad to just pursue that 
path. I do want to figure out where to move this forward at this IETF 
and not still be asking where to do the work 6 months from now.



On 3/4/2022 1:54 PM, Magnus Westerlund wrote:
> Hi Cullen,
> 
> As AVTCORE is the WG that is chartered to standardized RTP Payload 
> formats I would think it belongs there. Any specific reason you have for 
> not taking it there? I would note that this appear to have some 
> similarities with the MIDI RTP payload format. Although you appear to 
> indicate that is actually have less problematic issues than what 
> resulted in the recovery journal solution in RFC 6295 
> https://datatracker.ietf.org/doc/rfc6295/ 
> <https://datatracker.ietf.org/doc/rfc6295/>
> 
> I think the input aspects like head, and hands location and direction 
> are fairly straight forward streaming sources that appears to match RTP 
> model for sources.
> 
> Cheers
> 
> Magnus
> 
> 
> On Fri, 2022-03-04 at 12:28 -0700, Cullen Jennings wrote:
>> I would like to figure out how/where to proceed with
>>
>> draft-jennings-dispatch-game-state-over-rtp
>>
>> This draft describes a format for encoding game moves and the state of
>> game objects over RTP. Cisco is using it for an AR/VR hologram
>> conferencing system but there are a range of uses cases.
>>
>> Could we get some time to discuss where to do this work?
>>
>> Thank you, Cullen
>>
>>
>>
>>
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org  <mailto:dispatch@ietf.org>
>> https://www.ietf.org/mailman/listinfo/dispatch  <https://www.ietf.org/mailman/listinfo/dispatch>
>>