draft-ietf-cnrp-uri

Last Version:	draft-ietf-cnrp-uri-07.txt		Tracker Entry
Date:	02-Mar-2006
Disposition:	RFC3368 (diff)
Previous Versions:	draft-ietf-cnrp-uri-07.txt (diff)    - 29-Mar-2004
	draft-ietf-cnrp-uri-07.txt (diff)    - 07-Sep-2002
	draft-ietf-cnrp-uri-06.txt (diff)    - 23-Jun-2001
	draft-ietf-cnrp-uri-05.txt (diff)    - 25-Jan-2001
	draft-ietf-cnrp-uri-04.txt (diff)    - 02-Nov-2000
	draft-ietf-cnrp-uri-03.txt (diff)    - 18-Oct-2000
	draft-ietf-cnrp-uri-02.txt (diff)    - 14-Sep-2000
	draft-ietf-cnrp-uri-01.txt (diff)    - 22-Jul-2000
	draft-ietf-cnrp-uri-00.txt (diff)    - 09-Apr-2002

A new Request for Comments is now available in online RFC libraries.


        RFC 3368

        Title:      The 'go' URI Scheme for the Common Name Resolution
                    Protocol
        Author(s):  M. Mealling
        Status:     Standards Track
        Date:       August 2002
        Mailbox:    michael@verisignlabs.com
        Pages:      8
        Characters: 12726
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-cnrp-uri-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3368.txt


This document defines a URI scheme, 'go:' to be used with the Common
Name Resolution Protocol.  Specifically it lays out the syntactic
components and how those components are used by URI Resolution to find
the available transports for a CNRP service.  Care should be taken
with several of the URI components because, while they may look like
components found in other URI schemes, they often do not act like
them.  The "go" scheme has more in common with the location
independent "news" scheme than any other URI scheme.

This document is a product of the Common Name Resolution Protocol
Working Group of the IETF.

This is now a Proposed Standard Protocol.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.