User: Password:
|
|
Subscribe / Log in / New account

How not to get a protocol implementation merged

How not to get a protocol implementation merged

Posted Jan 13, 2011 8:36 UTC (Thu) by dmk (subscriber, #50141)
In reply to: How not to get a protocol implementation merged by busterb
Parent article: How not to get a protocol implementation merged

>Note that this protocol appears to provide no method to close a connection, for instance. Wow! Seems like OBSAI SIG had a case of NIH syndrome.

It's udp based. UDP is a stateless protocol. No Close() is necessary. ?


(Log in to post comments)

How not to get a protocol implementation merged

Posted Jan 13, 2011 13:43 UTC (Thu) by busterb (subscriber, #560) [Link]

It appears to be UDP only in the sense that SCTP and other reliable protocols can also be tunneled over UDP, presumably just to make it easier to get through firewalls and initial user-space implementations easier to build on existing socket apis (excluding raw sockets.)

However, it is definitely stateful because of the reliable transport it provides on top of UDP. DoS issues have been discussed on the mailing list, where spoofed UDP packets can flood the connection table:

http://marc.info/?l=linux-netdev&m=129404690806820&...


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds