Re: [Ecrit] PLEASE RESPOND: Should the WG adopt draft-rosen-ecrit-emergency-registries-01?

Brian Rosen <br@brianrosen.net> Tue, 30 August 2022 19:43 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 2E891C15DD4E for <ecrit@ietfa.amsl.com>; Tue, 30 Aug 2022 12:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CMe8Ov0fUkjm for <ecrit@ietfa.amsl.com>; Tue, 30 Aug 2022 12:43:12 -0700 (PDT)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C802BC14CF02 for <ecrit@ietf.org>; Tue, 30 Aug 2022 12:43:12 -0700 (PDT)
Received: by mail-il1-x132.google.com with SMTP id v15so3756250iln.6 for <ecrit@ietf.org>; Tue, 30 Aug 2022 12:43:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc; bh=gqKWLvgS9Ykxdmj2eClKiqO4HT7iw33KiBgMrUBPGpg=; b=i76r9Qg/9gZIcxFnc3Yla8qXF31SByjTjjBjcpdlGXA9RZjFoYYL/fZb09HELoUTkQ 6S9rFy/c1VOTUmmOP6xexEIzxm1RhXNOHjF5gP0PIjDnRrA3v2Hve+tHvlh/tO8IJglG 23cBcAIvAAyfrTu0Wxo8QQTH5+j5fyhIrdP/9n3oJ0w0+hDiOZJ5EBiSXCr6PIHKxNen 3M7xFJ7wkP92mKS02cJPvPH6o9PBPSaQpB7mFfp9TRryuyTRyRD8JXJkjA01DWevAtHD d6RsESuu+y/4/upNe/OA8XMwncwOlBxhTsEdwz3ptCZvCh1+8PbDX9BGRDk/1EB67irb sieQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc; bh=gqKWLvgS9Ykxdmj2eClKiqO4HT7iw33KiBgMrUBPGpg=; b=FZIbwsUSNobb0TbHPjsziL0UglWmi4pOKg5rgAwUAvUlrillAH1P9Oq44vzPNyzfLY aL2eHSduIIwpGWwmkMjUJvJ830xIBzJ6FdQMCku+yH/Am6v+Altj/+zUq3DgBU3cTMD6 K8AiEf2rhivZvFo2BFiJxXy/Nimr2ByHy1p6Wyd4YS4JT8f4t/6hti0KiIec8o68ZE4q lPYdrTv/NnyNZTMCcWPlHcwm1FfzzbmLsg0xCH09M7R//15YiQ17yWzrk5NAZisALfZt tJBkCTYe19iHuAHt7fnCFL7wgh57t6CVvK1r78XvCjE1reY/TfC2TaWnF83Gm6EcUKtJ GZ5A==
X-Gm-Message-State: ACgBeo09czBhCWQ7ATWxW0TSE48A96dio6oVsmqe6iJ+heicp+uUTUFa 1gNFMEcvYX5jQ40nYraGkRFdEY7cP6CeKd2Q
X-Google-Smtp-Source: AA6agR4OulcK1XZGwZdcdiHUr6MTMHz6pI2RMaOjqXxED5lwyaP5otjEoqjSZOO8e2UkCaY8pI4LEQ==
X-Received: by 2002:a92:c264:0:b0:2de:bf95:118a with SMTP id h4-20020a92c264000000b002debf95118amr12674698ild.160.1661888591561; Tue, 30 Aug 2022 12:43:11 -0700 (PDT)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id m5-20020a0566022ac500b006887ff8a069sm6651881iov.30.2022.08.30.12.43.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Aug 2022 12:43:11 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <9F5E19E4-6F10-4001-A327-1D6E41DD9C4C@gmail.com>
Date: Tue, 30 Aug 2022 15:43:09 -0400
Cc: ECRIT <ecrit@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2C6B797-D966-4D72-BA97-2634ECAF8A91@brianrosen.net>
References: <19072608-033F-495E-A711-1CDC6568586F@randy.pensive.org> <1EA3E530-CC3F-4E16-8EAC-FDC0DD0FFD80@gmail.com> <8FA8FDF8-F56D-40F4-97A3-123282BCF8AF@brianrosen.net> <9F5E19E4-6F10-4001-A327-1D6E41DD9C4C@gmail.com>
To: James Winterbottom <a.james.winterbottom@gmail.com>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/LHKfPwDUUMRPBaxLK6QmPSpJXP0>
Subject: Re: [Ecrit] PLEASE RESPOND: Should the WG adopt draft-rosen-ecrit-emergency-registries-01?
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Emergency Context Resolution with Internet Technologies <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: Tue, 30 Aug 2022 19:43:17 -0000

The use case that motivated the original effort was Video Relay Service, where a deaf or hard of hearing person signals a need for, say American Sign Language video in an emergency call, and the PSAP that gets the call signals audio- English.  That would prompt the PSAP to add a sign language interpreter and create a three way audio+video emergency call.

But exactly the same idea works if the caller signals French audio and the PSAP signals English Audio.

Apparently, that’s not what you need.

Brian


> On Aug 30, 2022, at 2:58 PM, James Winterbottom <a.james.winterbottom@gmail.com> wrote:
> 
> Thank Brian,
> 
> I think we can do something in ETSI. 
> I don’t think that RFC 8373 does what I need as it focuses on language in the SDP which isn’t going to suit my need as I won’t have SDP at that point and may not at all in some cases.
> 
> These tags have use way beyond SIP and protocol methods, which is why I was asking.
> 
> Cheers
> James
> 
> 
> 
> 
>> On 30 Aug 2022, at 11:01 pm, Brian Rosen <br@brianrosen.net> wrote:
>> 
>> James
>> 
>> These are all registries.  There is no protocol mechanisms defined.  The protocols are defined in NENA and ETSI/EENA documents.  Everyone wanted a common set of registries, and in fact committed to eventually reaching a common single world-wide standard, although it’s not a current work effort.  So any new service requires text in NENA and/or ETSI/EENA documents.  You are welcome to propose such text.
>> 
>> Depending on what you mean by “translation service”, there is provision in NENA documents for automatically adding a third party interpreter to an emergency call.  We haven’t broadened it to a third party language translation service yet, but it’s straightforward.  The key is the RFC8373 language negotiation mechanism.
>> 
>> Brian
>> 
>>> On Aug 29, 2022, at 6:39 PM, James Winterbottom <a.james.winterbottom@gmail.com> wrote:
>>> 
>>> Hi,
>>> 
>>> I like the concept, though I would like to see a translation service added at the same level as the responder as part of the document as increasingly there is a need to link in these services and, at least in Europe, these maybe third-party services that are regionalised depending on the type of service being asked for.
>>> 
>>> Cheers
>>> James
>>> 
>>> 
>>>> On 30 Aug 2022, at 1:10 am, Randall Gellens <rg+ietf@randy.pensive.org> wrote:
>>>> 
>>>> Members of ECRIT,
>>>> 
>>>> Please respond to the question: Should the ECRIT WG adopt draft-rosen-ecrit-emergency-registries-01 as a WG document?
>>>> 
>>>> Please do not ignore this message; the chairs need to see positive support for adoption. You can respond with "yes" or "no" or something else (e.g., "yes with the following changes...."), but PLEASE RESPOND.
>>>> 
>>>> Thank you,
>>>> 
>>>> --Randall
>>>> 
>>>> _______________________________________________
>>>> 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
>> 
>