Draft:  draft-ietf-crisp-iris-xpc-05.txt
Reviewer: Black_David@emc.com
Review Date: Tuesday 1/23/2007 8:12 PM CST (updated Wednesday 1/24/2007 11:43 AM CST)
IESG Telechat Date: January 25th, 2007

Summary: Ready. 

Comments (1/24/2007):
I think the -05 version of the draft is ok as-is. 

Comments (1/23/2007):
The -05 version of this draft responds to the open issue identified
in the Gen-ART review of the -04 version - Section 14.1 contains
the information that RFC 4422 requires for proper use of SASL.

A couple of minor concerns in the review were not responded to:

> 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.

The first one's a matter of taste, and the second one should
be fine to omit, as it can be inferred from the registrations
by analogy to HTTP and HTTPS.

The -05 draft is ready for publication as a Proposed Standard RFC.