Re: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt

I think there may still be an issue with the definition of Horizontal_Offset.  No definition is given for UHD and I'm not sure that the HD definition in terms of Y samples is always applicable.

The ANC data consists of 10-bit words in a 10-bit data stream (or a data channel of a data stream).  The position should be measured in terms of  10-bit words relative to the SAV sequence in the data stream.  A definition along those lines works regardless of the image format (YCbCr, RGB, 10-bit, 12-bit) or the mapping from source image to interface.

John Fletcher
________________________________________
From: payload [payload-bounces@ietf.org] on behalf of Ali C. Begen [ali.begen@networked.media]
Sent: 16 December 2017 14:21
To: payload@ietf.org
Subject: Re: [payload] I-D Action: draft-ietf-payload-rtp-ancillary-13.txt

Payload WG,

Is there any objection to the latest revision that addresses the issues Thomas pointed out earlier? The draft was in the RFC editor queue and if there are no objections, we will soon ship it back there. But to give people a chance to read and officially comment on the revision, I think we should start a new IETF LC for a week.

@Ben, could we do that?

-acbegen

> On Dec 15, 2017, at 10:40 PM, internet-drafts@ietf.org wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Payloads WG of the IETF.
>
>        Title           : RTP Payload for SMPTE ST 291-1 Ancillary Data
>        Author          : Thomas G. Edwards
>       Filename        : draft-ietf-payload-rtp-ancillary-13.txt
>       Pages           : 19
>       Date            : 2017-12-15
>
> Abstract:
>   This memo describes a real-time transport protocol (RTP) payload
>   format for the Society of Motion Picture and Television Engineers
>   (SMPTE) Ancillary data, as defined by SMPTE ST 291-1.  SMPTE
>   Ancillary data is generally used along with professional video
>   formats to carry a range of ancillary data types, including time
>   code, Closed Captioning, and the Active Format Description (AFD).
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-ancillary/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-payload-rtp-ancillary-13
> https://datatracker.ietf.org/doc/html/draft-ietf-payload-rtp-ancillary-13
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-rtp-ancillary-13
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> payload mailing list
> payload@ietf.org
> https://www.ietf.org/mailman/listinfo/payload

_______________________________________________
payload mailing list
payload@ietf.org
https://www.ietf.org/mailman/listinfo/payload