Re: [Ecrit] URN: for people with hearing loss
Gunnar Hellström <gunnar.hellstrom@omnitor.se> Wed, 12 July 2017 06:24 UTC
Return-Path: <gunnar.hellstrom@omnitor.se>
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 EE67C12EC34 for <ecrit@ietfa.amsl.com>; Tue, 11 Jul 2017 23:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 j1LWxrtu-L60 for <ecrit@ietfa.amsl.com>; Tue, 11 Jul 2017 23:24:32 -0700 (PDT)
Received: from bin-vsp-out-02.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 48C9012ECC8 for <ecrit@ietf.org>; Tue, 11 Jul 2017 23:24:32 -0700 (PDT)
X-Halon-ID: bf94ea8b-66ca-11e7-ba97-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [85.238.220.142]) by bin-vsp-out-02.atm.binero.net (Halon) with ESMTPSA id bf94ea8b-66ca-11e7-ba97-005056917f90; Wed, 12 Jul 2017 08:24:24 +0200 (CEST)
To: Henning Schulzrinne <hgs@cs.columbia.edu>, ECRIT <ecrit@ietf.org>
References: <CACgrgBaAVY7CJ4XWy8f4P83=HayYjqGQo_M7S_x0hSiRqHQuVQ@mail.gmail.com>
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Message-ID: <f8a9688f-ca56-3a1a-4c7e-dc871144f901@omnitor.se>
Date: Wed, 12 Jul 2017 08:24:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CACgrgBaAVY7CJ4XWy8f4P83=HayYjqGQo_M7S_x0hSiRqHQuVQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------604944F6DEA5157CC4CAAEA7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/toefw_lyySRO1Nuofk7t6-21VIA>
Subject: Re: [Ecrit] URN: for people with hearing loss
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: Wed, 12 Jul 2017 06:24:35 -0000
I doubt that the URN is the right mechanism for separating different technologies and media used for the emergency call. That gets in conflict with the specification of service type on the application level that was the original idea of using subtypes in the URN. You cannot specify "coastguard" and "text" at the same time, or you need a complicated logic that allows to hang the technology specification as a sub-service on any of the other services ( "sos.coastguard.text" ). The IETF SLIM WG is working with indication of desired language and modality. Emergency service is one of the main applications. We have only identified spoken, written and signed modalities, but also briefly discussed if "message" would be needed, as would be the need for SMS and fax. (with written modality we mean real-time text declared as text media. ) Maybe that mechanism can be considered for your needs. If you continue on the subtype track, I also agree that "hearing-loss" is not a good term to use, and also not "text". Maybe "message" if that is what the subtype is intended to handle. Or did you intend to handle all mixes of modality that can occur: sms, fax both ways, fax one way and speech the other, real-time text both ways, real-time text one way and speech the other, sign language both ways, instant messaging both ways, instant messaging combined with speech etc. ? How would the device know for which modality preferences to use the service subtype and when to use the regular "sos". Gunnar Den 2017-07-12 kl. 00:37, skrev Henning Schulzrinne: > Several countries have separate numbers (some short, some toll-free) where > people can send an SMS or fax for emergency assistance. (The US has made > the decision to use 911 for SMS as well, but that's not relevant for this > discussion. In those countries, such calls need to be routed separately and > you can't tell whether you are going to send a fax when dialing...) > > One possibility is to use *sos.text *(with the understanding that this > includes fax; none of the countries I checked separate those), but I'm not > terribly happy with this label. > > I want to avoid something like *sos.hearing-loss* since this assumes that > only people with hearing loss can use the service. Some countries do > require some kind of registration, but this does not seem like something we > want to encode in a URN. > > Henning > > > > _______________________________________________ > Ecrit mailing list > Ecrit@ietf.org > https://www.ietf.org/mailman/listinfo/ecrit -- ----------------------------------------- Gunnar Hellström Omnitor gunnar.hellstrom@omnitor.se +46 708 204 288
- [Ecrit] URN: for people with hearing loss Henning Schulzrinne
- Re: [Ecrit] URN: for people with hearing loss Gunnar Hellström
- Re: [Ecrit] URN: for people with hearing loss Henning Schulzrinne
- Re: [Ecrit] URN: for people with hearing loss Gunnar Hellström
- Re: [Ecrit] URN: for people with hearing loss Henning Schulzrinne
- Re: [Ecrit] URN: for people with hearing loss Drage, Keith (Nokia - GB)
- Re: [Ecrit] URN: for people with hearing loss Henning Schulzrinne