Re: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)

Dan Mongrain <dan@mongrain.org> Wed, 20 March 2013 02:12 UTC

Return-Path: <dan@mongrain.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 A44F921F8E23 for <ecrit@ietfa.amsl.com>; Tue, 19 Mar 2013 19:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level:
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H7GSfRp4gNRn for <ecrit@ietfa.amsl.com>; Tue, 19 Mar 2013 19:12:07 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8030921F8D3C for <ecrit@ietf.org>; Tue, 19 Mar 2013 19:12:00 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id c12so1514192ieb.6 for <ecrit@ietf.org>; Tue, 19 Mar 2013 19:12:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=dWP0pgu852lIwi0ZV8x+GkvFaYye8fAz2CUFADKi+5c=; b=lzx3xq25S6gk3QvIl+C/Esidf6+UhPoSkXaUgThHINYxQqJ6WPQO0/5V/uHOYTrDWc njKVIcJ6EBvMwVPqZUDknfRg9Qc6EY3h6/htDiydQrLM3YuyfF3lDHSkDobe3cKvfhhr G8qMzo+F1/5pGGuWro9DTkniFX0bflTOz9p/1vkkFUHwMwsf0OEyFbj30nKL911n+IbP HpbBQA9KHqqZWml2prV6BWjV6q8n2RfHJDSGBfK4xMWqAF8wx2N6Dv3ZGVqIo56t8W+X Nsemiw3MYT44oul/bGG9WXZrnLBTaSvJMDaTSYG+LRx0Av9PO59OjKjykBjEr9syvSgv sGqg==
MIME-Version: 1.0
X-Received: by 10.50.37.236 with SMTP id b12mr384865igk.42.1363745519934; Tue, 19 Mar 2013 19:11:59 -0700 (PDT)
Received: by 10.50.193.133 with HTTP; Tue, 19 Mar 2013 19:11:59 -0700 (PDT)
X-Originating-IP: [96.23.59.4]
In-Reply-To: <39B5E4D390E9BD4890E2B310790061010A7AFD@ESESSMB301.ericsson.se>
References: <CD6E08DB.3F093%mlinsner@cisco.com> <B321B1C2-086E-441B-B7C5-D0130587B851@neustar.biz> <39B5E4D390E9BD4890E2B310790061010A7AFD@ESESSMB301.ericsson.se>
Date: Tue, 19 Mar 2013 22:11:59 -0400
Message-ID: <CAME5mgu1xOu41hFmSCM79SDU7Zk75yM2__ggn7Y2hVdA6SWe9Q@mail.gmail.com>
From: Dan Mongrain <dan@mongrain.org>
To: "ecrit@ietf.org" <ecrit@ietf.org>
Content-Type: multipart/alternative; boundary="f46d044788d947bbf804d851bf40"
X-Gm-Message-State: ALoCoQnrq7MCWE1gx6AC98XrcY5nWlwVmq90EDOJL5W+AbFDfBx8P2fB42BxJH/AIMz2hCjIuphC
Subject: Re: [Ecrit] [IANA #658921] General Request for Assignment (urn-serviceid-labels)
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Mar 2013 02:12:08 -0000

I am currently writing a draft that will specify jurisdictional scope for a
Service URN.  I hope to have it completed and published early next week.
As I have suggested previously it documents the addition of a PIDF-LO civic
tag at the end of a Service URN to specify a specific jurisdiction in the
case multiple jurisdictions offer the service.  I think that by proceeding
this way, it alleviates the need to register multiple combinations of
Service URNs and jurisdictional scopes.  We can still register the generic
Service URNs (sos.police.traffic, sos.fire.highrise, etc.) and in locations
where the service is offered by multiple jurisdictions then one can add the
jurisdictional scope at the end of the Service URN.

Dan

On Tue, Mar 19, 2013 at 1:38 PM, Ivo Sedlacek <ivo.sedlacek@ericsson.com>wrote:

> Hello,
>
> I am the author of the IANA registration request.
>
> I would be happy with "country" instead of "national" in the URN, if
> that's the experts' preference.
> I would also be happy with "A3" instead of "local" in the URN, if that's
> the experts' preference.
>
> I.e.
> - urn:service:sos.police.country - The 'police.national' service refers to
> the emergency service offered by the police department or other law
> enforcement authorities of the government of a country.
> - urn:service:sos.police.A3 - The 'police.local' service refers to the
> emergency service offered by the police department or other law enforcement
> authorities of the authorities of a city, township, shi (JP).
>
> Do I need to send another IANA registration request or can the IANA
> existing registration request be modified?
>
> Kind regards
>
> Ivo Sedlacek
>
> This Communication is Confidential. We only send and receive email on the
> basis of the terms set out at www.ericsson.com/email_disclaimer
>
>
> -----Original Message-----
> From: ecrit-bounces@ietf.org [mailto:ecrit-bounces@ietf.org] On Behalf Of
> Rosen, Brian
> Sent: 19. března 2013 17:46
> To: Marc Linsner
> Cc: ecrit@ietf.org
> Subject: Re: [Ecrit] [IANA #658921] General Request for Assignment
> (urn-serviceid-labels)
>
> Yes
>
> In my opinion, urn:service:sos.police.national should be registered,
> although I would prefer the term "country" for reasons detailed below.
>
> I do not believe urn:service:sos.police.local should be registered,
> because the term "local" is ambiguous in many countries and regions.  In
> some areas, there are multiple levels of "local" that may have separate
> service URLs.  For example, you could have state, county and municipal
> police agencies, any of which could be considered "local".
>
> While an expert does not usually supply alternatives, I think the ecrit
> work group has considered the suggestion to use the "A" levels in PIDF-LO
> to denote the levels of "local".  So, for example,
> urn:service:sos.police.a2 would be the county police, assuming A1 was
> state, A2 was county and A3 was city.  One could speculate whether
> urn:service:sos.police.a6 (neighborhood) was useful for anything, but there
> are "neighborhood watch" organizations that might qualify, and "vigilante"
> is probably not a good registration.
>
> Using the "A" levels leads you to use "country" as that is the top level
> name for the field in PIDF-LO.  "national" is an obvious synonym, and I
> think it's okay to use it.
>
> However, "local" is ambiguous.
>
> Brian
>
> On Mar 19, 2013, at 12:32 PM, Marc Linsner <mlinsner@cisco.com>
>  wrote:
>
> > Brian,
> >
> > Would you please provide a review of this IANA request for registrations.
> >
> > Thanks,
> >
> > Marc & Roger
> >
> > -----Original Message-----
> > From: Amanda Baber via RT <iana-prot-param-comment@iana.org>
> > Reply-To: <iana-prot-param-comment@iana.org>
> > Date: Friday, February 15, 2013 6:34 PM
> > Cc: <ecrit-chairs@tools.ietf.org>
> > Subject: [IANA #658921] General Request for Assignment
> > (urn-serviceid-labels)
> > Resent-From: <wg-alias-bounces@tools.ietf.org>
> > Resent-To: <rmarshall@telecomsys.com>, <marc.linsner@cisco.com>
> > Resent-Date: Fri, 15 Feb 2013 23:22:12 +0000
> >
> >> Dear Marc and Roger,
> >>
> >> IANA just received a request for two registrations in the 'sos'
> >> Sub-Services registry at
> >> http://www.iana.org/assignments/urn-serviceid-labels, which has the
> >> ECRIT working group listed as its expert reviewer.
> >>
> >> Can you ask the working group to review the request below? If these
> >> are OK, how should we fill out the Description fields in the registry?
> >>
> >> thanks,
> >>
> >> Amanda Baber
> >> IANA Request Specialist
> >> ICANN
> >>
> >> ===
> >>
> >> Contact Name:
> >> Ivo Sedlacek
> >>
> >> Contact Email:
> >> ivo.sedlacek@ericsson.com
> >>
> >> Type of Assignment:
> >> Assignment of an service URN with the 'sos' service type as specified
> >> in RFC5031, section 4.2.
> >>
> >> The following service URNs are proposed to be registered:
> >> - urn:service:sos.police.local - The 'police.local' service refers to
> >> the emergency service offered by the police department or other law
> >> enforcement authorities of the local or municipal authorities.
> >> - urn:service:sos.police.national - The 'police.national' service
> >> refers to the emergency service offered by the police department or
> >> other law enforcement authorities of the national government.
> >>
> >> Registry:
> >> Service URN Labels, 'sos' Sub-Services as shown at
> >>
> http://www.iana.org/assignments/urn-serviceid-labels/urn-serviceid-labels.
> >> xml
> >>
> >> Description:
> >> In the Czech republic and Poland, there are two public safety
> >> answering points (PSAP) offering the police related emergency
> >> services. The PSAP of the municipal police and the PSAP of the
> >> national police. There is currently no way how to distinguish whether
> >> the user wishes to contact the PSAP of the municipal police or the PSAP
> of the national police.
> >>
> >> In Czech, the related regulation is
> >> http://aplikace.mvcr.cz/sbirka-zakonu/ViewFile.aspx?type=c&id=5134
> >> pages
> >> 9 and 10 section 4.5 which lists the number 156 for "Obecní policie"
> >> (= municipal police) and the numbers 158 for "Policie České
> >> republiky" (= Czech republic police). Both numbers are listed with
> >> note 2) which states "Číslo je národním číslem pro tísňové volání" (=
> >> the number is a national number for emergency calls).
> >>
> >> In Poland,
> >> http://uke.gov.pl/tablice-numerow-kierowania-alarmowego-nka-9410
> >> lists the number 986 for "straż miejska" (= municipal police) and the
> >> number
> >> 997 for Policja (= police) as "numery alarmowe" (= emergency numbers).
> >>
> >> Additional Info:
> >> The registry is defined by RFC5031, section 4.2
> >
> >
>
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit
>