IETF Logo Mail Archive

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

Regis Crinon <regisc@exchange.microsoft.com> Tue, 04 September 2007 17:10 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISbud-0000iX-PV; Tue, 04 Sep 2007 13:10:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISQQk-00089O-O0 for avt@ietf.org; Tue, 04 Sep 2007 00:54:26 -0400
Received: from mail1.exchange.microsoft.com ([131.107.1.17] helo=mail.exchange.microsoft.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ISQQk-0002ea-36 for avt@ietf.org; Tue, 04 Sep 2007 00:54:26 -0400
Received: from df-bhd-02.exchange.corp.microsoft.com (157.54.71.155) by DF-GWY-05.exchange.corp.microsoft.com (157.54.63.146) with Microsoft SMTP Server (TLS) id 8.1.192.0; Mon, 3 Sep 2007 21:54:25 -0700
Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.10]) by df-bhd-02.exchange.corp.microsoft.com ([157.54.71.155]) with mapi; Mon, 3 Sep 2007 21:54:25 -0700
From: Regis Crinon <regisc@exchange.microsoft.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Mon, 03 Sep 2007 21:54:18 -0700
Thread-Topic: Inquiry about RFC 4629 (optional parameters in SDP)
Thread-Index: Acfur6ZGVEANEHQiQ9Kj+olL8t5qHw==
Message-ID: <30C65F3A3407B943826897E025135BE6E6EA2B659D@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Spam-Score: -100.0 (---------------------------------------------------)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
X-Mailman-Approved-At: Tue, 04 Sep 2007 13:10:01 -0400
Subject: [AVT] Inquiry about RFC 4629 (optional parameters in SDP)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1474563646=="
Errors-To: avt-bounces@ietf.org

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.



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

v2.29.0 | Report a Bug | By Email | System Status