draft-ietf-avt-rfc4695-bis-00.txt   draft-ietf-avt-rfc4695-bis-01.txt 
INTERNET-DRAFT J. Lazzaro INTERNET-DRAFT J. Lazzaro
January 19, 2007 J. Wawrzynek February 28, 2007 J. Wawrzynek
Expires: July 19, 2007 UC Berkeley Expires: August 28, 2007 UC Berkeley
RTP Payload Format for MIDI RTP Payload Format for MIDI
<draft-ietf-avt-rfc4695-bis-00.txt> <draft-ietf-avt-rfc4695-bis-01.txt>
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware have applicable patent or other IPR claims of which he or she is aware have
been or will be disclosed, and any of which he or she becomes aware been or will be disclosed, and any of which he or she becomes aware
will be disclosed, in accordance with Section 6 of BCP 79. will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress." or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on July 19, 2007. This Internet-Draft will expire on August 28, 2007.
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This memo describes a Real-time Transport Protocol (RTP) payload This memo describes a Real-time Transport Protocol (RTP) payload
format for the MIDI (Musical Instrument Digital Interface) command format for the MIDI (Musical Instrument Digital Interface) command
language. The format encodes all commands that may legally appear on language. The format encodes all commands that may legally appear on
a MIDI 1.0 DIN cable. The format is suitable for interactive a MIDI 1.0 DIN cable. The format is suitable for interactive
applications (such as network musical performance) and content- applications (such as network musical performance) and content-
skipping to change at page 4, line 25 skipping to change at page 4, line 25
C.7.2. MIDI Network Musical Performance Applications . . . 152 C.7.2. MIDI Network Musical Performance Applications . . . 152
D. Parameter Syntax Definitions . . . . . . . . . . . . . . . . . . 161 D. Parameter Syntax Definitions . . . . . . . . . . . . . . . . . . 161
E. A MIDI Overview for Networking Specialists . . . . . . . . . . . 168 E. A MIDI Overview for Networking Specialists . . . . . . . . . . . 168
E.1. Commands Types . . . . . . . . . . . . . . . . . . . . . . 170 E.1. Commands Types . . . . . . . . . . . . . . . . . . . . . . 170
E.2. Running Status . . . . . . . . . . . . . . . . . . . . . . 170 E.2. Running Status . . . . . . . . . . . . . . . . . . . . . . 170
E.3. Command Timing . . . . . . . . . . . . . . . . . . . . . . 171 E.3. Command Timing . . . . . . . . . . . . . . . . . . . . . . 171
E.4. AudioSpecificConfig Templates for MMA Renderers . . . . . 171 E.4. AudioSpecificConfig Templates for MMA Renderers . . . . . 171
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Normative References . . . . . . . . . . . . . . . . . . . . . 176 Normative References . . . . . . . . . . . . . . . . . . . . . 176
Informative References . . . . . . . . . . . . . . . . . . . . 177 Informative References . . . . . . . . . . . . . . . . . . . . 177
Change Log for <draft-ietf-avt-rfc4695-bis-00.txt> . . . . . . . . . 181 Change Log for <draft-ietf-avt-rfc4695-bis-01.txt> . . . . . . . . . 181
1. Introduction 1. Introduction
The Internet Engineering Task Force (IETF) has developed a set of The Internet Engineering Task Force (IETF) has developed a set of
focused tools for multimedia networking ([RFC3550] [RFC4566] [RFC3261] focused tools for multimedia networking ([RFC3550] [RFC4566] [RFC3261]
[RFC2326]). These tools can be combined in different ways to support a [RFC2326]). These tools can be combined in different ways to support a
variety of real-time applications over Internet Protocol (IP) networks. variety of real-time applications over Internet Protocol (IP) networks.
For example, a telephony application might use the Session Initiation For example, a telephony application might use the Session Initiation
Protocol (SIP, [RFC3261]) to set up a phone call. Call setup would Protocol (SIP, [RFC3261]) to set up a phone call. Call setup would
skipping to change at page 166, line 50 skipping to change at page 166, line 50
C = %x43 C = %x43
D = %x44 D = %x44
E = %x45 E = %x45
F = %x46 F = %x46
G = %x47 G = %x47
H = %x48 H = %x48
J = %x4A J = %x4A
K = %x4B K = %x4B
M = %x4D M = %x4D
N = %x4E N = %x4E
P = %x51 P = %x50
Q = %x52 Q = %x51
T = %x54 T = %x54
V = %x56 V = %x56
W = %x57 W = %x57
X = %x58 X = %x58
Y = %x59 Y = %x59
Z = %x5A Z = %x5A
NZ-DIGIT = %x31-39 ; non-zero decimal digit NZ-DIGIT = %x31-39 ; non-zero decimal digit
U-HEXDIG = DIGIT / A / B / C / D / E / F U-HEXDIG = DIGIT / A / B / C / D / E / F
skipping to change at page 181, line 5 skipping to change at page 181, line 5
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary rights
that may cover technology that may be required to implement this that may cover technology that may be required to implement this
standard. Please address the information to the IETF at ietf- standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
Change Log for <draft-ietf-avt-rfc4695-bis-00.txt> Change Log for <draft-ietf-avt-rfc4695-bis-01.txt>
This I-D is a modified version of RFC 4695. For every error found to This I-D is a modified version of RFC 4695. For every error found to
date in RFC 4695, the I-D has been modified to fix the error. date in RFC 4695, the I-D has been modified to fix the error.
Below, we list the errors found in RFC 4695 that are most likely to Below, we list the errors found in RFC 4695 that are most likely to
confuse implementors. The fixes to Appendix D ABNF errors listed confuse implementors. The fixes to Appendix D ABNF errors listed
below are presented without comments; see Appendix D to see the below are presented without comments; see Appendix D to see the
commented rule in context. The list below includes the fixes for all commented rule in context. The list below includes the fixes for all
normative errors; most fixes for other types of errors are not listed. normative errors; most fixes for other types of errors are not listed.
However, the I-D itself contains fixes for all known errors. However, the I-D itself contains fixes for all known errors.
-- --
01.txt changes:
A typo was fixed in the Appendix D ABNF. P and Q are now
correctly defined as:
P = %x50
Q = %x51
Thanks to Alfred Hoenes for these changes.
--
00.txt changes: 00.txt changes:
Thanks to Alfred Hoenes for these changes. Thanks to Alfred Hoenes for these changes.
[1] In Appendix C.1 and Appendix C.2.3 of RFC 4695, an ABNF rule [1] In Appendix C.1 and Appendix C.2.3 of RFC 4695, an ABNF rule
related to System Chapter X is incorrectly defined as: related to System Chapter X is incorrectly defined as:
<parameter> = "__" <h-list> ["_" <h-list>] "__" <parameter> = "__" <h-list> ["_" <h-list>] "__"
The correct version of this rule is: The correct version of this rule is:
skipping to change at page 182, line 25 skipping to change at page 182, line 37
C = %x43 C = %x43
D = %x44 D = %x44
E = %x45 E = %x45
F = %x46 F = %x46
G = %x47 G = %x47
H = %x48 H = %x48
J = %x4A J = %x4A
K = %x4B K = %x4B
M = %x4D M = %x4D
N = %x4E N = %x4E
P = %x51 P = %x50 ; correct as shown, these values were
Q = %x52 Q = %x51 ; incorrect in the -00.txt I-D version
T = %x54 T = %x54
V = %x56 V = %x56
W = %x57 W = %x57
X = %x58 X = %x58
Y = %x59 Y = %x59
Z = %x5A Z = %x5A
[5] In Appendix D of RFC 4695, the definitions of the <four-octet>, [5] In Appendix D of RFC 4695, the definitions of the <four-octet>,
<nonzero-four-octet>, and <midi-chan> are incorrect. The correct <nonzero-four-octet>, and <midi-chan> are incorrect. The correct
definitions of these rules appear below: definitions of these rules appear below:
 End of changes. 8 change blocks. 
10 lines changed or deleted 22 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/