Comments regarding scalability issues with STUN/TURN/etc...
"Christopher A. Martin" <[email protected]>
| Newsgroups | gmane.ietf.midcom |
|---|---|
| Organization | SIP1 Information Services |
| Message-ID | <026501c4288a$9c4211b0$6402a8c0@HOME2> |
Hi everyone, it has been awhile since I last posted. These were some items posted to a common list for VoIP which I responded to regarding considerations that should be made for any protocol being used to address traversal of VoIP via middle boxes (in this case firewalls). Statements have been made that the solutions mentioned in the title provide scalability over the emerging session border controller technologies. Also the latest draft by Melinda brought up some additional points with direct statements naming a couple of these vendors. I would like to bring this discussion up a bit more to investigate the true scalability factors. I believe that we do need an IETF solution to the problem at hand that does not present yet another issue to the mix, and that the current protocol proposals need to consider scalability factors for a number of reasons. Let the attachments be a start to the discussion, while I formally write up some more examples, which were between me, Johnathan, and Jiri. Thanks in advance, Chris
(unnamed)
(message/rfc822, 3.5 KB) - not displayed
(unnamed)
(message/rfc822, 8 KB) - not displayed
(unnamed)
(message/rfc822, 6.7 KB) - not displayed