search

SpencerDawkins / net-collab-rqmts

Other
1 stars 0 forks source link

API #26

Closed danwing closed 3 weeks ago

danwing commented 1 month ago

Along the lines of SCONE's API, do we want to say anything about the API needs?

I noticed their API document conflates a single API with "receiving data over the QUIC flow", which of course isn't necessary considering that ICMP errors are sent to (connected) UDP sockets, and those are different flows. So, there could be a single API which does all your QUIC things and, under the covers, does a separate signaling channel with the ISP(s) router(s), exposing the information to the application without the application needing to do heavy lifting. We might call that a 'library' or I suppose in 2024 we would have to call that a 'framework' or 'wrapper' or some-such.

boucadair commented 1 month ago

This can be mentioned as part of a new OPS section, e.g., "Exposure Handling".

The local exposure (OS API) can be mentioned, e.g., next to REQ-SIGNAL-EXPOSURE-FAIRNESS in #25.

sridharangirish91 commented 4 weeks ago

I thought this would be more of a metadata specific aspect but we could list the "framework" as a requirement in the signaling. In that case, do we need to have API(s) for the client/host to network signaling as well? Include that in the framework as well?