Document: draft-ietf-tcpm-tcp-ao-crypto-02
Reviewer: Avshalom Houri
Review Date: 2010-03-09
IETF LC date: 2010-03-10
IESG Telechat date: 2010-03-11

Summary: The draft is ready for a standard track RFC (see minor issues 
and nits).
The document is a reasonable basis on which to build the salient part of 
the Internet infrastructure.

Major issues: None

Minor issues:

Line 211
   This is the initial specification of required cryptography for

Why it is initial? Initial RFC?

Lines 232-238
I do not see the requirements only MUSTs.

Line 260
   "MUST" to implement, in order to drive vendors toward its use, and to

Should the IETF include something as a must in order to drive its 
implementation?

Line 862:
   above.  We simply attempted to "put a fence around stupidity", in as

Maybe change the language for the RFC?


Nits/editorial comments:

Line 182
   verification between to end-points.  In order to accomplish this
->    verification between two end-points.  In order to accomplish this


Line 384
                   starts = 1.

-> starts at 1.