Re: [Ecrit] country specific emergency URNs

Brian Rosen <br@brianrosen.net> Sat, 15 July 2017 14:02 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 B9B74129B26 for <ecrit@ietfa.amsl.com>; Sat, 15 Jul 2017 07:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level:
X-Spam-Status: No, score=-2.588 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, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] 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 jVadWpewxNaF for <ecrit@ietfa.amsl.com>; Sat, 15 Jul 2017 07:02:32 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 2D678131671 for <ecrit@ietf.org>; Sat, 15 Jul 2017 07:02:32 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id v193so34477424ywg.2 for <ecrit@ietf.org>; Sat, 15 Jul 2017 07:02:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=k00IvZRtgUYZyooKhXEYlTtWZuo92S72AG11H8nVJ4o=; b=rOPQqZIATube3G8Pw7QAS+REbMCOR6AlScSiso5804KfDLH52zp5iLhb5Xon069G3T 2Hqw0a458hsGdIAyXv/Z0on7MtJscHJS4msb76ArqJ64J/8wVXTLuZmv+2KOwoFG9l08 /0fJwmymzZWs0f2uucJ6LYN4iOlnZVH6baRo4/ENyAyGwRWodXW3xq9Q0B9d/a7+qYLL 4/ptfi7W2OmG50WQ/1x41qFhS3bxnLuiAbaYJ4IBnnGgwzSDVcu9YVmmH1IN63WVlA6f QDMUZSMyFl0SEqjqZcVgdJsHcxuDvhLjA3x36uLTyxH/hEvjrm4oITWAt+Yg3MRxriuc Po9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=k00IvZRtgUYZyooKhXEYlTtWZuo92S72AG11H8nVJ4o=; b=DeLzz1uMEihDfP0KTyNQRgbEhBZFek0SzRxHLse/6RVbrRUd2rF0ikzLHvq6oV9XNJ 9xivNaKT6gUfN2IClG83cDWbT5r3DvuFvxAyofakQ/5QBCJQ5MEUBuAoPVcJivFjHCsa Nzv56BKFhrFwKRoFMjYIba5C+HSYllqYoFPMQLhPxf9lxxg7mrlD9N8E7x4Tcwa7Ohpr 7QquENaZejcrCLL8ujE+v6vfCLP/iThpU5M4k9A8qk/2H0IxuYuQKnG/7+wXcew5EXQt /2UgaJKSyRMPdFAawscQYHozai9S2A9ew5LoOWoStxNoVmxwJ882aNtunMxL6kklOZ2T fiSQ==
X-Gm-Message-State: AIVw1125BjMMiutHCc5rjd49vPMiOMlqsEMmOpeUIiIU9NY5l6VZXkXS SzMoxtufxQwBzoISGEJQ9Q==
X-Received: by 10.129.74.133 with SMTP id x127mr10338592ywa.42.1500127351393; Sat, 15 Jul 2017 07:02:31 -0700 (PDT)
Received: from [10.96.10.159] (neustar-sthide-nat1.neustar.biz. [156.154.81.54]) by smtp.gmail.com with ESMTPSA id u138sm3968760ywf.64.2017.07.15.07.02.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Jul 2017 07:02:30 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <FD4700F9-BF54-40D5-BC4E-C9661BBFE6F2@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CB6164BE-E0B7-4843-9110-BE3E2510B225"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sat, 15 Jul 2017 10:02:29 -0400
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4CC70318@ESESSMB109.ericsson.se>
Cc: "Drage, Keith (Nokia - GB)" <keith.drage@nokia.com>, "ecrit@ietf.org" <ecrit@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <52809D5B0606C049903AD6AD07E033E10326EF8FFD@ATWIREMXSC0101.sv.ad.tmo> <AF1BEB84-A0D2-44AD-9666-1C608B73BC68@brianrosen.net> <CACgrgBbgMqWn3ovUogw6o_pLPhJBpSOPZ+JgDcSfgzzChcUcAQ@mail.gmail.com> <DB5PR07MB14806FA9F5D0FA90DEF2E1E2F7AB0@DB5PR07MB1480.eurprd07.prod.outlook.com> <CACgrgBY1Y_cT_F-eT-R50H81o5=9xgTjdLgRKS2x59Ar0M4gxw@mail.gmail.com> <52809D5B0606C049903AD6AD07E033E10327096BB1@ATWIREMXSC0101.sv.ad.tmo> <CACgrgBazRYu_XAu2S1t5-mEoMPYmRVFG+az71LLej_wTVFTiqw@mail.gmail.com> <52809D5B0606C049903AD6AD07E033E1032709747D@ATWIREMXSC0101.sv.ad.tmo> <CACgrgBYUs=CfyjuPM9BX9Z1u9o7Boqtpj4=viOMB0VjYu0Aq9w@mail.gmail.com> <52809D5B0606C049903AD6AD07E033E1032709783F@ATWIREMXSC0101.sv.ad.tmo> <CACgrgBY+d==tTbVCuwLcTP_M6saYZw0UpV4Mi66DL2ToCbVeeA@mail.gmail.com> <52809D5B0606C049903AD6AD07E033E10327178504@ATWIREMXSC0101.sv.ad.tmo> <1599E1B5-CBA4-43F9-90FC-FA8D4EBAC28F@brianrosen.net> <52809D5B0606C049903AD6AD07E033E103271785EB@ATWIREMXSC0101.sv.ad.tmo> <ED1B93BE-A29D-46F5-8417-C8D56C9F83C5@brianrosen.net> <DB5PR07MB14809D599D828F1A5420CD34F7AF0@DB5PR07MB1480.eurprd07.prod.outlook.com> <1FFAF3E4-3FCF-43A9-8194-AA4B337FFFE2@brianrosen.net> <7594FB04B1934943A5C02806D1A2204B4CC600F4@ESESSMB109.ericsson.se> <3ABCE27C-CC6F-47AF-AD69-4AD38F3B55DE@brianrosen.net> <D58CED5D.1F468%christer.holmberg@ericsson.com> <ABB243B9-8F34-4E97-B71A-6035F005D09A@brianrosen.net> <7594FB04B1934943A5C02806D1A2204B4CC70318@ESESSMB109.ericsson.se>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/Ck_neP_B3xkZPzPkNQpmebnQJGU>
Subject: Re: [Ecrit] country specific emergency URNs
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 15 Jul 2017 14:02:35 -0000

