Re: Comment on DERIVE and B2BUAs

 

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Dean Willis
> Sent: Tuesday, October 28, 2008 3:32 PM
> To: Elwell, John
> Cc: [email protected]
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> 
> Elwell, John wrote:
> > 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.
> > 
> 
> Would the SBC not have to handle the SUBSCRIBE request locally? After
> all, since it is a terminal UA for the call, it also knows 
> about all the
> dialog states. The end-user UA would never even see the SUBSCRIBE.

If that's a problem, just use some different method that goes end to
end.  The always-loved INFO comes to mind.

-d

> So the SBC's lack of transparency on tags, etc. is irrelevant.
> 
> --
> Dean
> _______________________________________________
> 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

_______________________________________________
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