Re: [Endymail] [Cryptography] Secure universal message addressing

Hugo Maxwell Connery <hmco@env.dtu.dk> Wed, 06 April 2016 11:41 UTC

Return-Path: <hmco@env.dtu.dk>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFDAF12D18A for <endymail@ietfa.amsl.com>; Wed, 6 Apr 2016 04:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.93
X-Spam-Level:
X-Spam-Status: No, score=-1.93 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8aXdk2TrudcL for <endymail@ietfa.amsl.com>; Wed, 6 Apr 2016 04:41:06 -0700 (PDT)
Received: from spamfilter1.dtu.dk (spamfilter1.dtu.dk [130.225.73.112]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB71512D1B2 for <endymail@ietf.org>; Wed, 6 Apr 2016 04:41:05 -0700 (PDT)
Received: from ait-pexedg02.win.dtu.dk (ait-pexedg02.win.dtu.dk [192.38.82.192]) by spamfilter1.dtu.dk with ESMTP id u36BfFHi031503-u36BfFHk031503 (version=TLSv1.0 cipher=AES256-SHA bits=256 verify=CAFAIL); Wed, 6 Apr 2016 13:41:15 +0200
Received: from ait-pex02mbx06.win.dtu.dk (192.38.80.18) by ait-pexedg02.win.dtu.dk (192.38.82.192) with Microsoft SMTP Server (TLS) id 14.3.266.1; Wed, 6 Apr 2016 13:41:09 +0200
Received: from ait-pex01mbx01.win.dtu.dk ([169.254.1.158]) by ait-pex02mbx06.win.dtu.dk ([169.254.6.185]) with mapi id 14.03.0266.001; Wed, 6 Apr 2016 13:41:16 +0200
From: Hugo Maxwell Connery <hmco@env.dtu.dk>
To: aestetix <aestetix@aestetix.com>, Natanael <natanael.l@gmail.com>
Thread-Topic: [Endymail] [Cryptography] Secure universal message addressing
Thread-Index: AQHRjxruvTX09uLspEqOhQUlWhAAf598SeEAgACIl5E=
Date: Wed, 06 Apr 2016 11:41:15 +0000
Message-ID: <6CB05D82CE245B4083BBF3B97E2ED47016E56A15@ait-pex01mbx01.win.dtu.dk>
References: <CAAt2M1-AtpmREOi1Ex+sLjUqZtbcDOUC_zGd4u5Ot1cW+UT5ug@mail.gmail.com> <CAAt2M18W+k_bNL+WV1pa7dnbgzuThFqrqMcwVk5C20M-b_PrTg@mail.gmail.com> <CAAt2M19ThO-J3awEbKfx--mtpssB-Qk+5rHCcoBD57vytucvMw@mail.gmail.com> <CAAt2M19amebwCsdiNAqrBCD6OwGCUJCpKYkU7kvnRSafywTC=w@mail.gmail.com> <CAAt2M1-HOUjWLZOZycfcmGCgD+DkvsAOzjkd4bCuSjhSLVyDgw@mail.gmail.com> <CAAt2M1_C7OJZLZW7AnK1sYAK9ANpRS-FQ1__guKT7_Zacun+BA@mail.gmail.com> <CAAt2M19TiwGMmtsNyAWwaRk5Kup0for_AV0C=AFd--+kmUYcDw@mail.gmail.com> <CAAt2M19MWW-4CAoCejwYEZm-YzJ6UUWypeBtfPbWLh0ka=Ta8A@mail.gmail.com> <201604050717.u357HBfc014889@new.toad.com> <CAAt2M1-u0A5iROC3brGjMRReBj1fiBK1je_Kb4fU+TO7Y5n5MA@mail.gmail.com>, <20160406052601.GC6265@dan>
In-Reply-To: <20160406052601.GC6265@dan>
Accept-Language: en-AU, da-DK, en-US
Content-Language: en-AU
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.225.73.250]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/endymail/oRZ8D7NWqzNOWm0e5Nrs-0vv8xY>
X-Mailman-Approved-At: Wed, 06 Apr 2016 05:12:58 -0700
Cc: Cryptography Mailing List <cryptography@metzdowd.com>, Crypto List <cryptography@randombit.net>, John Gilmore <gnu@toad.com>, endymail <endymail@ietf.org>, messaging <messaging@moderncrypto.org>, Cryptographers List <crypto-practicum@lists.sonic.net>
Subject: Re: [Endymail] [Cryptography] Secure universal message addressing
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 11:41:08 -0000

A root (the person) uses multiple systems on which possibly 
multiple core identifiers are created and from each of those
potentially many *contact* identifiers are created and then 
associated with the communications service points to which the
person wishes them to be established.  

a.k.a: A tree: a person, with multiple devices, with multiple 
"core" identifiers yealding multiple end-point identifiers which 
are bound to selected communications services.

So long as the person gets to choose how one end-point identifier
leads to others, you're on the right track.  I suggest that as a 
minimum, no end-point identifier should every be able to be found
to lead to another which originates from a different "core"
identifier (traffic analysis and general op-sec notwithstanding).

/Hugo