Re: [Ecrit] I-D Action: draft-rosen-ecrit-service-urn-subregistries-00.txt

Brian Rosen <br@brianrosen.net> Wed, 21 December 2016 14:50 UTC

Return-Path: <br@brianrosen.net>
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 71028127071 for <ecrit@ietfa.amsl.com>; Wed, 21 Dec 2016 06:50:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 WCRGFwAMaRJV for <ecrit@ietfa.amsl.com>; Wed, 21 Dec 2016 06:50:17 -0800 (PST)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6CBE127A91 for <ecrit@ietf.org>; Wed, 21 Dec 2016 06:50:16 -0800 (PST)
Received: by mail-qk0-x22a.google.com with SMTP id u25so72978489qki.2 for <ecrit@ietf.org>; Wed, 21 Dec 2016 06:50:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=6R/bqlC5DhLQQExSPUcvSmBNP0EPZkbEgUOmnsst+ik=; b=H6g+15kgxDEmHa0hikOITmVTjLv/uvFzL7biB2jvFD2v03T/33wKO7u+yoDRdcRj7B bl7BpsfP2QYiTWHgfHMj02FrpJyX9j07dP0Fj3ib3OBpvT5ZpH4N7ehqT5kpls4tUuSr AN12/wA8/vO0C7AyEzvsd28UTieeyTmoIDlXqxlpsWYpycEMRfLN+2N7hMcYUkeFjtT7 8ElDnU0NOkpwfHhQ+F9Nrv1TIDUHhrSdmtdlxASrR+xE/9NYqoPbaFybK+nbCiQ2qX2E asS+SHsX1nSUqST9kj6XAhELBlyJW+2HX+OXEEsZH0Wav9PqRGTn9mMsI43EWiEyZPnA LoKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=6R/bqlC5DhLQQExSPUcvSmBNP0EPZkbEgUOmnsst+ik=; b=C8ZyAXZtrr0E/AaITX5hK8Wflz40JYw+oKT1yxGwkbXn+wkGJ7VHBC0A8uk49SkuYf F4Uktm64uKwWhf6WpBGNVzSQMQ50loeLLw0uXKxE5oRHCiPLQvJ/28fmGnQ2y3Ayn+Az WUTs+HqDZc7TZsFTSu0tVwX3fIgvOCzNWkvW6YRD0MTAj+/kZz7F7i4CNnMaf8//K8uC +D/MOzzc8OFzWib/jfUb2EfQoHG/Lo52rgbK3h6wJ3tDi5LWNn6jpi1plqTEqvpWfWKd tJ9ZfBWJLO2qu1aS4WRL+GV+/s01jFNhJ7PS+N64hFGydseAdsIWgVSczp7OHQ7TsDjD NETA==
X-Gm-Message-State: AIkVDXKuloDTCqgvlxd8xgJVYUkR8X+AxURcexYeQC4VU6TKoNEBp2ZtIqwrHe2yF7QyJQ==
X-Received: by 10.55.70.67 with SMTP id t64mr5706597qka.78.1482331815902; Wed, 21 Dec 2016 06:50:15 -0800 (PST)
Received: from [10.33.192.26] ([156.154.81.54]) by smtp.gmail.com with ESMTPSA id 6sm15670660qke.18.2016.12.21.06.50.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 21 Dec 2016 06:50:14 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_818211ED-3C6D-468D-AA16-E3C1B96C2C78"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <AM5PR0701MB24681A713CD739498C17C8C7E5930@AM5PR0701MB2468.eurprd07.prod.outlook.com>
Date: Wed, 21 Dec 2016 09:50:12 -0500
Message-Id: <2055C2AF-C910-44BE-81FC-CA06FE1E0E2C@brianrosen.net>
References: <148192031155.14691.15926529065829067237.idtracker@ietfa.amsl.com> <80337302-56F1-4A10-A531-14C09A499B6B@brianrosen.net> <AM5PR0701MB2468356AEB66DF2D791718E7E5900@AM5PR0701MB2468.eurprd07.prod.outlook.com> <BF57D33D-CCBF-4F9D-B131-4BEF1AC2F508@brianrosen.net> <AM5PR0701MB24681C78CFD6E6332E1CC889E5900@AM5PR0701MB2468.eurprd07.prod.outlook.com> <3F1B2A2C-97DB-4E07-9913-A50438A859FB@brianrosen.net> <AM5PR0701MB24681A713CD739498C17C8C7E5930@AM5PR0701MB2468.eurprd07.prod.outlook.com>
To: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/UXq9y3Id0QcePN679TNKi0BhQVo>
Cc: ECRIT <ecrit@ietf.org>
Subject: Re: [Ecrit] I-D Action: draft-rosen-ecrit-service-urn-subregistries-00.txt
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, 21 Dec 2016 14:50:19 -0000

