Re: [AVT] new MWPP I-D ...

[Colin Perkins <csp@csperkins.org>]

--> John Lazzaro writes:
>
>Hi everyone,
>
>	Just submitted the -05.txt draft for MWPP:
>
>http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-mwpp.txt
>
>	The change log is 3 pages long, so I won't summarize the
>additions here. The road ahead for MWPP:
>
>  [1] Write the first draft of the BCP for sending and receiving
>      MWPP RTP streams, hopefully in time for the Atlanta deadline
>      (although this may be an optimistic schedule). Should this
>      be an individual submission, or an WG item?

Initially, it should be an individual submission.

>  [2] Revisit a few "big ticket" requests folks have made for 
>      features in MWPP, that I've deferred for further research:
>
>        -- The MWPP "recovery journal" is true to its name: it's
>           a shallow, sketchy history for recovery, not the deep
>           complete history of the recent past that classical
>           redundancy schemes (RFC 2198, RFC 2733) offer. It may
>           make sense to incorporate optional deep redundancy in
>           the recovery journal, for efficiency reasons and to
>           simplify streaming server design (Herbie Robinson).
>
>        -- An "immediate execution" option -- a way to send MIDI 
>           commands that truly have no timestamp, but instead have
>           an "execute as soon as delivered" semantics relative to
>           other timestampped commands. This is not possible to do by 
>           manipulating timestamps in a single MWPP stream, because
>           timestamps must be monotonically increasing, in order to
>           simplify life for the recovery journal system. The current
>           solution is two synchronized streams, the normal stream and
>           an "emergency" stream whose timestamps lag (Martijn Sipkema).

Can you expand on the use for these untimed commands? What is the reason
they can't be timestamped as they are generated? 

>   [3] Combine the "big ticket" decisions with received comments
>       on -05.txt and bugfixes found during the BCP draft writing,
>       to write (potentially) the first candidate for Last Call.

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