IETF Logo Mail Archive

Re: [Uta] smtp-sts-04 JSON

Viktor Dukhovni <ietf-dane@dukhovni.org> Sun, 23 April 2017 02:58 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 C24C2126B6D for <uta@ietfa.amsl.com>; Sat, 22 Apr 2017 19:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 RNoDcBO8IFlT for <uta@ietfa.amsl.com>; Sat, 22 Apr 2017 19:58:27 -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 5B75A1294D4 for <uta@ietf.org>; Sat, 22 Apr 2017 19:58:27 -0700 (PDT)
Received: from [192.168.0.2] (cpe-67-241-70-168.twcny.res.rr.com [67.241.70.168]) (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 94AB27A32F1 for <uta@ietf.org>; Sun, 23 Apr 2017 02:58:26 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CANtKdUevHbQaUga2=X0tFy4K=po=DL=pKUn-2KZQgRUPTtYAig@mail.gmail.com>
Date: Sat, 22 Apr 2017 22:58:25 -0400
Content-Transfer-Encoding: 7bit
Reply-To: uta@ietf.org
Message-Id: <DE3A2AC6-63C0-4C17-9D9E-BF9CB2B3A289@dukhovni.org>
References: <52dde16a-a3bb-5844-7daa-a349def85049@wizmail.org> <80676A32-78CB-4FFA-AEE4-94DA95102B98@dukhovni.org> <a2a6e5f5-ff3b-272b-abda-b49fe23a485d@wizmail.org> <605FE793-3D82-4C4F-9F93-D50DF4320DF5@dukhovni.org> <9402ac0a4990432f994656ddaf94b9e2@COPDCEX19.cable.comcast.com> <CE55E42E-9845-46A6-B0AA-F56CE56F2936@dukhovni.org> <CANtKdUevHbQaUga2=X0tFy4K=po=DL=pKUn-2KZQgRUPTtYAig@mail.gmail.com>
To: uta@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/Vwgi3eZYqYfgHXTg5rDDgaHUk90>
Subject: Re: [Uta] smtp-sts-04 JSON
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: Sun, 23 Apr 2017 02:58:29 -0000

> On Apr 22, 2017, at 1:35 PM, Daniel Margolis <dmargolis@google.com> wrote:
> 
> That does not jive with relatively easy to parse...
> 
> JSON supports comments, elements that are integers, strings,
> arrays or associative arrays (nested JSON objects).  JSON
> strings are UTF-8 and allow embedded NUL octets.
> 
> Your JSON reference is to the obsolete RFC4627, the non-obsolete
> reference is RFC7159.

So any compelling arguments for JSON from MTA implementors?

A much simpler format would be a block of lines (CRLF terminated),
with each line either a boolean propery name, or a name value pair.

	version STSv1
	mode report
	max_age 8640000
	mx mx1.example.com
	mx mx2.example.com
	...

Line length is limited to the usual 1000 bytes including the
terminating CRLF.

This simplifies parsing, because a simple line-orienter parser
can now process the entire policy.  It is no longer possible
to have multiple policies, as with JSON, because there is no
way to express multiple objects.  The JSON format is much
too general for the needs at hand.

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email