Re: [AVTCORE] AD Review of draft-ietf-payload-vp9-12

["Murray S. Kucherawy" <[e-mail]>]

Hi Jonathan,

On Fri, May 7, 2021 at 11:31 AM Jonathan Lennox <[e-mail]>
wrote:

> Do you want me to publish a version -13 with the changes mentioned here?
> In the meantime my changes are in the GitHub repo at
> https://github.com/juberti/draughts/tree/master/vp9.
>

Yes, please.


>
> Shepherd writeup:
>
> * We should probably explain why a document coming out of AVTCORE bears a
> name that doesn't start with "draft-ietf-avtcore-...".  The shepherd
> writeup should mention this.  Or if you don't want to do that, please let
> me know what the history is there so I can include it in a note to the IESG.
>
>
> Either in the writeup or in the note is fine, but the history is that the
> Payload Working Group was merged back into the AVTCore group in September
> 2019, whereas this draft was first adopted as a WG item of the Payload
> group in 2015.  (Yes, we’ve been very slow about finishing this draft.)
>

Ah, thanks for that.  I'll do it in the note.  The merger predates the time
of most people on the current IESG, so I'm just hoping to head off any
questions during IESG Evaluation.

No, VP8 and VP9 are two different codecs, and they’re both expected to
> remain in active use.
>

OK, just checking.


>
> * The use of CONDITIONALLY RECOMMENDED or CONDITIONALLY REQUIRED is
> puzzling because one of them is a BCP 14 word and one isn't, but both look
> like they're supposed to be.  This might be better described in the prose
> for each of these fields, and just use the BCP 14 words here (or omit them
> entirely).
>
>
> I’ve made “Conditionally” only initially capitalized, and clarified the
> description of the fields to have capitalized BCP 14 words.
>

OK, that at least looks less strange.  Fair compromise.


> Section 6.1:
>
> * Does the media type's subtype name have to be "VP9", in specifically
> that case?
>
>
> No, media subtype names aren’t case-sensitive.  Do you think it would be
> clearer to write it in lower-case here?
>

Not necessarily.  Again, just checking; there have been media type
applications I've processed in the past that came in in all-caps because
the applicant didn't know they're case-insensitive.

When the new version appears, I'll send it for Last Call.

-MSK