architecture terminology

[Abdullah Rayhan <rayhan@ee.ryerson.ca>]

I have few comments regarding the terminology and the
description of the architecture draft for the sake of
clarity. I hope that they would be taken with an open
mind from the WG members.

I understand that there are three functional components
of the CDI architecture where they are supposed to reside
in what is called content peering gateway (CPG). Then
it goes on to describe content peering system, distribution
peering system, etc. It is unfortunate that these terms
are used in this way but being verbose and add little
clarity  to the text. Is this due to the fact that CDI
is a new concept and we are trying to understand it as
we go along?

My suggestion would be to simplify the terms being used.
For example, using content gateway (CG) or content router
(CR). When a gateway is a border device it runs the
inter-CN protocols and when it is intra-CN it runs
the intra-CN protocols. Of course, it might run both
if the design allows. Isn't this similar in theory
and practice to ip routing? Dropping the request-routing
system, distribution system, etc... After all, the
architecture is to describe functional components which
will translate into protocols and scenarios and not systems.

Furthermore, the implementation of the CG could couple
the various protocols in one device or follow a more
decoupled/distributed approach. In the latter case,
the WG might consider how these various devices
need to interact with each other if the experience
shows a need for it. Till then consider to be one
and make the distinction when discussing the request-
routing view, the distribution view, and the accounting
view of the scenarios.

my 2 cents,

regards
Abdallah Rayhan