[Sip] Comment on draft-willis-sip-answeralert-01

"MARJOU Xavier RD-MAPS-LAN" <xavier.marjou@francetelecom.com> Tue, 13 September 2005 22:02 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFIrN-0008NA-AH; Tue, 13 Sep 2005 18:02:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EFIrL-0008N5-Dw for sip@megatron.ietf.org; Tue, 13 Sep 2005 18:02:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00763 for <sip@ietf.org>; Tue, 13 Sep 2005 18:02:32 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EFIvn-00038c-W5 for sip@ietf.org; Tue, 13 Sep 2005 18:07:13 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Sep 2005 00:02:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Sep 2005 23:59:37 +0200
Message-ID: <B30D6148F304A743A53B9B44751CDB9A033BF229@FTRDMEL2.rd.francetelecom.fr>
Thread-Topic: Comment on draft-willis-sip-answeralert-01
Thread-Index: AcW4rfKGzGqqUweeSKSTGbDm/yJ0wA==
From: MARJOU Xavier RD-MAPS-LAN <xavier.marjou@francetelecom.com>
To: sip@ietf.org, dean.willis@softarmor.com
X-OriginalArrivalTime: 13 Sep 2005 22:02:31.0699 (UTC) FILETIME=[D6C51E30:01C5B8AE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [Sip] Comment on draft-willis-sip-answeralert-01
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

When reading Req-5 with "some sorts of emergency session", I understand
that an "emergency mass alert" is a candidate use-case. 

Thus, in section 6, I suggest a new value for the Alert-Mode header
field: "Amplified" so that as many people as possible are alerted (e.g.
an amplified ring tone). In this case, a UAS could also decide to
increase the volume of audio.

This also brings some potential new requirements for the ECRIT WG: 
- Need for a Public Safety Calling Point?
- Need for the emergency callee to use the "emergency identifier" to
identify an emergency context (in addition of course to the already
mentioned authentication)?

Xavier


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