- From: Arthur Barstow <art.barstow@gmail.com>
- Date: Wed, 09 Jul 2014 09:45:08 -0400
- To: public-webapps <public-webapps@w3.org>
Editors - please see Yves' e-mail re RFC2616 replacement and update your spec(s) accordingly. -Thanks, AB -------- Original Message -------- Subject: RFC723x (replace RFC2616 - Hypertext Transfer Protocol -- HTTP/1.1) Resent-Date: Wed, 09 Jul 2014 13:19:52 +0000 Resent-From: chairs@w3.org Date: Wed, 9 Jul 2014 09:19:50 -0400 (EDT) From: Yves Lafon <ylafon@w3.org> To: chairs@w3.org Hello Chairs, RFC2616 is now replaced by a set of new RFCs: RFC7230: HTTP/1.1, part 1: Message Syntax and Routing RFC7231: HTTP/1.1, part 2: Semantics and Content RFC7232: HTTP/1.1, part 4: Conditional Requests RFC7233: HTTP/1.1, part 5: Range Requests RFC7234: HTTP/1.1, part 6: Caching RFC7235: HTTP/1.1, part 7: Authentication Along with RFC7236: Initial HTTP Authentication Scheme Registrations RFC7237: Initial HTTP Method Registrations Please modify the references to HTTP/1.1 you are using in the specifications your WGs are working on. Note that you don't need to link to all the RFCs listed above when you replace the RFC2616 reference, it depends on what part of HTTP/1.1 the specification rely on. In most cases, referring to 7230 and 7231 should cover what W3C specifications usually needs when referring to HTTP. HTH, -- Baroula que barouleras, au tiéu toujou t'entourneras. ~~Yves
Received on Wednesday, 9 July 2014 13:45:39 UTC