Your IP Address is: 38.107.191.80
[moonv6] RE: Technical Volunteers Needed for 2 months Disaster Response Wireless and MESH Networks et al.
From: Bound, Jim (Jim.Bound@hp.com)
Date: 02/27/06
- Next message: Green, David B RDECOM CERDEC STCD SRI: "RE: [moonv6] RE: Technical Volunteers Needed for 2 months Disaste r Response Wireless and MESH Networks et al."
- Previous message: Bound, Jim: "[moonv6] Technical Volunteers Needed for 2 months Disaster Response Wireless and MESH Networks et al."
moonv6 post from "Bound, Jim" <Jim.Bound@hp.com>
whoops we are "NOW" developing strong relationships with WIMAX ...ouch
to much travel :--)
/jim
> -----Original Message-----
> From: Bound, Jim
> Sent: Monday, February 27, 2006 4:05 PM
> To: nav6tf@ipv6forum.com; moonv6@iol.unh.edu
> Cc: 'Chris Gunderson'; Aaron Budgor; Bound, Jim; 'Brett
> Thorson'; Buddenberg, Rex (CIV); Paul Mangione; Steckler,
> Brian (CIV); Desimone, Tony, Mr, OSD-NII; 'Brett Thorson'
> Subject: Technical Volunteers Needed for 2 months Disaster
> Response Wireless and MESH Networks et al.
>
> NAv6TF and Moonv6 Team,
>
> See attached Northcom Document. We need if possible to
> supply our new important partner W2COG www.w2cog.org (you all
> have met Chris Gunderson in cyber space) with some mobility,
> security, wireless, et al expertise not necessarily just
> IPv6. As an IPv6 Forum and NAv6TF we have over 6 years not
> only developed core technical expertise on IPv6 but also
> Routing, Mobility, Security, MESH/Ad Hoc Nets, etc from
> within our Subject Matter Expert (SME) ranks. This would dove
> tail well with our CAv6TF subchapter www.cav6tf.org lead on
> MetroNet6 http://www.cav6tf.org/html/metronet6.php project.
> I don't want to cannibalize MetroNet6, but the Northcom
> statement of work is so close to the of MetroNet6 it is very
> congruent. Maybe we can get two for one from our work. We
> clearly would learn a hell of a lot. Also see recent slides
> from Tom Worden California OES Geof Lambert and George Usi
> are working with for MetroNet6. Chris, Brett Thorson, and I
> are having lunch tomorrow to look at the long term tasks in
> this space for the partnership and also this will be
> important to the IPv6 Forum via Latif on a world wide scale
> and we are not developing strong relationships for example
> with the WIMAX forum.
>
> Also a similar effort is underway in NCOIC www.ncoic.org
> called volunteer Complex Humanitarian Disaster (CHD) project
> looking at similar SOW and Technical Analysis from Katrina,
> Tsunami, and 911. This is being led by one Mr. Paul Magione
> I have now known for some time. Yanick Pouffary and I have
> committed to help on that effort and Dave Green to some
> degree from our ranks here within NCOIC.
>
> So if you can help in this space please send me mail and I
> will get you connected. It would be review and technical
> analysis type work and then completing a report per the
> attached same as what we are to do for MetroNet6 and for CHD
> above. Then I will connect you with Mr. Aaron Budgor from
> W2COG who is the lead for Northcom.
>
> Also note a true volunteer group that straddles helping both
> Military and our Civil Sector is the Naval Post Graduate
> School (NPS) http://www.nps.edu/ who helped at Tsunami and
> Katrina. NPS Mr. Rex Buddenberg and Mr. Brian Steckler are
> copied here too. Kudos to these folks I have seen some of
> their reports it is quite amazing.
>
> As we move forward here please differentiate MESH Network
> from Ad Hoc Network, and an Ad Hoc Network is not always
> mobile, thus MANET does not always apply. Also for radio
> communications not all of us believe that next hop
> communications is always the best choice if base stations can
> be provided with each radio node, and with IPv6 suggested
> extensions to Neighbor Discovery the entire idea of routing
> between radio nodes is suspect for analysis too. The vision
> is 802.11 (with support for connect to 802.15) ---> 802.16
> ----) Satcom/802.20/22 and the base principle for MetroNet6.
> And last but not least the vendor agendas in this space are
> phenomenal and out of control as there is no clear market
> leader so we have to watch ALL VENDORs for their agenda when
> doing this work. Also the computer network infrastructure
> services for virtualization, high availability, Grid
> services, etc need to be part of what is available to the
> MESH Network. One thing is for sure what exists today is
> unacceptable and can cause lives to be lost and that is not
> good, whether it be warfighters, policeman, fireman, doctors,
> or EMS personnel. Lastly as you all have seen it is critical
> that we now begin to look at the principles of net centricity
> for NGN deployment and for this space that means the
> following essentially: connectivity, interoperability,
> discovery, security, and all end-to-end. Our bias here in
> NAv6TF is that this is not possible with IPv4 plumbing but
> requires IPv6 plumbing underneath, but reality is we need to
> provide a path for that end-to-end restoration and treat IPv4
> as legacy to introduce IPv6 for the topics previously
> mentioned. That is all possible with emerging projects as
> discussed here.
>
> I know your maxed, I know your tired, but we need you to
> help, no one else will except for money and you all know what
> that means. If we can get the studies to be done from
> non-profit and vendor-neutral view that gives hope to an
> honoroable open solution and there clearly will be money to
> be made after all these initial studies and plenty for all to
> compete out of the NAv6TF etc. Look at it this way. For
> just 25 hours of your time in March and April as volunteer
> could be one small part for tomorrow to save a soldiers or
> fireman's life by just helping to educate and review as a
> volunteer. There is no travel required is my understanding.
> And the work from this will apply directly to the WiFi
> Networks needed that can be done inexpensively for children's
> schools for our digital divide efforts too.
>
> Thanks for your considerations and support,
> /jim
> Chair NAv6TF www.nav6tf.org
> CTO IPv6 Forum www.ipv6fourm.org
>
>
This archive was generated by hypermail 2.1.7 : 12/01/06 EST
