Re: [AVT] 2833bis default event support

Flemming Andreasen <fandreas@cisco.com> Tue, 16 December 2003 17:56 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25504 for <avt-archive@odin.ietf.org>; Tue, 16 Dec 2003 12:56:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWJQX-0005UJ-Ik for avt-archive@odin.ietf.org; Tue, 16 Dec 2003 12:56:09 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGHu9SW021046 for avt-archive@odin.ietf.org; Tue, 16 Dec 2003 12:56:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWJQP-0005RS-Fp; Tue, 16 Dec 2003 12:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWJPx-0005Qx-89 for avt@optimus.ietf.org; Tue, 16 Dec 2003 12:55:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25447 for <avt@ietf.org>; Tue, 16 Dec 2003 12:55:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWJPv-00049t-00 for avt@ietf.org; Tue, 16 Dec 2003 12:55:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWJPu-00049m-00 for avt@ietf.org; Tue, 16 Dec 2003 12:55:31 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1AWJPu-00048h-00 for avt@ietf.org; Tue, 16 Dec 2003 12:55:30 -0500
Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 16 Dec 2003 17:55:03 +0000
Received: from cisco.com (sjc-vpn4-75.cisco.com [10.21.80.75]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id hBGHsviN026538; Tue, 16 Dec 2003 09:54:58 -0800 (PST)
Message-ID: <3FDF46F0.94F2C700@cisco.com>
Date: Tue, 16 Dec 2003 12:54:56 -0500
From: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Mozilla 4.79 [en]C-CCK-MCD (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tom Taylor <taylor@nortelnetworks.com>
CC: avt@ietf.org
Subject: Re: [AVT] 2833bis default event support
References: <3FDDD9CF.2080402@nortelnetworks.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
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-Transfer-Encoding: 7bit

I don't see any reason to require (0-15 btw). Implementations can support
whatever events they like and they MUST declare support for all the events
they want to use (0-15 included). It may be worthwhile saying, that for
2833 backwards compatibility, if you receive an SDP with 2833 events and no
fmtp parameter, that you assume events 0-15 are supported.

-- Flemming

Tom Taylor wrote:

> Suppose a receiver indicates support for the telephone-events payload
> type but does not indicate which events it supports.  Do we continue to
> require support for events 0 to 13 in all implementations?
>
> Tom Taylor
>
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www1.ietf.org/mailman/listinfo/avt


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