[rfc-dist] RFC 4696 on An Implementation Guide for RTP MIDI
rfc-editor at rfc-editor.org
Fri Nov 10 17:59:18 PST 2006
A new Request for Comments is now available in online RFC libraries.
Title: An Implementation Guide for RTP
Author: J. Lazzaro, J. Wawrzynek
Date: November 2006
Mailbox: lazzaro at cs.berkeley.edu,
johnw at cs.berkeley.edu
I-D Tag: draft-ietf-avt-rtp-midi-guidelines-15.txt
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.
This document is a product of the Audio/Video Transport
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
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
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
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
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
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