IETF Logo Mail Archive

Re: [saag] IETF 93 Agenda Request - Key Discovery

Richard Barnes <rlb@ipv.sx> Thu, 23 July 2015 12:30 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ECEF1A90D5 for <saag@ietfa.amsl.com>; Thu, 23 Jul 2015 05:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 4sDzZdiFcB-l for <saag@ietfa.amsl.com>; Thu, 23 Jul 2015 05:30:36 -0700 (PDT)
Received: from mail-vn0-f47.google.com (mail-vn0-f47.google.com [209.85.216.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B10A1A8733 for <saag@ietf.org>; Thu, 23 Jul 2015 05:30:36 -0700 (PDT)
Received: by vnk197 with SMTP id 197so59671883vnk.3 for <saag@ietf.org>; Thu, 23 Jul 2015 05:30:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=lu3hp6CDkg+wpW2h8PddVk1SYdnjYzYaWtRpE/h5bkE=; b=KnppAMHkHb6vPMYOJLeOHqK1CMvuza7I9GS5+m+8hONCnGzD2k1eLsjC9OJm+hnHcV rPrRt24FgiOcH1tMhscTIsD3juSaVbSdFLq5q5pw/WN/iuZ3M+i/bmPzj+PN1gDBhgUc MVSH34Mt9ERFSDALlBgqL+H0KgBdnOVu3ythIUC2LkgseO8rQ/dduwCbLExWiX4G2FXk qLvs9WPfHVwqKX1J2RrKH7pNaIDaybBOTzHf+H7zhFcICIjl46fWobdrmREAroseMdrM BP8YAG/ufpsqhbW3dJ13ZYqhpiYr2nIhSePaS3iaLihMqYfDCNV2229SHl837PEkC4oR FyVw==
X-Gm-Message-State: ALoCoQl/SX7Aqpy3DD/t2iWRw/cgWvemDYqU3B/Di9roPwz+PbHtnu8GraZpnAI99sK+fisFAhFi
MIME-Version: 1.0
X-Received: by 10.52.31.10 with SMTP id w10mr9657458vdh.54.1437654635052; Thu, 23 Jul 2015 05:30:35 -0700 (PDT)
Received: by 10.31.164.207 with HTTP; Thu, 23 Jul 2015 05:30:34 -0700 (PDT)
In-Reply-To: <20150721231021.59110.qmail@ary.lan>
References: <20150721222308.GU28047@mournblade.imrryr.org> <20150721231021.59110.qmail@ary.lan>
Date: Thu, 23 Jul 2015 14:30:34 +0200
Message-ID: <CAL02cgQ3aTwpt43YYWSL-pEGcA5v1a10BskuA7-U1YN1Jk+G2w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/BMyvvCGwXOGoeflaw8SB6c8_Prc>
Cc: IETF SAAG <saag@ietf.org>
Subject: Re: [saag] IETF 93 Agenda Request - Key Discovery
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2015 12:30:38 -0000

On Wed, Jul 22, 2015 at 1:10 AM, John Levine <johnl@taugh.com> wrote:
>>I've just glanced at
>>
>>    https://tools.ietf.org/html/draft-moore-email-addrquery-01
>>
>>I think it is a more promising effort in the intended direction.
>
> Agreed.  It distributes mail information through mail servers, rather
> than hoping one can keep mail servers and web servers synchronized.
>
> It's not perfect but the problems are fixable.

I'm kind of astonished that people still think that extending email
protocols is a good idea for things like this.  For example:

"BASE64 is used to avoid the need for the server to produce JSON text
which conforms to SMTP line-length restrictions."

Why, in 2015, would we continue to choose modalities that come with
these arcane restrictions?

Let's use modern technology for this.  What's needed here is
request/response protocol that can carry JSON, not a store-and-forward
protocol that carries an oddly constrained text format.  WebFinger
seems fine.

--Richard


>
> R's,
> John
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag

v2.23.0 | Report a Bug | By Email