Skip to content

Latest commit

 

History

History
124 lines (95 loc) · 6.21 KB

CONTRIBUTING.md

File metadata and controls

124 lines (95 loc) · 6.21 KB
Raw

QUIC version 1 is done

The base-drafts repository is the historical home of the QUIC version 1 specifications that were written by the IETF QUIC Working Group.

The set of documents are:

All of the documents have been approved for publication as RFCs. We will no longer consider design changes or substantial editorial changes unless they relate to severe security, interoperability or deployment problems. See Post-IESG Process below for further information

The QUIC Working Group welcomes discussion about new versions of QUIC, and new extensions to QUIC. See Engaging with the QUIC community for guidance

Be aware that all contributions fall under the "NOTE WELL" terms outlined below and our Code of Conduct applies.

Post-IESG Process

The consensus of the QUIC Working Group is reflected in the QUIC version 1 documents, which has been confirmed through the IETF Last Call and IESG review stages. The goal of the Post-IESG process is to minimize the risk of changes invalidating the established consensus in these documents. Consequently, design changes will no longer be considered unless they relate to severe security, deployment or implementation problems. If you believe you have identified such a problem, please raise the issue on the Working Group mailing list with a clear marking in the Subject: line e.g. "New Issue ...".

Any change will be subject to careful review and discussion, which might involve the editors, chairs, Working Group, and our Area Director. After this review and discussion, errata may need to be filed for the published RFCs, or the Working Group may otherwise address such valid issues.

Engaging with the QUIC community

The scope of work in the QUIC Working Group is described in our charter and it extends beyond the development of the documents held in this repository. Anyone is welcome to contribute to the QUIC Working Group; you don't have to join the Working Group, because there is no "membership" -- anyone who participates in the work is a part of the QUIC Working Group.

Before doing so, please familiarize yourself with our charter. If you're new to IETF work, you may also want to read the Tao of the IETF.

Following Discussion

The Working Group has a few venues for discussion:

  • We plan to meet at all IETF meetings for the foreseeable future, and possibly hold interim meetings between them as required. Agendas, minutes, and presentations are available in our meeting materials repository and the official proceedings.

  • Our mailing list is used for most communication, including notifications of meetings, new drafts, consensus calls and other business, as well as issue discussion.

  • We maintain several repositories in our GitHub organization Github. Specific issues are discussed on the relevant issues list. If you don't want to use Github to follow these discussions, you can subscribe to the issue announce list.

  • The quicdev Slack is used for more realtime communication, typcially amongst implementers, operators and researchers. Contact the WG chairs for an invitation. Note that discussions on Slack are subject to the contribution guideline described in this document.

To be active in the Working Group, you can participate in any of these places. Most activity takes place on the mailing list, but if you just want to comment on and raise issues, that's fine too.

Code of Conduct

The IETF Guidelines for Conduct applies to all Working Group communications and meetings.

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 8179.

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 8179 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.