Re: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Fri, 22 March 2013 10:20 UTC

Return-Path: <keith.drage@alcatel-lucent.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 C145C21F90CC for <ecrit@ietfa.amsl.com>; Fri, 22 Mar 2013 03:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.299
X-Spam-Level:
X-Spam-Status: No, score=-110.299 tagged_above=-999 required=5 tests=[AWL=-0.301, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_HI=-8, 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 wiuyX3HmySqd for <ecrit@ietfa.amsl.com>; Fri, 22 Mar 2013 03:20:53 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8820921F90BA for <ecrit@ietf.org>; Fri, 22 Mar 2013 03:20:53 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r2MAKna6003084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 22 Mar 2013 05:20:49 -0500 (CDT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r2MAKmgn010894 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Mar 2013 06:20:48 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 22 Mar 2013 06:20:48 -0400
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 22 Mar 2013 11:20:40 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Ivo Sedlacek <ivo.sedlacek@ericsson.com>, Richard Barnes <rlb@ipv.sx>
Thread-Topic: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)
Thread-Index: AQHOJXkliPQAg8Uiuk+EGiwTaCC+PpiupH0AgALZDbA=
Date: Fri, 22 Mar 2013 10:20:39 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0193EE@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CD6E08DB.3F093%mlinsner@cisco.com> <B321B1C2-086E-441B-B7C5-D0130587B851@neustar.biz> <CABkgnnVkgE8d=iKz2PY4tGaZxvHFoauPP53rM0zTyrB3Ef70vA@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B01831C@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CABkgnnW4RcuPOcD5UsifeCN65_9mDJMkrMz_hkcg2UAkvanPnQ@mail.gmail.com> <39B5E4D390E9BD4890E2B310790061010A7DB1@ESESSMB301.ericsson.se> <CAL02cgRHk14CazSud0xYLi7AjS0C3MKPmae2DtPqf59ZbtWLaA@mail.gmail.com> <39B5E4D390E9BD4890E2B310790061010A849E@ESESSMB301.ericsson.se>
In-Reply-To: <39B5E4D390E9BD4890E2B310790061010A849E@ESESSMB301.ericsson.se>
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: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B0193EEFR712WXCHMBA11zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: "Rosen, Brian" <Brian.Rosen@neustar.biz>, "ecrit@ietf.org" <ecrit@ietf.org>
Subject: Re: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)
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, 22 Mar 2013 10:20:54 -0000

I believe all the specifications require is that sos.police is handled appropriately if sos.police.national and sos.police.local exist and that depends on national regulation. It would be perfectly legitimate that sos.police is handled by a third set of PSAPs, but the likely scenario is that they are handled either by PSAPs relating to sos.police.national, or by PSAPS relating to sos.police.local.

The point is that depending on the nature of the national police force versus munical police force in any given country, either could apply, and I suspect we could identify European examples that support both.

Keith

________________________________
From: Ivo Sedlacek [mailto:ivo.sedlacek@ericsson.com]
Sent: 20 March 2013 15:32
To: Richard Barnes
Cc: Martin Thomson; DRAGE, Keith (Keith); Rosen, Brian; ecrit@ietf.org
Subject: RE: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)

Hello,

> How is the first of those two different from "urn:service:sos.police" ?  That is, do you envision a case where "sos.police", "sos.police.national", and "sos.police.local" all refer to different entities?

"sos.police.local" (municipal police) will refer to the PSAP of the municipal police.
"sos.police.national" (national police) will refer to the PSAP of the national police.
In the Czech republic, a request for "sos.police" will likely be routed to the PSAP of the national police. If a major crime is to be reported, the municipal police will need to hand it over to the national police anyway. I do not know requirements in other countries.

Kind regards

Ivo Sedlacek

This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>
From: Richard Barnes [mailto:rlb@ipv.sx]
Sent: 20. března 2013 15:42
To: Ivo Sedlacek
Cc: Martin Thomson; DRAGE, Keith (Keith); Rosen, Brian; ecrit@ietf.org
Subject: Re: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)

Ivo,

How is the first of those two different from "urn:service:sos.police" ?  That is, do you envision a case where "sos.police", "sos.police.national", and "sos.police.local" all refer to different entities?

--Richard


On Wed, Mar 20, 2013 at 2:15 AM, Ivo Sedlacek <ivo.sedlacek@ericsson.com<mailto:ivo.sedlacek@ericsson.com>> wrote:
Hello,

we need to distinguish:
- the emergency service of the municipal police (e.g. to be used to report a pickpocket)
- the emergency service of the national police (e.g. to be used to report a murder).

In a given location, the user can call any of them and get different service. That's why different emergency URNs are needed.

I have no strong view whether ".local" or other suffix (e.g. ".A3") is to identify the emergency service of the municipal police.

Kind regards

Ivo Sedlacek

This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>
-----Original Message-----
From: ecrit-bounces@ietf.org<mailto:ecrit-bounces@ietf.org> [mailto:ecrit-bounces@ietf.org<mailto:ecrit-bounces@ietf.org>] On Behalf Of Martin Thomson
Sent: 19. března 2013 21:03
To: DRAGE, Keith (Keith)
Cc: Rosen, Brian; ecrit@ietf.org<mailto:ecrit@ietf.org>
Subject: Re: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)
On 19 March 2013 12:27, DRAGE, Keith (Keith) <keith.drage@alcatel-lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
> Martin Thomson wrote:
>
>> I agree with Brian, "local" is not just ambiguous, it's redundant.
>> "urn:service:sos.police.local" is semantically equivalent to
>> "urn:service:sos.police".
>>
>
> I disagree with the last part of this.

I think that you missed my point.  By nature, all urn:service:sos sub-services are local.  That's why LoST exists.  Adding ".local" is redundant.
_______________________________________________
Ecrit mailing list
Ecrit@ietf.org<mailto:Ecrit@ietf.org>
https://www.ietf.org/mailman/listinfo/ecrit
_______________________________________________
Ecrit mailing list
Ecrit@ietf.org<mailto:Ecrit@ietf.org>
https://www.ietf.org/mailman/listinfo/ecrit