idnits 2.17.1 draft-ietf-cnrp-uri-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 3368 5 Title: The 'go' URI Scheme for the Common Name Resolution 6 Protocol 7 Author(s): M. Mealling 8 Status: Standards Track 9 Date: August 2002 10 Mailbox: michael@verisignlabs.com 11 Pages: 8 12 Characters: 12726 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-cnrp-uri-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3368.txt 19 This document defines a URI scheme, 'go:' to be used with the Common 20 Name Resolution Protocol. Specifically it lays out the syntactic 21 components and how those components are used by URI Resolution to find 22 the available transports for a CNRP service. Care should be taken 23 with several of the URI components because, while they may look like 24 components found in other URI schemes, they often do not act like 25 them. The "go" scheme has more in common with the location 26 independent "news" scheme than any other URI scheme. 28 This document is a product of the Common Name Resolution Protocol 29 Working Group of the IETF. 31 This is now a Proposed Standard Protocol. 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.