Re: [Ecrit] [Fwd: New Version Notification for draft-kim-ecrit-text-00]

In the UK automatic alarm systems and other telemetry type systems are not emergency calls. I assume that applies in many countries.

The only data type system I know of which are treated as emergency calls are the eCALL mechanisms being now introduced into vehicles, whereby if sensors in the car activate in response to say an accident, then the car automatically makes an emergency call. This emergency call is essentially a standard cellphone emergency call with some additional marking, and is made as a modem data call. SMS is NOT used.

In regard to SMS, it was designed as a store and forward service, with the delivery optimised to delivery over mobile phones with constraints caused by that. Asking if there is a technical problem with use for emergency calls, well the answer is something like asking if I can use the postal service for emergency calls. The service would have to be respecified, and then deployed in that new specification. 

regards

Keith

> -----Original Message-----
> From: Jong Yul Kim [mailto:jk2520@columbia.edu] 
> Sent: Tuesday, November 24, 2009 9:44 PM
> To: Wonsang Song
> Cc: DRAGE, Keith (Keith); ecrit@ietf.org
> Subject: Re: [Ecrit] [Fwd: New Version Notification for 
> draft-kim-ecrit-text-00]
> 
> Another example would be that it may be better for automatic 
> alarm systems (burglary alarms) or telematics systems with 
> full IP endpoints to use page-mode communications with the 
> PSAP as these would not be the traditional human-to-human 
> communication but a one-way communication.
> 
> Anyway, as more devices and protocols are used to ask for 
> emergency help, there may be some that fit the page-mode 
> model better than the session-based one.
> 
> Also, the fact that SMS is a deferred service is a big 
> limitation to its usefulness as an emergency communication 
> medium. But is this a technical problem? I think it's more of 
> a motivation problem: there's no motivation for carriers to 
> do anything else at this point since PSAPs do not answer SMS 
> anyway. I believe this will change.
> 
> Jong Yul
> 
> 
> 
> Wonsang Song wrote:
> > This draft does not suggest to use page mode instead of 
> session mode 
> > for the emergency text communication. This is for the case 
> where the 
> > endpoint is not capable of creating session or for the 
> existing text 
> > communication methods that are lack of session, such like 
> IM and SMS.
> > 
> > Wonsang Song
> > 
> > 
> > DRAGE, Keith (Keith) wrote:
> >> So did I read this correctly.
> >>  
> >> You are essentially saying you want to use page mode 
> messaging to do 
> >> session mode messaging?
> >>  
> >> Didn't SIMPLE investigate that path and reject it and go 
> for MSRP as 
> >> the solution to session mode messaging?
> >>  
> >> Why does emergency calling suddenly make the original 
> decision making 
> >> process in SIMPLE redundant?
> >>  
> >> regards
> >>  
> >> Keith
> >>
> >>     
> --------------------------------------------------------------
> ----------
> >>     *From:* ecrit-bounces@ietf.org 
> [mailto:ecrit-bounces@ietf.org] *On
> >>     Behalf Of *Wonsang Song
> >>     *Sent:* Monday, November 23, 2009 8:53 PM
> >>     *To:* ecrit@ietf.org
> >>     *Subject:* [Ecrit] [Fwd: New Version Notification for
> >>     draft-kim-ecrit-text-00]
> >>
> >>     Hi,
> >>
> >>     Just wanted to send a note about a new draft on using 
> SIP MESSAGE
> >>     for emergency texting.
> >>
> >>     The draft is an outcome of the collaboration between Columbia
> >>     University and Verizon to build an emergency texting prototype
> >>     system which allows people to use IM and SMS to "call" for
> >>     emergency help.
> >>
> >>     If you have comments or questions, please let me know.
> >>
> >>     Thank you,
> >>     Wonsang Song
> >>
> >>
> >>     -------- Original Message --------
> >>     Subject: New Version Notification for draft-kim-ecrit-text-00
> >>     Date: Tue, 17 Nov 2009 11:55:17 -0800 (PST)
> >>     From: IETF I-D Submission Tool <idsubmission@ietf.org>
> >>     To: jyk@cs.columbia.edu
> >>     CC: wonsang@cs.columbia.edu, hgs@cs.columbia.edu, 
> p.boni@verizon.com,
> >>          michael.g.armstrong@verizon.com
> >>
> >>
> >>     A new version of I-D, draft-kim-ecrit-text-00.txt has been
> >>     successfuly submitted by Jong Yul Kim and posted to the IETF
> >>     repository.
> >>
> >>     Filename:
> >>      draft-kim-ecrit-text
> >>     Revision:  00
> >>     Title:  Emergency Text Messaging using SIP MESSAGE
> >>     Creation_date:
> >>      2009-11-16
> >>     WG ID:  Independent Submission
> >>     Number_of_pages: 11
> >>
> >>     Abstract:
> >>     This memo describes best current practices on how to 
> use the SIP
> >>     MESSAGE method for emergency text messaging from 
> citizen and visitors
> >>     to authorities.
> >>
> >>     Status of this Memo
> >>
> >>     This Internet-Draft is submitted to IETF in full 
> conformance with the
> >>     provisions of BCP 78 and BCP 79.
> >>
> >>     Internet-Drafts are working documents of the Internet 
> Engineering
> >>     Task Force (IETF), its areas, and its working groups.  
> Note that
> >>     other groups may also distribute working documents as Internet-
> >>     Drafts.
> >>
> >>     Internet-Drafts are draft documents valid for a 
> maximum of six months
> >>     and may be updated, replaced, or obsoleted by other 
> documents at any
> >>     time.  It is inappropriate to use Internet-Drafts as reference
> >>     material or to cite them other than as "work in progress."
> >>
> >>     The list of current Internet-Drafts can be accessed at
> >>     http://www.ietf.org/ietf/1id-abstracts.txt.
> >>
> >>     The list of Internet-Draft Shadow Directories can be 
> accessed at
> >>     http://www.ietf.org/shadow.html.
> >>
> >>     This Internet-Draft will expire on May 20, 2010.
> >>
> >>     Copyright Notice
> >>
> >>     Copyright (c) 2009 IETF Trust and the persons identified as the
> >>     document authors.  All rights reserved.
> >>
> >>     This document is subject to BCP 78 and the IETF Trust's Legal
> >>     Provisions Relating to IETF Documents
> >>     (http://trustee.ietf.org/license-info) in effect on the date of
> >>     publication of this document.  Please review these documents
> >>     carefully, as they describe your rights and 
> restrictions with respect
> >>     to this document.  Code Components extracted from this 
> document must
> >>     include Simplified BSD License text as described in 
> Section 4.e of
> >>     the Trust Legal Provisions and are provided without warranty as
> >>     described in the BSD License.
> >>
> >>
> >>
> >>     The IETF Secretariat.
> >>
> >>
> >>
> >>
> > 
> > 
> ----------------------------------------------------------------------
> > --
> > 
> > _______________________________________________
> > Ecrit mailing list
> > Ecrit@ietf.org
> > https://www.ietf.org/mailman/listinfo/ecrit
> 