IETF Logo Mail Archive

Re: [Uta] MTA-STS-03 review

Viktor Dukhovni <ietf-dane@dukhovni.org> Mon, 27 March 2017 01:01 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEFDD128896 for <uta@ietfa.amsl.com>; Sun, 26 Mar 2017 18:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] 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 Orp18NSYtdzl for <uta@ietfa.amsl.com>; Sun, 26 Mar 2017 18:01:38 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2138E12878D for <uta@ietf.org>; Sun, 26 Mar 2017 18:01:38 -0700 (PDT)
Received: from vpro.lan (cpe-98-14-133-144.nyc.res.rr.com [98.14.133.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 5594C7A32F1 for <uta@ietf.org>; Mon, 27 Mar 2017 01:01:37 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <20170326205218.GN11426@blitiri.com.ar>
Date: Sun, 26 Mar 2017 21:01:36 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: uta@ietf.org
Message-Id: <92500952-2A50-4508-8686-03CDBF72485D@dukhovni.org>
References: <4C0807DA-4852-4DAC-80ED-8A25371CFFAA@dukhovni.org> <CANtKdUfOZYSr_SuGHdDHHgrF8J5VjEWwVw_7KC2xS5DrCKhu-w@mail.gmail.com> <20170326205218.GN11426@blitiri.com.ar>
To: uta@ietf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/WX1LNBS5KQsf2PWzgUkhkyVcoX8>
Subject: Re: [Uta] MTA-STS-03 review
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2017 01:01:40 -0000

> On Mar 26, 2017, at 4:52 PM, Alberto Bertogli <albertito@blitiri.com.ar> wrote:
> 
> There are lots of advantages of using JSON for this. It is well defined,
> standard and there are lots of well tested and widely used
> implementations.
> 
> It is used widely, it's familiar to many people, and its shortcomings
> (which are not few, admittedly) are well understood and documented.

Sure JSON is used widely in all kinds of software, but NOT in MTAs,
and STS is for MTAs.

> It support rich types (such as lists), and common libraries already
> handle difficult situations like non-ascii content, long integers,
> multi-line strings, malformed/malicious input, etc.

Sure in Perl, Python, Go, ... but Sendmail, Qmail, Postfix and Exim
are in C, and already have code to handle ESMTP attr=value lists, and
don't currently use JSON.  The extra features of JSON you mention are
not needed for this specification, and over-engineering to use JSON
is IMHO not useful.

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email