I have a draft in progress:
https://tools.ietf.org/html/draft-rosen-ecrit-service-urn-subregistries-00 <https://tools.ietf.org/html/draft-rosen-ecrit-service-urn-subregistries-00>

Henning and I are going to add subtrees for several kinds of services, and we can include the non-emergency services in that.

It is informational - in only asks IANA to create sub registries, and does not update 5031.  I don’t think we need to update 5031 if we do that.

Brian

> On Jul 15, 2017, at 4:20 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> Hi,
> 
>> As in my prior message to Gunnar, I’m convinced; let’s have non-emergency services, >including one for ambulance.
> 
> Great.
> 
> The question then is whether we should update RFC 5031, to make it more clear.
> 
> Regards,
> 
> Christer
> 
>> On Jul 13, 2017, at 2:38 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>> 
>> Hi,
>> 
>> 
>> 
>>>> RFC 5031 defines semantics for the sos sub-service, and at least my 
>>>> understanding is that sos is to be used for emergency services, and 
>>>> nothing else.
>>> 
>>> There is no limit expressed, or implied, that sos is restricted to 
>>> łflashing lights˛ emergencies.  Itąs suggestive of emergency, but not 
>>> exclusively used that way.
>>> The counter example was the non-emergency ambulance service.  Using 
>>> sos.ambulance for a non emergency ambulance service, unless a country 
>>> has both an emergency and a non-emergency ambulance service that 
>>> needs urns, is appropriate I think.
>>> I donąt think it would be wrong to create a non-emergency ambulance 
>>> registration, but I also donąt think we need to.
>> 
>> I think we should have separate URNs for emergency and non-emergency 
>> services - no matter if the emg and non-emg services are provided in 
>> the same country or in different countries.
>> 
>>> There is no MUST language at all.  Anything is acceptable, although 
>>> the expert review gets to offer an opinion, and take it to the list 
>>> if needed.
>>> 
>>> The review is merely supposed to make sure the service is distinct 
>>> from an existing registration.  Registrations are cheap.
>> 
>> Not if we are going to have list discussions about the name whenever a 
>> URN is to be registered. It would prolong the registration and, 
>> depending on who participate in such discussions, the outcome would be 
>> very inconsistent.
>> 
>> So, I strongly think that if the service is an emergency service, we 
>> use sos. If the service is not an emergency service, we donąt use sos.
>> 
>> And, *URNs* are cheap, so we are not going to łrun out of them˛ if we 
>> use different ones for emergency services and non-emergency services.
>> 
>> 
>>>> If we start using non-sos for emergency services, and sos for 
>>>> non-emergency services, I think we will end up in a messŠ
>>> 
>>> The above example is how I think we donąt get into a mess.  I donąt 
>>> think there is a good reason to create an ambulance service that 
>>> isnąt in the sos tree unless we have an incidence of two services and 
>>> we need to differentiate.  Even if the ambulance service in a country 
>>> is not considered an emergency service, using sos.ambulance for it is 
>>> fine in my opinion.
>> 
>> I have a different opinion :)
>> 
>> Regards,
>> 
>> Christer
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>