Changeset 2009 for draft-ietf-httpbis-http2/latest
- Timestamp:
- 28/11/12 15:39:31 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis-http2/latest/draft-ietf-httpbis-http2.html
r1998 r2009 406 406 } 407 407 @bottom-center { 408 content: "Expires May 30, 2013";408 content: "Expires June 1, 2013"; 409 409 } 410 410 @bottom-right { … … 445 445 <meta name="dct.creator" content="Peon, R."> 446 446 <meta name="dct.creator" content="Thomson, M."> 447 <meta name="dct.creator" content="Melnikov, A."> 447 448 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-http2-latest"> 448 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 6">449 <meta name="dct.issued" scheme="ISO8601" content="2012-11-28"> 449 450 <meta name="dct.abstract" content="This document describes SPDY, a protocol designed for low-latency transport of content over the World Wide Web. SPDY introduces two layers of protocol. The lower layer is a general purpose framing layer which can be used atop a reliable transport (likely TCP) for multiplexed, prioritized, and compressed data communication of many concurrent streams. The upper layer of the protocol provides HTTP-like RFC2616 semantics for compatibility with existing HTTP application servers."> 450 451 <meta name="description" content="This document describes SPDY, a protocol designed for low-latency transport of content over the World Wide Web. SPDY introduces two layers of protocol. The lower layer is a general purpose framing layer which can be used atop a reliable transport (likely TCP) for multiplexed, prioritized, and compressed data communication of many concurrent streams. The upper layer of the protocol provides HTTP-like RFC2616 semantics for compatibility with existing HTTP application servers."> … … 466 467 </tr> 467 468 <tr> 468 <td class="left">Expires: May 30, 2013</td>469 <td class="left">Expires: June 1, 2013</td> 469 470 <td class="right">Google, Inc</td> 470 471 </tr> … … 479 480 <tr> 480 481 <td class="left"></td> 481 <td class="right">November 26, 2012</td> 482 <td class="right">A. Melnikov, Editor</td> 483 </tr> 484 <tr> 485 <td class="left"></td> 486 <td class="right">Isode Ltd</td> 487 </tr> 488 <tr> 489 <td class="left"></td> 490 <td class="right">November 28, 2012</td> 482 491 </tr> 483 492 </tbody> … … 510 519 in progress”. 511 520 </p> 512 <p>This Internet-Draft will expire on May 30, 2013.</p>521 <p>This Internet-Draft will expire on June 1, 2013.</p> 513 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 514 523 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2015 2024 (editor) 2016 2025 <span class="n hidden"><span class="family-name">Thomson</span><span class="given-name">Martin</span></span></span><span class="org vcardline">Microsoft</span><span class="adr"><span class="street-address vcardline">3210 Porter Drive</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="postal-code">94043</span></span><span class="country-name vcardline">US</span></span><span class="vcardline">Email: <a href="mailto:martin.thomson@skype.net"><span class="email">martin.thomson@skype.net</span></a></span></address> 2026 <address class="vcard"><span class="vcardline"><span class="fn">Alexey Melnikov</span> 2027 (editor) 2028 <span class="n hidden"><span class="family-name">Melnikov</span><span class="given-name">Alexey</span></span></span><span class="org vcardline">Isode Ltd</span><span class="adr"><span class="street-address vcardline">5 Castle Business Village</span><span class="street-address vcardline">36 Station Road</span><span class="vcardline"><span class="locality">Hampton</span>, <span class="region">Middlesex</span> <span class="postal-code">TW12 2BX</span></span><span class="country-name vcardline">UK</span></span><span class="vcardline">Email: <a href="mailto:Alexey.Melnikov@isode.com"><span class="email">Alexey.Melnikov@isode.com</span></a></span></address> 2017 2029 </div> 2018 2030 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
Note: See TracChangeset
for help on using the changeset viewer.