Commit b7e0d2f7 authored by Jørn Åne de Jong's avatar Jørn Åne de Jong
Browse files

Add related work

parent 39a125c1
......@@ -111,9 +111,38 @@ These can share the same IPv4 address while having different IPv6 addresses.
What should go here? I have been running it for some sites, it runs stable.
\section{Related Work}
HAproxy is an open source high availability HTTP, HTTPS and TCP proxy.
For HTTP and HTTPS, it uses the incoming socket (IP address and port) and hostname provided in the HTTP header to provide VHost-capabilities.
In the case of HTTPS, this means that it needs to decrypt the traffic and therefore needs a private key.
The TCP proxy uses only the incoming socket.
There is currently no possibility to use the SNI value.
HAproxy is configured by defining front-ends (which an end-user connects to) and back-ends (which )
\heading{SNI Proxy}
SNI Proxy is an open source TCP proxy that uses the SNI value to provide VHost-capabilities.
It uses a configuration file which maps the SNI value to an IP address.
This is very similar to the behaviour of SNIP, except that SNIP uses DNS instead of a config file.
NAT64 is a transition technology in order to make external IPv4-only servers available to local IPv6 clients.
It is typically employed by a network administrator that has IPv6-only clients.
The goal is the counterpart of SNIP, where SNIP makes local IPv6 servers available to external IPv4-only clients.
In a setup with IPv6-only servers, it is possible to use both SNIP and NAT64 in tandem, in order to make the servers available for IPv4-only hosts, and to allow the servers to use external IPv4-only APIs.
\section{Implementation details}
A proof of concept of SNIP is implemented in the NodeJS language.
This language allows fairly complex operations to be done with small amounts of code.
The version that has been benchmarked for this extended abstract has been field-tested against some small, personal, websites.
It shows that the concept works; IPv4 and IPv6 users get the same experience.
The current implementation has stability issues when it needs to handle a lot of connections at the same time.
A small-scale experiment on location suggests that the current connection limit for SNIP lies close to the limit for Apache,
but code optimalization could improve this.
The concept of SNIP has been proven, when a more stable version is available,
SNIP will be a step towards the IPv6-only server park.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment