Skip to main content

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

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors John Lazzaro , John Wawrzynek
Last updated 2009-02-24 (Latest revision 2003-06-02)
Replaced by RFC 4696
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-avt-rtp-midi-guidelines
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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
John Wawrzynek

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