idnits 2.17.1 draft-alvestrand-content-language-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3282 5 Title: Content Language Headers 6 Author(s): H. Alvestrand 7 Status: Standards Track 8 Date: May 2002 9 Mailbox: Harald@Alvestrand.no 10 Pages: 8 11 Characters: 14022 12 Updates: 1766 14 I-D Tag: draft-alvestrand-content-language-03.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3282.txt 18 This document defines a "Content-language:" header, for use in cases 19 where one desires to indicate the language of something that has RFC 20 822-like headers, like MIME body parts or Web documents, and an 21 "Accept-Language:" header for use in cases where one wishes to 22 indicate one's preferences with regard to language. 24 This is now a Draft Standard Protocol. 26 This document specifies an Internet standards track protocol for 27 the Internet community, and requests discussion and suggestions 28 for improvements. Please refer to the current edition of the 29 "Internet Official Protocol Standards" (STD 1) for the 30 standardization state and status of this protocol. Distribution 31 of this memo is unlimited. 33 This announcement is sent to the IETF list and the RFC-DIST list. 34 Requests to be added to or deleted from the IETF distribution list 35 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 36 added to or deleted from the RFC-DIST distribution list should 37 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 39 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 40 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 41 help: ways_to_get_rfcs. For example: 43 To: rfc-info@RFC-EDITOR.ORG 44 Subject: getting rfcs 46 help: ways_to_get_rfcs 48 Requests for special distribution should be addressed to either the 49 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 50 specifically noted otherwise on the RFC itself, all RFCs are for 51 unlimited distribution.echo 52 Submissions for Requests for Comments should be sent to 53 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 54 Authors, for further information.