Hi Ben,
thanks for your comments. Answers inline:
[Oops, sent to SIP by mistake. Resending to SIPPING. Sorry for the duplicate.]
Hi,
This draft looks mostly done to me--my comments are pretty trivial. (Or maybe I am just too tired to be picky right now :-) )
Section 2:
Any SIP server, be it a proxy, B2BUA (Back-to-Back User Agent), or some hybrid, that receives a request, translates its Request-URI into one or more next-hop URIs (i.e., recipient URIs), and delivers the request to those URIs.
(editorial) Partial paragraph? I think this is the definition of a "relay", but the term never appears.
Fixed.
5.1
The name of this event package is "pending-additions".
Since the use of this package is scoped to the consent-framework, could we have less generic package name? Maybe "pending-consent" or "consent-pending-additions"?
Now it uses "consent-pending-additions"
I have posted a working copy of the next revision of this document at:
http://users.piuha.net/gonzalo/temp/draft-ietf-sipping-pending-additions-01.txt
Cheers,
Gonzalo
_______________________________________________ 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