Skip to content
Branch: master
Go to file
Code

Latest commit

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 

README.md

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

Development

  • edit rfc.xml
  • pip install xml2rfc
  • make

Relevant Documents

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

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
  • List normative and informative references

About

πŸ” turning the system behind GPG Sync into an Internet standard

Topics

Resources

Releases

No releases published
You can’t perform that action at this time.