Document: draft-ietf-sipping-pending-additions-03.txt
Reviewer: David L. Black
Review Date: 10 December 2007
IETF LC End Date: 20 December 2007

Summary:

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

Comments: 

I found open issues in Sections 5.1.2 and 5.1.7:

5.1.2.  SUBSCRIBE Bodies

   A SUBSCRIBE for Pending Additions events MAY contain a body.  This
   body would serve the purpose of filtering the subscription.  The
   definition of such a body is outside the scope of this specification.

How is that supposed to be interoperable?  A better approach would be to prohibit bodies now and allow a future specification to define them.

5.1.7.  Subscriber Processing of NOTIFY Requests

   NOTIFY requests contain full state.  The subscriber does not need to
   perform any type of information aggregation.

This text doesn't explain "the process followed by the subscriber upon receipt of a NOTIFY request, including any logic required to form a coherent resource state (if applicable)" (see Section 4.4.8 of RFC 3265).  This text needs to be rewritten and expanded.

---

idnits 2.05.03 found three small nits

  == Line 467 has weird spacing: '... Change  in XM...'

  == Outdated reference: A later version (-07) exists of
     draft-ietf-simple-xcap-diff-05

  == Outdated reference: A later version (-03) exists of
     draft-ietf-sip-consent-framework-01