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

[Ivo Sedlacek <[e-mail]>]

> Creating new entries is simple and fast.  So we request that new entries be created for different services.

I disagree that it is simple and fast.

I tried that (https://www.ietf.org/mail-archive/web/ecrit/current/msg08419.html) and it was rejected.

Kind regards

Ivo

From: Ecrit [mailto:[e-mail]] On Behalf Of Brian Rosen
Sent: Tuesday, November 15, 2016 5:25 PM
To: [e-mail]
Cc: ECRIT <[e-mail]>
Subject: Re: [Ecrit] Expert Reviewer's response to request to register 'country-specific' in 'sos' Subservice Registry in the Service URN Labels group

<leaving off IANA for now>
The URN is an address for routing, and not a user visible label. Creating new entries is simple and fast.  So we request that new entries be created for different services.

One simple approach is to create a “municipalPolice” urn, and use urn:service:sos.municipal.police for 986 and urn:service:sos.police for 997 in Poland.

Then any country that uses municipal police can use the same URN.

Actually, the problem of multiple police forces occurred in NENA, the North American emergency services group.  For internal routing purposes, we created a urn:nena::responder.police entry with sub registry for the various types of police.  I would be very willing to do the work to create a similar sub registry for urn:service:sos.police, which would allow urn:service:sos.police.municipal because many countries have multiple police forces that can be reached at different emergency numbers.  The sub registry could have “state”, “provincial”, “federal”, and other entries.

I also note that the registration says “This sub-service type is used before an appropriate sub-service type is registered with IANA for a specific emergency service.”  Emphasis added.  This explicitly says that this use is temporary and will be replaced with a “real” registration at some time.  Since registration is easy and fast, there is no need for a temporary work around to actual registration.

Brian

On Nov 16, 2016, at 10:07 AM, [e-mail]<mailto:[e-mail]> wrote:

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:[e-mail]] Im Auftrag von Brian Rosen
Gesendet: Donnerstag, 10. November 2016 15:54
An: [e-mail]<mailto:[e-mail]>
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 <[e-mail]<mailto:[e-mail]>> 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:
[e-mail]<mailto:[e-mail]>

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
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/ecrit

_______________________________________________
Ecrit mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/ecrit