Re: [Sipping] RFC4240, dash, and under bar

Eric Burger <eburger@cantata.com> Tue, 19 September 2006 22:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPnlk-0007v4-62; Tue, 19 Sep 2006 18:08:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GPnli-0007lX-OQ for sipping@ietf.org; Tue, 19 Sep 2006 18:08:42 -0400
Received: from outbound.cantata.com ([208.236.123.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GPnlh-0003c0-Bc for sipping@ietf.org; Tue, 19 Sep 2006 18:08:42 -0400
Received: from ma02exchtmp01.Cantata.com ([10.128.18.41]) by outbound.Cantata.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Sep 2006 18:08:40 -0400
Received: from 10.128.41.46 ([10.128.41.46]) by ma02exchtmp01.Cantata.com ([10.128.18.41]) with Microsoft Exchange Server HTTP-DAV ; Tue, 19 Sep 2006 22:08:40 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 19 Sep 2006 18:08:32 -0400
Subject: Re: [Sipping] RFC4240, dash, and under bar
From: Eric Burger <eburger@cantata.com>
To: olivier.ro.rousseau@alcatel.be
Message-ID: <C135E2A0.16A54%eburger@cantata.com>
Thread-Topic: [Sipping] RFC4240, dash, and under bar
Thread-Index: Acbb+mEjcpTEjj0nSCeJutuSE204CQAPcOlm
In-Reply-To: <450FF790.6030005@alcatel.be>
Mime-version: 1.0
X-OriginalArrivalTime: 19 Sep 2006 22:08:40.0900 (UTC) FILETIME=[2A15F840:01C6DC38]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Cc: Sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0534781824=="
Errors-To: sipping-bounces@ietf.org

Agreed.


On 9/19/06 9:58 AM, "olivier.ro.rousseau@alcatel.be"
<olivier.ro.rousseau@alcatel.be> wrote:

> But in that case can you explain me why for the locale parameter of the
> RFC 4240 I must use en_UK but if I put also an Accept-Language (defined
> in RFC3261) in the message, I have to use en-UK?
> 
> It is a little bit strange to have the same kind of information (the
> language requested/accepted) in two places of the SIP message and using
> different formatting for them.
> 
> 
> Anyway if the en_UK has to be used, I think an errata of the section 3.3
> should be published to remove the reference to RFC3066 :
> "   locale-param    = "locale=" token
>                         ; per RFC 3066, usually
>                         ; ISO639-1_ISO3166-1
>                         ; e.g., en, en_US, en_UK, etc."
> 
> 
> Olivier
> 
> Eric Burger wrote:
> 
>> >It was pointed out that while RFC 4240 references RFC 3066, RFC 3066
>> >indicates the use of a dash to separate language from local variant.  RFC
>> >4240 indicates the use of an under bar to separate language from local
>> >variant.
>> >
>> >Upon further inspection, it de facto, if not de jure standard for separating
>> >language from local variant is, in fact, the under bar.  This is what just
>> >about all operating systems will return when you ask it what locale you are
>> >in.  It is what Java returns when you ask it what locale you are in.  It
>> >seems to be pretty O/S independent.  If you are in Quebec, you get "EN_UK",
>> >and not "EN-UK".
>> >
>> >Thus we will NOT issue an errata on RFC 4240.
>> >
>> >
>> >_______________________________________________
>> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> >This list is for NEW development of the application of SIP
>> >Use sip-implementors@cs.columbia.edu for questions on current sip
>> >Use sip@ietf.org for new developments of core SIP
>> >
>> > 
>> >
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
> 


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP