Re: [Uta] smtp-sts-04 JSON

Viktor Dukhovni <ietf-dane@dukhovni.org> Mon, 24 April 2017 22:49 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 EF177131838 for <uta@ietfa.amsl.com>; Mon, 24 Apr 2017 15:49:39 -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 t3JADgAAq_Ha for <uta@ietfa.amsl.com>; Mon, 24 Apr 2017 15:49: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 66127131952 for <uta@ietf.org>; Mon, 24 Apr 2017 15:49:38 -0700 (PDT)
Received: from [172.31.31.193] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (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 6A4817A32F1 for <uta@ietf.org>; Mon, 24 Apr 2017 22:49: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.3 \(3273\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <907547420.8067868.1493073246224@mail.yahoo.com>
Date: Mon, 24 Apr 2017 18:49:36 -0400
Content-Transfer-Encoding: 7bit
Reply-To: uta@ietf.org
Message-Id: <271D533C-7C48-438C-8BBE-0EEC0DFB92DF@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> <DE3A2AC6-63C0-4C17-9D9E-BF9CB2B3A289@dukhovni.org> <CANtKdUer3CSruZRf-mXp+yvMKY_kCTaQ1vyZGVenNgVf5a9T2g@mail.gmail.com> <907547420.8067868.1493073246224@mail.yahoo.com>
To: uta@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/xvRlNaZvhG4X7PGdNwFMLZxmq8Q>
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: Mon, 24 Apr 2017 22:49:40 -0000

> On Apr 24, 2017, at 6:34 PM, Binu Ramakrishnan <prbinu@yahoo.com> wrote:
> 
> IMO the main hurdle with key-value format is that we do not have a standard
> format, and by extension off-the-shelf library support. So the question is
> - whether to write custom kv parsers or use a standard format - JSON.

SMTP MTAs already parse key-value pairs in EHLO responses, and ESMTP
extensions to the MAIL FROM and RCPT TO commands.  No additional code
is required to do similar parsing of the policy in question.

JSON is not a standard "format" it is a general syntax, that can 
represent a stream of composite objects.  This is a poor fit in
terms of the libraries needed to support JSON and having to deal
with attributes that hold the wrong kind of data (list instead
of scalar) or multiple objects instead of one...

-- 
	Viktor.