> On Apr 25, 2017, at 12:21 AM, Binu Ramakrishnan <[email protected]> wrote:
>
> 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?
That should be sufficient. We should use the simplest thing that does
the job and no simpler. Key-value fits the bill.
> Wondering why IETF doesn't have a RFC doc for kv pair syntax.
There's no reason for an RFC to describe trivial lists of pairs.
In ESMTP some of the values are xtext encoded, because the context
is restricted to US-ASCII and does not permit whitespace in the
values.
Here, if we emit one KV pair per line, there's no need for xtext.
The simplest design (perhaps either LF or CRLF terminated) is to
one line per item of multi-valued attributes like "mx". That way,
there's no need to parse internal delimiters in a value list.
version STSv1
...
mx smtp1.example.com
mx smtp2.example.com
...
--
Viktor.
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
