Re: [Ecrit] draft-ietf-ecrit-additional-data-11: Question on scope of the Contact URI, defined in section 3.1.5

Roger Marshall <RMarshall@telecomsys.com> Mon, 26 August 2013 20:33 UTC

Return-Path: <RMarshall@telecomsys.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 7E0EE21F9D80 for <ecrit@ietfa.amsl.com>; Mon, 26 Aug 2013 13:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhz38JvsywGf for <ecrit@ietfa.amsl.com>; Mon, 26 Aug 2013 13:33:15 -0700 (PDT)
Received: from sea-mx-02.telecomsys.com (sea-mx-02.telecomsys.com [199.165.246.42]) by ietfa.amsl.com (Postfix) with ESMTP id 42BC821F9D69 for <ecrit@ietf.org>; Mon, 26 Aug 2013 13:33:15 -0700 (PDT)
Received: from SEA-EXCAS-2.telecomsys.com (exc2010-local2.telecomsys.com [10.32.12.187]) by sea-mx-02.telecomsys.com (8.14.5/8.14.5) with ESMTP id r7QKX5tj006954 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 26 Aug 2013 13:33:06 -0700
Received: from SEA-EXMB-1.telecomsys.com ([169.254.1.145]) by SEA-EXCAS-2.telecomsys.com ([10.32.12.187]) with mapi id 14.01.0218.012; Mon, 26 Aug 2013 13:33:05 -0700
From: Roger Marshall <RMarshall@telecomsys.com>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, Brian Rosen <br@brianrosen.net>
Thread-Topic: [Ecrit] draft-ietf-ecrit-additional-data-11: Question on scope of the Contact URI, defined in section 3.1.5
Thread-Index: Ac6Sss0vFs+I00HHTNynzH+gXjYA8QBz4d9tAA91owAADWbXAANpY92g
Date: Mon, 26 Aug 2013 20:33:05 +0000
Message-ID: <FBD5AAFFD0978846BF6D3FAB4C892ACC3EDF01@SEA-EXMB-1.telecomsys.com>
References: <7594FB04B1934943A5C02806D1A2204B1C41E812@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1C422BC7@ESESSMB209.ericsson.se>, <CAOPrzE3XQGhXgH_zPpNDeLBrPb4hRUp2JefV2s9TqW1Ku0=RSA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C422DB7@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C422DB7@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.32.12.134]
Content-Type: multipart/alternative; boundary="_000_FBD5AAFFD0978846BF6D3FAB4C892ACC3EDF01SEAEXMB1telecomsy_"
MIME-Version: 1.0
Cc: "ecrit_ietf.org" <ecrit@ietf.org>
Subject: Re: [Ecrit] draft-ietf-ecrit-additional-data-11: Question on scope of the Contact URI, defined in section 3.1.5
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 26 Aug 2013 20:33:19 -0000

I agree with Christer's suggestion to add caution text.

-roger.

From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Thursday, August 08, 2013 9:44 PM
To: Brian Rosen
Cc: ecrit_ietf.org
Subject: Re: [Ecrit] draft-ietf-ecrit-additional-data-11: Question on scope of the Contact URI, defined in section 3.1.5

Hi,

If the PSAP is not supposed to use the field when/if making a callback, I think we shall explicitly state that in the document, and/or in general say that the field must not be used for calls that are expected to be given priority/special handling, and give callback as an example.

Regards,

Christer



Sent from Windows using TouchDown (www.nitrodesk.com<http://www.nitrodesk.com>)

-----Original Message-----
From: Brian Rosen [br@brianrosen.net]
To: Christer Holmberg [christer.holmberg@ericsson.com]
CC: ecrit_ietf.org [ecrit@ietf.org]
Subject: Re: [Ecrit] draft-ietf-ecrit-additional-data-11: Question on scope of the Contact URI, defined in section 3.1.5
The Contact is how the PSAP contacts the service provider to get help from the SP.

It's not a "call back" in the sense of an emergency call (the network doesn't treat it differently than a normal call), at least as far as I have considered it.  I suppose it might be nice to know that it's important, but I don't think that is worth any big new mechanism.

Brian


On Thursday, August 8, 2013, Christer Holmberg wrote:
I haven't seen any reply to this. Brian, do you have any opinion?

Regards,

Christer



Sent from Windows using TouchDown (www.nitrodesk.com<http://www.nitrodesk.com>)

-----Original Message-----
From: Christer Holmberg [christer.holmberg@ericsson.com]
To: ecrit@ietf.org [ecrit@ietf.org]
Subject: [Ecrit] draft-ietf-ecrit-additional-data-11: Question on scope of the Contact URI, defined in section 3.1.5

Hi,



A question on the scope of the Contact URI, defined in section 3.1.5 of draft-ietf-ecrit-additional-data-11.txt.



Is the Contact URI supposed by the PSAP when making callbacks?



If the value represents a "service provider", should PSAP callbacks also be made to the service provider?



Regards,



Christer


CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.