Document: draft-ietf-sipping-update-pai-01
Reviewer: Francois Audet
Review Date: 4/25/2008
Review Due: 5/12/2008
Review Type: Initial WG review

Summary: Almost ready; nits/procedural issue

Comments:
----------

I have no major issues with draft. Well written, and understandable.


Nits:

- Sections 3.1-3.6. Each one of those sections should conclude with a statement
  that "This draft allows for P-Asserted-ID to be included in....", as appropriate.
  That will make it easier to understand what is proposed, without having to jump
  ahead to section 4.

- Section 3.1 should clarify that RFC 3265 doesn't preclude a UAC inserting P-Asserted-ID
  either: it just doesn't describe it. Furthermore, the section should point out that
  UAC inserting P-Asserted-ID is widely used.


Procedural issue:

- This document does an excellent job at explaining how to clarify and expand RFC 3325.
  However, why don't we just obsolete RFC 3325 entirely and replace it with a document
  that has everything self-contained (i.e., rfc3325-bis)? I think it would be much
  easier for developppers.