http://www.6assistnet/ - call for test

[Templin, Fred L]

Hi - coming into this late and just noticing this thread, let's
not forget that there are many other reasons for tunneling besides
just IP protocol version bridging (including routing control,
security, mobility management, etc.). So, we have developed a
tunneling approach that covers all of these needs via a hybrid
tunnel broker / NBMA architecture with built in route optimization.
We have also taken care of the tunnel MTU issue to provide a
1500B-clean path.

The approach is known as IRON, and is made up of its constituent
technologies SEAL, VET and AERO:

https://datatracker.ietf.org/doc/draft-templin-ironbis/
https://datatracker.ietf.org/doc/draft-templin-intarea-seal/
https://datatracker.ietf.org/doc/draft-templin-intarea-vet/
https://datatracker.ietf.org/doc/rfc6706/

With IRON, a source tunnel endpoint sends initial packets via
a server that acts very much like a tunnel broker. The server
forwards the packets then sends a Redirect message (according
to the NBMA model) back to the source so that future packets
can be sent to a tunnel endpoint nearer the destination.

The work was originally inspired from earlier NBMA tunneling
approaches including RFC2529 and RFC5214, was later refined
through development in the IRTF Routing Research Group, and
is now being published in a second edition through the IETF
(first edition documents included RFC5320, RFC5558 and RFC6179).

We see a very broad array of use cases for these technologies,
from IPv6/IPv4 bridging, to aviation networking, to enterprise
user mobility, to mobile VPNs, etc. It would be interesting to
have some comments from this distribution on the approach.

Thanks - Fred
fred.l.templin at boeing.com