Subject: [Sipping] Review of draft-ietf-sipping-policy-package-03

From: "Even, Roni" <[email-masked]>
Date: Wed, 30 May 2007 17:11:00 +0300

Hi,

The draft is basically ready for publication. I have one clarification question and nits

In section 3.8 " For example, if the session was rejected due to a temporary shortage of resources and the notifier expects that these resources will become available again shortly it should keep the subscription alive"

How does the notifier keep the session alive what is sent in the notify body, is it an empty body?

Nits

1.    In the document you mention "session-policy+xml" as defined in the data set draft, I think it should be 

"media-policy-dataset+xml". This text appears in a couple of places starting in 3.3

2.    In section 4.  "Authenticating the two parties can performed using X.509" to "Authenticating the two parties can be performed using X.509".

Roni Even

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP