[RRG] Six/One Router: Provider-Independence, IPv4/IPv6 Interworking, Backwards-Compatibility

[Christian Vogt <christian.vogt@nomadiclab.com>]

Folks,

backwards compatibility has proven to be one of the bigger challenges
in the work of this RG.  It is hard in particular when identifiers are
to be provider-independent and therefore, for scalability reasons, non-
globally routable.  The use of tunneling exacerbates the problem because
the extra IP header makes packets unprocessable by recipients in legacy
edge networks.

I would like to propose Six/One Router [1], a network-based variant of
the original Six/One protocol, which avoids these problems through (1)
exclusive use of address translation (instead of tunneling), (2)
optional-to-support packet extensions (instead of mandatory-to-support
tunnel headers), and (3) the ability for hosts in upgraded edge networks
to be reached from legacy edge networks at a locator.

[1] http://users.piuha.net/chvogt/pub/2008/vogt-2008-six-one-router.pdf
    or via RRG homepage

Specifically, Six/One Router offers:

- Provider independence (independent of deployment elsewhere)

- Interworking between IPv4 and IPv6 (different IP versions on hosts,
 or path of different IP version than the common IP version of hosts)

- Backwards compatibility with legacy IPv4 and IPv6 Internet

Six/One Router interoperates with existing mapping resolution protocols,
such as NERD, APT Default Mappers, Cons, ALT, DNS Map.

A comprehensive analysis with respect to the RRG design goals is  
included
in the paper [1].

Your comments and opinions will be highly welcome.

- Christian



--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg