IETF Logo Mail Archive

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

Brian Rosen <br@salsgiver.com> Thu, 17 November 2016 04:50 UTC

Return-Path: <br@salsgiver.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 BC1BD129532 for <ecrit@ietfa.amsl.com>; Wed, 16 Nov 2016 20:50:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level:
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, 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 rRSBFdUhgj5W for <ecrit@ietfa.amsl.com>; Wed, 16 Nov 2016 20:50:37 -0800 (PST)
Received: from email.salsgiver.com (email.salsgiver.com [206.67.234.106]) (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 6E7C91293F3 for <ecrit@ietf.org>; Wed, 16 Nov 2016 20:50:37 -0800 (PST)
Received: from [10.96.8.226] ([156.154.81.54]) (authenticated bits=0) by email.salsgiver.com (8.15.2/8.15.2) with ESMTPA id uAH4o6q0025323; Wed, 16 Nov 2016 23:50:10 -0500 (EST) (envelope-from br@salsgiver.com)
X-Authentication-Warning: email.salsgiver.com: Host [156.154.81.54] claimed to be [10.96.8.226]
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Brian Rosen <br@salsgiver.com>
In-Reply-To: <p06240607d4529b214717@[99.111.97.136]>
Date: Thu, 17 Nov 2016 13:50:06 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <640F959A-2915-4037-A760-DAEEC3A8D30B@salsgiver.com>
References: <CAJD5LR00UgK2u-T8soQmSJ0QryoOio6Ezjn3FTf4KonBidcWjA@mail.gmail.com> <6337FF74-A230-42C9-989A-AA7A9EC07277@salsgiver.com> <8e9f6d731099499ca529eecb8236f4ce@HE105828.emea1.cds.t-internal.com> <AM5PR0701MB2468D8A9C64080873E9014D4E5BE0@AM5PR0701MB2468.eurprd07.pro d.outlook.com> <003EC069-30F6-4874-9CF1-6BB2110A3841@salsgiver.com> <p06240607d4529b214717@[99.111.97.136]>
To: Randall Gellens <rg+ietf@randy.pensive.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/V87NVnTEYRpj-iryFguCWeBXiKM>
Cc: "iana@iana.org" <iana@iana.org>, "ecrit@ietf.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: Thu, 17 Nov 2016 04:50:38 -0000

>> 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.
> 
> Since you've identified cases that don't fit well into the "a" levels, as long as we don't expect a large number of such police subservices to be registered, I'd suggest using the descriptive names instead.  (E.g., "police.municipal", "police.tourist", maybe "police.FBI" or "police.DEA".
> 

How would you suggest we handle multiple names for the same “level”.  An easy example is “State Police” vs “Provincial Police”.  These are the same A1 level.  You can have “County”, or “Borough” or “Regional” for A2.  You can have “City” or “Municipal” or “Local” or … for A3.

Do we have separate listings (they are cheap, but we really want to be able to differentiate easily.

Brian

v2.23.0 | Report a Bug | By Email