Hi,
On Jan 22, 2012, at 11:26 PM, Warren Kumari wrote:
> Comments:
> It is unclear (to me) what exactly was mean by "YES" vs "UNIT TEST" vs "SYS
> TEST" -- I could make some guesses, but a definition would be nice.
Speaking for my contribution; the one that mentions "Unit Test":
Our 'production' implementation is just the validator, so the cache that is the
server side of the protocol. It is tested using automated unit and functional
testing as well as interop-testing with different client implementations.
We also have test client code that we use for the unit tests. This client is
able to parse and understand PDUs in the table in section 3, but it's not
released as a real production stand-alone, interop-tested, client. Hence I say
"Unit Test". I can live with "Not Applicable" or N/A instead though.
I thought it might be useful to mention "unit test", because fwiw we don't see
problems in the PDU format for these 'client' PDUs.
Tim
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr
