Comment on draft-roach-sipcore-rfc3265bis-00

"Elwell, John" <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <0D5F89FAC29E2C41B98A6A762007F5D001AAD8F3@GBNTHT12009MSX.gb002.siemens.net>
Adam,

Thanks for producing this draft, which should set a good example for
revisions of the other SIPCORE RFCs.

I found little to comment on, apart from the following:

In 4.5.1:
"Notifiers MUST implement the GRUU extension defined in
   [I-D.ietf-sip-gruu], and MUST use a GRUU as their local target."

1. Is this just for a SUBSCRIBE-initiated dialog or for any dialog?

2. Should this be package-dependent? For example, there may be some
event packages for which there is no need for subscribing to a resource
on the same device.

3. What if the registrar doesn't support GRUU, and therefore the
notifier is unable to obtain a GRUU?

And by the way, in appendix C I didn't see a mention of changes relating
to the use of GRUU.

John
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.