Repository files navigation

This is the working area for the Working Group internet-draft, "Automatic Certificate Management Environment (ACME)".

• Editor's copy
• Build history
• Working Group Draft

Before submitting feedback, please familiarize yourself with our current issueslist and review theworking groupdocuments andmailinglist discussion. If you'renew to this, you may also want to read theTao of theIETF.

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

1. The best way to provide feedback (editorial or design) and ask questions issending an e-mail to our mailing list(info). This will ensure thatthe entire Working Group sees your input in a timely fashion.

2. If you haveeditorial suggestions (i.e., those that do not change themeaning of the specification), you can either:

a) Fork this repository and submit a pull request; this is the lowestfriction way to get editorial changes in.

b) Submit a new issue to GitHub, and mention that you believe it is editorialin the issue body. It is not necessary to notify the mailing list foreditorial issues.

c) Make comments on individual commits in GitHub. Note that this feedback isprocessed only with best effort by the editors, so it should only be used forquick editorial suggestions or questions.

3. For non-editorial (i.e.,design) issues, you can also create an issue onGitHub. However, youmust notify the mailing list when creating such issues,providing a link to the issue in the message body.

Note thatGitHub issues are not for substantial discussions; the onlyappropriate place to discuss design issues is on the mailing list itself.

Formatted text and HTML versions of the draft can be built usingmake.

$ make

This requires that you have the necessary software installed. There are severalother tools that are enabled by make, check the Makefile for details, includinglinks to the software those tools might require.

Mac users will need to installXcode to getmake, seethis answer for instructions.

Windows users will need to useCygwin to getmake.

All systems requirexml2rfc. ThisrequiresPython. The easiest way to getxml2rfc is withpip.

Using avirtualenv:

$ virtualenv --no-site-packages venv# remember also to activate the virtualenv before any 'make' run$source venv/bin/activate$ pip install xml2rfc

To your local user account:

$ pip install --user xml2rfc

Or globally:

$ sudo pip install xml2rfc

xml2rfc depends on development versions oflibxml2 andlibxslt1. These packages are namedlibxml2-dev andlibxslt1-dev (Debian, Ubuntu) orlibxml2-devel andlibxslt1-devel (RedHat,Fedora).

If you use markdown, you will also need to installkramdown-rfc2629,which requires Ruby and can be installed using the Ruby packagemanager,gem:

$ gem install kramdown-rfc2629

Some other helpful tools are listed inconfig.mk.

Any submission to theIETF intended by the Contributorfor publication as all or part of an IETF Internet-Draft or RFC and anystatement made within the context of an IETF activity is considered an "IETFContribution". Such statements include oral statements in IETF sessions, aswell as written and electronic communications made at any time or place, whichare 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 groupor 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 ofRFC 5378 andRFC 3979(updated byRFC 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 orfunction, are not IETF Contributions in the context of this notice.

Please consultRFC 5378 andRFC3979 for details.

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

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