Re: [Ecrit] 3GPP impact on draft-ecall: usage of legacy modem to transport MSD

"Drage, Keith (Nokia - GB)" <keith.drage@nokia.com> Wed, 08 June 2016 12:27 UTC

Return-Path: <keith.drage@nokia.com>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3EA112D0A9 for <ecrit@ietfa.amsl.com>; Wed, 8 Jun 2016 05:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 vyUtk1jo1xjP for <ecrit@ietfa.amsl.com>; Wed, 8 Jun 2016 05:27:55 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FD1F12B03B for <ecrit@ietf.org>; Wed, 8 Jun 2016 05:27:55 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id DAA6A6D15C82A; Wed, 8 Jun 2016 12:27:49 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u58CRrDB004757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Jun 2016 12:27:53 GMT
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 u58CRqGr007917 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Jun 2016 14:27:52 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.147]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Wed, 8 Jun 2016 14:27:33 +0200
From: "Drage, Keith (Nokia - GB)" <keith.drage@nokia.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>, Christer Holmberg <christer.holmberg@ericsson.com>, "ecrit@ietf.org" <ecrit@ietf.org>
Thread-Topic: [Ecrit] 3GPP impact on draft-ecall: usage of legacy modem to transport MSD
Thread-Index: AQHRvru1CGX6/X+gHEe7TsYhX7N4gp/aNUKAgAABmQCABFxsAIAA3Oug
Date: Wed, 08 Jun 2016 12:27:32 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8BADF117BD@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <D37746CF.9B27%christer.holmberg@ericsson.com>, <p06240607d3791933156a@[99.111.97.136]>,<7594FB04B1934943A5C02806D1A22 04B380360BE@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B3803614C@ESESSMB209.ericsson.se> <p06240606d37d10d420cc@[99.111.97.136]>
In-Reply-To: <p06240606d37d10d420cc@[99.111.97.136]>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/iI2ubymmjxWecjhwAmOJvYzBVQA>
Subject: Re: [Ecrit] 3GPP impact on draft-ecall: usage of legacy modem to transport MSD
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 08 Jun 2016 12:27:58 -0000

I have made similar comments to Christer at least a couple of times.

Firstly, the only usage of this draft is in 3GPP networks. Noone has identified a use case or a deployment for this draft outside 3GPP. 3GPP has special usages of SIP for emergency calls, which essentially require it to be used via IMS entities. Try and use SIP outside this, and it will not be an emergency call in the 3GPP network, and the call will probably fail for roaming users. The IMS standards do specify what happens in regard to correlation with the CS domain, and the URNs defined for emergency call usage must take account of it.

The URNs identity the resource to which the call should be routed. 

For the existing sos URNs, the interworking with the CS domain has no special capabilities and is handled within IMS. The media bearers used for IMS based emergency calls are a superset of those used for CS domain emergency call, and therefore there is no disparity in the URN usage.

In 3GPP ecall, that resource must be a resource capable of handling both the data transfer mechanism specifically designed for IMS, but also the existing data transfer mechanism using a modem based mechanism. There is no interworking point defined for converting one mechnanism to the other, and the PSAP is expected to handle both (as is the calling UA). Therefore the URNs must identity a resource that handles both. If transmission fails using the mechanism defined by this draft (presumably because of interworking) then the UA and PSAP will drop back to trying to use the existing modem based approach. 

Therefore the draft that defined the URN must define these semantics for the resource addressed.

No one is saying you need to write the rest of the story relating to CS data transfer, but the URN definition must encompass it.

Regards

Keith

-----Original Message-----
From: Ecrit [mailto:ecrit-bounces@ietf.org] On Behalf Of Randall Gellens
Sent: 08 June 2016 01:03
To: Christer Holmberg; ecrit@ietf.org
Subject: Re: [Ecrit] 3GPP impact on draft-ecall: usage of legacy modem to transport MSD

Hi Christer,

The URNs are registered as child elements of the SOS service URN, so they are in no way limited to INFO.

At 5:27 AM +0000 6/5/16, Christer Holmberg wrote:

>  Clarification: the URNs cannot be limited to the INFO mechanism for 
> transporting MSD.
>
>  Regards,
>
>  Christer
>
>  Sent from my Windows Phone
>
>  From: <mailto:christer.holmberg@ericsson.com>Christer Holmberg
>  Sent: 05/06/2016 08:21
>  To: <mailto:rg+ietf@randy.pensive.org>Randall Gellens; 
> <mailto:ecrit@ietf.org>ecrit@ietf.org
>  Subject: Re: [Ecrit] 3GPP impact on draft-ecall: usage of legacy 
> modem to transport MSD
>
>  Hi,
>
>  The draft also defines eCall URNs, and those cannot be limited to SIP.
>
>  Regards,
>
>  Christer
>
>  Sent from my Windows Phone
>
>  From: <mailto:rg+ietf@randy.pensive.org>Randall Gellens
>  Sent: 05/06/2016 02:49
>  To: <mailto:christer.holmberg@ericsson.com>Christer Holmberg; 
> <mailto:ecrit@ietf.org>ecrit@ietf.org
>  Subject: Re: [Ecrit] 3GPP impact on draft-ecall: usage of legacy 
> modem to transport MSD
>
>  Hi Christer,
>
>  I think in-band modem is out of scope of the draft.  The draft is  
> limited to SIP signaling aspects.
>
>  --Randy
>
>  At 11:35 AM +0000 6/3/16, Christer Holmberg wrote:
>
>>   Hi,
>>
>>   3GPP agreed that, when communicating with a PSTN PSAP, it shall be
>>   possible to transport MSD using a legacy modem on the media plane. The
>>   reason is for not mandating the network to perform "interworking between
>>   MSD transported in INVITE/INFO and MSD transported using a legacy modem on
>>   the media plane".
>>
>>   I don't think the ecall draft needs to consider WHEN the MSD will be
>>   transported using a legacy modem on the media plane, but I think the draft
>>   should describe the possibility, so that PSAPs are aware of it.
>>
>>   Also, as the same eCall URNs will be used for calls where the MSD is
>>   transported using a legacy modem on the media plane, the draft must enable
>>   usage of the eCall URNs in setup of an IMS emergency call where MSD is
>>   transported using the legacy modem on the media plane.
>>
>>   Regards,
>>
>>   Christer
>>
>>   _______________________________________________
>>   Ecrit mailing list
>>   Ecrit@ietf.org
>> 
>> <https://www.ietf.org/mailman/listinfo/ecrit>https://www.ietf.org/mai
>> lman/listinfo/ecrit
>
>
>  --
>  Randall Gellens
>  Opinions are personal;    facts are suspect;    I speak for myself only
>  -------------- Randomly selected tag: ---------------
>>From new transmitters came the old stupidities.   --Bertolt Brecht


--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: --------------- True patriotism hates injustice in its own land more than anywhere else.
    --Clarence Darrow

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit