added open more open issues; status (std->info); Acknowledgments update

Bernie Hoeneisen 3 years ago
parent f2c572c7cb
commit c21e978cd2

@ -4,7 +4,7 @@ coding: utf-8
title: "Privacy and Security Threat Analysis for Private Messaging"
abbrev: "Private Messaging: Threat Analysis"
docname: draft-symeonidis-pearg-private-messaging-threats-01
category: std
category: info
stand_alone: yes
pi: [toc, sortrefs, symrefs, comments]
@ -30,7 +30,7 @@ informative:
# I-D.birk-pep-trustwords:
# I-D.marques-pep-rating:
# I-D.marques-pep-handshake:
# I-D.pep-keysync:
{::include ../shared/references/clark-seuring-email.mkd}
{::include ../shared/references/diaz-measuring-anonymity.mkd}
@ -468,7 +468,7 @@ This document requests no action from IANA.
The authors would like to thank the following people who have provided
feedback or significant contributions to the development of this
document: Athena Schumacher, Claudio Luck, Hernani Marques, Kelly
Bristol, Krista Bennett, and Nana Karlstetter.
Bristol, Krista Bennett, Nana Karlstetter, and Sara Dickinson.
--- back
@ -480,6 +480,10 @@ Bristol, Krista Bennett, and Nana Karlstetter.
* Initial version
* this document partially replaces draft-symeonidis-medup-requirements-00
* draft-symeonidis-pearg-private-messaging-threats-01:
* Intended Status: std -> info
# Open Issues
\[\[ RFC Editor: This section should be empty and is to be removed
@ -490,6 +494,13 @@ Bristol, Krista Bennett, and Nana Karlstetter.
* Decide on whether or not "enterprise requirement" will go to this
* Check for occurrences of string "standard" and ajust accordingly
* Section on related work in the IETF
* Use RFC6973 terminology where applicable and sensible, or explain,
why differenct terms are used herein
<!-- LocalWords: utf docname symeonidis medup toc sortrefs symrefs
<!-- LocalWords: vspace blankLines pre Autocrypt autocrypt Unger