There shouldn’t be any hurry to get a URN defined.  Deployments typically take years of planning, acquiring new systems, training, etc.
If there is a time crunch, the expert can authorize a temporary registration as we did with police.national until the sub registry document is published.

Most services won’t need this two level registration.

Brian

> On Dec 21, 2016, at 1:50 AM, Ivo Sedlacek <ivo.sedlacek@ericsson.com> wrote:
> 
> > You need a document with IANA considerations to create a registry, but an INFO will do.
>  
> Do you mean an RFC?
>  
> That makes getting emergency URN a lot toughter than today and pretty much prevents easy and quick deployment of new emergency services, which are subservices of an existing emergency service.
>  
> Kind regards
>  
> Ivo
>  
>  
>  
> From: Brian Rosen [mailto:br@brianrosen.net <mailto:br@brianrosen.net>] 
> Sent: Tuesday, December 20, 2016 5:43 PM
> To: Ivo Sedlacek <ivo.sedlacek@ericsson.com <mailto:ivo.sedlacek@ericsson.com>>
> Cc: ECRIT <ecrit@ietf.org <mailto:ecrit@ietf.org>>
> Subject: Re: [Ecrit] I-D Action: draft-rosen-ecrit-service-urn-subregistries-00.txt
>  
> I think it’s an issue of whether we expect a number of registrations of subfoos.  If there is only 1 maybe not bother, but if we expect several, create the sub registry.  The expert can help guide.
>  
> You need a document with IANA considerations to create a registry, but an INFO will do.
>  
> The policy for the sub registry would be specified in that document.  I specified expert review in these 3. 
>  
> Brian
>  
> On Dec 20, 2016, at 10:19 AM, Ivo Sedlacek <ivo.sedlacek@ericsson.com <mailto:ivo.sedlacek@ericsson.com>> wrote:
>  
> Hello,
>  
> > Although the ABNF allows it, I think that it’s much cleaner to have the separate registries.  I will note that we have allowed the registration in
> > the existing registry, although if/when this document is published, we will remove it from the main sos registry and put it in the police sub registry.
>  
> How would it work for other services?
>  
> Imagine that a person X registers
>  
>                 urn:service.sos.foo
>  
> and later on a person Y would like to register:
>  
>                 urn:service.sos.foo.subfoo1
>                                and
>                 urn:service.sos.foo.subfoo2
>  
> What would the IANA registration policy for request to establish sub-registry of urn:service.sos.foo?
> And what would the IANA registration policy be for new entries in the urn:service.sos.foo subregistry?
>  
> > However, I do think “national” is actually a better token for this service, and I will change it in the next version.  
>  
> Thanks.
>  
> Kind regards
>  
> Ivo
>  
>  
>  
> From: Brian Rosen [mailto:br@brianrosen.net <mailto:br@brianrosen.net>] 
> Sent: Tuesday, December 20, 2016 4:04 PM
> To: Ivo Sedlacek <ivo.sedlacek@ericsson.com <mailto:ivo.sedlacek@ericsson.com>>
> Cc: ECRIT <ecrit@ietf.org <mailto:ecrit@ietf.org>>
> Subject: Re: [Ecrit] I-D Action: draft-rosen-ecrit-service-urn-subregistries-00.txt
>  
> Thanks for your comments.
>  
> Although the ABNF allows it, I think that it’s much cleaner to have the separate registries.  I will note that we have allowed the registration in the existing registry, although if/when this document is published, we will remove it from the main sos registry and put it in the police sub registry.  I have consulted with IANA on this.
>  
> I was careful to note that the token is NOT the name of the service, and trying to actually have the token be the actual name of the service will lead to many, many registrations that are effectively duplicates of one another.  Any police force which has true national scope would use the same token.  In the US, for example, it’s the FBI.
>  
> However, I do think “national” is actually a better token for this service, and I will change it in the next version.  However, I would not want to see a registration for the FBI, nor any other specific name for a national police force.  Having said that, in many countries, there are several national police forces with specialized responsibilities.  In the U.S., we have U.S. Marshalls, Drug Enforcement Agency, Immigration and Customs. Secret Service, and several others.  We don’t have emergency calling to them, so we don’t need sos tokens for them, but there are countries where there are more than one national police that do have emergency numbers and we will need tokens for them.  I would not want a “city” token instead of “municipal”.
>  
> At one point I was thinking of explicitly referencing the “A” levels from PIDF-LO for these tokens (so “A1” instead of “Provincial” and A2 instead of “Municipal”), but eventually decided that since we didn’t have A levels for all the tokens we would need that it didn’t make sense to use the A levels as the token name.  But I intended the tokens to be used that way.
>  
> Brian
>  
> On Dec 20, 2016, at 8:58 AM, Ivo Sedlacek <ivo.sedlacek@ericsson.com <mailto:ivo.sedlacek@ericsson.com>> wrote:
>  
> Hello,
>  
> Two comments to the draft:
>  
> Comment-1:
> rfc5031 defines sub-services using the following ABNF where several sub-services can be included in a service URN.
>  
>  
>      service-URN  = "URN:service:" service
>     service      = top-level *("." sub-service)
>      top-level    = let-dig [ *25let-dig-hyp let-dig ]
>      sub-service  = let-dig [ *let-dig-hyp let-dig ]
>      let-dig-hyp  = let-dig / "-"
>      let-dig      = ALPHA / DIGIT
>      ALPHA        = %x41-5A / %x61-7A   ; A-Z / a-z
>      DIGIT        = %x30-39 ; 0-9
>  
> rfc7163 allows registration of additional sub-services of the service URN with the 'sos' service type using expert review.
>  
> Thus, registration of sub-services under urn:service.sos.police (under urn:service.sos.ambulance, and under urn:service.sos.fire) is possible already now and there should be no need to define new subregistries.
>  
> Comment-2:
>  
> The proposed new police emergency services do not address the needs of the Czech republic as:
> - Czech republic defines emergency service of national police; and
> - Czech republic is not a federation of states or provinces (and thus "federal" does not fit).
> Proposal: change "federal" to "national".
>  
> Kind regards
>  
> Ivo Sedlacek
>  
>  
> From: Ecrit [mailto:ecrit-bounces@ietf.org <mailto:ecrit-bounces@ietf.org>] On Behalf Of Brian Rosen
> Sent: Friday, December 16, 2016 9:33 PM
> To: ECRIT <ecrit@ietf.org <mailto:ecrit@ietf.org>>
> Subject: [Ecrit] Fwd: I-D Action: draft-rosen-ecrit-service-urn-subregistries-00.txt
>  
> FYI
> 
> 
> 
> 
> Begin forwarded message:
>  
> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
> Subject: I-D Action: draft-rosen-ecrit-service-urn-subregistries-00.txt
> Date: December 16, 2016 at 3:31:51 PM EST
> To: <i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>>
> Reply-To: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>  
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>        Title           : A Subregistry for urn:service:sos.police, fire and ambulance
>        Author          : Brian Rosen
>             Filename        : draft-rosen-ecrit-service-urn-subregistries-00.txt
>             Pages           : 5
>             Date            : 2016-12-16
> 
> Abstract:
>   In most countries, there are multiple kinds of police forces.
>   RFC5031 defines a "Service URN" which is used to route emergency
>   calls.  The urn has a sub registry for different kinds of emergency
>   services that may be reached from different telephone numbers or
>   service numbers (as opposed to a single number like 112).  In many
>   countries, the "police" service is not a single service, but more
>   than one service where the service area and/or types of emergencies
>   they respond to are different.  In some countries there are multiple
>   ambulance services.  This document defines sub registries for
>   urn:service:sos.police, urn:service:sos.ambulance and, for
>   completeness, urn:service:sos.fire.  It also provides an initial set
>   of entries for these sub registries.  These services are in addition
>   to the base urn:service:sos.police, etc. services.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-rosen-ecrit-service-urn-subregistries/ <https://datatracker.ietf.org/doc/draft-rosen-ecrit-service-urn-subregistries/>
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-rosen-ecrit-service-urn-subregistries-00 <https://tools.ietf.org/html/draft-rosen-ecrit-service-urn-subregistries-00>
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/ <ftp://ftp.ietf.org/internet-drafts/>
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
> https://www.ietf.org/mailman/listinfo/i-d-announce <https://www.ietf.org/mailman/listinfo/i-d-announce>
> Internet-Draft directories: http://www.ietf.org/shadow.html <http://www.ietf.org/shadow.html>
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt <ftp://ftp.ietf.org/ietf/1shadow-sites.txt>