Re: [Ecrit] draft-gellens-ecrit-car-crash-01.txt

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Sun, 19 January 2014 05:18 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1291AD944 for <ecrit@ietfa.amsl.com>; Sat, 18 Jan 2014 21:18:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zItuiY4vw8w2 for <ecrit@ietfa.amsl.com>; Sat, 18 Jan 2014 21:18:28 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 59B2B1AD943 for <ecrit@ietf.org>; Sat, 18 Jan 2014 21:18:27 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0J5I86p028467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 18 Jan 2014 23:18:10 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0J5I8bo018152 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jan 2014 06:18:08 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Sun, 19 Jan 2014 06:18:08 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "DOLLY, MARTIN C" <md3135@att.com>, "ecrit@ietf.org" <ecrit@ietf.org>
Thread-Topic: [Ecrit] draft-gellens-ecrit-car-crash-01.txt
Thread-Index: AQHPFGwJ35cCxUMkLEeJk1f2S6xtxpqLd+WQ
Date: Sun, 19 Jan 2014 05:18:07 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B11D930@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <E42CCDDA6722744CB241677169E83656024AF821@MISOUT7MSGUSR9I.ITServices.sbc.com> <52DAAE4F.9030904@gmx.net>
In-Reply-To: <52DAAE4F.9030904@gmx.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Ecrit] draft-gellens-ecrit-car-crash-01.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 19 Jan 2014 05:18:30 -0000

I don't know which 3GPP timetable you are using, but the December 2006 version of 3GPP TS 22.101 defines eCall as being in the CS domain (TS12). This was release 8.

The only IMS work I am aware of was in release 9 where they looked at sending the CS ecall data as a media in an IMS call. No standard came out of this.

Regards

Keith Drage 

> -----Original Message-----
> From: Ecrit [mailto:ecrit-bounces@ietf.org] On Behalf Of 
> Hannes Tschofenig
> Sent: 18 January 2014 16:40
> To: DOLLY, MARTIN C; ecrit@ietf.org
> Subject: Re: [Ecrit] draft-gellens-ecrit-car-crash-01.txt
> 
> Hi all,
> 
> Already in 2008 Brian and myself submitted the first version 
> of draft-rosen-ecrit-ecall, which described how to re-use the 
> existing work in ECRIT and GEOPRIV for use with emergency 
> calls triggered by vehicles.
> 
> This was long before anyone in Europe had figured out that 
> their approach of using the legacy cellular infrastructure 
> for making these types of emergency calls by cars will at 
> some point in time have to transition to IP, as everything 
> transitions to the Internet.
> 
> Moving forward to 2013 the work on IP-based eCall was indeed 
> started by ETSI and a task force had been established to look 
> at the solutions.
> Based on the presentations in ECRIT the suggestion was made 
> to separate the document and to move content from the 
> additional data draft to those documents.
> 
> The two resulting documents were:
> http://datatracker.ietf.org/doc/draft-gellens-ecrit-ecall/
> http://datatracker.ietf.org/doc/draft-gellens-ecrit-car-crash/
> 
> These documents provide valuable insight into how IP-based 
> in-vehicle emergency calls work by re-using our existing architecture.
> 
> I personally believe it is a good idea to work on these 
> documents in ECRIT. I hope the group sees the value and 
> provides the necessary support for the work on these two documents.
> 
> Ciao
> Hannes
> 
> On 12/10/2013 11:57 AM, DOLLY, MARTIN C wrote:
> > Greetings,
> >  
> > We support draft-gellens-ecrit-car-crash-01.txt being adopted as a 
> > working group document.
> >  
> > Regards,
> >  
> > Martin Dolly
> > Lead Member Technical Staff
> > Core & Government/Regulatory Standards AT&T Standards and Industry 
> > Alliances _md3135@att.com_ <mailto:md3135@att.com>
> > +1-609-903-3360
> >  
> >  
> >  
> > 
> > 
> > _______________________________________________
> > Ecrit mailing list
> > Ecrit@ietf.org
> > https://www.ietf.org/mailman/listinfo/ecrit
> > 
> 
>