Your IP Address is: 38.107.191.98
RE: [moonv6] Moonv6 Test Requests
From: Bound, Jim (jim.bound@hp.com)
Date: 05/20/04
- Next message: Bound, Jim: "FW: [moonv6] Moonv6 Test Requests"
- Previous message: JORDI PALET MARTINEZ: "Re: [moonv6] Moonv6 Test Requests"
- Maybe in reply to: Bound, Jim: "[moonv6] Moonv6 Test Requests"
- Next in thread: Marc Blanchet: "RE: [moonv6] Moonv6 Test Requests"
- Reply: Marc Blanchet: "RE: [moonv6] Moonv6 Test Requests"
moonv6 post from "Bound, Jim" <jim.bound@hp.com>
Marc,
Can you send where the TB is used I have not seen it on any of the Moonv6 maps and I would like this reported in Ben and Major Dixons talk at the IPv6 US Summit in Santa Monica.
Regarding TB for Moonv6 I am now awaiting in a queue with Ben and he is very maxed right now and why I am asking two important queestions:
- Can folks donate some time to assist UNH with some of the technical work in support of the greater good at UNH?
- Or do we need to ask Internet2 or our ISP colleagues to help with Moonv6 as UNH is to maxed out?
So I am trying to fix this now as Chair of NAV6TF. For example, NAv6TF had to get a second response to DOC for IPv6, your truly was to maxed. Hence, I found NAv6TF SME volunteers to do the work and helped them and met the DOC deadline. UNH now needs to do this too we cannot any longer operate like this and we all need to support UNH either by helping or offload some of the Moonv6 responsibilities from them.
Also another bogus thing we need to fix on the Moonv6 page is that the test requirements are not solely defined by the DOD. The DOD is our priority for U.S. moonv6 site peerings yes, but Moonv6 must support the commercial sector test requirements too.
Thanks Marc,
/jim
> -----Original Message-----
> From: Marc Blanchet [mailto:Marc.Blanchet@hexago.com]
> Sent: Thursday, May 20, 2004 12:35 AM
> To: Bound, Jim
> Cc: moonv6@iol.unh.edu
> Subject: Re: [moonv6] Moonv6 Test Requests
>
>
>
> -- Wednesday, May 19, 2004 23:11:19 -0400 "Bound, Jim"
> <jim.bound@hp.com> wrote/a ecrit:
>
> > Folks,
> >
> > DOD JITC has asked that we step up the pace to do
> International Testing.
> > We must also must begin testing Tunnel Broker,
>
> moonv6 phase 1 and phase 2 involves a lot of tests with
> tunnel broker, in a multi-vendor setup.
>
> >Teredo, ISATAP, and DSTM
> > A.S.A.P. Many are asking we no longer going to wait on the IETF
> >process for transition in the market we must begin to test all the
> >mechanisms for interoperability, connectivity, security,
> and scalability now.
> > Implementations exist for all these Transition Mechanisms
> and we need
> >to begin to test them.
>
> as discussed before and based on your initial idea, we are
> ready and willing to provide off-net access to moonv6 network
> with tunnel broker for all participants, behind nats or not.
> Document on howto/who/when was sent.
> Waiting for next steps.
>
> Marc.
>
> >
> > We also need to schedule further IPsec tests across all Moonv6 site
> > peerings E2E with the entire IPv6 packet encrypted except
> for the IPv6
> > Header E2E.
> >
> > If we cannot do all of this at UNH IOL then I ask that we need help
> > from
> > Internet2 Labs and emerging PAIX now.
> >
> > Or we need to find some volunteer resources to assist UNH
> IOL. But we
> > cannot become dormant and not keep evolving.
> >
> > It is coming up on June and we have added no new tests or
> mechanisms
> > to
> > Moonv6 we need to keep moving?
> >
> > China IPv6 Council? Have you been contacted about
> connecting to Moonv6?
> >
> > Seoul Korea IPv6? Have you been contacted about connecting
> to Moonv6?
> >
> > Other Asia sites?
> >
> > 6NET? Have you been contacted?
> >
> > French IPv6 Task Force have you been contacted?
> >
> > U.S., Asia, and Europe ISP partners are you all ok and working to
> > connect?
> >
> > Thanks for your support,
> > /jim
> > Chair North American IPv6 Task Force
>
>
>
> ------------------------------------------
> Marc Blanchet
> Hexago
> tel: +1-418-266-5533x225
> ------------------------------------------
> http://www.freenet6.net: IPv6 connectivity
> ------------------------------------------
>
>
This archive was generated by hypermail 2.1.7 : 12/01/06 EST
