Your IP Address is: 38.103.63.55
[moonv6] Moonv6 and Tunnel Service Broker in the Home
From: carlw@mcsr-labs.org
Date: 04/16/04
- Next message: Marc Blanchet: "[moonv6] Re: Call to Action: Teredo and Tunnel Service Broker on Moonv6 Network Pilot"
- Previous message: Bound, Jim: "[moonv6] Call to Action: Teredo and Tunnel Service Broker on Moonv6 Network Pilot"
- Next in thread: Tim Chown: "[moonv6] Re: [nav6tf] Moonv6 and Tunnel Service Broker in the Home"
- Reply: Tim Chown: "[moonv6] Re: [nav6tf] Moonv6 and Tunnel Service Broker in the Home"
- Reply: S. Daniel Park: "RE: [moonv6] Moonv6 and Tunnel Service Broker in the Home"
moonv6 post from "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>
Jim,
This is something that we started to pilot here in phase II. We deployed two TB and tested various scenarios including from our homes.
What we are interested in doing as part of a follow-up is to have some IPv6 application/services that are for the home as well as some IPv6 enabled home devices accessing the DSL connection via WLAN. We are building IPv6 native in the home but tunneling over the local ISP (who doesn't support it yet).
We have tested with and without NAT as well as double NATed scnearios. We have also piloted the roaming of IPv6 home devices and moved them to WLAN hotspots - keeping the same user and AAA data.
Indeed, today we will pilot over Moonv6 a IPv6 HomeGateway and test access to IPv6 devices behind the IPv6 HomeGateway from outside of the home ---- something that is impossible to do with IPv4 private addresses (behind a NAT).....
So we are continuing our Moonv6 pilots using Tunnel Service Broker in a home deployment scenario ... including roaming of those IPv6 devices outside the home in a WLAN hotspot.
Carl (for Shu and Jeff as well)
Original Message:
From: Bound, Jim jim.bound@hp.com
Date: Fri, 16 Apr 2004 08:21:02 -0400
To: nav6tf@ipv6forum.com, moonv6@iol.unh.edu, members@ipv6forum.com Subject: [moonv6] Call to Action: Teredo and Tunnel Service Broker on Moonv6 Network Pilot
moonv6 post from "Bound, Jim" <jim.bound@hp.com>
I want to call to action that we now do something aggressive to promote IPv6 in the home to our Moonv6 Network Pilot by us beginning to deploy within Moonv6 the Teredo and Tunnel Broker industry mechanisms defined as work in the IETF awaiting some more analysis. We cannot wait on the IETF process, and need to move forward. We can work in the IETF as our members do now to assist with that specification process. I would like to log into UNH from my home to a server that permits me to avoid NAT with IPv6 and get around my ISP until they can fully support IPv6 as one example from Linux or XP, which are my client OS's used for IPv6. We should ask our ISP participants if they would support a pilot trial of Teredo and/or Tunnel Broker servers/relays in support of the Moonv6 Network Pilot.
This does not preclude other transition mechanisms for other purposes which are being deployed across the IPv6 earth each with key benefits too like manual tunnels, DSTM, and ISATAP. The IPv6 carpenters of the world will need many tools and one size does not fit all is our theme.
Latif, Yanick, Patrick C., and I had an excellent discussion with China IPv6 Council members and we will and must help China IPv6 network pilots to participate in Moonv6 in addition to European and others parts of the Asian region, and all regions within our IPv6 circumference.
Lets make 2006 the year of wide IPv6 ready production deployment and in the home too.
Thank You for your support and esp. to the engineers/architects inventing transition mechanisms and keep them coming, /jim
mail2web - Check your email from the web at http://mail2web.com/ .
This archive was generated by hypermail 2.1.7 : 12/01/06 EST
