I-D ACTION:draft-ietf-cdi-known-request-routing-03.txt

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Content Distribution Internetworking Working Group of the IETF.

	Title		: Known CN Request-Routing Mechanisms
	Author(s)	: A. Barbir, B. Cain et al.
	Filename	: draft-ietf-cdi-known-request-routing-03.txt
	Pages		: 24
	Date		: 2003-4-4
	
The work presents a summary of Request-Routing techniques that are
used to direct client requests to surrogates based on various
policies and a possible set of metrics. The document covers
techniques that were commonly used in the industry on or before
December 2000. In this memo the term Request-Routing represents
techniques that is commonly called content routing or content
redirection. In principle, Request-Routing techniques can beclassified under: DNS Request-Routing, Transport-layer
Request-Routing, and Application-layer Request-Routing.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-cdi-known-request-routing-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-cdi-known-request-routing-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email protected].
In the body type:
	"FILE /internet-drafts/draft-ietf-cdi-known-request-routing-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="[email protected]"

Content-Type: text/plain
Content-ID:	<[email protected]>

ENCODING mime
FILE /internet-drafts/draft-ietf-cdi-known-request-routing-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-cdi-known-request-routing-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<[email protected]>

--OtherAccess--

--NextPart--