Draft:  draft-ietf-crisp-iris-xpc-04.txt
Reviewer: Black_David@emc.com
Review Date: Thursday 8/24/2006 3:27 PM CST
IETF LC Date: 8/28/2006

Summary: This draft is on the right track but has open issues,
described in the review.

I found one open issue - Section 14's discussion of the use
of SASL is incomplete, as it does not satisfy the requirements
stated in Section 4 of RFC 4422.  See Section 4 of RFC 4422.

I also found a few minor concerns/nits:

Sections 5 and 6 ought to contain ASCII diagrams of the
bit fields in the Block Header and Chunk Descriptor.

The discussion of chunk ordering in Section 6 on p.9
combines restrictions on which chunk types may co-exist
in a single block with requirements on ordering of those
types within a block.  The combined discussion is somewhat
confusing - it would be clearer if these two topics were
separated - specify what is allowed within a single block,
then specify ordering requirements for what is allowed.

Section 9 should state how the client and server determine
whether TLS is to be used.  Since well-known ports are
registered for both XPC and XPCS, this appears to be
determined by client selection of which server port to use.