Fwd: Re: ACS and GCI: Neener neener neener (WAS: Re: KDE 3.5.3, IPv6, and CUPS)

Oops. Accidently did reply instead of reply all and I wasn't going to type it again,
Jim Gribbin

-- Attached file included as plaintext by Ecartis --

Received: from [66.223.252.115] by ims01.prv.nwc.acsalaska.net (mshttpd);
  Mon, 26 Jun 2006 19:41:00 -0800
From: <jgribbin@alaska.net>
To: James Zuelow <e5z8652@zuelow.net>
Message-ID: <a18ada1954.a1954a18ad@acsalaska.net>
Date: Mon, 26 Jun 2006 19:41:00 -0800
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.18 (built Jul 28 2003)
MIME-Version: 1.0
Content-Language: en
Subject: Re: ACS and GCI: Neener neener neener (WAS: Re: KDE 3.5.3, IPv6,
  and CUPS)
X-Accept-Language: en
Priority: normal
Content-Type: multipart/mixed; boundary="--36c6443774b450a3"

This is a multi-part message in MIME format.

----36c6443774b450a3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

I don't remember an 'accidental' one, but I do seem to remember when I first got involved with AKLUG there were a couple of members wanting to do something like this as a 'Community Service Project'.

There was talk of using a 'Ring' ATU used to have (pre-Internet) and even some sort of laser or microwave wireless setup.

I don't recall offhand who was involved in the discussion, but it seems like Mike Tibor and Aurthur Corliss were among them. This was just about the time of the Installfest at APU.

Of course, the Internet was a lot smaller then. I think Internet Alaska and GCI had something like 4 T1s each for Internet backbone up here. You'd probably need need to get one of AT&T OC12s to even think about doing that now.

Jim Gribbin

----- Original Message -----
From: James Zuelow <e5z8652@zuelow.net>
Date: Monday, June 26, 2006 6:19 pm
Subject: ACS and GCI: Neener neener neener (WAS: Re: KDE 3.5.3, IPv6, and CUPS)

> On Monday 26 June 2006 08:50, Leif Sawyer wrote:
> > James Zuelow wrote:
> > > [ snip ]
> > > So is KDE using DNS to lookup localhost? Here's what I get
> > > using the ACS DNS servers (GCI just times out on me, maybe
> > > because the request is coming from the ACS netblock, or maybe
> > > because the request has to go through the lower-48 to get to
> > > GCI next door. Sigh. ACS and GCI still acting like
> children.)
> > From a consumer point-of-view, you might make this generalization,
> > because you just want 'things to work'.
> >
>
> Well, I are a consumer.
>
> At home I am currently an ACS broadband customer, used to be a GCI
> broadband customer (the switch wasn't because of anything GCI did,
> it just happened for a variety of reasons). I still get bills in
> the mail from both, and all in all they're both OK companies.
> (They both have their bad moments, though!) This isn't really a
> burning issue for me, until I get told how expensive it is to
> implement.
> In a work environment I have had to work around the lack of
> peering. Every so often something breaks in Seattle, and network
> traffic from a Juneau GCI cable modem address that is pointed at a
> Juneau ACS DSL address gets routed through San Jose or even
> Atlanta. I know, because I notice or someone complains about slow
> service so I do a traceroute. From a consumer point of view, it
> is dumb to have to worry about network issues in Seattle slowing
> down traffic that only has to go a couple of miles as the crow
> flies. Worse to subsidize the whole thing by buying connections
> to both networks to provide quality service to hometown
> connections on both networks. (And then spend staff time
> customizing individual user's settings based on their personal ISP
> choice!) That is money needlessly wasted on the consumer's end.
>
> I am sure that either company could put together quite the
> spreadsheet showing how local peering would destroy the Alaska
> network infrastructure by bankrupting both ACS and GCI because it
> is cheaper to route traffic through Seattle instead of Anchorage,
> leaving us all with 28.8k long distance AOL dialup. I don't
> really believe it and will still readily resort to namecalling on
> this matter though. :)
>
> > Your best bet, if you -really- want one, is to start one
> yourself. I'll
> > leave it to you to figure out how to pay for it.
> >
>
> Didn't someone up in Anchorage accidentally do exactly this a few
> years back? Cable modem to DSL bridge that slowed everything down
> because it was suddenly the shortest route between the two networks?
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
>

----36c6443774b450a3
Content-Type: text/x-vcard; name="jgribbin@alaska.net.vcf";
 charset="windows-1252"
Content-Disposition: attachment; filename="jgribbin@alaska.net.vcf"
Content-Description: Card for <jgribbin@alaska.net>
Content-Transfer-Encoding: quoted-printable

begin=3Avcard
n=3AGribbin=3BJim
fn=3AJim Gribbin
tel=3Bcell=3A(907) 229-5085
tel=3Bfax=3A(907) 562-5485
tel=3Bwork=3A(907) 273-7348
url=3Ahttp=3A//www=2EJimGribbin=2Ecom
org=3APrudential Jack White/Vista Real Estate=3B
adr=3A=3B=3B3801 Centerpoint Dr =23200=3BAnchorage=3BAK=3B99503=3BUSA
version=3A2=2E1
email=3Binternet=3Ajgribbin=40alaska=2Enet
title=3ASales Associate
end=3Avcard

----36c6443774b450a3--

-- Binary/unsupported file stripped by Ecartis --
-- Type: text/x-vcard
-- File: jgribbin@alaska.net.vcf
-- Desc: Card for <jgribbin@alaska.net>

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Mon Jun 26 19:45:30 2006