Draft:  draft-ietf-sipping-session-policy-framework-01
Reviewer: Roni Even
Review Date: 15/8/06
Review Deadline: 25/8/06
Status: Initial review 

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

The document looks good and being asked a lot about bandwidth management in SIP I find it very important.

I have a question:

In the session specific policy call flows the UA that send the invite insert a header field (Policy-Id) indicating to the proxy that it contacted the Policy server. How does the proxy on the other side know that the UA contacted the policy server when it gets the 200 with the answer.

A nit

Introduction section - says "In contrast to other methods for inserting a media intermediary, the use of session policies does not require the inspection or modification of SIP message bodies".  Looking at section 4.3.1 for example shows that at least the two proxies PA and PB will change the SIP message.  I also assume that policy enforcement will require inspection of the messages.