Draft: draft-ietf-simple-iscomposing-02.txt
Reviewer: Joel Halpern
Date: 7/1/2004

This draft is basically ready for publication, but has nits that should be
fixed before publication.

There were a couple of things that bothered me, but as I write them down I 
conclude that they are not show stoppers.

Moderate Issues:

1) There is no textual description of the format of the message.  The 
document assumes that the reader will understand from the XML Schema that 
there is an outer wrapper of "isConposing" , that there is a mandatory 
element call "state", the specific name space to be used for this, and 
similar properties.  As this schema is very small, this is almost 
defensible.  But it seems to me that this is a bad practice.  (This is 
currently being debated on the SIMPLE list.  I am providing my opinion 
here.)  It would be better to simply include a bit of text about the 
structure of the XML message.  There is text about the optional elements, 
but none about the mandatory elements as XML

2) The document says that usage of this feature can be negotiated with 
SDP.  It is probably obvious to those very conversant with SDP, but it 
would be helpful to those who are less conversant to indicate which SDP 
element this is used with.  I would that this somehow goes on the m= 
line.  I am guessing that if I were more conversant with SDP I would know 
that it is okay to have multiple media lines with the same port number, etc.

Minor:
Given the discussion of SDP negotiation in the document, shouldn't there be 
a reference?  I think that would be a normative reference.