Re: IETF and APIs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue Mar 29 12:28:55 2011, Eric Burger wrote:
Would we not be better off just asking (mandating?) at least one open source implementation? That effort would produce a de facto API.

Unfortunately this doesn't work in practise.

One of the examples that Sam raised originally concerned TLS, and that has (at least) three different open-source implementations in library form, all with fairly different APIs.

Some effort has been made to provide basic functionality in some libraries using an OpenSSL compatible layer, but given OpenSSL's API is only sparingly documented, I'm not sure of the utility.

Dave.
--
Dave Cridland - mailto:dave@xxxxxxxxxxxx - xmpp:dwd@xxxxxxxxxxxxxxxxx
 - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
 - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]