RE: What to call that direction/redirection/routing thing

["Condry, Michael W" <michael.w.condry@intel.com>]

Yes, Content routing will work as well.

Sounds like we need a vote
	1.Content routing
	2.Steering
	3. Request Navigation
	4. Redirection

I put them in my order, how about a ranking from others.

-----Original Message-----
From: Gary Tomlinson [mailto:garyt@entera.com]
Sent: Wednesday, November 08, 2000 11:05 PM
To: Fred Douglis; Mark Day
Cc: cdn@ops.ietf.org
Subject: RE: What to call that direction/redirection/routing thing 


I have long held that the correct term to use is content routing.  At this
point in time, our current redirection mechanisms are crude compared what
many of us think content routing can develop into.  However, its clear that
"content routing" is really what we want to aspire to, so why not define the
space properly now.  We can make it very clear that the current systems fall
short in the architecture ID.

Gary

-----Original Message-----
From: Fred Douglis [mailto:douglis@research.att.com]
Sent: Wednesday, November 08, 2000 9:10 AM
To: Mark Day
Cc: cdn@ops.ietf.org
Subject: Re: What to call that direction/redirection/routing thing 


I think I missed the call when the name changed to 'steering' and I, too,
was 
taken aback by the change. 

I vote for redirection.  In the context of CDN peering, one fields a request

from a client, and handles it in one's own CDN, or REDIRECTs it to another
CDN.
In that case, there is a change of direction: the client first goes to CDN 1

and then goes to CDN 2.  

Fred