Re: [perpass] perpass: what next?

"John Levine" <johnl@taugh.com> Sun, 19 April 2015 03:26 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C26A1A883F for <perpass@ietfa.amsl.com>; Sat, 18 Apr 2015 20:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 d8B8RuJQnJV1 for <perpass@ietfa.amsl.com>; Sat, 18 Apr 2015 20:26:33 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65B201A883C for <perpass@ietf.org>; Sat, 18 Apr 2015 20:26:33 -0700 (PDT)
Received: (qmail 84135 invoked from network); 19 Apr 2015 03:26:32 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 19 Apr 2015 03:26:32 -0000
Date: Sun, 19 Apr 2015 03:26:10 -0000
Message-ID: <20150419032610.1333.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: perpass@ietf.org
In-Reply-To: <CACsn0cn7sY8MFCumUknXfqPWqELUtLdyh55Z=av-0NSbMb3xYw@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/5LJNCl-LA85WXO9yJJudKJh_BzM>
Cc: watsonbladd@gmail.com
Subject: Re: [perpass] perpass: what next?
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Apr 2015 03:26:34 -0000

>-Key discovery in email has been kicked around a bunch, but no
>reasonable proposals yet. Doesn't seem that hard.

There's a draft in DANE which I think is fatally flawed for reasons
that boil down to DNS lookups are utterly unlike mailbox lookups.  

I agree it's not that hard.  Something like webfinger with the http
server found via SRV should work.

R's,
John