RE: Query re request routing

[Steve Rudkin <srudkin@jungle.bt.co.uk>]

I agree 1x is very relevant to broadband streaming. However 1y and 1z would
offer simpler ways of enabling an ACN to deliver *on-demand* broadband
streamed media, since in the on-demand case, surrogates will most likely be
pre-populated.

Steve

-----Original Message-----
From:	owner-cdn@ops.ietf.org [SMTP:owner-cdn@ops.ietf.org] On Behalf Of
DonE@activate.net
Sent:	Monday, March 12, 2001 5:07 PM
To:	srudkin@jungle.bt.co.uk
Cc:	cdn@ops.ietf.org
Subject:	RE: Query re request routing

Steve,
 
Case 1x would be very relevant to broadband streaming media.  The objective
of our efforts is to be able to implement 1x instead of being restricted to
1y or 1z, which in practice is a significant restriction.
 
Don

-----Original Message-----
From: Steve Rudkin [mailto:srudkin@jungle.bt.co.uk]
Sent: Sunday, March 11, 2001 1:00 PM
To: Gary Tomlinson; Phil Rzewski; Eric Dean
Cc: cdn@ops.ietf.org
Subject: Re: Query re request routing

>From the discussion so far I conclude that there are four ways in which an
Access Content Network (ACN) may deliver content (labelled 1x, 1y, 1z and
2). Cases 1y and 1z are most relevant to the example of an ACN delivering
broadband streamed media on demand. 


1 The ACN delivers content acting as a SURROGATE. 

x) Proper RR peering. The ACN peers RRSs, Distribution Systems and
Accounting Systems. Routing requests may be fowarded to another Content
Network. 

y) Delegated RR Peering. The ACN peers RRSs, Distribution Systems and
Accounting Systems. There is a single authoritative RRS which delegates
routing decisions to the ACN's RRS for requests arising from within the
ACN. Only a basic level of RRS peering - sufficient to received delegated
authority - needs to be supported by the ACN. Routing requests are handled
locally. 

z)No RR peering. The ACN only peers Distribution Systems and Accounting
Systems and does not peer Request Routing Systems. Routing requests are
handled locally. For a given content unit, there is one authoritative RRS
amongst the set of peered RRSs, but since the ACN RRS is not peered it must
be authoritative for requests arising from within the ACN. 


2) ACN delivers the content acting as a AVATAR. In this model the ACN does
not peer in terms of request routing or accounting and there is no explicit
distribution peering. Implicit distribution peering in the form of content
signalling and replication takes place. 

Steve 





Email : srudkin@jungle.bt.co.uk
Tel: +44 1473 640886
Fax: +44 1473 640929