Draft: draft-ietf-sipping-cc-conferencing-07 
Reviewer: Elwyn Davies [elwynd@dial.pipex.com]
Date: Monday 6/6/2005 2:34 AM CST

Summary: Ready.

Follow-up comments:

I commented on the update already... in the meantime the BCP stuff has 
been discussed, and it appears that we are happy to publish this sort of 
things.

Review comments (from 6/6/2005):
A snapshot of a proposed v07 of the draft is now available at
http://ee.wustl.edu/~alan/draft-ietf-sipping-cc-conferencing-07.txt

This is, IMO, a considerable improvement and answers all my comments, 
except the fundamental one: *Is it a BCP?*  I note that the conference 
notify package example has been made consistent with the conference 
package draft.

One nit (relevant to Brian's IESG comment): RFC2119 is now mentioned and 
appears in the refs list but there is no reference to it in s2.

Regards,
Elwyn

Previous message:

I reviewed this document for IETF LC and corresponded with the author on
some changes that addressed most of my comments.  The author is
currently in discussion with Allison about how to instantiate the
changes (new version or RFC Editor notes).

Assuming the changes that were discussed are implemented, the one
remaining concern which I raised was punted to Allison.  That one is
whether the document is really a BCP or actually a 'standard' for the
tightly coupled SIP conferencing application masquerading as a BCP.

My main reasons for doubting whether it is really a BCP is that it is
not couched as recommendations and contains no discussion of
alternatives, but rather gives 'examples' of how to do conferencing
through a single focus with basic SIP commands using a single 'feature
parameter'.

I'll send an update if and when the RFC Editor notes or a new draft
appear.  Otherwise Allison needs to justify why this is a BCP, and if
not, the document status needs to be considered.

Regards,
Elwyn