An Implementation Guide for RTP MIDI
draft-lazzaro-avt-mwpp-coding-guidelines-03

Document Type Replaced Internet-Draft (individual)
Last updated 2009-02-24 (latest revision 2003-06-02)
Replaced by draft-ietf-avt-rtp-midi-guidelines
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-avt-rtp-midi-guidelines
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-lazzaro-avt-mwpp-coding-guidelines-03.txt

Abstract

This memo offers non-normative implementation guidance for the RTP MIDI payload format. The memo presents its advice in the context of a network musical performance application. In this application two musicians, located in different physical locations, interact over a network to perform as they would if located in the same room. Underlying the performances are RTP MIDI sessions over unicast UDP. Algorithms for sending and receiving recovery journals (the resiliency structure for the payload format) are described in detail.

Authors

John Lazzaro (lazarro@cs.berkeley.edu)
John Wawrzynek (johnw@cs.berkeley.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)