RE: [AVT] Inquiry about RFC 4629 (optional parameters in SDP)

Hi,

The reason for this selection of annexes was based on the ones being
used by products in the markets.  There is no need to specify parameters
that are not used.

You can also use annex X based profiles for specifying other application
based profile.

Roni Even

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
A consensus means that everyone agrees to say collectively what no one
believes individually
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 

________________________________

From: Regis Crinon [mailto:regisc@exchange.microsoft.com] 
Sent: Tuesday, September 04, 2007 7:54 AM
To: avt@ietf.org
Subject: [AVT] Inquiry about RFC 4629 (optional parameters in SDP)

Hello everyone,

I have the following question regarding RFC 4629. I would really
appreciate your feedback.

Thank you in advance,

Regis J. Crinon

Fact 1:

H.263+ includes a set of new Annexes: Annex I through T. 

Fact 2:

RFC 4629 account for ONLY a subset of these annexes. See excerpts from
the RFC below:

A list of optional annexes specifies which annexes of H.263 are

      supported.  The optional annexes are defined as part of H263-1998,

      H263-2000.  H.263 annex X [H263] defines profiles that group

      annexes for specific applications.  A system that supports a

      specific annex SHALL specify its support using the optional

      parameters.  If no annex is specified, then the stream is Baseline

      H.263.

      The allowed optional parameters for the annexes are "F", "I", "J",

      "T", "K", "N", and "P".

Question

How are the other annexes signaled? Example: How can I signal that an
H.263+ bistream uses Annex L or Annex M or Annex O or Annex Q or Annex R
or Annex S? It seems that I cannot use SDP to tell a video bitstream
that uses one or more of these annexes from one that does not. Hence the
question.