Re: WG chairs affiliation

Hi -

> From: "Romascanu, Dan (Dan)" <dromasca <at> avaya.com>
> To: <wgchairs <at> ietf.org>
> Sent: Thursday, September 03, 2009 6:54 AM
> Subject: WG chairs affiliation 
>
> The issue below was discussed by the IESG in the  last telechat as a
> management item. 
>
> Some WGs have more than one co-chair. It is considered a good practice
> that co-chairs of the same WG are not affiliated or their particpation
> is not sponsored by the same company. However this is not a mandatory
> requirement and situations may happen where individuals change
> affiliation or sponsorship. It is recommended that such cases are made
> known to the community and especially to the other WG participants. For
> this purpose ADs will recommend the chairs of the WGs to disclose their
> affiliation or participation sponsorship at nomination and in cases of
> changes of affiliation or sponsorship - especially when these are not
> obvious from their email addresses - by sending a message to the WG mail
> list.
>
> Dan

As co-chair...

My situation remains unchanged from when ltru was formed.
I'm retired, and have no affiliation or sponsorship for my IETF
participation.  The "mindspring.com" in my email address is
merely my ISP.

RFC 5645 on Update to the Language Subtag Registry

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5645

        Title:      Update to the Language Subtag 
                    Registry 
        Author:     D. Ewell, Ed.
        Status:     Informational
        Date:       September 2009
        Mailbox:    doug <at> ewellic.org
        Pages:      13
        Characters: 27902
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ltru-4645bis-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5645.txt

This memo defines the procedure used to update the IANA Language
Subtag Registry, in conjunction with the publication of RFC 5646, for
use in forming tags for identifying languages.  This memo provides 
information for the Internet community.

This document is a product of the Language Tag Registry Update Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

BCP 47, RFC 5646 on Tags for Identifying Languages

A new Request for Comments is now available in online RFC libraries.

        BCP 47        
        RFC 5646

        Title:      Tags for Identifying Languages 
        Author:     A. Phillips, Ed.,
                    M. Davis, Ed.
        Status:     Best Current Practice
        Date:       September 2009
        Mailbox:    addison <at> inter-locale.com, 
                    markdavis <at> google.com
        Pages:      84
        Characters: 208592
        Obsoletes:  RFC4646
        See Also:   BCP0047

        I-D Tag:    draft-ietf-ltru-4646bis-23.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5646.txt

This document describes the structure, content, construction, and
semantics of language tags for use in cases where it is desirable to
indicate the language used in an information object.  It also
describes how to register values for use in language tags and the
creation of user-defined extensions for private interchange.  This document 
specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

Re: BCP 47, RFC 5646 on Tags for Identifying Languages

rfc-editor <at> rfc-editor.org scripsit:

> A new Request for Comments is now available in online RFC libraries.
> 
>         BCP 47        
>         RFC 5646

Well, I'm sure glad it's out, but couldn't we have gotten, like,
RFC 5656 instead?  Much cooler.

--

-- 
John Cowan  http://ccil.org/~cowan    cowan <at> ccil.org
There are books that are at once excellent and boring.  Those that at
once leap to the mind are Thoreau's Walden, Emerson's Essays, George
Eliot's Adam Bede, and Landor's Dialogues.  --Somerset Maugham

Re: BCP 47, RFC 5646 on Tags for Identifying Languages

Hi -

Both as co-chair and as a technical contributor,
I'd like to thank Mark and Addison for their work as
editors of this document, co-chair Martin for shepherding
this through the final weeks, and all the participants in this
working group for their contributions and patience in bringing
this work to a successful conclusion.

Randy

> From: <rfc-editor <at> rfc-editor.org>
> To: <ietf-announce <at> ietf.org>; <rfc-dist <at> rfc-editor.org>
> Cc: <ltru <at> ietf.org>; <rfc-editor <at> rfc-editor.org>
> Sent: Friday, September 04, 2009 3:20 PM
> Subject: [Ltru] BCP 47, RFC 5646 on Tags for Identifying Languages
>
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>         BCP 47        
>         RFC 5646
> 
>         Title:      Tags for Identifying Languages 
>         Author:     A. Phillips, Ed.,
>                     M. Davis, Ed.
>         Status:     Best Current Practice
>         Date:       September 2009
>         Mailbox:    addison <at> inter-locale.com, 
>                     markdavis <at> google.com

Re: RFC 5645 on Update to the Language Subtag Registry

Hi -

