Hi all,+1 for the K/V solution. Adding JSON dependencies does not seem a good idea to me too :-)
Cheers, Max On 7/22/17 9:53 AM, Viktor Dukhovni wrote:
On Fri, Jul 21, 2017 at 12:59:51PM +0100, Jeremy Harris wrote:I would prefer to have more opinions (implementors in particular) butThere's no way I would add JSON support to exim.On Fri, Jul 21, 2017 at 04:50:46AM -0700, Claus Assmann wrote:There's no way I would add JSON support to sendmail.I'll chime in with no plans to add a JSON dependency to Postfix. The current KV proposal is fine. I would have avoided the superfluous ":" characters after the keys: mx foo.example.com rather than: mx: foo.example.com but I don't care enough to make this an issue. The authors are free to drop the unnecessary ":" if they agree. The K/V would then be a sequence of lines, with one K/V per line, with each line of the form: <KEY><whitespace><VALUE><optional trailing whitespace><EOL> <EOL> is whatever goes for EOL in HTTP text/plain content types, which IIRC is <CRLF>. Client implementations MAY be liberal and also allow <LF>, but server implementations SHOULD only use <CRLF>.
-- Best Regards, Massimiliano Pala, Ph.D. OpenCA Labs Director OpenCA Logo
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
