Re: Reminder: "Group last call": draft-day-cdnp-model-08

["Phil Rzewski" <philr@inktomi.com>]

I had a chance to go through this again as a refresher for editing my own (now late) draft. :)

Section 2.3 (Page 6). "Some of the goals of a a server farm include:"... remove duplicate "a".

Section 2.4 (Page 8). "...compared to the time it would take fetch it from the origin server." Insert the word "to" so it's "take to fetch it".

Section 2.4.1 (Page 9). May want to make brief reference to the term "MDN" (Media Distribution Network), since the term has started to be used in the industry since the initial draft. That is, "For a streaming media CDN ("Media Distribution Network", or MDN)..." I don't think it's necessary to put the word in the definitions section, however, since we say clearly that we're referring to both types when we say CDN.

Section 3 (Page 12). "...a CONTENT NETWORK ELEMENT is a device whose processing depends on examining some or all of an IP packet's body..." I'm not sure if this is a statement that could get us in trouble (I'm also not sure if I may have originally written it :) ). We know the IETF traditionally frowns upon in-line network elements that peek at IP packet bodies. For the historical sections where we catalog web switches as an example, I think it's a safe thing to acknowledge. But for our own definitions going forward, we may want to leave this out. In a an "IETF legal" CDN context, when a RRS or surrogate is handling content requests/responses, the IP packets have already been assembled into app-layer messages before any processing is done. Whereas the data originally came from IP packet bodies, I'm not sure that would be clear to an outside reader, and we might get the opposite effect.

Section 5 (Page 12). "CONTENT INTERNETWORKING GATEWAY... can be interconnected with others.  through one or more kinds of peering". Should probably remove everything after the period rather than just changing the period to a comma, since we use the naughty "p" word in there. :)  (and the statement is clear without it)

Section 5, (Page 16). "CONTENT REPLICATION... this is specifically the movement of CONTENT from one system or network to another." Should we not remove the "system or"? We go on to say "There may be ... mechanisms that move CONTENT around within a single network's DISTRIBUTION SYSTEM." But that would also be "movement of CONTENT from one system to another".

Section 5, Page 16. Should we just remove the definition of "REQUEST-ROUTING ADVERTISEMENT" altogether? We use the naughty "p" word, plus I imagine it's in conflict with "AREA ADVERTISEMENT".

Section 5. I know this is a general gripe, but just reading this document with an open mind, I have difficulty envisioning the difference between an AREA ADVERTISEMENT and a DISTRIBUTION ADVERTISEMENT. I guess my main worry is the open-ended word "capabilities" in the definition of DISTRIBUTION ADVERTISEMENT. Is "performance" (as described in AREA ADVERTISEMENT) not a part of capabilities? Is an AREA ADVERTISEMENT trying to aggregate the performance of an "entire" CONTENT NETWORK in a single advertisement (if so we may want to add the word "entire")? If we want this kind of detail to be deferred to the architecture draft, that's ok. Perhaps in the intro to section 5 we could make another reference to the architecture document as the primary place to see how these all fit together in context.

--
Phil


At 01:02 PM 11/2/2001 -0500, Mark Day wrote:
>There is one week left on the group last call for the "model document", see
>below.
>
>--Mark
>
>-----Original Message-----
>From: Mark Day [mailto:markday@cisco.com]
>Sent: Friday, October 26, 2001 2:40 PM
>To: cdn@ops.ietf.org
>Subject: "Group last call": draft-day-cdnp-model-08
>
>
>This is a CDI "Group last call" for comments on draft-day-cdnp-model-08.txt.
>This last call closes Saturday November 10th. Please post any final comments
>you have on this draft to this list by that date.
>
>The draft is available at
>http://www.ietf.org/internet-drafts/draft-day-cdnp-model-08.txt
> 
--
Phil Rzewski - Senior Architect - Inktomi Corporation                  
650-653-2487 (office) - 650-303-3790 (cell) - 650-653-1848 (fax)