datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

RTP Payload Format for MIDI
draft-ietf-payload-rfc4695-bis-02

RFC
Document Stream: IETF
Last updated: 2011-03-07
Replaces: draft-ietf-avt-rfc4695-bis
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (payload)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6295
IANA Action State: RFC-Ed-Ack 
Responsible AD: Robert Sparks
IESG Note: Roni Even (even.roni@huawei.com) is the document shepherd.
Send notices to: payload-chairs@tools.ietf.org, draft-ietf-payload-rfc4695-bis@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-payload-rfc4695-bis.

Abstract:
This memo describes a Real-time Transport Protocol (RTP) payload format for the MIDI (Musical Instrument Digital Interface) command language. The format encodes all commands that may legally appear on a MIDI 1.0 DIN cable. The format is suitable for interactive applications (such as network musical performance) and content-delivery applications (such as file streaming). The format may be used over unicast and multicast UDP and TCP, and it defines tools for graceful recovery from packet loss. Stream behavior, including the MIDI rendering method, may be customized during session setup. The format also serves as a mode for the mpeg4-generic format, to support the MPEG 4 Audio Object Types for General MIDI, Downloadable Sounds Level 2, and Structured Audio. This document obsoletes RFC 4695. [STANDARDS-TRACK]

Authors:
John Wawrzynek <johnw@cs.berkeley.edu>
John Lazzaro <lazzaro@cs.berkeley.edu>

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