Re: Requirements for Content Distribution

["Hilarie Orman" <HORMAN@novell.com>]

A pseurorandomly chosen advertisement identifier that
must be carried through in aggregation?  If CDN_C
finds two independent advertisements of attribute "a",
it can choose one or the other, or both, for its
advertisements, but must included the originator's
unique ID (e.g. hash(originator_ip_address, attribute
code, attribute value)) with the aggregation.

Hilarie

>>> Oliver Spatscheck <spatsch@research.att.com> 01/15/01 02:07PM >>>
Stephen Thomas writes:
 > 
 > Many good questions. In some cases I have a tentative opinion; in all more 
 > discussion would be helpful.
 > 
 > At 12:42 PM 2001-01-15 -0700, Hilarie Orman wrote:
 > >In section 3, does the protocol indicate that CDN B is an agent for CDN A, or
 > >does CDN B aggregate messages from its "lefthand" CDN's of surrogates
 > >and promote them rightward as if they originated from CDN B?
 > 
 > In the interest of simplicity, I was assuming that CDN B would aggregate 
 > all information it receives from other content destinations and advertise 
 > those capabilities as its own. At least, I think that simplifies the 
 > protocol. (I also think that's how it would work in practice, as, in a 
 > business relationship, CDN B may not want to reveal that the capabilities 
 > its advertising are really "outsourced" from someone else.) That 
 > conclusion, however, was a personal assumption not necessarily justified by 
 > any discussion on the list. Further comments, anyone? (Subsequent drafts 
 > will address this point explicitly, one way or the other.)

One problem here is loop avoidance.

Oliver