Re: [Sipping] I-D ACTION:draft-ietf-sipping-dialogusage-02.txt

[Paul Kyzivat <pkyzivat at cisco.com>]

Robert,

This is pretty much done I think.

Down to nits now:

In 1:

   Usages have state that is not shared in the dialog.  For example, a
   subscription has a duration.  Multiple subscriptions in the same
   dialog each have thier own duration.

True, but subscribe usages have more state than that. Also Event type 
and Event ID. (I guess the parameters on the event type are part of the 
type.) So perhaps the above should say:

   Usages have state that is not shared in the dialog.  For example, a
   subscription has a duration, event type, and event id.  Multiple
   subscriptions in the same dialog each have thier own duration, event
   type, and event id.

In description of 603 handling: Is the implication different if the 
request declined is one that would terminate the usage? Or in that case 
must one just wait for the usage to expire?

	Thanks,
	Paul

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP