Merge github.com:httpwg/http-extensions into contributing

# Conflicts:
#	CONTRIBUTING.md

CONTRIBUTING.md

@@ -44,7 +44,9 @@ discussion and their resolution.
 Before filing a new issue, please consider a few things:
 
 * Issues should be just that; issues with our deliverables, **not questions or support requests**.
+
 * Please review the issues list to make sure that you aren't filing a duplicate.
+
 * If you're not sure how to phrase your issue, please ask on the [mailing list](https://lists.w3.org/Archives/Public/ietf-http-wg/).
 
 Issues can also be raised on the [Working Group mailing
@@ -113,23 +115,22 @@ 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 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](https://tools.ietf.org/html/rfc5378) and 
-   [RFC 3979](https://tools.ietf.org/html/rfc3979) 
+ * All IETF Contributions are subject to the rules of [RFC
+   5378](https://tools.ietf.org/html/rfc5378) and [RFC 3979](https://tools.ietf.org/html/rfc3979)
    (updated by [RFC 4879](https://tools.ietf.org/html/rfc4879)).
 
 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](https://tools.ietf.org/html/rfc5378) and
-[RFC3979](https://tools.ietf.org/html/rfc3979) for details.
+Please consult [RFC 5378](https://tools.ietf.org/html/rfc5378) and [RFC
+3979](https://tools.ietf.org/html/rfc3979) 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.