MessageVortex Protocol
draft-gwerder-messagevortexmain-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Internet Engineering Task Force                                  Gwerder
Internet-Draft                                         November 29, 2018
Intended status: Experimental
Expires: June 2, 2019

                         MessageVortex Protocol
                   draft-gwerder-messagevortexmain-00

Abstract

   MessageVortex Protocol specifies messages embedded within existing
   transfer protocols such as SMTP or XMPP to send them anonymously from
   peer to peer.

   The protocol outperforms other protocols by decoupling transport from
   the final transmitter and receiver party.  There is no trust put into
   any infrastructure except for the infrastructure of the sending and
   receiving party of a message.  The Message flow is entirely selected
   by the creator of the routing block.  Routing nodes gain no non-
   obvious knowledge about messages even when collaborating.  Third-
   party anonymity is always achieved.  Furthermore, one out of sender
   and receiver anonymity may be achieved.

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 June 2, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents

Gwerder                   Expires June 2, 2019                  [Page 1]
Internet-Draft           MessageVortex Protocol            November 2018

   (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.  NodeSpec  . . . . . . . . . . . . . . . . . . . . . .   5
         2.1.1.1.  NodeSpec for SMTP nodes . . . . . . . . . . . . .   6
         2.1.1.2.  NodeSpec for XMPP nodes . . . . . . . . . . . . .   6
     2.2.  Peer Partner  . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Encryption keys . . . . . . . . . . . . . . . . . . . . .   6
       2.3.1.  Identity Keys . . . . . . . . . . . . . . . . . . . .   7
       2.3.2.  Peer Key  . . . . . . . . . . . . . . . . . . . . . .   7
       2.3.3.  Sender Key  . . . . . . . . . . . . . . . . . . . . .   7
     2.4.  Vortex Message  . . . . . . . . . . . . . . . . . . . . .   7
     2.5.  Message . . . . . . . . . . . . . . . . . . . . . . . . .   8
     2.6.  Key and MAC specifications and usages . . . . . . . . . .   8
       2.6.1.  Asymmetric Keys . . . . . . . . . . . . . . . . . . .   9
       2.6.2.  Symmetric Keys  . . . . . . . . . . . . . . . . . . .   9
     2.7.  Blocks  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     2.8.  Transport Address . . . . . . . . . . . . . . . . . . . .   9
     2.9.  Identity  . . . . . . . . . . . . . . . . . . . . . . . .  10
       2.9.1.  Peer Identity . . . . . . . . . . . . . . . . . . . .  10
       2.9.2.  Ephemeral Identity  . . . . . . . . . . . . . . . . .  10
       2.9.3.  Official Identity . . . . . . . . . . . . . . . . . .  10
     2.10. Workspace . . . . . . . . . . . . . . . . . . . . . . . .  10
   3.  Layer Overview  . . . . . . . . . . . . . . . . . . . . . . .  11
     3.1.  Transport Layer . . . . . . . . . . . . . . . . . . . . .  11
     3.2.  Blending Layer  . . . . . . . . . . . . . . . . . . . . .  11
     3.3.  Routing Layer . . . . . . . . . . . . . . . . . . . . . .  12
     3.4.  Accounting Layer  . . . . . . . . . . . . . . . . . . . .  12
   4.  Vortex Message  . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .  12