A few comments/suggestions on this preliminary draft.
a. The draft should specifically include seperate sections capturing requirements placed by the Distribution Peering System on the Request Routing System (RRS) and Accounting System (AS)
b. Section 2
To support the N:1 and 1:N Content Distribution: Content Source capabilities, are some minimum set of capabilities assumed or required from the underlying network or the CPGs?
b. Section 2
".... Routing services, the CPGs for Distribution-only CDNs MUST support
Accounting and Request Routing peering protocols, in addition to
Distribution Peering protocols....... "
This is inconsistent with what is captured in the scenario's document. Although I agree with what captured in this draft, I would like it to state why this requirement is being enforced with examples.
c. Section 2
".......That is, the CPG of a
Distribution-only CDN must interface with the CPGs of the Accounting
and Request Routing CDNs, and optionally, other Distribution CDNs...... "
I am assuming what you mean here is within a CPG, the DPS, RRS and AS must interface, while between CPGs, it are the the DPS system that interface.
d. Section 2.1
This section is confusing! It is more tied to scenario's and RRS as opposed to DPS. Can you please state the original intent of this section.
e. Section 3.1
For the 3 components of the DPS sepcified, you should list common base functionality and then any deltas. Please add to list what underlying transport mechanism is: TCP, UDP...etc
f. Section 3.4
Are there any plans to include status messages
g. Section 4.1
"...... 1. The Content Source will make a decision to request content
distribution services from a Content Destination. This decision
may have been preceded by one or more Content Destinations
sending distribution capabilities advertisements to the Content
Source, negotiation of an offline contractual agreement, or some
combination. ...."
The draft should be clear of the peering arrangement type: Out-of-band or through advrtisments. (i.e list the options clearly)
h. Section 4.2
Should include the base underlying protocol and attain consistency with RRS and AS.
i: Section 4.2
".... Protocols must support the ability to optionally conduct
authenticated and/or encrypted exchanges. ...."
I am bit suprised by the optional statement. I would like to hear from the service providers on this one!
j. Section 4.4
"....... 4. The CPG of a Content Destination MAY support advertising. That
is, real-time advertisement of distribution capabilities are
not be required to establish a Distribution Peering
arrangement. Distribution capabilities may be specified
offline (e.g., as part of contractual negotiations between the
parties) or through some, UDDI for example, web based service
exchange. ....."
Can I assume there are 2 parts: Policy configuration (done offline), Advertisments ? This paragraph needs to be cleaned up.
k. Section 4.4
"....
Capacity: The storage capacity that the CDN can provide. ...."
Are there plans to provide fine granularity?
- Nalin
> -----Original Message-----
> From: Lisa Amini [mailto:aminil@us.ibm.com]
> Sent: Friday, February 02, 2001 2:15 PM
> To: cdn@ops.ietf.org
> Subject: Distribution Draft
>
>
> I've attached the latest draft for CDI Distribution
> Requirements. It is
> still very much a work-in-progress, so I would appreciate any
> comments or
> suggestions.
>
> --Lisa
>
> (See attached file: draft-cdnp-distreqs-2.txt)
>