[rfc-dist] RFC 4695 on RTP Payload Format for MIDI

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Nov 10 17:59:04 PST 2006

A new Request for Comments is now available in online RFC libraries.

        RFC 4695

        Title:      RTP Payload Format for MIDI 
        Author:     J. Lazzaro, J. Wawrzynek
        Status:     Standards Track
        Date:       November 2006
        Mailbox:    lazzaro at cs.berkeley.edu, 
                    johnw at cs.berkeley.edu
        Pages:      169
        Characters: 403808
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-rtp-midi-format-15.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4695.txt

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.  [STANDARDS TRACK]

This document is a product of the Audio/Video Transport
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


More information about the rfc-dist mailing list