[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
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.
From: firstname.lastname@example.org [SMTP:email@example.com] On Behalf Of DonE@activate.net
Sent: Friday, March 09, 2001 12:47 AM
Cc: firstname.lastname@example.org; email@example.com
Subject: RE: Query re request Routing
> -----Original Message-----
> From: Eric Dean [mailto:firstname.lastname@example.org]
> Sent: Thursday, March 08, 2001 4:33 PM
> To: DonE@activate.net
> Cc: email@example.com; firstname.lastname@example.org
> Subject: RE: Query re request Routing
> On Thu, 8 Mar 2001 DonE@activate.net wrote:
> > > The question to answer then is: should distribution
> and/or accounting
> > > peering necessitate a basic level of request routing peering
> > > (namely the
> > > ability to handover authority to route certain requests for
> > > given content
> > > units)?
> > Yes, as long as the RR you are talking about doesn't require the use of
> > protocol.
> How can it not require a protocol? How would one know which
> clients are
> more proximate to a peered network if they are not advertised.
Yes, this RR is necessary, but I'm thinking of the case this is done by the
CDN's (possibly proprietary) RRS. What I'm saying is CDN RR peering should
be required when CDN Distribution and/or Accounting peering is used.
> > That is, the handover of the request routing could be set up
> > manually.
> I'd be interested to understand how this can be handled offline.
> Theoretically, the Internet culd be statically routed but is highly
By manually creating a link to the CDN's RRS.
Email : email@example.com
Tel: +44 1473 640886
Fax: +44 1473 640929