SMTP Strict Transport Security
Clone or download
abrotman Update reporting.md
Punycode for IDNs
Latest commit 339c4ac Aug 13, 2018

README.md

SMTP Strict Transport Security and TLS Reporting

Working drafts for https://datatracker.ietf.org/doc/draft-ietf-uta-mta-sts/ and https://datatracker.ietf.org/doc/draft-ietf-uta-smtp-tlsrpt/

Contributing

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

  • Questions and larger design issues: Email the authors and/or the IETF UTA mailing list.
  • Editorial suggestions: Fork the repository and submit a pull request, or open an issue on Github.

Editing and Building

The RFC XML and TXT files are generated from the master Markdown documents mta-sts.md and reporting.md. Please make all edits in those master documents, then regenerate the formatted files by running make.

The Makefile depends upon mmark and xml2rfc.

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.