[AVTCORE] Re: Call for adoption (CfA) of "Viewport and Region-of-Interest-Dependent Delivery of Visual Volumetric Media"

[Xavier de Foy <[e-mail]>]

Here is some context info from (my understanding of) a conversation
with a co-author, which can illustrate how this draft is complementary
to the existing WG draft on V3C "RTP Payload Format for Visual
Volumetric Video-based Coding".

While the WG draft on V3C enables the transport of V3C media as
defined in ISO/IEC 23090-5, it does not enable a receiver to define a
region of interest that it wishes to receive (e.g., a group of tiles)
within a V3C media.

This feature is called "partial access and delivery" and is defined in
ISO/IEC 23090-10 for media stored in an ISO base media file format.
For real-time media communication, we need to support the same
feature, and it is defined in this draft.

For this reason, I support adoption of "Viewport and
Region-of-Interest-Dependent Delivery of Visual Volumetric Media”.

Regards,
Xavier.

On Fri, Jul 12, 2024 at 1:23 PM Jonathan Lennox
<jonathan.lennox=[e-mail]> wrote:
>
> I apologize — I obviously copied and pasted from a previous call for adoption.
>
> Your responses should of course contain one of *these* following:
>
> * I support adoption of "Viewport and Region-of-Interest-Dependent Delivery of Visual Volumetric Media”.
>
> * I object to adoption of "Viewport and Region-of-Interest-Dependent Delivery of Visual Volumetric Media" due to the following open Issues: <link to filed issues>
>
> My apologies!
>
> Jonathan Lennox
> For the Chairs
>
> On Jul 12, 2024, at 4:15 PM, Jonathan Lennox <[e-mail]> wrote:
>
> This is a call for adoption of "Viewport and Region-of-Interest-Dependent Delivery of Visual Volumetric Media”. The draft is available for inspection here:
>
> https://datatracker.ietf.org/doc/draft-gudumasu-avtcore-rtp-volumetric-media-roi/
>
> The call for adoption will run until Midnight Pacific Time on Friday, July 26, 2024 — the end of the IETF meeting week.
>
> We will also ask the group in person at the meeting on July 22.
>
> In response, please indicate one of the following:
>
> * I support adoption of "RTP Payload for Haptics”.
>
> * I object to adoption of "RTP Payload for Haptics" due to the following open Issues: <link to filed issues>
>
> Jonathan Lennox
> For the Chairs
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> To unsubscribe send an email to [e-mail]