1. Summary
The document shepherd is Michael Scharf <michael.scharf@hs-esslingen.de>.
The responsible Area Director is Martin Duke <martin.h.duke@gmail.com>.
This document provides test vectors to validate implementations of the TCP
Authentication Option (TCP-AO) over both IPv4 and IPv6. With the test vectors
multiple TCP-AO implementations can be validated against each other to ensure
interoperability.
The TCPM working group requests publication as Informational RFC, as indicated
on the title page.
2. Review and Consensus
This document has been reviewed by several contributors in the TCPM working
group and is considered ready for publication. The WGLC has passed successfully
without any comments.
As TCP-AO is in particular relevant for routers, the document is only of
interest to a small subset of the TCPM working group. As a result, there has
been less working group discussion than for other documents. Nonetheless, there
has always been strong consensus in TCPM that documenting test vectors is
useful for those implementers that need TCP-AO. And there has never been any
controversy regarding the content of this informational document.
Tests with several different closed source TCP-AO implementations have been
reported by the authors. This should ensure that the test vectors are indeed
correct.
There have also been recent announcements of further planned TCP-AO
implementations, including open source code. As a result, the publication of
test vectors is very timely work.
3. Intellectual Property
Each author has stated that their direct, personal knowledge of any IPR related
to this document has already been disclosed, in conformance with BCPs 78 and 79.
There are no IPR disclosures.
4. Other Points
Idnits reports that private range IPv4 addresses are used instead of
documentation addresses according to RFC 6890. Yet, this seems appropriate as
actual TCP-AO validation tests would typically indeed use private addresses.