Hi Martin, sorry to be late on this:
the hint within the draft is not to develop API within IETF, but to collaborate with W3C to exchange experiences and see what information would be interesting for them expose on their API.==Building an API: During Lisa's REST presentation yesterday, she noted that APIs aren't often done by the IETF. Aside from the fact that these were pretty hard, her thesis was that APIs tend to build tight coupling and that they constrain implementations. Based on this (and the fact that the W3C already does XMLHttpRequest) the API piece can be dropped.
o Possible improvements/extensions to XMLHttpRequest (XHR) API
[W3C.WD-XMLHttpRequest2-20090820] to expose connection-handling
details (e.g., use of pconns, pipelining, etc.)
/Sal
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.