Both as co-chair and as a technical contributor, I'd like to
thank Doug for his tireless work on this massive (or at least,
massive until publication  undertaking, co-chair Martin for
shepherding this through the final weeks, and all the participants
in this working group for their contributions and patience in
bringing this work to a successful conclusion.

Randy

> From: <rfc-editor <at> rfc-editor.org>
> To: <ietf-announce <at> ietf.org>; <rfc-dist <at> rfc-editor.org>
> Cc: <ltru <at> ietf.org>; <rfc-editor <at> rfc-editor.org>
> Sent: Friday, September 04, 2009 3:20 PM
> Subject: [Ltru] RFC 5645 on Update to the Language Subtag Registry
>
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>         
>         RFC 5645
> 
>         Title:      Update to the Language Subtag 
>                     Registry 
>         Author:     D. Ewell, Ed.
>         Status:     Informational
>         Date:       September 2009
>         Mailbox:    doug <at> ewellic.org
>         Pages:      13

Re: BCP 47, RFC 5646 on Tags for Identifying Languages

Re: BCP 47, RFC 5646 on Tags for Identifying Languages

Very good!

But wasn't BCP 47 supposed to be the concatenation of RFC 5646 and RFC 4647
(just like the previous instance of BCP 47 was the concatenation of RFC 4646
and RFC 4647).

What is currently given as BCP 47 is RFC 5646 alone, no RFC 4647.

    /kent k

Den 2009-09-05 00.20, skrev "rfc-editor <at> rfc-editor.org"
<rfc-editor <at> rfc-editor.org>:

> 
> A new Request for Comments is now available in online RFC libraries.
> 
>         BCP 47   
>         RFC 5646
> 
>         Title:      Tags for Identifying Languages
>         Author:     A. Phillips, Ed.,
>                     M. Davis, Ed.
>         Status:     Best Current Practice
>         Date:       September 2009
>         Mailbox:    addison <at> inter-locale.com,
>                     markdavis <at> google.com
>         Pages:      84
>         Characters: 208592
>         Obsoletes:  RFC4646
>         See Also:   BCP0047

Re: BCP 47, RFC 5646 on Tags for Identifying Languages

Re: BCP 47, RFC 5646 on Tags for Identifying Languages

I'd likewise like to thank Mark and Addison and Doug for their work as 
editors of our documents, and co-chair Randy for keeping track of 
issues, among a lot else, and everybody on the WG for all their 
contributions.

Regards,   Martin.

On 2009/09/05 7:42, Randy Presuhn wrote:
> Hi -
>
> Both as co-chair and as a technical contributor,
> I'd like to thank Mark and Addison for their work as
> editors of this document, co-chair Martin for shepherding
> this through the final weeks, and all the participants in this
> working group for their contributions and patience in bringing
> this work to a successful conclusion.
>
> Randy
>
>> From:<rfc-editor <at> rfc-editor.org>
>> To:<ietf-announce <at> ietf.org>;<rfc-dist <at> rfc-editor.org>
>> Cc:<ltru <at> ietf.org>;<rfc-editor <at> rfc-editor.org>
>> Sent: Friday, September 04, 2009 3:20 PM
>> Subject: [Ltru] BCP 47, RFC 5646 on Tags for Identifying Languages
>>
>>
>> A new Request for Comments is now available in online RFC libraries.
>>
>>          BCP 47
>>          RFC 5646
>>
>>          Title:      Tags for Identifying Languages
>>          Author:     A. Phillips, Ed.,
>>                      M. Davis, Ed.
>>          Status:     Best Current Practice
>>          Date:       September 2009
>>          Mailbox:    addison <at> inter-locale.com,
>>                      markdavis <at> google.com
>>          Pages:      84
>>          Characters: 208592
>>          Obsoletes:  RFC4646
>>          See Also:   BCP0047
>>
>>          I-D Tag:    draft-ietf-ltru-4646bis-23.txt
>>
>>          URL:        http://www.rfc-editor.org/rfc/rfc5646.txt
>>
>> This document describes the structure, content, construction, and
>> semantics of language tags for use in cases where it is desirable to
>> indicate the language used in an information object.  It also
>> describes how to register values for use in language tags and the
>> creation of user-defined extensions for private interchange.  This document
>> specifies an Internet Best Current Practices for the
>> Internet Community, and requests discussion and suggestions for
>> improvements.
>>
>> This document is a product of the Language Tag Registry Update Working Group of the IETF.
>>
>>
>> BCP: This document specifies an Internet Best Current Practices for the
>> Internet Community, and requests discussion and suggestions for
>> improvements. Distribution of this memo is unlimited.
>>
>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>> To subscribe or unsubscribe, see
>>    http://www.ietf.org/mailman/listinfo/ietf-announce
>>    http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>
>> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>>
>> Requests for special distribution should be addressed to either the
>> author of the RFC in question, or to rfc-editor <at> rfc-editor.org.  Unless
>> specifically noted otherwise on the RFC itself, all RFCs are for
>> unlimited distribution.
>>
>>
>> The RFC Editor Team
>> USC/Information Sciences Institute
>>
>>
>> _______________________________________________
>> Ltru mailing list
>> Ltru <at> ietf.org
>> https://www.ietf.org/mailman/listinfo/ltru
>
> _______________________________________________
> Ltru mailing list
> Ltru <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ltru
>

--

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst <at> it.aoyama.ac.jp