[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Candidate re-charter/new WG



> As long as we're on the topic, I have similar concerns about the
> interchangeable use of the terms "CDN Peering" and "Content
> Peering", which
> seem to imply they're equivalent.

I think we started out with "content peering" and subsequently decided the
"content" part was technically inaccurate, so we changed to talking about
"CDN peering".

I think we've recently decided in design team discussions that the "peering"
part is also technically inaccurate, so we might be better off calling it
"CDN interoperation" or "content distribution internetworking."  But the
CDNP acronym has become a handy shorthand for people, so it didn't seem
vital to do another name change right away.

Whatever we call it, I'd like to get the definitions and names right so that
you feel comfortable that your scenario is included within what we're
discussing in CDNP. You're absolutely right that your scenario is not
between two CDNs, but I think that it's an example of what we'd like to be
covered.  It still has two distinct but cooperating administrative domains,
and it still has the issues of how to distribute, cache, and serve content
in the context of that cooperation across different admin domains.

--Mark

Mark Stuart Day
Senior Scientist
Cisco Systems
+1 (781) 663-8310
markday@cisco.com