p≡p I-Ds (IETF Internet-Drafts)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Kelly Bristol 65b30c8cfc KRB LAMPS HP edits 6 months ago
forwarded-no added make publish (use with care) 1 year ago
ietf-lamps-hp KRB LAMPS HP edits 6 months ago
ietf-lamps-hp-requirements Typo 6 months ago
lamps-header-protection Typo 6 months ago
medup-requirements added make publish (use with care) 1 year ago
medup-ux-considerations added make publish (use with care) 1 year ago
misc approved by Alexey 6 months ago
pearg-analysis added open more open issues; status (std->info); Acknowledgments update 1 year ago
pep fix pep-email to compile incl updating asciiarts and .mkd to follow convention: 7 months ago
pep-email krb: pep email edits 6 months ago
pep-handshake Archive draft-marques-pep-handshake-05. Set next reivision to 06. 6 months ago
pep-keyreset added make publish (use with care) 1 year ago
pep-keysync Updated Acknowledgements section (hope I got everyone who provided feedback...) 6 months ago
pep-rating There is no grey/gray color; that's no color! :) 7 months ago
pep-trustwords pep-trustwords: next rev to be 06 1 year ago
shared is-140 changes, updated ascii art 6 months ago
.gitignore optizimed regexps 7 months ago
README.md added https clone variant 6 months ago



This repository contains different p≡p and other (e.g., MEDUP) Internet-Drafts, some already submitted in different versions, others under development and yet to be submitted in a first version -- to the IETF Internet-Drafts repository:


In each directory an Internet-Draft (I-D) is provided, e.g.:

  • pep (pEp's general draft)
  • pep-email (pEp for email)
  • pep-handshake (pEp's method to authenticate peers)
  • pep-keysync (pEp's method to synchronize secret keys)
  • pep-rating (pEp's rating system to signal privacy levels)
  • pep-trustwords (pEp's replacement for fingerprints)


The mandatory ASCII or XML files for submission are created using the kramdown-rfc2629 tool creating the XMLv2 format initially described as RFC2629 (obsoleted by RFC7749):


Please install kramdown-rfc2629, ruby and xml2rfc through your package system or directly from the respective sites:

You can also install kramdown-rfc2629 through the ruby gem packaging system if your packaging system doesn't know anything about this tool:


Structure and contents of each I-D

Each p≡p I-D consists of the following raw files:

  • ${name_of_the_draft}.mkd
  • Makefile

Abstracts should give a rough overview of what the I-D is about: this is to happen over 5-10 lines. Less than 3 and more than 20 lines should be avoided.

The main content goes into the middle section: make sure you also provide “Introduction” and “Security Consideration” subsections. For the latter, please check RFC3552 to see what aspects to consider:


A back section can be used for appendix information like listings or information which provides additional information, but which is not mandatory to understand the I-D.

Basic metadata (e.g., authors’ names, email addresses and the draft title), but also references (including RFCs, by instance) are made available through a special syntax at the beginning of the Markdown file.

Makefiles contain the build instructions to generate the I-Ds in the required ASCII and xml2rfc v2 forms accepted by the IETF submission system. Additionally, they also create HTML versions.

By default, revision number (REV) is set to “00”: make sure to increment this as IETF contributions are furthered.

Version Control System (git)

Most important commands:

Clone repository

 git clone ssh://gitea@gitea.pep.foundation:23065/pEp.foundation/internet-drafts.git
 git clone https://gitea.pep.foundation/pEp.foundation/internet-drafts.git

Update local directories to latest remote repository state

 cd internet-drafts
 git pull

Note: Merge handling may be required to take care of (if by git)

Upload local changes to repository

Important: To avoid conflicts, always update the local directories to the latest repository state (see commands in last bullet point) before doing a commit!

 git commit -m "<Changelog, short description of changes>" [ <filename> ]
 git push

More information