> > How are you going to do this when you don’t know what applies to connection > opening, connection maintenance, data transfer? What kinds of error messages > are available? We need that of course but I don’t see now any list of what are the common features between all transports (to start with) and then how to discover the rest :-) > I think it’s a much more obvious step from draft-welzl-taps-transports to a > generic TAPS API than from draft-ietf-taps-transports, and that’s the whole > point. draft-ietf-taps-transports is a nice survey but it doesn’t really help > you much for creating an API, I think. I did not suggest abandoning it. Just making sure it does focus on what is needed. > > Cheers, > Michael >
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
