On 10/12/2010 12:15 PM, Iñaki Baz Castillo wrote: > Second paragraph of Section 18.1.1 of RFC 3261: > > ------------------------- > If a request is within 200 bytes of the path MTU, or if it is larger > than 1300 bytes and the path MTU is unknown, the request MUST be sent > using an RFC 2914 [43] congestion controlled transport protocol, such > as TCP. > ------------------------- > > IMHO this is an exotic specification. What about if the > proxy/registart has to route a long request to a user registered in a > UDP location? should the proxy try TCP? to which port? what about NAT? > So this is a so exotic "feature" that I strongly understand everybody > ignores it [*].
Strongly agreed. This is one of the most batshit inane, idiotic requirements I have ever seen, and it should be rightly ignored by everyone in light of the realities of today's Internet. UDP is designed to be able to transport up to 65535 bytes of payload, and that is what a protocol using UDP as a transport should allow. All SIP UDP endpoints and ALGs should support IP/UDP reassembly, without question. Mandating use of TCP in this situation is simply not realistic, especially when so many otherwise mainstream and well-heeled, stable SIP stacks don't support it (for example, Asterisk, many softphones, etc.). -- Alex Balashov - Principal Evariste Systems LLC 1170 Peachtree Street 12th Floor, Suite 1200 Atlanta, GA 30309 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
