Re: Comment on DERIVE and B2BUAs

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

> -----Original Message-----
> From: Dean Willis [mailto:[email protected]] 
> Sent: 28 October 2008 22:32
> To: Elwell, John
> Cc: Victor Pascual Ávila; [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.
> 
> So the SBC's lack of transparency on tags, etc. is irrelevant.
[JRE] Then we would only achieve confirmation of identity on the first hop (or hop-by-hop, if each B2BUA did it), resulting in transitive trust - no better than PAI.

John

> 
> --
> 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
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.