Re: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group

<R.Jesske@telekom.de> Wed, 16 November 2016 17:22 UTC

Return-Path: <prvs=1219dd181=R.Jesske@telekom.de>
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 DAF5E127076 for <ecrit@ietfa.amsl.com>; Wed, 16 Nov 2016 09:22:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.816
X-Spam-Level:
X-Spam-Status: No, score=-5.816 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 xEyVlEQJ-Reu for <ecrit@ietfa.amsl.com>; Wed, 16 Nov 2016 09:21:57 -0800 (PST)
Received: from mailout23.telekom.de (MAILOUT23.telekom.de [80.149.113.253]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AFEA12941E for <ecrit@ietf.org>; Wed, 16 Nov 2016 09:21:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1479316916; x=1510852916; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=QhC/jKpNf0dj6eLkzKBF2sq5RcLttjrDa2y71WFKUuQ=; b=KCxfNTEAxVrKmrnY8Pz7e3CeZA2qRUolsXh7mbUPm1ec4ymcrXpYoFsF LNGM1XC8l4fagNUNzlrnZxJWaEKjZ116W1GeCDdtDfitPBodXBBRKduQE uQzkmwfMoYYo7LQ+zhbqjLeDQ0TvZhnrfr8/vlCyKlt+TFiYJpFr24YjF ZJQBB87xPDPJhfKGJsTPLHtyRyNIqkml/2sRJaKYfsKqJ5rZFv64ViAkh noWF4EcPRBS4ve7Ajk03HLJwfTAsfpCuSilJh4O4ViPXJ7JrKldysNzFI wYVV6o4g/fsCiSuIFSUQZ2Tp4AOKXS2d8Sv65L7IPtpNDynH+9ssb+qCv g==;
Received: from s4de8nsazdfe010.bmbg.telekom.de ([10.175.246.202]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES128-SHA; 16 Nov 2016 18:21:54 +0100
X-IronPort-AV: E=Sophos;i="5.31,500,1473112800"; d="scan'208,217";a="1010368598"
Received: from he105828.emea1.cds.t-internal.com ([10.169.119.31]) by q4de8nsa015.bmbg.telekom.de with ESMTP/TLS/AES256-SHA; 16 Nov 2016 18:20:53 +0100
Received: from HE105828.EMEA1.cds.t-internal.com (10.169.119.31) by HE105828.emea1.cds.t-internal.com (10.169.119.31) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Wed, 16 Nov 2016 18:20:53 +0100
Received: from HE105828.EMEA1.cds.t-internal.com ([fe80::753e:c05:6c77:b585]) by HE105828.emea1.cds.t-internal.com ([fe80::753e:c05:6c77:b585%26]) with mapi id 15.00.1236.000; Wed, 16 Nov 2016 18:20:53 +0100
From: <R.Jesske@telekom.de>
To: <DBanks@ddti.net>, <br@salsgiver.com>, <ivo.sedlacek@ericsson.com>
Thread-Topic: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group
Thread-Index: AQHSO2N1SSks5YzXS0q00MWDl4FDs6Da0cIQ///1CoCAAAdNgIAA886AgAAhFtA=
Date: Wed, 16 Nov 2016 17:20:52 +0000
Message-ID: <78b53186b0e845c4b1eb8304f25f5c37@HE105828.emea1.cds.t-internal.com>
References: <CAJD5LR00UgK2u-T8soQmSJ0QryoOio6Ezjn3FTf4KonBidcWjA@mail.gmail.com> <6337FF74-A230-42C9-989A-AA7A9EC07277@salsgiver.com> <8e9f6d731099499ca529eecb8236f4ce@HE105828.emea1.cds.t-internal.com> <AM5PR0701MB2468D8A9C64080873E9014D4E5BE0@AM5PR0701MB2468.eurprd07.prod.outlook.com> <003EC069-30F6-4874-9CF1-6BB2110A3841@salsgiver.com> <MWHPR17MB10716E9F0F6BAD91523CF9BDA7BE0@MWHPR17MB1071.namprd17.prod.outlook.com>
In-Reply-To: <MWHPR17MB10716E9F0F6BAD91523CF9BDA7BE0@MWHPR17MB1071.namprd17.prod.outlook.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.213.108.52]
Content-Type: multipart/alternative; boundary="_000_78b53186b0e845c4b1eb8304f25f5c37HE105828emea1cdstintern_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/UuVip_mF7lwkmjK18cV9ljkkx80>
Cc: iana@iana.org, ecrit@ietf.org
Subject: Re: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group
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, 16 Nov 2016 17:22:03 -0000

Hi,
pointing to your words: “To me, that calls into question whether the urn:service prefix should be used at all.”

So even if it is used only within 3GPP networks it is still an emergency call and routed towards a PSAP.
We will use the IMS structure for emergency calling i.e. E-CSCF (Emergency Call Session Control Function).
So the 3GPP network (IMS) will use the urn for routing purposes.

Best Regards

Roland



Von: Ecrit [mailto:ecrit-bounces@ietf.org] Im Auftrag von Dan Banks
Gesendet: Mittwoch, 16. November 2016 17:16
An: Brian Rosen; Ivo Sedlacek
Cc: iana@iana.org; ecrit@ietf.org
Betreff: Re: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group

I generally agree with Brian so far in this discussion in that the barrier to registration should be low (RFC 7163 lowered it from what it was) and the proposed registration is not well aligned with the way the service names are intended to be defined and used.   This is further reinforced by the suggestion that the proposed registration is “3GPP networks only and not to be intended to be used everywhere.”  To me, that calls into question whether the urn:service prefix should be used at all.

I do have one specific issue with what Brian is suggesting below, however – the service name syntax does not allow periods in a top level service name (for good reason).

Aside from that, I do see potential value in defining subservices under .police.  I would lean toward borrowing the “a” levels for indicating police services by the level of government under which they function, as these seem sufficiently broad and reusable.  It may also make sense to separately have subservices to indicate police for specific concerns (drugs, traffic, etc.).  I think all of these could co-exist under .police because they describe different things, even though the answers may overlap.

Dan Banks

From: Ecrit [mailto:ecrit-bounces@ietf.org] On Behalf Of Brian Rosen
Sent: Tuesday, November 15, 2016 8:43 PM
To: Ivo Sedlacek
Cc: iana@iana.org<mailto:iana@iana.org>; ecrit@ietf.org<mailto:ecrit@ietf.org>
Subject: Re: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group

Ivo, I apologize for not making sure this request was not ultimately concluded satisfactorily.

I would like to ask the work group for advice for police, and I will do the work to make registrations simple.

We can use the “a” levels, or we can create a sub registry for .police.  Either requires a standards track document to create a sub registry.  Alternatively, we could just allow a period in a name and register “police.municipal” or “police.a2” as top level registrations in a registration.

Let’s first decide which way: .police.a2 or .police.municipal

The  former is more regular and handles political subdivision easily.  However, there are police forces which don’t fit this pattern.  US has “Federal Marshals” and “FBI” and “Secret Service” although some of them don’t have emergency numbers.

My suggestion is to create the sub registry for police, have the “a” levels as initial values, and allow additional values to be added with expert review.

I am not aware of similar issues with fire or emergency medical.  There are many countries which have multiple medical services but AFAIK only one emergency number that is used for emergency medical.  If there are some isolated instances, I’d allow a random sub service (urn:service:sos.medical.mountain) registration.

I do think that if we don’t allow “country-specific” then we are obligated to make handling these kinds of requests straightforward.

Brian


On Nov 16, 2016, at 10:17 AM, Ivo Sedlacek <ivo.sedlacek@ericsson.com<mailto:ivo.sedlacek@ericsson.com>> wrote:

Hello,

> Since the management policy of the emergency service is “expert review”, the barrier to adding new, possibly experimental services is low,
> and the consequences of having services that are not eventually deployed persisting in the registry is minimal.

I tried to register emergency URNs
- for emergency service of municipal police; and
- for emergency service of national police
(both of which are used in Czech republic) with IANA in https://www.ietf.org/mail-archive/web/ecrit/current/msg08419.html

The registration was rejected ....

So, I disagree that barrieer is low.

Kind regards

Ivo Sedlacek

From: Ecrit [mailto:ecrit-bounces@ietf.org] On Behalf Of R.Jesske@telekom.de<mailto:R.Jesske@telekom.de>
Sent: Tuesday, November 15, 2016 5:08 PM
To: br@salsgiver.com<mailto:br@salsgiver.com>; iana@iana.org<mailto:iana@iana.org>
Cc: ecrit@ietf.org<mailto:ecrit@ietf.org>
Subject: Re: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group

Hi Brian,
the aimed registration is for 3GPP networks only and not to be intended to be used everywhere.

So from my understanding there are a many of existing specific emergency services out in the world which need the equivalent within the 3GPP IMS world.

An example is Poland:
Please see http://uke.gov.pl/tablice-numerow-kierowania-alarmowego-nka-9410 which lists the number 986 for "straż miejska" (= municipal police) and the number 997 for Policja (= police) as "numery alarmowe" (= emergency numbers).
Which cannot use the normal sos urn.

3GPP had the requirement to specify this for the 3GPP IMS world. And the easiest way was to have such an mechanism.
Since this is only used for the 3GPP IMS world, 3GPP would like to have a mechanism to allow these  specific suptypes.

So what could be done to get such an solution where IETF can agree upon?

Best Regards

Roland

Von: Ecrit [mailto:ecrit-bounces@ietf.org] Im Auftrag von Brian Rosen
Gesendet: Donnerstag, 10. November 2016 15:54
An: iana@iana.org<mailto:iana@iana.org>
Cc: ECRIT
Betreff: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group

I am the expert reviewer designated by the ecrit working group for this request.

I believe this request is not consistent with the words and the intent of the registry.  “country-specific’ is not an emergency service.  Since the management policy of the emergency service is “expert review”, the barrier to adding new, possibly experimental services is low, and the consequences of having services that are not eventually deployed persisting in the registry is minimal.  The URN was not intended to have a generic X- service or equivalent, which is what this registration attempts to do.  New services, even experimental services, should register the service with IANA following the normal procedure.

Therefore, I recommend that we deny this request and suggest that the specific services be registered with IANA as they are deployed.  This decision has been reviewed with the ecrit working group.

Brian

On Nov 3, 2016, at 3:59 PM, Az Mankin <azmankin@gmail.com<mailto:azmankin@gmail.com>> wrote:

ECRIT Working Group,
We need a volunteer for the following IANA Expert Review request that Amanda Baber of IANA just sent to Roger and me.  It needs to be written and sent to the mailing list, per the IESG's appointment of the WG as the Expert Reviewer (http://www.iana.org/assignments/urn-serviceid-labels/urn-serviceid-labels.xhtml).  Amanda's message is under the line. Who'd like to step up for this?
Thanks!  from your Chairs
----------------

The IANA Services Operator has received a request for registration in the 'sos' Sub-Services registry in the Service URN Labels group. This request comes from Frederic Firmin of ETSI.

According to RFC 7163, registration in 'sos' Sub-Services requires expert review as designated by the ECRIT working group or its successor (or, in their absence, the IESG). Can you send this request for review?

The IESG has asked that expert reviews be completed within two weeks, if possible.

See below.

thanks,

Amanda Baber
Lead IANA Services Specialist
PTI

===

Contact Name:
Frederic Firmin

Contact Email:
frederic.firmin@etsi.org<mailto:frederic.firmin@etsi.org>

Type of Assignment:
sub-service URN

Registry:
Service URN Labels registry with the "sos" URN Service Labels subregistry.

Description:
This sub-service type is used before an appropriate sub-service type is registered with IANA for a specific emergency service. This sub-service type is not used where an appropriate sub-service type has been registered with IANA for the specific emergency service.
The next level of sub-services indicates the country where the specific emergency service is used. Subtypes below this are defined by national regulation of that country and are not registered with IANA.


Additional Info:
The following service URN is proposed to be registered:
urn:service:sos.country-specific

reference: 24.229 12.14.0 available at http://www.3gpp.org/ftp/Specs/archive/24_series/24.229/24229-ce0.zip (cf subclause 7.11.1)
_______________________________________________
Ecrit mailing list
Ecrit@ietf.org<mailto:Ecrit@ietf.org>
https://www.ietf.org/mailman/listinfo/ecrit