APIs are not that useful unless there is code behind them. Are you proposing code that goes with those APIs? Also the language that you do this in is important depending on the area of applicability. For instance, if these APIs are related to modern applications, C is all but useless because its not used to build most of those; you need Java/python/etc... for these cases. --Tom > 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 > >
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail