Keylist RFC

This repository contains the materials produced in the preparation of the RFC to standardize the keylist format and functionality provided by GPG Sync.

What's with the weird filenames?

The IETF specifies that independently submitted I-D (Internet-Drafts) should follow the filename format draft-[first author's last name]-[document name]-[version]. rfc.xml is where development takes place. When a new version of the I-D is submitted, a copy of the .xml file submitted at that time is copied to the submissions directory.

Quick Links

• IETF Datatracker (for reading the official copy of the document)
• Mailing list (for discussion and development)

Development

• edit rfc.xml
• pip install xml2rfc
• make

Relevant Documents

Non-RFC documents relevant to the preparation of this RFC are listed below.

• The IETF Area List
• RFC Editorial Guidelines and Procedures
• IETF Standards Process

Relevant RFCs

RFCs that are potentially relevant to the preparation of this document are listed below. This list includes both RFC style guides and existing RFCs related to OpenPGP.

• RFC7322: RFC Style Guide
• RFC7997: The Use of Non-ASCII Characters in RFCs
• RFC2026: The Internet Standards Process (rev.3; note: errata exist)
• RFC4880: OpenPGP Message Format
• RFC2629: Writing I-Ds and RFCs using XML

Updates

• August 6, 2018 — first draft published
• August 21, 2018 — mailing list created
• August 22, 2018 — second draft published
• October 13, 2018 — third draft published

TODO

• [ ] Expand acronyms on first use
• [x] List normative and informative references