W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2007

Re: NEW ISSUE: classifying and updating informative references

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 12 Jun 2007 22:40:02 +1000
Message-Id: <1C21BFFF-CB95-4324-8F50-147C2C065009@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
To: Julian Reschke <julian.reschke@gmx.de>

http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/issues/#i65


On 29/05/2007, at 12:14 AM, Julian Reschke wrote:

>
> Hi,
>
> as far as I can tell, the references below are informative and  
> should be classified as such. In some cases, they need to be  
> updated as well:
>
>     Luo1998 ("Tunneling TCP based protocols through Web proxy  
> servers", also update reference to quote the expired Internet Draft  
> properly).
>
>     Nie1997 ("Network Performance Effects of HTTP/1.1, CSS1, and  
> PNG").
>
>     Pad1995 ("Improving HTTP Latency").
>
>     RFC821 (SMTP), also update the reference to RFC2821.
>
>     RFC822 ("STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT  
> MESSAGES") -- but add another instance as RFC822ABNF for the cases  
> where the reference if for the ABNF part (these references will  
> later be replaced by references to RFC4234 (see issue abnf)).
>
>     RFC959 (FTP).
>
>     RFC1036 ("Standard for Interchange of USENET Messages").
>
>     RFC1123 ("Requirements for Internet Hosts -- Application and  
> Support") -- it is only used as a background reference for rfc1123- 
> date, which this spec defines itself (note that note this disagrees  
> with draft-gettys-http-v11-spec-rev-00 which made it normative).
>
>     RFC1305 ("Network Time Protocol (Version 3)").
>
>     RFC1436 (Gopher).
>
>     RFC1630 (URI Syntax) -- there'll be a normative reference to a  
> newer spec.
>
>     RFC1738 (URL) -- there'll be a normative reference to a newer  
> spec.
>
>     RFC1806 ("Communicating Presentation Information in Internet  
> Messages: The Content-Disposition Header").
>
>     RFC1808 (Relative Uniform Resource Locators).
>
>     RFC1867 ("Form-based File Upload in HTML"), also update the  
> reference to RFC2388 ("Returning Values from Forms: multipart/form- 
> data").
>
>     RFC1900 ("Renumbering Needs Work").
>
>     RFC1945 (HTTP/1.0).
>
>     RFC1950 (ZLIB).
>
>     RFC1951 (DEFLATE).
>
>     RFC1952 (GZIP).
>
>     RFC2026 ("The Internet Standards Process -- Revision 3").
>
>     RFC2049 ("Multipurpose Internet Mail Extensions (MIME) Part  
> Five: Conformance Criteria and Examples").
>
>     RFC2068 (HTTP/1.1).
>
>     RFC2076 ("Common Internet Message Headers").
>
>     RFC2110 (MHTML), also update the reference to RFC2557.
>
>     RFC2145 ("Use and Interpretation of HTTP Version Numbers").
>
>     RFC2183 ("Communicating Presentation Information in Internet  
> Messages: The Content-Disposition Header Field").
>
>     RFC2277 ("IETF Policy on Character Sets and Languages").
>
>     RFC2279 (UTF8), also update the reference to RFC3629.
>
>     RFC2324 (HTCPCP/1.0).
>
>     Spero ("Analysis of HTTP Performance Problems").
>
>     Tou1998 ("Analysis of HTTP Performance").
>
>     WAIS ("WAIS Interface Protocol Prototype Functional  
> Specification (v1.5)").
>
>
> Please review & confirm.
>
> Best regards, Julian
>
>
>


--
Mark Nottingham     http://www.mnot.net/
Received on Tuesday, 12 June 2007 12:40:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:10 GMT