HTTP/2.0 Draft Specification

This is the working area for the IETF HTTPbis Working Group draft of HTTP/2.0.

Published drafts can be found on the IETF tools site, and are marked with tags here.

The source for our current draft is draft-ietf-httpbis-http2.xml, using the RFC2629 format.

An HTML copy of the current (unsubmitted) draft can be found here, and the text version can be found here.

Providing Feedback

Before submitting feedback, please familiarise yourself with our current issues list, and see our home page for more information about participating.

1. The best way to provide feedback and ask questions is sending an e-mail to our mailing list. This will assure that the entire Working Group sees your input in a timely fashion.

2. If you have editorial suggestions, you can fork this repository and submit a pull request; this is the lowest friction way to get such changes in. While this method can also be used to suggest more substantial changes, they'll need to be discussed on the list first.

3. You can also create an issue on github. However, questions should be asked on the mailing list, not in an issue. Likewise, issues should identify problems, not offer solutions, which can be submitted by one of the mechanisms described above. Issues that violate these guidelines will be closed without comment.

4. Finally, you can make comments on individual commits in Github. Note that this feedback is processed only with best effort by the editors, so it should only be used for quick editorial suggestions or questions, not substantial feedback.

Working With the Draft

If you're an editor, or forking a copy of the draft, a few things to know:

• Pushing to the master branch will automatically generate the HTML on the gh-pages branch.
• You'll need xml2rfc, java and saxon available. You can override the default locations in the environment, if you use "make -e".
• Making the txt and html for the latest draft is done with "make latest".

NOTE WELL

Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:

• The IETF plenary session
• The IESG, or any member thereof on behalf of the IESG
• Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices
• Any IETF working group or portion thereof
• Any Birds of a Feather (BOF) session
• The IAB or any member thereof on behalf of the IAB
• The RFC Editor or the Internet-Drafts function
• All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).

Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.

Please consult RFC 5378 and RFC 3979 for details.

A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.

A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.