RTP Payload Format for MIDI
RFC 6295, “RTP Payload Format for MIDI”, is a Proposed Standard document published in June 2011 by J. Lazzaro, J. Wawrzynek. It obsoletes RFC 4695. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6295 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6294 Survey of Proposed Use Cases for the IPv6 Flow Label
- RFC 6296 IPv6-to-IPv6 Network Prefix Translation
- RFC 6293 Requirements for Internet-Draft Tracking by the IETF Community in the Datatracker
- RFC 6297 A Survey of Lower-than-Best-Effort Transport Protocols
- RFC 6292 Requirements for a Working Group Charter Tool
- RFC 6298 Computing TCP's Retransmission Timer
- RFC 6291 Guidelines for the Use of the "OAM" Acronym in the IETF
- RFC 6290 A Quick Crash Detection Method for the Internet Key Exchange Protocol