On 4/30/2014 8:20 AM, IAB Chair wrote:
We often see proposals for APIs (most commonly C APIs) discussed in
the IETF.
A protocol "API" isn't language-specific; it describes (or ought to) the
upper and lower layer interactions, e.g., as was done in RFC793.
When we propose an API in the IETF, it should be for that protocol API,
not for a language API (which is an instance, specific to a language and
also often an OS, of that protocol API).
(that doesn't preclude the benefit of a liason to a language-standards
group, but we shouldn't be seeing IETF proposals for such instances IMO).
Joe