idnits 2.17.1 draft-ietf-cdi-known-request-routing-03.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 3568 5 Title: Known Content Network (CN) Request-Routing 6 Mechanisms 7 Author(s): A. Barbir, B. Cain, R. Nair, O. Spatscheck 8 Status: Informational 9 Date: July 2003 10 Mailbox: abbieb@nortelnetworks.com, bcain@storigen.com, 11 nair_raj@yahoo.com, spatsch@research.att.com 12 Pages: 19 13 Characters: 42443 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-cdi-known-request-routing-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3568.txt 20 This document presents a summary of Request-Routing techniques that 21 are used to direct client requests to surrogates based on various 22 policies and a possible set of metrics. The document covers 23 techniques that were commonly used in the industry on or before 24 December 2000. In this memo, the term Request-Routing represents 25 techniques that is commonly called content routing or content 26 redirection. In principle, Request-Routing techniques can be 27 classified under: DNS Request-Routing, Transport-layer 28 Request-Routing, and Application-layer Request-Routing. 30 This document is a product of the Content Distribution Internetworking 31 Working Group of the IETF. 33 This memo provides information for the Internet community. It does 34 not specify an Internet standard of any kind. Distribution of this 35 memo is unlimited. 37 This announcement is sent to the IETF list and the RFC-DIST list. 38 Requests to be added to or deleted from the IETF distribution list 39 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 40 added to or deleted from the RFC-DIST distribution list should 41 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 43 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 44 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 45 help: ways_to_get_rfcs. For example: 47 To: rfc-info@RFC-EDITOR.ORG 48 Subject: getting rfcs 50 help: ways_to_get_rfcs 52 Requests for special distribution should be addressed to either the 53 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 54 specifically noted otherwise on the RFC itself, all RFCs are for 55 unlimited distribution.echo 56 Submissions for Requests for Comments should be sent to 57 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 58 Authors, for further information.