idnits 2.17.1 draft-hoffman-stringprep-07.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 3454 5 Title: Preparation of Internationalized Strings 6 ("stringprep") 7 Author(s): P. Hoffman, M. Blanchet 8 Status: Standards Track 9 Date: December 2002 10 Mailbox: paul.hoffman@imc.org, Marc.Blanchet@viagenie.qc.ca 11 Pages: 91 12 Characters: 138684 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-hoffman-stringprep-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3454.txt 19 This document describes a framework for preparing Unicode text strings 20 in order to increase the likelihood that string input and string 21 comparison work in ways that make sense for typical users throughout 22 the world. The stringprep protocol is useful for protocol identifier 23 values, company and personal names, internationalized domain names, 24 and other text strings. 26 This document does not specify how protocols should prepare text 27 strings. Protocols must create profiles of stringprep in order to 28 fully specify the processing options. 30 This document is a product of the IDN Working Group of the IETF. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.