RFC3066bis progress: extensions

Mark Davis mark.davis at jtcsv.com
Fri Mar 5 17:41:28 CET 2004

I don't recall the message. But you all should look at the latest draft


You will see that we have changed the extensions quite significantly from the
original. It is now basically a way of having a language tag with some
private-use stuff attached to it.

So you can have, as before in RFC 3066, "x-constable-gorp", but you can also
have in RFC 3066bis, something like "de-de-x-constable-gorp". Everything after
the "x-" in either case is private use, not defined by this RFC. The purpose is
to allow people to attach information which more finely specifies the language
or usage without having to have registered tags.


[BTW, the IETF process for drafts is pretty painful; we've submitted pdfs
because they are phenomenally easier to read, but with only random success at
getting them posted, and no feedback as to why...]

► शिष्यादिच्छेत्पराजयम् ◄

----- Original Message ----- 
From: "Peter Constable" <petercon at microsoft.com>
To: <ietf-languages at alvestrand.no>
Sent: Fri, 2004 Mar 05 08:22
Subject: RFC3066bis progress: extensions

> The current expiration date is in 2004. Before that date the draft
> hopefully advance to the next stage of standardization (or be revised
> that it can so progress).

Speaking of progress, there were some questions I raised for the authors
to comment on a month and a half ago, and I still haven't heard their

Specifically, I was asking what the case was for creating an extensions
mechanism. (See my msg of Jan 12.)


Peter Constable
Globalization Infrastructure and Font Technologies
Microsoft Windows Division
Ietf-languages mailing list
Ietf-languages at alvestrand.no

More information about the Ietf-languages mailing list