I'm copying Adam because he was author of 3265, and Robert because of
his work on the dialog usage draft.
Comments inline.
Paul
Jeroen van Bemmel wrote:
Paul,
Are you sure?
Well, I *thought* I was sure.
A thread some time ago
(http://lists.cs.columbia.edu/pipermail/sip-implementors/2002-November/004066.html)
says they're not, quoting issues with shared dialog usages
I was part of that thread. But I don't remember that part of it. (Maybe
I suppressed the memory.)
I reviewed both 3261 and 3265 on this point. 3261 does say that the only
target refresh request it defines is INVITE, and that others may be
defined. (Though it doesn't say *how* they are to be defined. There is
no table, no IANA registry, no procedures of any kind.) And 3265 says
nothing about target refresh, positive or negative.
It had been my assumption (obviously unsupported by text) that if a
request can define the initial target of a dialog, and if it may also be
used within an established dialog, then it should be treated as a target
refresh request.
Perhaps the interpretation should be that there is a contact per dialog
usage?
No, no, no. 3261 is very clear that the target belongs to the dialog,
not the dialog usage. There is no way that having separate ones could work.
Paul
Jeroen
Suganthi Chinnappan - NPD, Chennai wrote:
Hi All,
In RFC 3261,it is clearly mentioned that " For dialogs that have
been
established with an INVITE, the only target refresh request defined is
re-INVITE ".Similarly,for SUBSCRIBE created dialogs,What will be the the
Target refresh Request?
(re)SUBSCRIBE and NOTIFY are target refresh requests.
Paul
Thanks,
Suganthi
Disclaimer:
This message and any attachment(s) contained here are information
that is confidential, proprietary to HCL Technologies and its
customers, privileged or otherwise protected by law. The information
is solely intended for the individual or the entity it is addressed
to. If you are not the intended recipient of this message, you are
not authorized to read, forward, print, retain, copy or disseminate
this message or any part of it. If you have received this e-mail in
error, please notify the sender immediately by return e-mail and
delete it from your computer.
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
