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

"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com> Tue, 24 November 2009 14:46 UTC

Return-Path: <drage@alcatel-lucent.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A57573A690D for <ecrit@core3.amsl.com>; Tue, 24 Nov 2009 06:46:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level:
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[AWL=0.550, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 pL2Sek3NpgaF for <ecrit@core3.amsl.com>; Tue, 24 Nov 2009 06:46:10 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by core3.amsl.com (Postfix) with ESMTP id 471923A6A85 for <ecrit@ietf.org>; Tue, 24 Nov 2009 06:46:10 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id nAOEjYQb032185 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 24 Nov 2009 15:45:56 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Tue, 24 Nov 2009 15:45:41 +0100
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Richard Barnes <rbarnes@bbn.com>
Date: Tue, 24 Nov 2009 15:45:38 +0100
Thread-Topic: [Ecrit] [Fwd: New Version Notification for draft-kim-ecrit-text-00]
Thread-Index: AcptE2KUmGBQYNayQs6IZ8nacjiy3QAAKn7Q
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE209C57E86@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <4B0AF639.7020501@cs.columbia.edu> <EDC0A1AE77C57744B664A310A0B23AE209B00796@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <7BCE4D5F-0455-4F59-95D3-B80D003A749B@bbn.com>
In-Reply-To: <7BCE4D5F-0455-4F59-95D3-B80D003A749B@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_EDC0A1AE77C57744B664A310A0B23AE209C57E86FRMRSSXCHMBSC3d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.83
Cc: ecrit <ecrit@ietf.org>
Subject: Re: [Ecrit] [Fwd: New Version Notification for draft-kim-ecrit-text-00]
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2009 14:46:12 -0000

But...

The use case under discussion here is an end entity running LOST (and therefore presumably an IP terminal) communicating with an IP connected PSAP, and therefore not involving any SMS at all. Therefore for this use case, the endpoints presumably have the full range of choice of standardised messaging mechanisms as defined by IETF.

If you did want to extend the use case to SMS, I would also content that the current standardised SMS to SIP based IM mechanisms would break the solution suggested here as well.

(Also ignoring the fact as well that current SMS is by default deferred delivery (i.e. delivered in the operator's own time and when the recipient is available, and therefore not suitable for emergency calls in the first place.)

Keith

________________________________
From: Richard Barnes [mailto:rbarnes@bbn.com]
Sent: Tuesday, November 24, 2009 2:35 PM
To: DRAGE, Keith (Keith)
Cc: ecrit
Subject: Re: [Ecrit] [Fwd: New Version Notification for draft-kim-ecrit-text-00]

The problem here is that SMS is a page-mode medium that's used for session-mode-style conversations (see, e.g., the iPhone SMS interface).  So if you're going to gateway SMS into SIP and preserve these pseudo-sessions, you either have to do something like what this draft does, or you have to somehow have the gateway create sessions and map SMS messages into them.  I'm not immediately sure which would be a better solution, but using MESSAGE seems marginally more light-weight.

--Richard




On Nov 23, 2009, at 8:34 PM, 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<mailto: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><mailto:idsubmission@ietf.org>
To: jyk@cs.columbia.edu<mailto:jyk@cs.columbia.edu>
CC: wonsang@cs.columbia.edu<mailto:wonsang@cs.columbia.edu>, hgs@cs.columbia.edu<mailto:hgs@cs.columbia.edu>, p.boni@verizon.com<mailto:p.boni@verizon.com>,      michael.g.armstrong@verizon.com<mailto: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<mailto:Ecrit@ietf.org>
https://www.ietf.org/mailman/listinfo/ecrit