[dispatch] Charter proposal: SIP Alert-Info URN
<L.Liess@telekom.de> Mon, 21 September 2009 17:44 UTC
Return-Path: <L.Liess@telekom.de>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2867C3A699E for <dispatch@core3.amsl.com>; Mon, 21 Sep 2009 10:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.922
X-Spam-Level:
X-Spam-Status: No, score=-2.922 tagged_above=-999 required=5 tests=[AWL=0.327, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mhxaRbsvR7e4 for <dispatch@core3.amsl.com>; Mon, 21 Sep 2009 10:44:19 -0700 (PDT)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by core3.amsl.com (Postfix) with ESMTP id D2AC53A6AC0 for <dispatch@ietf.org>; Mon, 21 Sep 2009 10:44:18 -0700 (PDT)
Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail51.telekom.de with ESMTP; 21 Sep 2009 19:45:11 +0200
Received: from S4DE9JSAANI.ost.t-com.de ([10.125.177.223]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Mon, 21 Sep 2009 19:45:11 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 21 Sep 2009 19:45:10 +0200
Message-ID: <40FB0FFB97588246A1BEFB05759DC8A0036E29AD@S4DE9JSAANI.ost.t-com.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Charter proposal: SIP Alert-Info URN
Thread-Index: Aco640Ol88Y9X4ViRTeB08Ydf9e9qw==
From: L.Liess@telekom.de
To: dispatch@ietf.org
X-OriginalArrivalTime: 21 Sep 2009 17:45:11.0307 (UTC) FILETIME=[446705B0:01CA3AE3]
Cc: R.Jesske@telekom.de
Subject: [dispatch] Charter proposal: SIP Alert-Info URN
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2009 17:44:20 -0000
Hello, Please find below our charter proposal for the SIP Alert-Info URN. Comments are very welcome! Kind regards, Laura The SIP Alert-Info URN (SAIU) working group is chartered to define a new URN-scheme which allows SIP to convey a particular alert indication using a name instead of a referenced URI. The Alert-Info URN solves interoperability problems which we encounter today around the use of the Alert-Info header field for services as call waiting, call forwarding, blind transfer, automatic callback, call hold or emergency announcements sent over PBX systems. RFC 3261 allows a UAS or proxy to provide a specific ring-/ringback-tone as a reference (e.g. HTTP URI) which can be played to the user in the Alert-Info header. This mechanism does not ensure interoperability on the semantic level when there is no common understanding of the referenced content (different countries, hearing impaired) or when the user has his own tones configured in the end device. There are a variety of URI conventions and proprietary Alert-Info header field parameters to provide this today, all of which are non-interoperable. A standardized set of Alert-Info URNs will increase SIP interoperability for this header field by replacing proprietary conventions. The group will produce: - A specification which describes the problem statement, the Alert-Info URN-scheme and defines the specific Alert-Info URNs identifiers to solve the known service interoperability problems. Goals and Milestones ==================== Dec 10 - Alert-Info URN specification to IESG (PS)
- [dispatch] Charter proposal: SIP Alert-Info URN L.Liess
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Dean Willis
- Re: [dispatch] Charter proposal: SIP Alert-Info U… L.Liess
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Dean Willis
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Paul Kyzivat
- Re: [dispatch] Charter proposal: SIP Alert-Info U… L.Liess
- Re: [dispatch] Charter proposal: SIP Alert-Info U… L.Liess
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Paul Kyzivat
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Paul Kyzivat
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Dean Willis
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Tom Taylor
- Re: [dispatch] Charter proposal: SIP Alert-Info U… L.Liess
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Francois Audet
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Paul Kyzivat
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Tom Taylor
- Re: [dispatch] Charter proposal: SIP Alert-Info U… Francois AUDET
- Re: [dispatch] Charter proposal: SIP Alert-Info U… L.Liess