Hi, I'm new to Ubuntu development, although my testing of this code for the Linux kernel was done on a Ubuntu platform. But I've many more years as a *BSD and MacOS developer, going back to the '80s. And the Linux TCP/IP stack has many elements of our (late 80s-early 90s) KA9Q NOS code.
I'd originally contacted the Linux net and kernel mailing lists, to give them a heads up about symbol changes made (at the request of a prominent reviewer) in the final weeks of the RFC editing process. The Linux code was the original trial implementation, but is now lagging behind the documents. RFC-6013 is Experimental. Somebody on LKML actually had the temerity to argue with me (the RFC author) whether the newer symbols were correct, based on a 7 month old draft they'd found laying around. The Linux kernel list seems to be painfully slow and contentious! At about the same time, I also asked the developers list here, to try to give a heads up *before* the RFC was published. But it took a over a month before the moderator let the message through. Experiments are being done using Ubuntu, so it would be very helpful to have the current symbols, especially in the LTS branch. Any experimental application code (A*B*I) out there should continue to work until recompiled (A*P*I). The positions of the flag bits themselves has been stable since the initial kernel implementation posted in mid-2008. But many fields and symbols previously changed in 2009, and those changes were released in the January 2010 kernel 2.6.33. As the symbols are now published in the RFC, I cannot imagine them changing again (although additional symbols are expected to be added over time). There is one new error condition, detecting a flag being set without corresponding data. I reorganized the code a little for that. But that shouldn't matter in practice. Code review is welcomed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740065 Title: TCP Cookie Transactions (RFC-6013) API updates -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
