As per Relevance of the word registration, we have this rfc below:
Network Working Group P.
Request for Comments: 2987 Internet Mail
Category: Standards Track November 2000
Registration of Charset and Languages Media Features
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document contains the registration for two media feature tags
"charset" and "language". These media features allow
of character sets and human languages that can be understood
devices and the devices' users. The templates in this document
derived from RFC 2506.
1. Registration for
To: media-feature-tags@apps.ietf.org (Media feature tags mailing list
Subject: Registration of media feature tag
Media feature tag name
ASN.1 identifier associated with feature tag
1.3.6.1.8.1.31
Summary of the media feature indicated by this feature tag
Ability to display particular charsets as defined in [CHARSET].
For most devices, this media feature is usually a capability
that is, most devices cannot intelligently process text in
charset that is unknown to the device
Hoffman Standards Track [Page 1]
RFC 2987 Charset and Languages Media Features Tags November 2000
Values appropriate for use with this feature tag
The values are tokens as defined in [CHARSET]. The values
only be compared for equality. Comparison is not
sensitive
The feature tag is intended primarily for use in the
applications, protocols, services, or negotiation mechanisms
Any protocol that uses media
Examples of typical use
(| (charset=utf-8);q=1.0 (charset=iso-8859-1);q=0.9
(charset=utf-16);q=0.5 )
Related standards or documents
"IANA Charset Registration Procedures", RFC 2978
Considerations particular to use in individual applications
protocols, services, or negotiation mechanisms
Interoperability considerations: Aliases for charsets should not
used in media feature expressions because feature
manipulation tools may convert aliases to the the
name for the charset. Even though charset names are
case-sensitive, values should be expressed as all
letters to increase the likelihood of interoperability.
"charset" capability should always be indicated
conjunction with any capability to handle textual data
Security considerations
If it is known that there is a security bug in the display of
particular charset in a particular environment, knowing that
device can accept that charset may slightly help an attacker
Additional information
Name(s) & email address(es) of person(s) to contact for
information
Paul Hoffman
Intended usage
Author/Change controller
Hoffman Standards Track [Page 2]
RFC 2987 Charset and Languages Media Features Tags November 2000
Requested IANA publication delay
Other information
2. Registration for
To: media-feature-tags@apps.ietf.org (Media feature tags mailing list
Subject: Registration of media feature tag
Media feature tag name
ASN.1 identifier associated with feature tag
1.3.6.1.8.1.32
Summary of the media feature indicated by this feature tag:
to display particular human languages as defined in [LANG].
that "display" in this case will most often mean speech by
computer. For most devices, this media feature is a preference
not a requirement
Values appropriate for use with this feature tag
The values are tokens, with allowable values defined
registration as defined in [LANG]. The values can only
compared for equality. As described in [LANG], language
are always handled as a single token, and "subtags" are
used for comparison. Comparison is not case sensitive
The feature tag is intended primarily for use in the
applications, protocols, services, or negotiation mechanisms
Any protocol that uses media
Examples of typical use
(| (language=no-nynorsk);q=1.0 (language=no-bokmaal);q=0.9
(language=i-sami-no);q=0.5 )
Related standards or documents
"Tags for the Identification of Languages", RFC 1766
Considerations particular to use in individual applications
protocols, services, or negotiation mechanisms
Hoffman Standards Track [Page 3]
RFC 2987 Charset and Languages Media Features Tags November 2000
Interoperability considerations
Even though language tags are not case-sensitive, values should
expressed as all lowercase letters to increase the
of interoperability
Security considerations
If it is known that there is a security bug in the display of
particular language in a particular environment, knowing that
device can accept that language may slightly help an attacker
Additional information
Name(s) & email address(es) of person(s) to contact for
information
Paul Hoffman
Intended usage
Author/Change controller
Requested IANA publication delay
Other information
3. Security
The security considerations are listed in the two registrations above
4. IANA
The bulk of this document is IANA registrations
5.
[CHARSET] Freed, N. and J. Postel, "IANA Charset
Procedures", BCP 19, RFC 2978, October 2000.
[LANG] Alvestrand, H., "Tags for the Identification of Languages",
RFC 1766, March 1995.
[TAG-REG] Holtman, K., Mutz, A. and T. Hardie, "Media Feature
Registration Procedure", BCP 31, RFC 2506, March 1999.
Hoffman Standards Track [Page 4]
RFC 2987 Charset and Languages Media Features Tags November 2000
6. Author's
Paul
Internet Mail
127 Segre
Santa Cruz, CA 95060
EMail: phoffman@imc.
Hoffman Standards Track [Page 5]
RFC 2987 Charset and Languages Media Features Tags November 2000
7. Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Hoffman Standards Track [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
