Browse Prior Art Database

The 'go' URI Scheme for the Common Name Resolution Protocol (RFC3368)

IP.com Disclosure Number: IPCOM000009518D
Original Publication Date: 2002-Aug-01
Included in the Prior Art Database: 2002-Aug-29
Document File: 9 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Mealling: AUTHOR

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 22% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � M. Mealling

Request for Comments: 3368� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � VeriSign, Inc.

Category: Standards Track� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � August 2002

� � � � � The 'go' URI Scheme for the Common Name Resolution Protocol

Status of this Memo

� � This document specifies an Internet standards track protocol for the

� � Internet community, and requests discussion and suggestions for

� � improvements.� Please refer to the current edition of the "Internet

� � Official Protocol Standards" (STD 1) for the standardization state

� � and status of this protocol.� Distribution of this memo is unlimited.

Copyright Notice

� � Copyright (C) The Internet Society (2002).� All Rights Reserved.

Abstract

� � 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.

Mealling� � � � � � � � � � � � � � � � � � � Standards Track� � � � � � � � � � � � � � � � � � � � [Page 1]

RFC 3368� � � � � � � � � � � � � � � CNRP URI Specification� � � � � � � � � � � � � � August 2002

Table of Contents

� � 1.� � � Goals� . . . . . . . . . . . . . . . . . . . . . . . . . . .� 2

� � 2.� � � Terminology� . . . . . . . . . . . . . . . . . . . . . . . .� 2

� � 3.� � � Syntax Rules . . . . . . . . . . . . . . . . . . . . . . . .� 3

� � 3.1� � General Syntax . . . . . . . . . . . . . . . . . . . . . . .� 3

� � 3.2� � ABNF Grammar . . . . . . . . . . . . . . . . . . . . . . . .� 3

� � 3.3� � Special Cases and Default Values . . . . . . . . . . . . . .� 4

� � 3.3.1 If There is Only a Server� . . . . . . . . . . . . . . . . .� 4

� � 3.3.2 If Server is Empty Then server=localhost . . . . . . . . . .� 4

� � 3.3.3 Default Port . . . . . . . . . . . . . . . . . . . . . . . .� 4

� � 3.4� � Encoding Rules . . . . . . . . . . . . . . . . . . . . . . .� 4

� � 4.� � � Transport Independence . . . . . . . . . . . . . . . . . . .� 4

� � 5.� � � Examples . . . . . . . . . . . . . . . . . . . . . . . . . .� 4

� � 6.� � � Security Considerations� . . . . . . . . . . . . . . . . . .� 5

� � 7.� � � IANA Considerations� . . . . . . . . . . . . . . . . . . . .� 5

� � � � � � � � References . . . . . . . . . . . . . . . . . . . . . . . . .� 6

� � A.� � � Registration Template� . . . . . . . . . . . . . . . . . . .� 7

� � � � � � � � Author's Address . . . . . . . . . . . . . . . . . . . . . .� 7

� � � � � � � � Full Copyright Statement . . . . . . . . . ....