Re: Utility of Alert-Info (was: Re: [Sipping] draft-stucker-sipping-early-media-coping)

Dale.Worley@comcast.net Fri, 10 November 2006 01:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiKsm-0001ds-Bc; Thu, 09 Nov 2006 20:08:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiKsl-0001dn-7C for sipping@ietf.org; Thu, 09 Nov 2006 20:08:35 -0500
Received: from sccrmhc14.comcast.net ([63.240.77.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiKsk-0001uh-1F for sipping@ietf.org; Thu, 09 Nov 2006 20:08:35 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (sccrmhc14) with ESMTP id <2006111001083301400qd4vme>; Fri, 10 Nov 2006 01:08:33 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id kAA18XQg021623 for <sipping@ietf.org>; Thu, 9 Nov 2006 20:08:33 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id kAA18XY6021619; Thu, 9 Nov 2006 20:08:33 -0500
Date: Thu, 09 Nov 2006 20:08:33 -0500
Message-Id: <200611100108.kAA18XY6021619@dragon.ariadne.com>
To: sipping@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <E6A348B4-D013-4E36-8C85-8283C74AF207@softarmor.com> (dean.willis@softarmor.com)
Subject: Re: Utility of Alert-Info (was: Re: [Sipping] draft-stucker-sipping-early-media-coping)
References: <6FC4416DDE56C44DA0AEE67BC7CA43715DFA91@zrc2hxm2.corp.nortel.com> <454F7E9F.3030403@cisco.com> <E6A348B4-D013-4E36-8C85-8283C74AF207@softarmor.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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

   > I think it would be far better to define a URN namespace for  
   > ringtones and use local configuration to map those to specific  
   > files. What you are proposing will only work in the most closed and  
   > homogeneous environments.

I don't think a URN namespace would be particularly useful because the
only use case is vanity customizations -- there is no set of
conceptual ringtones that has meaning over a broad swathe of users.
So Alert-Info URIs are going to be either URLs that are only locally
significant (http://127.0.0.1/spears1.wav) or nearly arbitrary URNs
that are only locally significant (urn:oid:1.3.6.1.4.1.14490.4.1).

Dale

_______________________________________________
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