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

Randall Gellens <rg+ietf@randy.pensive.org> Wed, 08 June 2016 00:03 UTC

Return-Path: <rg+ietf@randy.pensive.org>
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 ACDD312D65E for <ecrit@ietfa.amsl.com>; Tue, 7 Jun 2016 17:03:14 -0700 (PDT)
X-Quarantine-ID: <tVDU-vzrf927>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 tVDU-vzrf927 for <ecrit@ietfa.amsl.com>; Tue, 7 Jun 2016 17:03:13 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 1182C12D0DB for <ecrit@ietf.org>; Tue, 7 Jun 2016 17:03:13 -0700 (PDT)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 7 Jun 2016 17:03:13 -0700
Mime-Version: 1.0
Message-Id: <p06240606d37d10d420cc@[99.111.97.136]>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B3803614C@ESESSMB209.ericsson.se>
References: <D37746CF.9B27%christer.holmberg@ericsson.com>, <p06240607d3791933156a@[99.111.97.136]>,<7594FB04B1934943A5C02806D1A22 04B380360BE@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B3803614C@ESESSMB209.ericsson.se>
X-Mailer: Eudora for Mac OS X
Date: Tue, 07 Jun 2016 17:03:08 -0700
To: Christer Holmberg <christer.holmberg@ericsson.com>, "ecrit@ietf.org" <ecrit@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/XHLMKBpzZJ16XIZVDuxwJtCu33g>
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 00:03:15 -0000

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