RE: comments for WG Last Call: draft-ietf-cdi-known-request-routi ng-00.txt
"Abbie Barbir"<[email protected]> Tue, 7 May 2002 15:30:14 -0400
| Newsgroups | gmane.ietf.cdi |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1F5FD.9C46B498 Content-Type: text/plain; charset="iso-8859-1" Christophe, thanks for the feedback. here is a summary of the changes to the document. see in line below. abbie -----Original Message----- From: Christophe Deleuze [mailto:[email protected]] Sent: Tuesday, April 16, 2002 10:46 AM To: [email protected] Subject: comments for WG Last Call: draft-ietf-cdi-known-request-routing-00.txt 1. Introduction >>> Too many spaces... -------- abbie fixed. ----- SNIP and responses for content. Content Networks rely on layer 7 protocols such as HTTP [4] OR RTP [8] for transport. >>> This sentence seems to imply that RTP is a layer 7 protocol! But also >>> look on my comment about SSL in section 4.1. ------------ abbie fixed the reference to RTP. ---- SNIP 4.1 Header Inspection Applications such as HTTP [4], RTSP [3], and SSL [2] provide hints >>> I may sound quibbling, but I would call HTTP and RTSP application level >>> protocols rather than applications. As for SSL, [2] describes >>> "Transport Layer Security" which doesn't sound "application". I guess >>> that "application" in this document is to be understood as anything >>> that's above the Internet standard transport protocols, TCP and UDP. If >>> this is the case, this should probably be stated more explicitly >>> (probably early in the document). ---- Abbie fixed to Application Level protocols. -------- SNIP 4.1.1 URL-Based Request-Routing A Uniform Resource Locator (URL) [7] consists of a naming scheme followed by a string whose format is a function of the naming scheme. The string must start with a constant prefix "URL:". >>> What? Here is what [7] says: -------- Abbie I changed the text to just a reference to URL RFC. --- SNIP 4.1.1.2 In-Path Element [...] The technique allows for the possibility of portioning the traffic >>> pArtitioning ------- Abbie fixed. --- SNIP 8. References [...] [5] Day, M., Cain, B. and G. Tomlinson, " A Model for Content Internetworking (CDI)", http://www.ietf.org/internet-drafts/ draft-day-cdnp-model-09.txt (Group Last Call). >>> This is the old name of the draft. --------- Abbie Fixed. [6] Partridge, C., Mendez, T., Milliken W., "Host Anycasting Service", RFC 1546, November 1993. [7] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform Resource Locator (URL), RFC 1738,May 1994. >>> LocatorS -- space typos --------- Abbie Fixed. ------_=_NextPart_001_01C1F5FD.9C46B498 Content-Type: text/html; charset="iso-8859-1" <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35"> <TITLE>RE: comments for WG Last Call: draft-ietf-cdi-known-request-routing-00.txt</TITLE> </HEAD> <BODY> <BR> <P><FONT SIZE=2>Christophe,</FONT> </P> <P><FONT SIZE=2>thanks for the feedback.</FONT> </P> <P><FONT SIZE=2>here is a summary of the changes to the document.</FONT> </P> <P><FONT SIZE=2>see in line below.</FONT> </P> <P><FONT SIZE=2>abbie</FONT> </P> <BR> <P><FONT SIZE=2>-----Original Message-----</FONT> <BR><FONT SIZE=2>From: Christophe Deleuze [<A HREF="mailto:[email protected]">mailto:[email protected]</A>]</FONT> <BR><FONT SIZE=2>Sent: Tuesday, April 16, 2002 10:46 AM</FONT> <BR><FONT SIZE=2>To: [email protected]</FONT> <BR><FONT SIZE=2>Subject: comments for WG Last Call:</FONT> <BR><FONT SIZE=2>draft-ietf-cdi-known-request-routing-00.txt</FONT> </P> <BR> <BR> <P><FONT SIZE=2>1. Introduction</FONT> </P> <P><FONT SIZE=2>>>> Too many spaces...</FONT> </P> <P><FONT SIZE=2>-------- abbie fixed.</FONT> </P> <BR> <P><FONT SIZE=2>----- SNIP</FONT> </P> <P><FONT SIZE=2> and responses for content. Content Networks rely on layer 7 </FONT> <BR><FONT SIZE=2> protocols such as HTTP [4] OR RTP [8] for transport.</FONT> </P> <P><FONT SIZE=2>>>> This sentence seems to imply that RTP is a layer 7 protocol! But also</FONT> <BR><FONT SIZE=2>>>> look on my comment about SSL in section 4.1.</FONT> </P> <P><FONT SIZE=2>------------ abbie fixed the reference to RTP.</FONT> </P> <BR> <P><FONT SIZE=2>---- SNIP</FONT> </P> <P><FONT SIZE=2>4.1 Header Inspection</FONT> </P> <P><FONT SIZE=2> Applications such as HTTP [4], RTSP [3], and SSL [2] provide hints</FONT> </P> <P><FONT SIZE=2>>>> I may sound quibbling, but I would call HTTP and RTSP application level</FONT> <BR><FONT SIZE=2>>>> protocols rather than applications. As for SSL, [2] describes</FONT> <BR><FONT SIZE=2>>>> "Transport Layer Security" which doesn't sound "application". I guess</FONT> <BR><FONT SIZE=2>>>> that "application" in this document is to be understood as anything</FONT> <BR><FONT SIZE=2>>>> that's above the Internet standard transport protocols, TCP and UDP. If</FONT> <BR><FONT SIZE=2>>>> this is the case, this should probably be stated more explicitly</FONT> <BR><FONT SIZE=2>>>> (probably early in the document).</FONT> </P> <BR> <P><FONT SIZE=2>---- Abbie fixed to Application Level protocols.</FONT> </P> <P><FONT SIZE=2>-------- SNIP</FONT> </P> <P><FONT SIZE=2>4.1.1 URL-Based Request-Routing</FONT> </P> <P><FONT SIZE=2> A Uniform Resource Locator (URL) [7] consists of a naming scheme </FONT> <BR><FONT SIZE=2> followed by a string whose format is a function of the naming </FONT> <BR><FONT SIZE=2> scheme. The string must start with a constant prefix "URL:". </FONT> </P> <P><FONT SIZE=2>>>> What? Here is what [7] says:</FONT> <BR><FONT SIZE=2>-------- Abbie I changed the text to just a reference to URL RFC.</FONT> <BR><FONT SIZE=2>--- SNIP</FONT> </P> <P><FONT SIZE=2>4.1.1.2 In-Path Element</FONT> </P> <P><FONT SIZE=2>[...]</FONT> </P> <P><FONT SIZE=2> The technique allows for the possibility of portioning the traffic </FONT> </P> <P><FONT SIZE=2>>>> pArtitioning</FONT> </P> <BR> <P><FONT SIZE=2>------- Abbie fixed.</FONT> </P> <P><FONT SIZE=2>--- SNIP</FONT> </P> <P><FONT SIZE=2>8. References</FONT> </P> <P><FONT SIZE=2>[...]</FONT> </P> <P><FONT SIZE=2> [5] Day, M., Cain, B. and G. Tomlinson, " A Model for Content </FONT> <BR><FONT SIZE=2> Internetworking (CDI)", <A HREF="http://www.ietf.org/internet-drafts/" TARGET="_blank">http://www.ietf.org/internet-drafts/</A></FONT> <BR><FONT SIZE=2> draft-day-cdnp-model-09.txt (Group Last Call). </FONT> </P> <P><FONT SIZE=2>>>> This is the old name of the draft.</FONT> </P> <P><FONT SIZE=2>--------- Abbie Fixed.</FONT> </P> <P><FONT SIZE=2> [6] Partridge, C., Mendez, T., Milliken W., "Host Anycasting </FONT> <BR><FONT SIZE=2> Service", RFC 1546, November 1993.</FONT> </P> <P><FONT SIZE=2> [7] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform Resource </FONT> <BR><FONT SIZE=2> Locator (URL), RFC 1738,May 1994.</FONT> </P> <P><FONT SIZE=2>>>> LocatorS -- space typos</FONT> </P> <P><FONT SIZE=2>--------- Abbie Fixed.</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C1F5FD.9C46B498--