draft-ietf-avt-rfc4695-bis-06.txt   draft-ietf-avt-rfc4695-bis-07.txt 
INTERNET-DRAFT J. Lazzaro INTERNET-DRAFT J. Lazzaro
August 10, 2009 J. Wawrzynek February 1, 2010 J. Wawrzynek
Expires: February 10, 2010 UC Berkeley Expires: August 1, 2010 UC Berkeley
Intended Status: Proposed Standard Intended Status: Proposed Standard
RTP Payload Format for MIDI RTP Payload Format for MIDI
<draft-ietf-avt-rfc4695-bis-06.txt> <draft-ietf-avt-rfc4695-bis-07.txt>
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 February 10, 2010. This Internet-Draft will expire on August 1, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal Provisions
Provisions Relating to IETF Documents in effect on the date of Relating to IETF Documents (http://trustee.ietf.org/license-info)
publication of this document (http://trustee.ietf.org/license-info). in effect on the date of publication of this document. Please
Please review these documents carefully, as they describe your rights review these documents carefully, as they describe your rights and
and restrictions with respect to this document. restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License
text as described in Section 4.e of the Trust Legal Provisions and
are provided without warranty as described in the Simplified BSD
License.
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-
delivery applications (such as file streaming). The format may be delivery applications (such as file streaming). The format may be
used over unicast and multicast UDP and TCP, and it defines tools for used over unicast and multicast UDP and TCP, and it defines tools for
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-06.txt> . . . . . . . . . 180 Change Log for <draft-ietf-avt-rfc4695-bis-07.txt> . . . . . . . . . 180
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
include negotiations to agree on a common audio codec [RFC3264]. include negotiations to agree on a common audio codec [RFC3264].
skipping to change at page 179, line 23 skipping to change at page 179, line 23
John Wawrzynek John Wawrzynek
UC Berkeley UC Berkeley
CS Division CS Division
631 Soda Hall 631 Soda Hall
Berkeley CA 94720-1776 Berkeley CA 94720-1776
EMail: johnw@cs.berkeley.edu EMail: johnw@cs.berkeley.edu
Full Copyright Statement Full Copyright Statement
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal Provisions
Provisions Relating to IETF Documents in effect on the date of Relating to IETF Documents (http://trustee.ietf.org/license-info)
publication of this document (http://trustee.ietf.org/license-info). in effect on the date of publication of this document. Please
Please review these documents carefully, as they describe your rights review these documents carefully, as they describe your rights and
and restrictions with respect to this document. restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License
text as described in Section 4.e of the Trust Legal Provisions and
are provided without warranty as described in the Simplified BSD
License.
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
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-06.txt> Change Log for <draft-ietf-avt-rfc4695-bis-07.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.
-- --
03-06.txt changes: 03-07.txt changes:
No errata has been reported for RFC 4695 in the past year. No errata has been reported for RFC 4695 in the past year.
Apart from updates in the document name and expiration dates, Apart from updates in the document name and expiration dates,
03-06.txt contains no changes from 02.txt 03-07.txt contains no changes from 02.txt
-- --
02.txt changes: 02.txt changes:
No errata has been reported for RFC 4695 in the past six months. No errata has been reported for RFC 4695 in the past six months.
Apart from updates in the document name and expiration dates, Apart from updates in the document name and expiration dates,
02.txt contains no changes from 01.txt 02.txt contains no changes from 01.txt
-- --
 End of changes. 12 change blocks. 
21 lines changed or deleted 29 lines changed or added

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