changes for JOSS publication (#36)

* minor changes in paper.md

* minor changes in paper.bib
joss
Daniel S. Katz 2024-08-26 14:53:45 -05:00 committed by GitHub
parent a1dc0ce0ab
commit 5f5c81baef
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 7 additions and 7 deletions

View File

@ -34,7 +34,7 @@
doi = {10.17487/RFC3920}, doi = {10.17487/RFC3920},
url = {https://www.rfc-editor.org/info/rfc3920}, url = {https://www.rfc-editor.org/info/rfc3920},
author = {Peter Saint-Andre}, author = {Peter Saint-Andre},
title = {{Extensible Messaging and Presence Protocol (XMPP): Core}}, title = {Extensible Messaging and Presence Protocol ({XMPP}): Core},
pagetotal = 30, pagetotal = 30,
year = 2004, year = 2004,
month = oct, month = oct,
@ -81,7 +81,7 @@ keywords = {ethernet switch, flow-based, virtualization}
doi = {10.17487/RFC7047}, doi = {10.17487/RFC7047},
url = {https://www.rfc-editor.org/info/rfc7047}, url = {https://www.rfc-editor.org/info/rfc7047},
author = {Ben Pfaff and Bruce Davie}, author = {Ben Pfaff and Bruce Davie},
title = {{The Open vSwitch Database Management Protocol}}, title = {The Open {vSwitch} Database Management Protocol},
pagetotal = 35, pagetotal = 35,
year = 2013, year = 2013,
month = dec, month = dec,
@ -95,14 +95,14 @@ keywords = {ethernet switch, flow-based, virtualization}
doi = {10.17487/RFC8926}, doi = {10.17487/RFC8926},
url = {https://www.rfc-editor.org/info/rfc8926}, url = {https://www.rfc-editor.org/info/rfc8926},
author = {Jesse Gross and Ilango Ganga and T. Sridhar}, author = {Jesse Gross and Ilango Ganga and T. Sridhar},
title = {{Geneve: Generic Network Virtualization Encapsulation}}, title = {Geneve: Generic Network Virtualization Encapsulation},
pagetotal = 34, pagetotal = 34,
year = 2020, year = 2020,
month = nov, month = nov,
} }
@inproceedings{zhang2015cloud, @inproceedings{zhang2015cloud,
title={The cloud is not enough: Saving $\{$IoT$\}$ from the cloud}, title={The cloud is not enough: Saving {IoT} from the cloud},
author={Zhang, Ben and Mor, Nitesh and Kolb, John and Chan, Douglas S and Lutz, Ken and Allman, Eric and Wawrzynek, John and Lee, Edward and Kubiatowicz, John}, author={Zhang, Ben and Mor, Nitesh and Kolb, John and Chan, Douglas S and Lutz, Ken and Allman, Eric and Wawrzynek, John and Lee, Edward and Kubiatowicz, John},
booktitle={7th USENIX Workshop on Hot Topics in Cloud Computing (HotCloud 15)}, booktitle={7th USENIX Workshop on Hot Topics in Cloud Computing (HotCloud 15)},
year={2015}, year={2015},
@ -117,7 +117,7 @@ keywords = {ethernet switch, flow-based, virtualization}
doi = {10.17487/RFC5245}, doi = {10.17487/RFC5245},
url = {https://www.rfc-editor.org/info/rfc5245}, url = {https://www.rfc-editor.org/info/rfc5245},
author = {Jonathan Rosenberg}, author = {Jonathan Rosenberg},
title = {{Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols}}, title = {Interactive Connectivity Establishment ({ICE}): A Protocol for Network Address Translator ({NAT}) Traversal for Offer/Answer Protocols},
pagetotal = 117, pagetotal = 117,
year = 2010, year = 2010,
month = apr, month = apr,

View File

@ -27,7 +27,7 @@ bibliography: paper.bib
# Summary # Summary
This paper describes the `EdgeVPN.io` [@evio_v24] software, a novel technique that enables virtual private Ethernet networks that span edge and cloud resources including those constrained by NATs and firewalls. `EdgeVPN.io` has been implemented as an open-source virtual network software solution, and experiments with the software have demonstrated its functionality and scalability. The design and evaluation are discussed further in [@subratie2023edgevpn]. This paper describes the `EdgeVPN.io` software [@evio_v24], a novel technique that enables virtual private Ethernet networks that span edge and cloud resources including those constrained by NATs and firewalls. `EdgeVPN.io` has been implemented as an open-source virtual network software solution, and experiments with the software have demonstrated its functionality and scalability. The design and evaluation are discussed further in @subratie2023edgevpn.
# Statement of need # Statement of need
@ -58,7 +58,7 @@ The `EdgeVPN.io` software integrates the following features:
The goal of EdgeVPN.io is to deliver scalable layer 2 forwarding for dynamic edge and cloud network environments where the peer nodes act as software-defined bridges. `EdgeVPN.io` integrates a Symphony (1-D Kleinberg routable small-world network [@manku2003symphony]) topology and a decentralized layer-2 switching into a network fabric. Each node runs three components as depicted in \autoref{fig:sysov}: (1) the topology controller creates and maintains the overlay, while (2) the OpenFlow layer 2 controller programs the corresponding switching rules, and (3) Tincan, the default datapath. While each node is parameterized to be independently tuned, they are true peers with identical functional capabilities, and each is independently maintained by its local controllers. While there are no centralized components for overlay management and SDN-programmed switching, it uses XMPP [@rfc3920] for peer authentication and messaging, and ICE for endpoint discovery and tunnel bootstrapping. The goal of EdgeVPN.io is to deliver scalable layer 2 forwarding for dynamic edge and cloud network environments where the peer nodes act as software-defined bridges. `EdgeVPN.io` integrates a Symphony (1-D Kleinberg routable small-world network [@manku2003symphony]) topology and a decentralized layer-2 switching into a network fabric. Each node runs three components as depicted in \autoref{fig:sysov}: (1) the topology controller creates and maintains the overlay, while (2) the OpenFlow layer 2 controller programs the corresponding switching rules, and (3) Tincan, the default datapath. While each node is parameterized to be independently tuned, they are true peers with identical functional capabilities, and each is independently maintained by its local controllers. While there are no centralized components for overlay management and SDN-programmed switching, it uses XMPP [@rfc3920] for peer authentication and messaging, and ICE for endpoint discovery and tunnel bootstrapping.
# Source Code and Packaging # Source Code and Packaging
`EdgeVPN.io` is available as an MIT-licensed open-source project hosted on [Github](https://github.com/EdgeVPNio). The two primary repositories are [EdgeVPNio/evio](https://github.com/EdgeVPNio/evio) and [EdgeVPNio/tincan](https://github.com/EdgeVPNio/tincan). `EdgeVPN.io` is available as an MIT-licensed open-source project hosted on [GitHub](https://github.com/EdgeVPNio). The two primary repositories are [EdgeVPNio/evio](https://github.com/EdgeVPNio/evio) and [EdgeVPNio/tincan](https://github.com/EdgeVPNio/tincan).
Evio is the Python implementation of SDN controllers for topology, layer 2 switching, and other auxillary functions. Tincan is the `EdgeVPN.io` default datapath. It is implemented in C++ and creates the fundamental tunnel abstraction consisting of a Linux TAP device and a WebRTC data link. Tincan requires WebRTC source code or prebuilt libraries for compiling. The tools repo provides several scripts that assist with building and packaging. Evio is the Python implementation of SDN controllers for topology, layer 2 switching, and other auxillary functions. Tincan is the `EdgeVPN.io` default datapath. It is implemented in C++ and creates the fundamental tunnel abstraction consisting of a Linux TAP device and a WebRTC data link. Tincan requires WebRTC source code or prebuilt libraries for compiling. The tools repo provides several scripts that assist with building and packaging.