Closed rsgmodelworks closed 2 years ago
there have been mailing list feedback comments, check back later for input to this discussion.
it may be the case the COM report is not detected properly. Multiple PD implementations reporting issues. Plan is to change the code so it does the COMSET and then (does something maybe a delay) so as to really really make sure we waited for an answer.
current code supports comset/com testing. multiple tools now available test comset/com combinations. retry behavior and how it relates to COMSET is not an entirely addressed question, opening a replacement issue on that.
comset should be there. com report is the response, not nak, per committee dialog. if com doesn't come back, proper retry logic should resend the comset. that being said, a conservative CP implementation may well "give up and switch anyway". I intend to invoke the "be conservative in what you except" rule and add "give up and switch anway" logic. Need to add proper retry. need to instrument tester to capture this behavior for conformance testing. This is intended to more accurately conform with the commitee consensus. change planned for 0.2-build-1 i.e. post-isc build of libosdp-conformance.