Abstract
The first implementation of new E6 stack of networking protocols within the kernel of an operating system is presented. Stack E6 was developed to increase the efficiency of a network entirely built on the base of Ethernet technology. It uses a uniform hierarchical E6 address on all the levels and annuls TCP, UDP and IP protocols. The experimental implementation adds a new system call to the kernel of Linux and a new type of Ethernet E6 frame. All the application interface standards are saved according to RFC except of E6 address usage instead of IP address and instead of Ethernet MAC address as well.
Highlights
Stack of protocols E6 was presented in [1] the corresponding patent of Ukraine on utility model [2] was obtained and the robustness of E6 networks was acknowledged [3] via modeling in CPN Tools
The steps assume its implementation within real-life operating systems and the development of special hardware namely switching routers E6 (SRE6)
All the code was developed as a loadable Linux kernel module E6udpmod.ko save the minor changes to the static part of the kernel with the goal to add a new system call
Summary
Stack of protocols E6 was presented in [1] the corresponding patent of Ukraine on utility model [2] was obtained and the robustness of E6 networks was acknowledged [3] via modeling in CPN Tools. Different approaches could be chosen but the present implementation is developed as an independent one without the integration with Unix socket facilities This approach is justified by the fact that Unix sockets are rather heavy and closely related with TCP/IP protocols family while the stack E6 does not use their facilities. The usage of TCP and UPD application interface standards [4,5] provides the possibility of the code reuse in other operating systems. This implementation within Linux kernel could be considered rather non Unix-de pendent as far as it is not based on the Unix socket facilities. The present experimental implementation does not employ Ethernet LLC2 facilities and provides the application interfaces of UPD protocol only. The implementation of TCP application interfaces requires Ether-net LLC2 sliding window procedures usage instead of TCP protocol procedures and is the subject for future work
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
