IETF Logo Mail Archive

Re: [Atoca] Language and Media Type

Art Botterell <artbotterell@gmail.com> Mon, 17 January 2011 03:45 UTC

Return-Path: <artbotterell@gmail.com>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1184F3A6E70 for <earlywarning@core3.amsl.com>; Sun, 16 Jan 2011 19:45:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level:
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id guojP28XUc2K for <earlywarning@core3.amsl.com>; Sun, 16 Jan 2011 19:45:10 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id E4E753A6DA2 for <earlywarning@ietf.org>; Sun, 16 Jan 2011 19:45:09 -0800 (PST)
Received: by yxt33 with SMTP id 33so2025239yxt.31 for <earlywarning@ietf.org>; Sun, 16 Jan 2011 19:47:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:in-reply-to:mime-version :content-type:message-id:content-transfer-encoding:cc:x-mailer:from :subject:date:to; bh=GMUCMo0Xc0hysPF1lg/1wKgqb5771w7o+7NCixZqy9w=; b=h5Hj3Kv1XxPOPhhoNjSJO72OKxOHkcpDLtU24BhTWgAcogtCdftBSZSwpkuMixCBks iDkCrOalGKq+2PARfI4/2WL7R+fhtfcE6zCeBVwoHCbKAmgy9ELac5mEhj5OyxLlgD8q pGubK6fvijWE7EekRVkInaM5gvge6ckUwXynE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to; b=TSayKbG+oc5s5P4uCnyz6kL7r6vUCoAE9ctQDDl7rmKqw0aYu+CJyK18LVjrQnom8e +fQBSXrsbwHRSWoCgdHCWKD1d4o/dxemP86vdXaloYormT8wcWU89IxmEmDxbprYl5Za RpY7Smgc4/ewaepywI9XWhla8Mh5PjZB0nF8E=
Received: by 10.100.132.12 with SMTP id f12mr2249206and.7.1295236062729; Sun, 16 Jan 2011 19:47:42 -0800 (PST)
Received: from [10.10.1.90] ([200.6.58.236]) by mx.google.com with ESMTPS id c34sm4941744anc.10.2011.01.16.19.47.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 16 Jan 2011 19:47:40 -0800 (PST)
References: <A01B3425-F7E8-4C71-8902-DF41154FDF58@gmx.net> <8B0A9FCBB9832F43971E38010638454F03F52595D2@SISPE7MB1.commscope.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03F52595D2@SISPE7MB1.commscope.com>
Mime-Version: 1.0 (iPad Mail 8C148)
Content-Type: text/plain; charset="us-ascii"
Message-Id: <8B3C3AB2-6384-45C0-97A8-79DBE18831DA@gmail.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (8C148)
From: Art Botterell <artbotterell@gmail.com>
Date: Sun, 16 Jan 2011 23:51:23 -0400
To: "Thomson, Martin" <Martin.Thomson@andrew.com>
X-Mailman-Approved-At: Sun, 16 Jan 2011 21:03:52 -0800
Cc: "earlywarning@ietf.org" <earlywarning@ietf.org>
Subject: Re: [Atoca] Language and Media Type
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for the IETF Authority-to-Citizen Alert \(atoca\) working group." <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2011 03:45:11 -0000

Would this be duplicative of the CAP language element?

Thanks!

- Art

On Jan 16, 2011, at 7:08 PM, "Thomson, Martin" <Martin.Thomson@andrew.com> wrote:

> On 2011-01-16 at 06:30:11, Hannes Tschofenig wrote:
>> Keeping Li (if the meeting minutes reflect his name correctly) noticed
>> that we had a language requirement in the requirements draft but
>> provided no corresponding solution in the SIP-CAP document.
> 
> A solution does seem desirable.  Though I suspect that many alerting systems will be deployed with one language or with all of the small number of "official" or "supported" languages present in the message.  This is probably going to be necessary for all "implicit" subscriptions anyhow.
> 
> In HTTP-land, the Accept-Language header is used for that sort of thing.  The header is present in SIP, but it's use seems limited - and what evidence I have supports the notion that most servers ignore it.
> 
> We could define a use for Accept-Language and see how that flies.
> 
> _______________________________________________
> earlywarning mailing list
> earlywarning@ietf.org
> https://www.ietf.org/mailman/listinfo/earlywarning

v2.23.0 | Report a Bug | By Email