Hi, as time did not permit to discuss all open issues in the session today, I’ll take them to the list as proposed. This issue is based on Github issue #305: https://github.com/ietf-tapswg/api-drafts/issues/305
Following the architecture draft, only protocol stacks that are equivalent can be safely raced. What should happen if selection properties result in a candidate set that includes protocol stacks that are not intuitively equivalent? Resolution Proposals: a) Define Protocol Stack Equivalence more rigorously. A possible way to do this would be to say two stacks are equivalent with respect to the applications’ requirements if both fulfil all require properties specified by the applications and do not violate any of the prohibit properties. b) Generate some kind of Error Event for configurations with unlike protocol stack candidates. (May need a definition of "unlike”). c) Do nothing and close the issue. AVE! Philipp S. Tiesel -- Philipp S. Tiesel https://philipp.tiesel.net/ _______________________________________________ Taps mailing list Taps@ietf.org https://www.ietf.org/mailman/listinfo/taps
