On 03/19/2016 11:03 PM, Marrold wrote:
That's essentially what I'm hoping for, although I appreciate from an
RFC purist perspective it's probably a bit of a nasty hack.
It's not a question of pedantic RFC purism so much as:
(a) Whether it creates at least as many complications as it solves;
solutions like this one create so many complications, corner cases and
statekeeping requirements that they represent - to borrow a term from
philosophy of science - a "degenerative heuristic". This means crawling
down a rabbit hole to solve the wrong problem the wrong way and just
getting tangled.
But perhaps a more applicable term would be:
https://en.wikipedia.org/wiki/Anti-pattern
(b) Whether it's truly the most effective solution to the problem. It
seems to me you're solving the wrong problem; solutions for UDP
fragmentation (use TCP, remove other, less essential headers) and
topology hiding (B2BUA) are well-understood and canonical.
(c) Technically possible.
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
1447 Peachtree Street NE, Suite 700
Atlanta, GA 30309
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
