IETF Logo Mail Archive

Re: [Ecrit] country specific emergency URNs

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 11 August 2017 13:33 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 0A53013218C for <ecrit@ietfa.amsl.com>; Fri, 11 Aug 2017 06:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 uGgBvXRK5SHX for <ecrit@ietfa.amsl.com>; Fri, 11 Aug 2017 06:33:37 -0700 (PDT)
Received: from outprodmail01.cc.columbia.edu (outprodmail01.cc.columbia.edu [128.59.72.39]) (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 1616313201A for <ecrit@ietf.org>; Fri, 11 Aug 2017 06:33:36 -0700 (PDT)
Received: from hazelnut (hazelnut.cc.columbia.edu [128.59.213.250]) by outprodmail01.cc.columbia.edu (8.14.4/8.14.4) with ESMTP id v7BDU5gE045883 for <ecrit@ietf.org>; Fri, 11 Aug 2017 09:33:35 -0400
Received: from hazelnut (localhost.localdomain [127.0.0.1]) by hazelnut (Postfix) with ESMTP id C16F96D for <ecrit@ietf.org>; Fri, 11 Aug 2017 09:33:35 -0400 (EDT)
Received: from sendprodmail04.cc.columbia.edu (sendprodmail04.cc.columbia.edu [128.59.72.16]) by hazelnut (Postfix) with ESMTP id 949456D for <ecrit@ietf.org>; Fri, 11 Aug 2017 09:33:35 -0400 (EDT)
Received: from mail-oi0-f69.google.com (mail-oi0-f69.google.com [209.85.218.69]) by sendprodmail04.cc.columbia.edu (8.14.4/8.14.4) with ESMTP id v7BDXZMV048038 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <ecrit@ietf.org>; Fri, 11 Aug 2017 09:33:35 -0400
Received: by mail-oi0-f69.google.com with SMTP id x3so3840815oia.8 for <ecrit@ietf.org>; Fri, 11 Aug 2017 06:33:35 -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=9B5N+nRMPCSUnJm/BB84vJnzKza6e3B1cFl5+AD5Acg=; b=l3NpZ75p6Bo56kMYAre42fUGXSdmHNFyvcW5Ga+sNEr2N818b0X2D39Z+pulJuZEBD 8ZKe5ga7CHDJ5o632rDeAa7ZnYpp4WfaB1+sEQkbN073XSPPVeTHaWij/9l3jTkbN3Gi gknuGX0jUd9ue4gZ5xJQ6bNRjmQWC8fl2GiXt8NcGmKm/o3WCdEojqPiGO8vVYW3rePm ydHYfZRGnvapkKXJcD2X1kJIYOkHowXITZlaHN6S7YWlfH0fEzKnCLq7hasL359C1uca dxyw2hz94VbwsxiMpFKKsesP2YZYr0Oj3bj84geMHwdOqlKVzq1kSSIx7celLLNPcz35 gKog==
X-Gm-Message-State: AHYfb5ithzeolcGT2qdPw6PifSzCfFOpmVd6QR9MIX8w1UPS5mS2jd07 8Jpnz8Owi76G71IjDzzyyNo2917/13pOiWAnB38uwR6NAjhNqVfd/Wkl6pL1wJwJpp9Dwzi7o5P o6Kz48QTkQC5Ue89iPNZM
X-Received: by 10.202.241.10 with SMTP id p10mr16592230oih.56.1502458414793; Fri, 11 Aug 2017 06:33:34 -0700 (PDT)
X-Received: by 10.202.241.10 with SMTP id p10mr16592210oih.56.1502458414505; Fri, 11 Aug 2017 06:33:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.232.225 with HTTP; Fri, 11 Aug 2017 06:33:13 -0700 (PDT)
In-Reply-To: <AM5PR0701MB2468386DA9EB4D511C6E9669E5890@AM5PR0701MB2468.eurprd07.prod.outlook.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> <CACgrgBbTTBv0ZHShmsSyW3GS06t-MC3YnRqr-K2rD+_r-+PobA@mail.gmail.com> <52809D5B0606C049903AD6AD07E033E10327178B14@ATWIREMXSC0101.sv.ad.tmo> <CACgrgBYfshZjN9Q7CZsZoAetfO_g7cs-TwzEyT7n6BhbXoQWkQ@mail.gmail.com> <52809D5B0606C049903AD6AD07E033E10327CBCE55@ATWIREMXSC0101.sv.ad.tmo> <CACgrgBb5syk=NaPF+ud30OiQJyMdDPtWn-fEvC0nhhC0FX3pSQ@mail.gmail.com> <AM5PR0701MB2468A700FA1E0170D1540197E5890@AM5PR0701MB2468.eurprd07.prod.outlook.com> <AM5PR0701MB2468386DA9EB4D511C6E9669E5890@AM5PR0701MB2468.eurprd07.prod.outlook.com>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Fri, 11 Aug 2017 09:33:13 -0400
Message-ID: <CACgrgBbSsE=sYZCmYVeseaFmBEyTKu1MtDBKWWOWhbC8WH0FRw@mail.gmail.com>
To: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
Cc: "Aleksiev, Vasil" <Vasil.Aleksiev@t-mobile.at>, "ecrit@ietf.org" <ecrit@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0933a816361c05567a5cdb"
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.78 on 128.59.72.16
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/S7RN2nmoe5SgZTQqXEWxv2It8xs>
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: Fri, 11 Aug 2017 13:33:39 -0000

Carriers are not asked to "define" an emergency service or create a new
one. You are translating an existing emergency number, defined by
regulators, statute or just custom, into an internal protocol identifier
(SOS URN) invisible to users. Can you point to an actual regulation that
prevents carriers (or standards bodies) from defining protocol constants?
Again, I think we'll make more progress if we can get beyond feelings and
fears and to facts.

Henning

On Fri, Aug 11, 2017 at 6:09 AM, Ivo Sedlacek <ivo.sedlacek@ericsson.com>
wrote:

> To be clear - by referring to "the operators" below, I meant the operators
> which expressed the view in this discussion so far.
>
>
>
> Kind regards
>
>
>
> Ivo
>
>
>
> *From:* Ecrit [mailto:ecrit-bounces@ietf.org] *On Behalf Of *Ivo Sedlacek
> *Sent:* Friday, August 11, 2017 8:55 AM
> *To:* Henning Schulzrinne <hgs@cs.columbia.edu>; Aleksiev, Vasil <
> Vasil.Aleksiev@t-mobile.at>
> *Cc:* ecrit@ietf.org
> *Subject:* Re: [Ecrit] country specific emergency URNs
>
>
>
> Hello,
>
>
>
> Case 1: The regulator does not care about SOS URNs, considering this a
> user-invisible network-internal matter. The local (national) carriers map
> the emergency numbers in a country to a SOS URN. If there's no suitable
> match, a new URN is defined, with a short registration process that we are
> currently exercising. (I suspect that the US would work that way.)
>
>
>
> you still do not seem to understand the point.
>
>
>
> The operators do not feel authorized to request definition of the new
> emergency service and its sos URN.
>
>
>
> They operators feel that this is responsiblity of the regulator.
>
>
>
> Kind regards
>
>
>
> Ivo
>

v2.23.0 | Report a Bug | By Email