MessageVortex Protocol
draft-gwerder-messagevortexmain-05
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Martin Gwerder
|
|
Last updated |
|
2020-09-12
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
Experimental
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force M. Gwerder
Internet-Draft FHNW
Intended status: Experimental September 12, 2020
Expires: March 16, 2021
MessageVortex Protocol
draft-gwerder-messagevortexmain-05
Abstract
The MessageVortex (referred to as Vortex) protocol achieves different
degrees of anonymity, including sender, receiver, and third-party
anonymity, by specifying messages embedded within existing transfer
protocols, such as SMTP or XMPP, sent via peer nodes to one or more
recipients.
The protocol outperforms others by decoupling the transport from the
final transmitter and receiver. No trust is placed into any
infrastructure except for that of the sending and receiving parties
of the message. The creator of the routing block (Routing block
builder;RBB) has full control over the message flow. Routing nodes
gain no non-obvious knowledge about the messages even when
collaborating. While third-party anonymity is always achieved, the
protocol also allows for either sender or receiver anonymity.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 16, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
Gwerder Expires March 16, 2021 [Page 1]
Internet-Draft MessageVortex Protocol September 2020
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 5
1.2. Protocol Specification . . . . . . . . . . . . . . . . . 5
1.3. Number Specification . . . . . . . . . . . . . . . . . . 5
2. Entities Overview . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Node . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.1. Blocks . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2. NodeSpec . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2.1. NodeSpec for SMTP nodes . . . . . . . . . . . . . 6
2.1.2.2. NodeSpec for XMPP nodes . . . . . . . . . . . . . 6
2.2. Peer Partners . . . . . . . . . . . . . . . . . . . . . . 7
2.3. Encryption keys . . . . . . . . . . . . . . . . . . . . . 7
2.3.1. Identity Keys . . . . . . . . . . . . . . . . . . . . 7
2.3.2. Peer Key . . . . . . . . . . . . . . . . . . . . . . 7
2.3.3. Sender Key . . . . . . . . . . . . . . . . . . . . . 7
2.4. Vortex Message . . . . . . . . . . . . . . . . . . . . . 8
2.5. Message . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.6. Key and MAC specifications and usage . . . . . . . . . . 9
2.6.1. Asymmetric Keys . . . . . . . . . . . . . . . . . . . 9
2.6.2. Symmetric Keys . . . . . . . . . . . . . . . . . . . 9
2.7. Transport Address . . . . . . . . . . . . . . . . . . . . 10
2.8. Identity . . . . . . . . . . . . . . . . . . . . . . . . 10
2.8.1. Peer Identity . . . . . . . . . . . . . . . . . . . . 10
2.8.2. Ephemeral Identity . . . . . . . . . . . . . . . . . 10
2.8.3. Official Identity . . . . . . . . . . . . . . . . . . 10
2.9. Workspace . . . . . . . . . . . . . . . . . . . . . . . . 11
2.10. Multi-use Reply Blocks . . . . . . . . . . . . . . . . . 11
2.11. Protocol Version . . . . . . . . . . . . . . . . . . . . 11
3. Layer Overview . . . . . . . . . . . . . . . . . . . . . . . 11
3.1. Transport Layer . . . . . . . . . . . . . . . . . . . . . 12
3.2. Blending Layer . . . . . . . . . . . . . . . . . . . . . 12
Show full document text