As an engineer I agree with you and would be hesitant to add additional
dependencies to my software. But when we talk about IETF and standards, is it
not better to promote widely accepted syntax/format?
Wondering why IETF doesn't have a RFC doc for kv pair syntax.
thanks-binu
From: Viktor Dukhovni <[email protected]>
To: [email protected]
Sent: Monday, 24 April 2017 3:49 PM
Subject: Re: [Uta] smtp-sts-04 JSON
> On Apr 24, 2017, at 6:34 PM, Binu Ramakrishnan <[email protected]> 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.
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
