On 5/28/2015 11:05 AM, Mirja Kühlewind wrote: > Hi Joe, > > here is where the confusion comes from: this doc is not about APIs, > it’s about transport services, or to say it even more concrete, > transport services components and features.
Such services are either inherent to the transport (e.g., in-order, reliable delivery) or exposed as a control to the user (by the API). I.e., APIs are necessary but not sufficient to describe transport services. > We do have a section on > interfaces for each protocol but that just an add-on which might or > might not be useful to have in this document, but the core of the > document is to describe the components that are currently implemented > independent of the current provided (app-layer) interface and then add > some discuss of which of these components are useful to expose to the > app as transport services feature (and which level of detail/degree of > decision freedom for each feature). But then isn't it critical to also know what's already exposed, e.g., in the existing API? Joe _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
