On 6/5/2015 5:11 AM, Helge Backhaus wrote: > Am 04.06.2015 um 23:20 schrieb Joe Touch: ... >> There are many services built on top of HTTP, at which point HTTP is just >> another part of what this document calls a "transport service". >> >> As a result, unless you'll be describing every possible stack between the >> user program and the link layer, > > Shouldn't this ideally be the (long-term) goal of TAPS?
This would require an exponential number of service descriptions. IMO, it's better to describe them as a linear number of composable components and declare the composition rules. (that's not novel; that's what we do throughout the IETF) >> this document cannot proceed with the current definitions. > > So could a possible way forward be to leave the definitions as they are > and add a description of the considered stack(s) to the document? For > now "just" TCP, UDP, SCTP, ... over IPv4/6 etc. If you ignore the deficiency of the definitions, then it's impossible to move together on the remainder of the doc. Joe _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
