Draft: draft-ietf-opes-http-02
Reviewer: Lucy E. Lynch
Date: 8 July 2004

no major objections

This draft is well written, and the "OPES Document Map" section was
very helpful (as was appendix B: change log, although I assume this
will get dropped in a final doc).

NITS:

- idnits 1.31 (30 May 2004) draft-ietf-opes-http-02.txt

  Checking conformance with RFC 2026 boilerplate...
  There are 1 instances of lines with non-ascii characters in the
  document.
  There are 185 instances of lines with control characters in the
  document.

- I found the use of "iana.org" in the http examples a bit confusing
(I'd use something generic like somedomain.tld) and I'll just note that
the rfcdiff tool thought these were "real" urls.

- I wonder about the security section - are there truely no http based
threats that might deserve a mention here?

- I also find no section for IANA considerations.