[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: registration of iso-8859-15: v1.1 [cs and MIBenum needed]
Maybe it is a bug in RFC 2278, but the cs symbol and a MIBenum value is
essiential to be included in each new charset registry.
Otherwise, the IETF standards track Printer MIB (RFC 1759 and soon to
be a draft standard), will NOT be able to indicate this new important
charset. I also believe the SLP is using the charset enums, instead
of the MIME charset names.
So please keep csISOLatin9 alias and add a MIBenum value
(being careful to assign the next avaible number in the propose
range as explained in the beginning of the charset registry).
Does RFC 2278 have to be fixed too, or can we just follow what is
in the beginning of the charset registry?
Here is the beginning of the charset registry that explains all this:
====================================================================
CHARACTER SETS
These are the official names for character sets that may be used in
the Internet and may be referred to in Internet documentation. These
names are expressed in ANSI_X3.4-1968 which is commonly called
US-ASCII or simply ASCII. The character set most commonly use in the
Internet and used especially in protocol standards is US-ASCII, this
is strongly encouraged. The use of the name US-ASCII is also
encouraged.
The character set names may be up to 40 characters taken from the
printable characters of US-ASCII. However, no distinction is made
between use of upper and lower case letters.
The MIBenum value is a unique value for use in MIBs to identify coded
character sets.
The value space for MIBenum values has been divided into three
regions. The first region (3-999) consists of coded character sets
that have been standardized by some standard setting organization.
This region is intended for standards that do not have subset
implementations. The second region (1000-1999) is for the Unicode and
ISO/IEC 10646 coded character sets together with a specification of a
(set of) sub-repetoires that may occur. The third region (>1999) is
intended for vendor specific coded character sets.
Assigned MIB enum Numbers
-------------------------
0 Reserved
1 Reserved
3-106 Set By Standards Organizations
1000-1010 Unicode / 10646
2000-2087 Vendor
2250-2258 Vendor
The aliases that start with "cs" have been added for use with the
Printer MIB (see RFC 1759) and contain the standard numbers along with
suggestive names in order to facilitate applications that want to
display the names in user interfaces. The "cs" stands for character
set and is provided for applications that need a lower case first
letter but want to use mixed case thereafter that cannot contain any
special characters, such as underbar ("_") and dash ("-"). If the
character set is from an ISO standard, its cs alias is the ISO
standard number or name. If the character set is not from an ISO
standard, but is registered with ISO (ECMA is the current ISO
Registration Authority), the ISO Registry number is specified as
ISOnnn followed by letters suggestive of the name or standards number
of the code set. When a national or international standard is
revised, the year of revision is added to the cs alias of the new
character set entry in the IANA Registry in order to distinguish the
revised character set from the original character set.
Character Set Reference
------------- ---------
Name: ANSI_X3.4-1968 [RFC1345,KXS2]
MIBenum: 3
Source: ECMA registry
Alias: iso-ir-6
Alias: ANSI_X3.4-1986
Alias: ISO_646.irv:1991
Alias: ASCII
Alias: ISO646-US
Alias: US-ASCII (preferred MIME name)
Alias: us
Alias: IBM367
Alias: cp367
Alias: csASCII
Name: ISO-10646-UCS-2
MIBenum: 1000
Source: the 2-octet Basic Multilingual Plane, aka Unicode
this needs to specify network byte order: the standard
does not specify (it is a 16-bit integer space)
Alias: csUnicode
Name: ISO-10646-UCS-4
MIBenum: 1001
Source: the full code space. (same comment about byte order,
these are 31-bit numbers.
Alias: csUCS4
...
At 11:56 03/30/1998 PST, Marc Blanchet wrote:
>At 18:36 98-03-30 +0000, Misha Wolf wrote:
>>Why do we need the aliases? I suggest (just):
>>
>> Name: ISO-8859-15 (preferred MIME name)
>>
>>Misha Wolf
>>Chair, W3C I18N WG
>
>Well, I'm also against complexity without need! But, referring to IANA
>registry document
>(http://www.isi.edu/in-notes/iana/assignments/character-sets), the cs alias
>is for the printer MIB. And latin9 alias is to follow other iso-8859
>registrations. But, if nobody cares about it, then I would certainly drop
>them when I will rerequest the registration after the iso final ballot.
>
>I will also put the request at that time(after iso final ballot) with the
>new rfc procedure (rfc2278).
>
>Regards, Marc.
>>
>>
>>> Hi,
>>> modified request per comments:
>>> - removed alias latin0
>>> - preferred alias in uppercase
>>> - csISOLatin changed to 9
>>>
>>> The new request will be:
>>>
>>> Name: ISO-8859-15
>>> Alias: ISO-8859-15 (preferred MIME name)
>>> Alias: latin9
>>> Alias: csISOLatin9
>>>
>>>
>>> Since the ISO standard is at its final ballot stage, then I will wait until
>>> final approval and resubmit it to the list at that time. In between,
>>> people can use it for software development.
>>>
>>> Thanks everybody,
>>>
>>> Marc.
>>>
>>>
>>>
>>> -----------------------------------------------------------
>>> Marc Blanchet | Marc.Blanchet@viagenie.qc.ca
>>> Viagénie inc. | http://www.viagenie.qc.ca
>>> 3107 des hôtels | tél.: 418-656-9254
>>> Ste-Foy, Québec | fax.: 418-656-0183
>>> Canada, G1W 4W5 | radio: VA2-JAZ
>>> ------------------------------------------------------------
>>> pgp: 57 86 A6 83 D3 A8 58 32 F7 0A BB BD 5F B2 4B A7
>>> ------------------------------------------------------------
>>> Auteur du livre TCP/IP Simplifié, Éditions Logiques, 1997
>>> ------------------------------------------------------------
>>
>>
>>
>>------------------------------------------------------------------------
>>Any views expressed in this message are those of the individual sender,
>>except where the sender specifically states them to be the views of
>>Reuters Ltd.
>>
>>
>
>-----------------------------------------------------------
>Marc Blanchet | Marc.Blanchet@viagenie.qc.ca
>Viagénie inc. | http://www.viagenie.qc.ca
>3107 des hôtels | tél.: 418-656-9254
>Ste-Foy, Québec | fax.: 418-656-0183
>Canada, G1W 4W5 | radio: VA2-JAZ
>------------------------------------------------------------
>pgp: 57 86 A6 83 D3 A8 58 32 F7 0A BB BD 5F B2 4B A7
>------------------------------------------------------------
>Auteur du livre TCP/IP Simplifié, Éditions Logiques, 1997
>------------------------------------------------------------
>
>
>