[AVT] RFC2833(bis): Duration = 0

"Prabhu, Raghavendra" <Raghavendra.Prabhu@intel.com> Fri, 18 October 2002 17:43 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04587 for <avt-archive@odin.ietf.org>; Fri, 18 Oct 2002 13:43:05 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9IHir431652 for avt-archive@odin.ietf.org; Fri, 18 Oct 2002 13:44:53 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9IHhBv31616; Fri, 18 Oct 2002 13:43:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9IHf2v31504 for <avt@optimus.ietf.org>; Fri, 18 Oct 2002 13:41:02 -0400
Received: from hermes.fm.intel.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04443 for <avt@ietf.org>; Fri, 18 Oct 2002 13:38:44 -0400 (EDT)
Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39]) by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc, v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id g9IHdWH27950 for <avt@ietf.org>; Fri, 18 Oct 2002 17:39:32 GMT
Received: from fmsmsxv040-1.fm.intel.com (fmsmsxvs040.fm.intel.com [132.233.42.124]) by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc, v 1.27 2002/10/16 23:46:59 dmccart Exp $) with SMTP id g9IHhof28048 for <avt@ietf.org>; Fri, 18 Oct 2002 17:43:50 GMT
Received: from fmsmsx26.fm.intel.com ([132.233.42.26]) by fmsmsxv040-1.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002101810413000716 for <avt@ietf.org>; Fri, 18 Oct 2002 10:41:30 -0700
Received: by fmsmsx26.fm.intel.com with Internet Mail Service (5.5.2653.19) id <VB7S6M4Q>; Fri, 18 Oct 2002 10:40:56 -0700
Message-ID: <621F928C3A39D61185C700508BB26843072D95B3@fmsmsx101.fm.intel.com>
From: "Prabhu, Raghavendra" <Raghavendra.Prabhu@intel.com>
To: "'avt@ietf.org'" <avt@ietf.org>
Date: Fri, 18 Oct 2002 10:40:55 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [AVT] RFC2833(bis): Duration = 0
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>

Hi listeners,

The draft says

             The special duration value of 0 is reserved to indicate      |
             that the event lasts "forever", i.e., is a state and is      |
             considered to be effective until updated. For robustness,    |
             the sender SHOULD still retransmit the named event           |
             periodically.


1) From an implementation perspective, if we receive Event packet with '0'
duration, is this event supposed to be played out infinitely until either
the 'End-bit' or a new timestamp ?  What are consequences if the 'End-bit'
packets (even if transmitted multiple times) get lost and the other side is
then in a mode of DTX (discontinuous transmission), will this mean the tone
gets elongated beyond actual length ?

2) Also what does RFC2833 say about the expected behaviour when duration is
0 for tone packet (the other kind of rfc2833 packet) ? 

Thanks,
Raghavendra

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