IETF Logo Mail Archive

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

🔓Dan Wing <dwing@cisco.com> Thu, 23 July 2015 12:51 UTC

Return-Path: <dwing@cisco.com>
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 C3F231AC435 for <saag@ietfa.amsl.com>; Thu, 23 Jul 2015 05:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level:
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 OdcUHKC2HLQs for <saag@ietfa.amsl.com>; Thu, 23 Jul 2015 05:51:44 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F9C31A0155 for <saag@ietf.org>; Thu, 23 Jul 2015 05:50:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1470; q=dns/txt; s=iport; t=1437655834; x=1438865434; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=b8961kL6hbvQu/IIRk9yisatsWhHQ0l1N4eXABWdqno=; b=P60yur0OgRNIYnJarauKzNd2vmslSFHRHTc9Fhb9wexPhq8APjLiqE5f /SV9tP29QBFKbeCNJfnCJMzMXswj32I0vH+ktOuTEeV8JmJxRgb4Yfgkg sY4zxYZHDath8+CQY2MwE/C18HPSN++4lwtJLpdYQoSCeYODfoh2rY0Mk E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BICwDk4bBV/5tdJa1bgxVUabtgCYFrCoYBAoFIOBQBAQEBAQEBgQpBAoNhAQEEAQEBNy0HCxALDgouJzAGE4guDcshAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSLTIQjEAIBBUsHgxiBFAEElGCEdodEiE+FfIpQJmODGzwxgksBAQE
X-IronPort-AV: E=Sophos;i="5.15,530,1432598400"; d="scan'208";a="14268316"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP; 23 Jul 2015 12:50:33 +0000
Received: from [10.24.241.169] ([10.24.241.169]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t6NCoUar025161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Jul 2015 12:50:33 GMT
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: 🔓Dan Wing <dwing@cisco.com>
In-Reply-To: <CAL02cgQ3aTwpt43YYWSL-pEGcA5v1a10BskuA7-U1YN1Jk+G2w@mail.gmail.com>
Date: Thu, 23 Jul 2015 14:50:29 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <193AA5CF-878F-4075-8A71-EDCA9D04DAED@cisco.com>
References: <20150721222308.GU28047@mournblade.imrryr.org> <20150721231021.59110.qmail@ary.lan> <CAL02cgQ3aTwpt43YYWSL-pEGcA5v1a10BskuA7-U1YN1Jk+G2w@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/5PI6GxcRUv0UGkvMTlETvCvcPqo>
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:51:50 -0000

On 23-Jul-2015 02:30 pm, Richard Barnes <rlb@ipv.sx> wrote:
> 
> 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.

+1.

-d


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

v2.23.0 | Report a Bug | By Email