[AVT] RFC 2833bis: open issues

[Henning Schulzrinne <hgs@cs.columbia.edu>]

As requested by Colin, the Vienna discussion items for 2833bis (named 
events and tones):

There have been no major changes, except a cleanup of MF description 
based on ITU and other documents. I believe this is now essentially correct.

The example was extended to include a sequence of packets, not just one. 
Based on feedback from a number of readers, editorial changes were made 
to make the document easier to read.

I believe the draft would be ready for last call if we weren't blocked 
on interop statements to progress the document to Draft Standard. There 
has been essentially no progress on this, unfortunately.

There are two choices:
(1) Cycle at Proposed and hope that somebody else has the energy to drum 
up interop reports so that the document can progress to Draft at some 
later point. I wouldn't hold my breath, so this means that 2833bis joins 
the list of Proposed Standards that run the Internet.

(2) Try to come up with a reasonably small list of items to test, such as
- support for end-of-event indication
- support for end-of-event replication
- support for long events
- RFC 2198
- frequency generation
- list of events supported

and hope that people will step up and report. Finding pairs of 
implementations that, say, support a particular code point is going to 
be rather challenging, unless we define support as "printf the correct 
number". I would suggest that a report of usage (transmit & receive) of 
an event type should be considered sufficient here since there's no 
dependency on the sender.

Henning



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