[routing-wg]BGP Update Report

Sun Sep 10 02:43:13 UTC 2006

Was it merely not enough customers? or were there other issues? inquiring
minds is all =)

-brandon

On 9/9/06, Michael Painter <tvhawaii at shaka.com> wrote:
>
>
> From their webpage:
> Service Advisory
> On Aug. 17, 2006, the Boeing Company announced that a detailed business
> and market analysis of Connexion by Boeing is complete, and
> the company has decided to exit the high-speed broadband communications
> connectivity markets. Boeing will work with its customers to
> facilitate an orderly phase out of the Connexion by Boeing service.
> Passengers traveling on Internet-equipped flights will be able
> to use the service until it is phased out between now and the end of the
> year, depending on the airline.
>
> ----- Original Message -----
> From: "Joe Provo" <nanog-post at rsuc.gweep.net>
> To: "Hank Nussbacher" <hank at efes.iucc.ac.il>
> Cc: <cidr-report at potaroo.net>; <nanog at merit.edu>; <routing-wg at ripe.net>
> Sent: Friday, September 08, 2006 6:35 AM
> Subject: Re: [routing-wg]BGP Update Report
>
>
> >
> > On Fri, Sep 08, 2006 at 05:57:10PM +0300, Hank Nussbacher wrote:
> >>
> >> On Fri, 8 Sep 2006, cidr-report at potaroo.net wrote:
> >>
> >> Strike me as curious, but this seems as if Connexion by Boeing is
> handing
> >> off a /24 from ASN to ASN as a certain plane moves over certain
> geographic
> >> areas.  Or is there some other explanation?
> >
> > Detailed at nanog 31 (among other meetings):
> > http://www.nanog.org/mtg-0405/abarbanel.html
> >
> > 2005 detail from a blogger:
> > http://bayosphere.com/node/879
> >
> > 2006 detail from another blogger:
> > http://www.renesys.com/blog/2006/04/tracking_plane_flight_on_inter.shtml
> >
> > --
> >             RSUC / GweepNet / Spunk / FnB / Usenix / SAGE
> >
>
>

-- 
Brandon Galbraith
Email: brandon.galbraith at gmail.com
AIM: brandong00
Voice: 630.400.6992
"A true pirate starts drinking before the sun hits the yard-arm. Yarrrr.
--thelost"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20060909/fc8d665d/attachment.html>