Re: [Ecrit] country specific emergency URNs

Henning Schulzrinne <hgs@cs.columbia.edu> Mon, 10 July 2017 12:45 UTC

Return-Path: <hgs10@columbia.edu>
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 CD2B1131745 for <ecrit@ietfa.amsl.com>; Mon, 10 Jul 2017 05:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 H_IpKI-0DH0r for <ecrit@ietfa.amsl.com>; Mon, 10 Jul 2017 05:45:26 -0700 (PDT)
Received: from outprodmail02.cc.columbia.edu (outprodmail02.cc.columbia.edu [128.59.72.51]) (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 18AAD13173F for <ecrit@ietf.org>; Mon, 10 Jul 2017 05:45:25 -0700 (PDT)
Received: from hazelnut (hazelnut.cc.columbia.edu [128.59.213.250]) by outprodmail02.cc.columbia.edu (8.14.4/8.14.4) with ESMTP id v6ACj7NZ048541 for <ecrit@ietf.org>; Mon, 10 Jul 2017 08:45:25 -0400
Received: from hazelnut (localhost.localdomain [127.0.0.1]) by hazelnut (Postfix) with ESMTP id 028EE6D for <ecrit@ietf.org>; Mon, 10 Jul 2017 08:45:25 -0400 (EDT)
Received: from sendprodmail02.cc.columbia.edu (sendprodmail02.cc.columbia.edu [128.59.72.14]) by hazelnut (Postfix) with ESMTP id AA1C46D for <ecrit@ietf.org>; Mon, 10 Jul 2017 08:45:24 -0400 (EDT)
Received: from mail-oi0-f72.google.com (mail-oi0-f72.google.com [209.85.218.72]) by sendprodmail02.cc.columbia.edu (8.14.4/8.14.4) with ESMTP id v6ACjOld026189 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <ecrit@ietf.org>; Mon, 10 Jul 2017 08:45:24 -0400
Received: by mail-oi0-f72.google.com with SMTP id t187so7883421oie.3 for <ecrit@ietf.org>; Mon, 10 Jul 2017 05:45:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=f/qm+VKSJdjrGPrzVhqernagNlCddeFAdC+4+Nj+vco=; b=dcnp59se5PYafLxUWLf80pX+TWZQecMlmnfQaf1aEJqWbD6Y/BWgPExtQhqrwgYDj0 Rsu3elK5bpRUWE345uz+UQdKHoGmoo136bieGGsOEM53nolH/GJ+izklW+9/xcB3Zl00 gvBazKSUPSbnXUSKh9Sz2YDUFdVFfMak3QwRwFUXbPu9GqiXwd8L9V5PxX/Ng72vRH2h Y0VmZtR4kNM0AKVdECcOIUAsdX7K5DmxZ5y319Jqjn7VmY1jvypLbdmOsg8wBtWodnzk qybsDMlhPyH5OWImoC5ljHFulZfs/uKMIpCjNClUDsr//fUEM6Ksj46OAZJPg9uu5D4Z myGw==
X-Gm-Message-State: AIVw110rD+4+zsAIu/xXdoPomrUuBYOPD7jfdcX5zNWxvmH9NGXt7Rr4 JDsbxkby1e6x4PoJmztKLRdFvYrI95OKystHSkxMAnekxj81k4p5HscxoNNMpOc88zWTRAADkiR ZQqE0vWef7lJy+mFMHsE0
X-Received: by 10.202.80.135 with SMTP id e129mr7276831oib.8.1499690723510; Mon, 10 Jul 2017 05:45:23 -0700 (PDT)
X-Received: by 10.202.80.135 with SMTP id e129mr7276828oib.8.1499690723315; Mon, 10 Jul 2017 05:45:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.65.66 with HTTP; Mon, 10 Jul 2017 05:45:02 -0700 (PDT)
In-Reply-To: <52809D5B0606C049903AD6AD07E033E10327096BB1@ATWIREMXSC0101.sv.ad.tmo>
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>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Mon, 10 Jul 2017 08:45:02 -0400
Message-ID: <CACgrgBazRYu_XAu2S1t5-mEoMPYmRVFG+az71LLej_wTVFTiqw@mail.gmail.com>
To: "Aleksiev, Vasil" <Vasil.Aleksiev@t-mobile.at>
Cc: "ecrit@ietf.org" <ecrit@ietf.org>
Content-Type: multipart/alternative; boundary="001a113b0260d623d70553f5f4f7"
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.78 on 128.59.72.14
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/ZDdZJ11gmhkMPH4t9Erd8gXjSs0>
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: Mon, 10 Jul 2017 12:45:28 -0000

We can't predict what unknown third parties, such as regulators, will do,
but since registrations of sos URNs is not a high-effort project, we can
always go back and try again. I think it is incumbent upon standards
organizations to explain that these are "mechanical" protocol constants,
not user interface elements.

The most productive way forward would be to enumerate the services by
description (and, for concreteness, the [short code] number and country)
and whether these services are meant as emergency services (i.e., a vehicle
with flashing lights get dispatched) or as counseling (i.e., somebody
provides advice or information over the phone, with no expectation that
anything or anyone is dispatched to your location). That way, we can
collectively judge which ones are sufficiently similar and avoid any
collisions, as well as judge whether a hierarchical label is useful. As I
mentioned, the goal is collision avoidance within a country and rough
categorization, without worrying about fine details. (After all, we don't
get too concerned for 112/911 of how each country or region organizes their
fire brigades and whether dispatch is done across services, integrated or
separated by service.)

>From your note, it is clear that we're lacking an authoritative description
in some cases. For example, I admit that I don't understand the 197 service
(why would children call in terrorism alerts?). I'm afraid in some cases,
nuance or substance has been lost in translation (literally, in some cases).

Since you seem to have a good list of emergency services, maybe you can get
this started and others can chime in. Again, I wouldn't worry about the
labels at this point as that is probably more of a distraction.

In some cases, I think it would be helpful to have somebody with local
knowledge contribute, possibly after consulting with local authorities.

Henning

On Mon, Jul 10, 2017 at 5:31 AM, Aleksiev, Vasil <Vasil.Aleksiev@t-mobile.at
> wrote:

> Hi to all,
>
>
>
> In my first bullet regarding unique emergency URN I have given the example
> with differences between IMS and CS and to show that emergency numbers are
> handled differently and also to show the roaming treatment. For every
> emergency number defined by regulator it is needed to have sos domain. Sos
> triggers the respective routing with emergency category and this is
> different from the CS treatment where some numbers currently are not
> handled as emergency and detected as such on a later stage. I am glad to
> understand that this is also the view of ECRIT and for every emergency
> service defined by local law there shall be sos definition.
>
>
>
> In my second bullet regarding difficulties of consolidating services in
> different nations I have given examples of 142 – Telefonseelsorge
> (telephone soul care), 106 – Mental problems hotline. Just looking to the
> names - the services look quite similar, so how these two services will be
> named under sos? Sos.soulcare and sos.mentalhealth?
>
> 197 – Terror Alert – Child Alert in France – I suppose the name shall be
> sos.terror-child? I think somebody from France should explain the specifics
> regarding this emergency service.
>
> 114- Child emergency in Italy – here is easy – sos.children.
>
>
>
> In my third bullet regarding counselling services in one country
> considered as emergency in other I have given examples of 147 and
> +498001110333 <+49%20800%201110333>. I suppose 147 (emergency service for
> children and youth) shall be sos.children-and-youth. The service does not
> have the same name as 114- child emergency in Italy. +498001110333
> <+49%20800%201110333> shall be counseling.children.
>
>
>
> In my fourth bullet regarding the will of the local regulator – I fully
> agree that the urns may even look like sos.1, sos.2, sos.3, sos.4 … But the
> problem might be that the local regulator does not think so. Till now in
> Austria there is no law regarding routing of IMS emergency calls, but when
> it is written it could be written inside that urns shall be
> sos.telefonseelsorge, sos.kinder.147.
>
>
>
> I see a problem with that I am not authorized to make registrations
> regarding emergency URNs – I am not representing the regulator or the other
> operators in the respective countries.
>
> Of course I could try to define sos.children and I agree that this will be
> enough, but if the regulator later decides that this is not ok?
>
>
>
> Best regards,
>
>
>
> Vasil
>
>
>