idnits 2.17.1 draft-hoffman-char-lang-media-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 186 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 9 instances of lines with control characters in the document. ** The abstract seems to contain references ([TAG-REG]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 22, 1999) is 9045 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2278 (ref. 'CHARSET') (Obsoleted by RFC 2978) ** Obsolete normative reference: RFC 1766 (ref. 'LANG') (Obsoleted by RFC 3066, RFC 3282) Summary: 10 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Paul Hoffman 2 draft-hoffman-char-lang-media-01.txt Internet Mail Consortium 3 July 22, 1999 4 Expires in six months 6 Registration of Charset and Languages Media Features Tags 8 Status of this memo 10 This document is an Internet-Draft and is in full conformance with all 11 provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering Task 14 Force (IETF), its areas, and its working groups. Note that other 15 groups may also distribute working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference material 20 or to cite them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Abstract 30 This document contains the registration for two media feature tags: 31 "charset" and "language". These media features allow specification of 32 character sets and human languages that can be understood by devices 33 and the devices' users. The templates in this document are derived from 34 [TAG-REG]. 36 1. Registration for charset 38 To: media-feature-tags@apps.ietf.org (Media feature tags mailing list) 39 Subject: Registration of media feature tag charset 41 Media feature tag name: 42 charset 44 ASN.1 identifier associated with feature tag: 45 New assignment by IANA 47 Summary of the media feature indicated by this feature tag: 48 Ability to display particular charsets as defined in [CHARSET] 50 Values appropriate for use with this feature tag: 51 The values are strings as defined in [CHARSET]. The values can only 52 be compared for equality. Comparison is not case sensitive. 54 The feature tag is intended primarily for use in the following 55 applications, protocols, services, or negotiation mechanisms: 56 Any protocol that uses media tags 58 Examples of typical use: 59 (| (charset=utf-8);q=1.0 (charset=iso-8859-1);q=0.9 60 (charset=utf-16);q=0.5 ) 62 Related standards or documents: 63 "IANA Charset Registration Procedures", RFC 2278 65 Considerations particular to use in individual applications, 66 protocols, services, or negotiation mechanisms: 67 None 69 Interoperability considerations: 70 Even though charset names are not case-sensitive, values should be 71 expressed as all lowercase letters to increase the liklihood of 72 interoperability. 74 Security considerations: 75 If it is known that there is a security bug in the display 76 of a particular charset in a particular environment, knowing 77 that a device can accept that charset may slightly help an 78 attacker. 80 Additional information: 81 None 83 Name(s) & email address(es) of person(s) to contact for 84 further information: 85 Paul Hoffman 87 Intended usage: 88 COMMON 90 Author/Change controller: 91 IETF 93 Requested IANA publication delay: 94 None 96 Other information: 97 None 99 2. Registration for language 101 To: media-feature-tags@apps.ietf.org (Media feature tags mailing list) 102 Subject: Registration of media feature tag language 104 Media feature tag name: 105 language 107 ASN.1 identifier associated with feature tag: 108 New assignment by IANA 110 Summary of the media feature indicated by this feature tag: 111 Ability to display particular human languages as defined in [LANG]. 112 Note that "display" in this case will most often mean speech 113 by a computer. 115 Values appropriate for use with this feature tag: 116 The values are tokens, with allowable values defined by 117 registration as defined in [LANG]. The values can only be compared 118 for equality. As described in [LANG], language tags are always 119 handled as a single token, and "subtags" are not used for 120 comparison. Comparison is not case sensitive. 122 The feature tag is intended primarily for use in the following 123 applications, protocols, services, or negotiation mechanisms: 124 Any protocol that uses media tags 126 Examples of typical use: 127 (| (language=no-nynorsk);q=1.0 (language=no-bokmaal);q=0.9 128 (language=i-sami-no);q=0.5 ) 130 Related standards or documents: 131 "Tags for the Identification of Languages", RFC 1766 133 Considerations particular to use in individual applications, 134 protocols, services, or negotiation mechanisms: 135 None 137 Interoperability considerations: 138 Even though langage tags are not case-sensitive, values should be 139 expressed as all lowercase letters to increase the liklihood of 140 interoperability. 142 Security considerations: 143 If it is known that there is a security bug in the display 144 of a particular language in a particular environment, knowing 145 that a device can accept that language may slightly help an 146 attacker. 148 Additional information: 149 None 151 Name(s) & email address(es) of person(s) to contact for 152 further information: 153 Paul Hoffman 155 Intended usage: 156 COMMON 158 Author/Change controller: 159 IETF 161 Requested IANA publication delay: 162 None 164 Other information: 165 None 167 3. Security Considerations 169 The security considerations are listed in the two registrations above. 171 4. References 173 [CHARSET] "IANA Charset Registration Procedures", RFC 2278 175 [LANG] "Tags for the Identification of Languages", RFC 1766 177 [TAG-REG] "Media Feature Tag Registration Procedure", RFC 2506 179 5. Author Contact Information 181 Paul Hoffman 182 Internet Mail Consortium 183 127 Segre Place 184 Santa Cruz, CA 95060 USA 185 phoffman@imc.org