[Sipping] Re: I-D ACTION:draft-bryan-sipping-midi-01.txt

Colin Perkins <csp@csperkins.org> Fri, 08 June 2007 14:27 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwfR8-00030l-90; Fri, 08 Jun 2007 10:27:34 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1HwfR6-00030f-FP for sipping-confirm+ok@megatron.ietf.org; Fri, 08 Jun 2007 10:27:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwfR6-00030X-5w for sipping@ietf.org; Fri, 08 Jun 2007 10:27:32 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwfR4-0004PH-Qy for sipping@ietf.org; Fri, 08 Jun 2007 10:27:32 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:60717) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1HwfR4-0000Vw-6w; Fri, 08 Jun 2007 15:27:30 +0100
In-Reply-To: <E1HvIZ0-0002i7-GW@stiedprstage1.ietf.org>
References: <E1HvIZ0-0002i7-GW@stiedprstage1.ietf.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <17BA3E22-B340-44DA-BC89-59B3EADD106C@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Date: Fri, 08 Jun 2007 15:27:38 +0100
To: Cullen Jennings <fluffy@cisco.com>, dbryan@sipeerior.com
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: "sipping (E-mail)" <sipping@ietf.org>
Subject: [Sipping] Re: I-D ACTION:draft-bryan-sipping-midi-01.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

On 4 Jun 2007, at 20:50, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: Telephony Tones Using MIDI in SIP
> 	Author(s)	: C. Jennings, D. Bryan
> 	Filename	: draft-bryan-sipping-midi-01.txt
> 	Pages		: 68
> 	Date		: 2007-6-4
> 	
> This document describes conventions for using MIDI to generate tones
>    on SIP UAs.  This does not define any changes to SIP but describes
>    how to use the existing Alert-Info header to play tones that can be
>    used to indicate specialized PSTN tones such as the ringback tones
>    from various countries.  The tones are described using MIDI which
>    results in a compact representation that is simple for a UA to
>    generate and easy to render into audio.
>
>    This work is being discussed on the sipping@ietf.org mailing list.
>    This draft was revived at request of a few people so it could be
>    discussed.  Parts of it need to be updated since it was written in
>    2003.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-bryan-sipping-midi-01.txt

Interesting draft. A couple of comments:

How would this compare to sending audio/tone [RFC 4733 section 4.3.3]  
data in SIP? (I realise the audio/tone format is currently only  
defined for transport via RTP, but it could easily be extended for  
this use, and is simpler than MIDI).

Also, one could presumably achieve a similar effect using early media  
with either the RFC 4733 or RFC 4695 RTP payload formats. Some  
discussion of the trade-off between the approaches would be valuable.

-- 
Colin Perkins
http://csperkins.org/




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP