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

"Amanda Baber via RT" <iana-questions@iana.org> Wed, 16 November 2016 06:06 UTC

Return-Path: <iana-shared@icann.org>
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 5914612969B for <ecrit@ietfa.amsl.com>; Tue, 15 Nov 2016 22:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.677
X-Spam-Level:
X-Spam-Status: No, score=-4.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1RRsnV6KF_9b for <ecrit@ietfa.amsl.com>; Tue, 15 Nov 2016 22:06:46 -0800 (PST)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.46.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD6D129461 for <ecrit@ietf.org>; Tue, 15 Nov 2016 22:06:46 -0800 (PST)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id 71458E0E41 for <ecrit@ietf.org>; Wed, 16 Nov 2016 06:06:45 +0000 (UTC)
Received: by request3.lax.icann.org (Postfix, from userid 48) id 342ABC204D5; Wed, 16 Nov 2016 06:06:45 +0000 (UTC)
RT-Owner: Nobody
From: "Amanda Baber via RT" <iana-questions@iana.org>
In-Reply-To: <003EC069-30F6-4874-9CF1-6BB2110A3841@salsgiver.com>
References: <RT-Ticket-937364@icann.org> <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>
Message-ID: <rt-4.2.9-6088-1479276405-1540.937364-7-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #937364
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: ecrit@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 16 Nov 2016 06:06:45 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/Y3TQbYeSAwXXJNs75oWPc6pTZ9c>
Subject: [Ecrit] [IANA #937364] AW: 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
Reply-To: iana-questions@iana.org
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 06:06:48 -0000

Hi all,

Because we have no way to gauge consensus ourselves, and because each message is generating a new ticket, we would suggest removing iana@iana.org asking the designated expert to contact us when/if the registration(s) have been approved. We understand that Brian has been designated as the expert. 

Best regards,

Amanda Baber
Lead IANA Services Specialist
PTI

On Wed Nov 16 01:43:40 2016, br@salsgiver.com wrote:
> 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> 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
> > <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 <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 <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 <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
> > <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
> > <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
> > <https://www.ietf.org/mailman/listinfo/ecrit>