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

Richard Barnes <rbarnes@bbn.com> Tue, 24 November 2009 14:35 UTC

Return-Path: <rbarnes@bbn.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 583C73A6A84 for <ecrit@core3.amsl.com>; Tue, 24 Nov 2009 06:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 GqB+J-2+y+aV for <ecrit@core3.amsl.com>; Tue, 24 Nov 2009 06:35:26 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id E69083A6A7F for <ecrit@ietf.org>; Tue, 24 Nov 2009 06:35:25 -0800 (PST)
Received: from [192.1.255.180] (helo=col-dhcp-192-1-255-180.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from <rbarnes@bbn.com>) id 1NCwUB-0006Ph-Ad; Tue, 24 Nov 2009 09:35:19 -0500
Message-Id: <7BCE4D5F-0455-4F59-95D3-B80D003A749B@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE209B00796@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-1--554238808"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 24 Nov 2009 09:35:18 -0500
References: <4B0AF639.7020501@cs.columbia.edu> <EDC0A1AE77C57744B664A310A0B23AE209B00796@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
X-Mailer: Apple Mail (2.936)
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:35:27 -0000

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
> 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