IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 09 August 2013 04:44 UTC

Return-Path: <christer.holmberg@ericsson.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 E620021F9E62 for <ecrit@ietfa.amsl.com>; Thu, 8 Aug 2013 21:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level:
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[AWL=-1.401, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 wSzl2RZKP5EI for <ecrit@ietfa.amsl.com>; Thu, 8 Aug 2013 21:44:19 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 78CF121F9E47 for <ecrit@ietf.org>; Thu, 8 Aug 2013 21:44:18 -0700 (PDT)
X-AuditID: c1b4fb38-b7fb48e000000a68-63-520473a14a2c
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 5F.DD.02664.1A374025; Fri, 9 Aug 2013 06:44:17 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.135]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0328.009; Fri, 9 Aug 2013 06:44:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: 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+gXjYA8QBz4d9t///kzQCAAIy+2Q==
Date: Fri, 09 Aug 2013 04:44:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C422DB7@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1C41E812@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1C422BC7@ESESSMB209.ericsson.se>, <CAOPrzE3XQGhXgH_zPpNDeLBrPb4hRUp2JefV2s9TqW1Ku0=RSA@mail.gmail.com>
In-Reply-To: <CAOPrzE3XQGhXgH_zPpNDeLBrPb4hRUp2JefV2s9TqW1Ku0=RSA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1C422DB7ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+Jvre7CYpYgg9vtchZP709js2hc9JTV gcnj/re/7B5LlvxkCmCK4rJJSc3JLEst0rdL4MpYvqyLvWCDTcXdW++YGhgfmHQxcnJICJhI 3Lr6nhXCFpO4cG89WxcjF4eQwFFGiaM7d0I5ixklpi75DlTFwcEmYCHR/U8bpEFEQFli561O dpAwM5B9ojMeJCwsUCWxeOJHJoiSaoktRzcxgpSICDhJLOoNBQmzCKhIrDx9gQkkzCvgK/Fo Si7EomuMEhf3bgQ7h1MgUGLFzFksIDYj0GnfT60BG8ksIC5x68l8JoiTBSSW7DnPDGGLSrx8 /I8VoiZf4sH9NjYQm1dAUOLkzCcsExhFZiFpn4WkbBaSMoi4gcT7c/OZIWxtiWULX0PZ+hIb v5xlRBZfwMi+ipGjOLU4KTfdyGATIzByDm75bbGD8fJfm0OM0hwsSuK8W/TOBAoJpCeWpGan phakFsUXleakFh9iZOLglGpg1NwZEKO2ocqD6X9Wss2774wnrD6s2cETMmv9bv+Dr83y7poZ fPD1m7Uj+vbSz8leVk/OSs3q2tZvvK9lXozZWanSc8HKr2cm/Frws82k+oaK/5nu23t2ty/b 86iStXVT99f4kJice2JTX89bJCf9cuHi19yuLTnV4ZwcVvby7yIFJ+XMWvY7TYmlOCPRUIu5 qDgRAKpFjKRqAgAA
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: Fri, 09 Aug 2013 04:44:24 -0000

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)

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

v2.23.0 | Report a Bug | By Email