aprescott / http-extensions

HTTP Extensions in progress

Draft HTTP Extension Specifications

This is the working area for the IETF HTTP Working Group draft extensions. Currently, this includes:

Alternative Services

• Editors' Draft (plain text)
• Working Group Draft (less recent, more official)
• Open Issues

HTTP Opportunistic Security

• Editors' Draft (plain text)
• Working Group Draft (less recent, more official)
• Open Issues

Tunnel Protocol for CONNECT

Working Group Last Call ends 10 Apr 2015.

• Editors' Draft (plain text)
• Working Group Draft (less recent, more official)
• Open Issues

HTTP Authentication-Info Header Field

in RFC Editor queue

• Editors' Draft (plain text)
• Working Group Draft (less recent, more official)
• Open Issues

HTTP Client-Initiated Content-Encoding

• Editors' Draft
• Working Group Draft (less recent, more official)
• Open Issues

HTTP Legally Restricted Status Code

• Editors' Draft
• Working Group Draft (less recent, more official)
• Open Issues

Contributing

See our contribution guidelines for information about how to participate.

Be aware that all contributions to the specification fall under the "NOTE WELL" terms below.

Working with the Drafts

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-HE available. You can override the default locations in the environment. On a Mac with Homebrew, "saxon-b" is the right package.
• For some drafts, you will need kramdown-rfc2629
• Some of the make targets require GNU Make 4.0
• Making the txt and html for the latest drafts is done with "make".

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.