RFC 4696: An Implementation Guide for RTP MIDI
In plain English — editorial summary, not part of the RFC
This memo offers non-normative implementation guidance for the Real-time Protocol (RTP) MIDI (Musical Instrument Digital Interface) 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. Although the memo focuses on network musical performance, the presented implementation advice is relevant to other RTP MIDI applications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4696
- Published
- November 2006
- Authors
- J. Lazzaro; J. Wawrzynek
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4695RTP Payload Format for MIDIObsoleted
November 2006
- RFC 6295RTP Payload Format for MIDICurrent
June 2011
- RFC 4102Registration of the text/red MIME Sub-TypeUpdated
June 2005
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
- RFC 3952Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) SpeechCurrent
December 2004
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5584RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) FamilyCurrent
July 2009
- RFC 5691RTP Payload Format for Elementary Streams with MPEG Surround Multi-Channel AudioCurrent
October 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?