idnits 2.17.1 draft-ietf-cnrp-12.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 3367 5 Title: Common Name Resolution Protocol (CNRP) 6 Author(s): N. Popp, M. Mealling, M. Moseley 7 Status: Standards Track 8 Date: August 2002 9 Mailbox: npopp@verisign.com, michael@verisignlabs.com, 10 marshall@netword.com 11 Pages: 42 12 Characters: 86889 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-cnrp-12.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3367.txt 19 People often refer to things in the real world by a common name or 20 phrase, e.g., a trade name, company name, or a book title. These 21 names are sometimes easier for people to remember and type than URLs. 22 Furthermore, because of the limited syntax of URLs, companies and 23 individuals are finding that the ones that might be most reasonable 24 for their resources are being used elsewhere and so are unavailable. 25 For the purposes of this document, a "common name" is a word or a 26 phrase, without imposed syntactic structure, that may be associated 27 with a resource. 29 This effort is about the creation of a protocol for client 30 applications to communicate with common name resolution services, as 31 exemplified in both the browser enhancement and search site 32 paradigms. Although the protocol's primary function is resolution, 33 it is also intended to address issues of internationalization and 34 localization. Name resolution services are not generic search 35 services and thus do not need to provide complex Boolean query, 36 relevance ranking or similar capabilities. The protocol is a simple, 37 minimal interoperable core. Mechanisms for extension are provided, 38 so that additional capabilities can be added. 40 This document is a product of the Common Name Resolution Protocol 41 Working Group of the IETF. 43 This is now a Proposed Standard Protocol. 45 This document specifies an Internet standards track protocol for 46 the Internet community, and requests discussion and suggestions 47 for improvements. Please refer to the current edition of the 48 "Internet Official Protocol Standards" (STD 1) for the 49 standardization state and status of this protocol. Distribution 50 of this memo is unlimited. 52 This announcement is sent to the IETF list and the RFC-DIST list. 53 Requests to be added to or deleted from the IETF distribution list 54 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 55 added to or deleted from the RFC-DIST distribution list should 56 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 58 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 59 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 60 help: ways_to_get_rfcs. For example: 62 To: rfc-info@RFC-EDITOR.ORG 63 Subject: getting rfcs 65 help: ways_to_get_rfcs 67 Requests for special distribution should be addressed to either the 68 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 69 specifically noted otherwise on the RFC itself, all RFCs are for 70 unlimited distribution.echo 71 Submissions for Requests for Comments should be sent to 72 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 73 Authors, for further information.