public marks

PUBLIC MARKS from digitalmonkey with tag rfc

September 2005

August 2005

RFC 2192 : IMAP URL Scheme - C. Newman, Innosoft - September 1997

imap://<iserver>/ imap://<iserver>/<enc_list_mailbox>;TYPE=<list_type> imap://<iserver>/<enc_mailbox>[uidvalidity][?<enc_search>] imap://<iserver>/<enc_mailbox>[uidvalidity]<iuid>[isection]

RFC 3187 (Informational) : Using International Standard Book Numbers as Uniform Resource Names ~ J. Hakala, Helsinki University Library - H. Walravens, The International ISBN Agency - October 2001

"This document discusses how International Standard Book Numbers (ISBN) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141".

July 2005

RFC 2397 : The "data" URL scheme ~ L. Masinter, Xerox Corporation - August 1998

by 1 other
"A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally".

RFC 2326 : Real Time Streaming Protocol (RTSP) ~ H. Schulzrinne, Columbia U. - A. Rao, Netscape - R. Lanphier, RealNetworks - April 1998

"The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties".

June 2005

RFC 2141 : URN Syntax ~ R. Moats, AT&T - May 1997

"Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers".

RFC 2244 : ACAP -- Application Configuration Access Protocol ~ C. Newman, Innosoft - J. G. Myers Netscape November 199

"The Application Configuration Access Protocol (ACAP) is designed to support remote storage and access of program option, configuration and preference information".