On Fri,= Aug 31, 2012 at 12:12 PM, Stephan Wenger <stewe@stewe.org> wr= ote:

Hi,

I had a quick look at the diff file only. =A0I think the introduction of th= e
two new (optional) parameters max_fs and max_fr address the concerns I
raised earlier. =A0I hope implementers will read 6.2.2 carefully and
understand that "optional" really meant "conditionally manda= tory" :-)

The one substantial thing that needs further discussion (though not
necessarily a change in the draft, IMO), is Sandy's idea of including a=
parameter for signaling the maximum number of coefficient
partitions--something that apparently may be useful for multi-threaded
decoders. =A0You google guys may want to comment on his idea.

A small nit for section 6.2.2: the final sentence of the section starts
with "In *many* practical applications, the max frame size and max fra= me
rate are known from other information; [...]". =A0I personally don'= ;t believe
that the word "many" is justified, and it may even be misleading.= =A0I would
claim that in the vast majority of video-over-RTP implementations, there is no pre-arranged knowledge of decoder capabilities before the
negotiation. =A0I don't see why VP8 is different here. =A0I believe tha= t not
even in the webrtc case (which is, AFAIK, the main customer for this
payload format) there is pre-arranged knowledge of receiver capabilities. So perhaps it's better to replace "many applications" with &q= uot;some
applications".

Regards,
Stephan

On 8.31.2012 09:59 , "inte= rnet-drafts@ietf.org" <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 Workin= g
>Group of the IETF.
>
> =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : RTP Payload Format for VP8 Vid= eo
> =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Patrik Westin
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Henrik F Lundin
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Michael Glover
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Justin Uberti
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Frank Galligan
> =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-payload-vp8-05.txt > =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 29
> =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-08-31
>
>Abstract:
> =A0 This memo describes an RTP payload format for the VP8 video codec.=
> =A0 The payload format has wide applicability, as it supports
> =A0 applications from low bit-rate peer-to-peer usage, to high bit-rat= e
> =A0 video conferences.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-payload-vp8<= br> >
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-payload-vp8-05
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-payload-v= p8-05
>
>
>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