[payload] RFC 6295 on RTP Payload Format for MIDI

rfc-editor@rfc-editor.org Tue, 07 June 2011 04:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91DD11E808A; Mon, 6 Jun 2011 21:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.15
X-Spam-Level:
X-Spam-Status: No, score=-102.15 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WleFksYXPNdp; Mon, 6 Jun 2011 21:17:41 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 423AF11E8086; Mon, 6 Jun 2011 21:17:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C585B98C4EE; Mon, 6 Jun 2011 21:17:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110607041740.C585B98C4EE@rfc-editor.org>
Date: Mon, 06 Jun 2011 21:17:40 -0700
Cc: payload@ietf.org, rfc-editor@rfc-editor.org
Subject: [payload] RFC 6295 on RTP Payload Format for MIDI
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 04:17:42 -0000

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

        
        RFC 6295

        Title:      RTP Payload Format for MIDI 
        Author:     J. Lazzaro, J. Wawrzynek
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2011
        Mailbox:    lazzaro@cs.berkeley.edu, 
                    johnw@cs.berkeley.edu
        Pages:      171
        Characters: 409730
        Obsoletes:  RFC4695

        I-D Tag:    draft-ietf-payload-rfc4695-bis-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6295.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.  This document obsoletes RFC 4695.
[STANDARDS-TRACK]

This document is a product of the Audio/Video Transport Payloads 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 unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC