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

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