[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sip] Comment on DERIVE and B2BUAs



2008/10/28 Elwell, John <john.elwell at siemens.com>:
> Viktor,
>
> An interesting draft addressing a known problem space. Dan Wing has already pointed out similarities with draft-wing-sip-e164-rrc (now expired). I fear the present draft will not work in the presence of B2BUAs along the path of the INVITE request, since these tend to change things like call-ID, to-tag and from-tag. Since B2BUAs, and SBCs in particular, are the main reasons why RFC 4474 will not work, any solution has to be able to work through these devices.

Since the B2BUA has detailed info of both legs A and B, it is capable
of doing needed changes, as replacing call-id and to-tag in Event
header.
Also, the B2BUA could handle the SUBSCRIBE by its own, this is,
becoming a dialog presence server instead of forwarding the SUBSCRIBE
to the UA.
B2BUA must handle all this stuff since they are, in fact, the end
point, not the UA's behind them.


-- 
Iñaki Baz Castillo
<ibc at aliax.net>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip