IETF Logo Mail Archive

[Slim] Question about "asymmetrical language use"

Bernard Aboba <bernard.aboba@gmail.com> Tue, 09 January 2018 23:07 UTC

Return-Path: <bernard.aboba@gmail.com>
X-Original-To: slim@ietfa.amsl.com
Delivered-To: slim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1498312D837 for <slim@ietfa.amsl.com>; Tue, 9 Jan 2018 15:07:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 U1ef007nYlcQ for <slim@ietfa.amsl.com>; Tue, 9 Jan 2018 15:07:39 -0800 (PST)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (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 5DF80124D68 for <slim@ietf.org>; Tue, 9 Jan 2018 15:07:39 -0800 (PST)
Received: by mail-vk0-x22f.google.com with SMTP id n4so195378vkd.6 for <slim@ietf.org>; Tue, 09 Jan 2018 15:07:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pwrC1aZ2dGUuIOK5mR6TQzS3PzvhtVvnGllvmbQwcEs=; b=ZRCjxw2V1s9TpUhXUBjeLaQWnpXp47eFNwLPojghpXVJWTIKwCtSBoz3koeCzaRkAN Ht7OwwJt3tZIgZqwxhrZylIHr2AaEtaXymQeUOxdxlanXckck0dUmPcT96t6pvoZoxs9 jVF1Wxqloy6YkK7CQnqBJ+FLNPyO8HwQphfP+1b7BZ9QxBioIKHcWShhhJkfucBzId64 BoImfmZtRs25Zx8i1p41Mz1zK15i1GHA1LoWbTCWiGtXkmyFOGp1ZFaOEp42zRi029Ry lzzUX3ggOVAiABHJihQToF0PciJ1z+qXhog5KPL3nsDbYP+80i+bJRsj2XG5CeFIPh1j 41mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pwrC1aZ2dGUuIOK5mR6TQzS3PzvhtVvnGllvmbQwcEs=; b=GTSsE/BELig8oezX8o5UAgqXt9RaT9Yk5v8UqVc5s/jV20e550aj1aJQ1+FXv3DB5n ztJU2Y/NVza2mbHl7VTtk5+TQSg9qVo0Rnx02qX50FqLUoys3g+y9zAwlX1nGsBqon2e NHtD1vJx9XNNOsNuwWYWnjnEUT50CNi5MXc0iPfRyddVWs4mQxEBulKtzDj+bIx76ivX c/ZPMMkvcZLsFXNkmiYBlHsovOy3Wt5O9sOCj5NXZZzyu5CqQsTUyG0DKX+Fxn8DyI3M PxzZ9T8VrJ+dTfH5xHyEArsleTQYfUbz6tfR9lQERprBQj9DF8Vd4p2/zayBHG9GdMwP qmBA==
X-Gm-Message-State: AKwxyteKIaOGT3jfi9+q1q4hDWxbC1VOc2mmFJEZ8ezn0gP6NScQzUYd ckWxuUAnSr1RYxw3yLVW2+NzLLiRYztjTRr8ipmdObWr
X-Google-Smtp-Source: ACJfBouVUivNxJ+JWiy7iYC688+lMKfifm3dbN6/86XqUfzUNR5ke4MpeziRXXY/SS5HUUl+XOMEUx061MhoiPajIqA=
X-Received: by 10.31.82.194 with SMTP id g185mr15242156vkb.15.1515539257816; Tue, 09 Jan 2018 15:07:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.54.138 with HTTP; Tue, 9 Jan 2018 15:07:17 -0800 (PST)
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 09 Jan 2018 15:07:17 -0800
Message-ID: <CAOW+2du2Cf6BhjoNQ43scbVstL+J70Myc1Mhtz0KVcTVi+vLTg@mail.gmail.com>
To: slim@ietf.org, Gunnar Hellström <gunnar.hellstrom@omnitor.se>, Randall Gellens <rg+ietf@randy.pensive.org>
Content-Type: multipart/alternative; boundary="001a114f76c41afbd405625ffb0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/Xuiguxnf-5N2i1naHcaV9Rij4YM>
Subject: [Slim] Question about "asymmetrical language use"
X-BeenThere: slim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Selection of Language for Internet Media <slim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/slim>, <mailto:slim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/slim/>
List-Post: <mailto:slim@ietf.org>
List-Help: <mailto:slim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/slim>, <mailto:slim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 23:07:41 -0000

In Section 5.1 of -22, I noted the following sentence:

" When placing an emergency call, and in any other case where the language
cannot be inferred from context, in an offer each media stream primarily
intended for human language communication SHOULD specify both (or for
asymmetrical language use, one of) the 'hlang- send' and 'hlang-recv'
attributes."

[BA] In our previous discussions, we have talked about scenarios (e.g.
speech impaired, but not hearing impaired) in which it is useful to include
both 'hlang-send' and 'hlang-recv' so as to accommodate user needs.
Wouldn't such a scenario qualify as "asymmetrical language use"?  If so,
how could the user's needs be accommodated with only one of the
'hlang-send' or 'hlang-recv' attributes?

v2.23.0 | Report a Bug | By Email