Re: [AVT] I-D Action:draft-ietf-avt-rtp-rfc3984bis-08.txt

["Charles Eckel (eckelcu)" <eckelcu at cisco.com>]

As written, I can see how the SDP negotiation is used to determine to
the maximum capabilities of the receivers (max-mbps, max-fs, max-br,
etc.). Once these maximums are determined, it is often the case that
multiple combinations of frame rate and resolution are possible. For
example, it may be possible to receive the following:

720p at a low frame rate
4CIF at a medium frame rate
CIF at a high frame rate

I do not see any mechanism to indicate a preference among these. It
seems such a mechanism would be useful. Am I overlooking something.

Thanks,
Charles

> -----Original Message-----
> From: avt-bounces at ietf.org [mailto:avt-bounces at ietf.org] On Behalf Of
Ye-Kui Wang
> Sent: Monday, September 21, 2009 1:54 PM
> To: avt at ietf.org
> Cc: 'Tom Taylor'; 'Roni Even'
> Subject: Re: [AVT] I-D Action:draft-ietf-avt-rtp-rfc3984bis-08.txt
> 
> 
> The changes compared to -07 are just those sent, by me, to the mailing
list
> on Thursday, 9/17.
> 
> BR, YK
> 
> > -----Original Message-----
> > From: avt-bounces at ietf.org [mailto:avt-bounces at ietf.org] On
> > Behalf Of Internet-Drafts at ietf.org
> > Sent: Monday, September 21, 2009 4:45 PM
> > To: i-d-announce at ietf.org
> > Cc: avt at ietf.org
> > Subject: [AVT] I-D Action:draft-ietf-avt-rtp-rfc3984bis-08.txt
> >
> > A New Internet-Draft is available from the on-line
> > Internet-Drafts directories.
> > This draft is a work item of the Audio/Video Transport
> > Working Group of the IETF.
> >
> >
> > 	Title           : RTP Payload Format for H.264 Video
> > 	Author(s)       : Y. Wang, et al.
> > 	Filename        : draft-ietf-avt-rtp-rfc3984bis-08.txt
> > 	Pages           : 105
> > 	Date            : 2009-09-21
> >
> > This memo describes an RTP Payload format for the ITU-T
> > Recommendation H.264 video codec and the technically
> > identical ISO/IEC International Standard 14496-10 video
> > codec, excluding the Scalable Video Coding (SVC) extension
> > and the Multivew Video Coding extension, for which the RTP
> > payload formats are defined elsewhere.
> > The RTP payload format allows for packetization of one or
> > more Network Abstraction Layer Units (NALUs), produced by an
> > H.264 video encoder, in each RTP payload.  The payload format
> > has wide applicability, as it supports applications from
> > simple low bit-rate conversational usage, to Internet video
> > streaming with interleaved transmission, to high bit-rate
> > video-on-demand.
> >
> > This memo obsoletes RFC 3984.  Changes from RFC 3984 are
> > summarized in section 18.  Issues on backward compatibility
> > to RFC 3984 are discussed in section 17.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-rfc3984
> > bis-08.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > Below is the data which will enable a MIME compliant mail
> > reader implementation to automatically retrieve the ASCII
> > version of the Internet-Draft.
> >
> 
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt at ietf.org
> https://www.ietf.org/mailman/listinfo/avt