idnits 2.17.1 draft-presuhn-rfc2482-historic-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC2482, but the abstract doesn't seem to directly say this. It does mention RFC2482 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 7, 2010) is 5035 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2482 (Obsoleted by RFC 6082) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Whistler 3 Internet-Draft Sybase, Inc. 4 Obsoletes: 2482 (if approved) G. Adams 5 Intended status: Informational Skynav (Phil), Inc. 6 Expires: January 8, 2011 M. Duerst 7 Aoyama Gakuin University 8 R. Presuhn, Ed. 9 J. Klensin 10 July 7, 2010 12 Deprecating Unicode Language Tag Characters: RFC 2482 is Historic 13 draft-presuhn-rfc2482-historic-02.txt 15 Abstract 17 RFC 2482, Language Tagging in Unicode Plain Text, described a 18 mechanism for using special Unicode language tag characters to 19 identify languages when needed without more general markup such as 20 that provided by XML. The Unicode Consortium has deprecated that 21 facility and strongly recommends against its use. RFC 2482 should be 22 moved to Historic to reduce the possibility that Internet 23 implementers would consider that system an appropriate mechanism for 24 identifying languages. 26 Status of this Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on January 8, 2011. 43 Copyright Notice 45 Copyright (c) 2010 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 63 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 64 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 3 65 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 6.1. Normative References . . . . . . . . . . . . . . . . . . . 4 67 6.2. Informative References . . . . . . . . . . . . . . . . . . 4 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 70 1. Introduction 72 RFC 2482, Language Tagging in Unicode Plain Text [RFC2482], described 73 a mechanism for using special Unicode language tag characters to 74 identify languages when needed. It was an idea whose time never 75 quite came. It has been superseded by whole-transaction language 76 identification such as the MIME Content-language header [RFC3282] and 77 more general markup mechanisms such as those provided by XML. The 78 Unicode Consortium has deprecated the language tag character facility 79 and strongly recommends against its use. RFC 2482 should be moved to 80 Historic to reduce the possibility that Internet implementers would 81 consider that tagging system an appropriate mechanism for identifying 82 languages. 84 A discussion of the status of the language tag characters and their 85 applicability appears in Section 16.9 of the Unicode Standard 86 [Unicode52]. 88 2. Action 90 RFC 2482 is deprecated and reclassified as Historic. Internet 91 protocols and Standards-track documents should not use the facilities 92 described in that document. 94 3. IANA Considerations 96 [RFC Editor: Please remove this section before publication.] 98 This memo includes no requests to or actions for IANA. 100 4. Security Considerations 102 By deprecating RFC 2482, we eliminate a facility that is no longer 103 encouraged and supported by the Unicode Consortium and that may have 104 been slightly risky in use if misinterpreted or if expectations of 105 support were not met. So, if this action has any effect on Internet 106 security at all, it should be positive. 108 5. Acknowledgments 110 Helpful comments were received from Peter Koch and S. Moonesamy. 112 6. References 113 6.1. Normative References 115 [RFC2482] Whistler, K. and G. Adams, "Language Tagging in Unicode 116 Plain Text", RFC 2482, January 1999. 118 [Unicode52] 119 The Unicode Consortium. The Unicode Standard, Version 120 5.2.0, defined by:, "The Unicode Standard, Version 5.2.0", 121 (Mountain View, CA: The Unicode Consortium, 2009. ISBN 122 978-1-936213-00-9)., 123 . 125 6.2. Informative References 127 [RFC3282] Alvestrand, H., "Content Language Headers", RFC 3282, 128 May 2002. 130 Authors' Addresses 132 Kenneth Whistler 133 Sybase, Inc. 134 One Sybase Dr. 135 Dublin, CA 94568 136 USA 138 Phone: +1 925 236 7429 139 Email: kenw@sybase.com 141 Glenn Adams 142 Skynav (Phil), Inc. 143 Lot 14 Boton Area 144 Subic Bay Freeport Zone 2222 145 Philippines 147 Phone: 148 Email: glenn@skynav.com 149 Martin Duerst 150 Aoyama Gakuin University 151 5-10-1 Fuchinobe 152 Sagamihara, Kanagawa 229-8558 153 Japan 155 Phone: +81 42 759 6329 156 Fax: +81 42 759 6495 157 Email: duerst@it.aoyama.ac.jp 159 Randy Presuhn (editor) 160 San Jose, CA 95120 161 USA 163 Phone: 164 Email: randy_presuhn@mindspring.com 166 John C Klensin 167 1770 Massachusetts Ave, Ste 322 168 Cambridge, MA 02140 169 USA 171 Phone: +1 617 245 1457 172 Email: john+ietf@jck.com