A B2BUA is proxying requests, but it is, strictly speaking a B2BUA and hence not a proxy. Confusing that an element that is proxying requests is not a proxy..... Which of course, begs the question -- if a B2BUA is not a dialog stateful proxy then what is a dialog stateful proxy? I guess I must conclude there's no such thing or at least that it is not necessarily a B2BUA.
Regards, Ranga. Ranga wrote: >Inline > >On 3/8/06, M. Rangnathan <[EMAIL PROTECTED]> wrote: > > >>The CDR example does not require that the proxy be dialog stateful - >>just call stateful. >> >> > > >Agreed > >Here's what I think : > > >>Dialog stateful proxy servers are useful for policy enforcement. For >>example : if you are proxying requests to an intranet you may want to >>establish a secure dialog state with a caller from the internet side of >>the firewall ( using tls). On the intranet side of the firewall, you can >>start another dialog with the Intranet client that is not secure (using >>UDP). You may want to do this because Dialog state may be sensitive ( >>ie. route sets to endpoints etc. ) that you may not want to make >>publicly visible outside the intranet. >> >> > > >This sounds to me more like an SBC or B2BUA or a Gateway but not a proxy. > > >/ Ranga V >_______________________________________________ >Sip-implementors mailing list >[email protected] >https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > -- M. Ranganathan Advanced Networking Technologies Division, National Institute of Standards and Technology (NIST), 100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/ Advanced Networking Technologies For the People! _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
