You are not logged in. Login Now
 0-24   1-25   26-50   51-75   76-91      
 
Author Message
25 new of 91 responses total.
janc
response 26 of 91: Mark Unseen   May 13 23:03 UTC 2000

We know a lot about Ameritech, but it is mostly bad (their field service
people seem to be really good, but very few people who fly desks there
seem to have any idea what they are up to).

We probably know more about Voyager than Ameritech, and it ain't bad.
richard
response 27 of 91: Mark Unseen   May 14 03:53 UTC 2000

maybe ameritech would give grex a break on its phone lines costs if it
agreed to let them be its internet provider as well-- a package deal.
surely someone in ameritech's marketing department has a little intelligence
scg
response 28 of 91: Mark Unseen   May 14 04:33 UTC 2000

Richard, we really don't want Ameritech as our ISP.  For one thing, Ameritech
won't give such a discount -- they're heavily regulated and tarriffed, in
addition to being a huge bureaucracy, so even if somebody there thought Grex
was a good cause and wanted to give Grex a discount, they couldn't.  Anyhow,
Ameritech's DSL service isn't targeted at networks or anybody providing
content, and won't do what we need it to do, as far as I know.

We really do need to get moving on this.  Since the board indicated that I
should coordinate it, does anybody have any objection to me contacting Jared
and getting the Voyager order put through?  Already we may have waited long
enough that getting the DSL line in in time will be somewhat iffy, so
Voyager's ability to give us a temporary ISDN connection while we're waiting
for the DSL install, if necessary, is also something Grex very much needs.
aruba
response 29 of 91: Mark Unseen   May 14 04:44 UTC 2000

I think we should get the installation and monthly rates in writing before
we commit to anything.
scg
response 30 of 91: Mark Unseen   May 14 05:21 UTC 2000

Once we give the goahead to order this, there will be a contract we need to
sign.  That contract will have the rates in it.
other
response 31 of 91: Mark Unseen   May 14 06:31 UTC 2000

Ameritech was just bought up by SBC Communications, which apparently has a
much better track record with DSL, but it could be a while before the takeover
effects trickle down to Ameritech's customer base and service area.

Steve, if putting in the order results in having a contract drawn up but does
not commit us to anything, then by all means go ahead, but I'd still like to
see us get similar information from other attractive providers such as
speakeasy.net.  If the same situation applies there, then let's get their
numbers also.
scg
response 32 of 91: Mark Unseen   May 14 08:12 UTC 2000

Given that we have already been told what the pricing will be, written in a
very public place (this conference) by a Voyager employee, I really don't
expect to get the contract and have it say anything different, so I really
don't feel like wasting a lot of time pretending to be ready to order this
if you still want to pursue other options.

I'm still rather confused about what's causing you to refer to Speakeasy as
an "attractive provider."  They appear to have some nice marketing material
on their webpage.  They appear not to have figured out multi-homing and BGP,
which are rather a must for anybody who wants to provide reliable service.
Their webpage makes no mention of ISDN, and we're on a tight enough schedule
that we will probably have to be begging to any provider who we buy the DSL
connection from to give us a temporary ISDN connection while we're waiting
for the DSL connection to get installed.

Let me know when you're ready for me to get this taken care of.
janc
response 33 of 91: Mark Unseen   May 14 16:49 UTC 2000

My search for DSL providers wasn't amazingly thorough or complete, but I
think I did hit a pretty good sample.  Good enough to establish that
voyager's prices are on the very bottom end of the spectrum.  I think it
is very unlikely that many other cheaper alternatives can be found.

Of those few that appeared to be cheaper, most appeared to be offering
services that were in some way incompatible with Grex's needs - single
IPs instead of multiple IPs, bridges instead of routers.  Upgrading them
to what we need would make them more expensive than voyager.

Speakeasy is the only one I found who offers a service that meets our
specifications at a price that is lower than voyager's.  They'd save us
about $10 a month, and they appear to be kind of cool, but as Steve
says, they are a *much* smaller organization than voyager, less
technically proficient, less experienced, and with no real presence in
our area.  With DSL, if we have problems we have to talk to our ISP, who
talk to Covad, who talk to Ameritech.  It's good to have an ISP who has
a lot of experience dealing with those chowderheads, and who is big
enough to have some influence with them.  Steve says speakeasy.net is
not multi-homed, which is really rather pathetic.  I think even Dorian
was multi-homed, so going with speakeasy could be a step down in network
reliability.

Personally, I'd kind of like to do business with the smaller company
offering the lower price rather than the big major player.  I've never
liked the "nobody ever gets fired for buying Microsoft" philosophy.  But
on the whole I think the advantages that voyager offers are worth $10 a
month.

I also believe in trusting the judgement of our experts, and Steve is
definitely that.  I'm willing to try to convince him that speakeasy
might be worth looking at, but I'm not going to argue with him if after
due consideration he thinks it's a bad idea.

If we want to go with a reasonably large and well-established company,
then we don't really need to do any more searching for altenatives. 
We've looked at everyone who is big in this business in this area. 
Voyager is clearly the best deal of the lot.  Even the vast majority of
the second tier companies offering inferior service cost more.

So I think Steve should go ahead with the voyager deal.

There are a couple things that weren't quite clear to me on the voyager
deal:

  - There was talk of them giving us a break on the installation, due
    to being such nice guys.  I'm not sure I know exactly what this
    break consists of.

  - I've seen some hints that the DSL prices generally quoted on the
    net don't include taxes, and some hints that the taxes can be
    substantial..  I'd like to know how big the taxes would be on
    our payments.
aruba
response 34 of 91: Mark Unseen   May 14 17:23 UTC 2000

We are also exempt from state sales taxes, but not some other taxes, which
makes the situation more complicated.  THe reason I want us to get it in
writing is because we got screwed so badly when we had our ISDN lines
installed.  I don't know why that was, but I want to do our best to avoid
it happening again.
other
response 35 of 91: Mark Unseen   May 15 03:13 UTC 2000

I didn't mean to hold up the process, and I certainly don't want my opinion
to be given undue weight against that of someone with the specific applicable
technical expertise that I lack.  If the choice is clear then go right ahead.

(This may sound like a petty retort but it's really not.  Trust me.)
scg
response 36 of 91: Mark Unseen   May 15 03:33 UTC 2000

I need to apologize for the tone of #32.  I really should know better than
to enter responses here while frustrated by lack of sleep at 4 am.

I'll send mail to Jared and get the ball rolling on this again.
jared
response 37 of 91: Mark Unseen   May 15 16:43 UTC 2000

temp isdn while waiting for dsl will not be a prob on our side.
dpc
response 38 of 91: Mark Unseen   May 19 19:56 UTC 2000

Voyager sounds like the best way to go to me.
devnull
response 39 of 91: Mark Unseen   May 20 23:23 UTC 2000

From what I've seen I get the distinct impression that Voyager is the best way
to go.

From what I've seen of DSL installations in Boston, some work perfectly,
and some have issues.  Knowing that we can get ISDN from Voyager until
the DSL line has been installed and tested has a lot of value.

Knowing competent people who can offer good support is valuable.  Apparently
grex knows people at Voyager who have a clue who we can actually talk to
when problems appear.  With speakeasy, grex would just be another random
customer quite likely, which generally doesn't lead to a good level of
support.

I'm not convinced that relying on InterNAP to do outsourced BGP4 multihoming
is all that horrible if they happen to be doing a competent job.  I deal
with maintaining the BGP4 config for a company of about 75 employees,
and I've occasionally wasted substantial amounts of time working around
uunet lossage.  Having someone else pick the optimal routing can have
its benefits in reducing the amount of attention needed.

That said, I'm not sure InterNAP does a great job; they seem to heavily
prefer sprint, which tends to heavily bias traffic between me and them
through MAE-EAST, even if I'm going from one point in Boston off of cent.net
to another point in Boston that's going through InterNAP.

As of a few months ago, speakeasy in Boston was sending all the traffic
through internap in seattle.  Now they're only sending Boston customer
traffic through New York on its way back to random things in Boston.
Speakeasy in Ann Arbor may or may not send all their traffic through Seattle.
scg
response 40 of 91: Mark Unseen   May 21 03:12 UTC 2000

(It's not an issue of optimal routing.  I'm convinced InterNAP can do pretty
well with that.  The issue I'm concerned about is a single point of failure,
and a lack of control over their own network.  With connections from multiple
providers, an ISP can just route around it when one of them has problems, and
it will route around it automatically if the connection goes down.  With a
connection to a single provider, all the ISP can do is fingerpoint.)
devnull
response 41 of 91: Mark Unseen   May 22 03:11 UTC 2000

I'm not especially familiar with exactly what internap does, but it seems
that internap is capable of setting things up so that their customers
have multiple redundant connections to internap, such that this shouldn't
necessarily be a problem.
scg
response 42 of 91: Mark Unseen   May 22 03:22 UTC 2000

Well, yes and no.  You can pull circuits to multiple InterNAP POPs, and if
one of the POPs goes down your connectivity will still be up.  You've still
got room for problems beyond your control, though.  A system wide software
update or configuration change could go wrong.  The billing could get screwed
up resulting in both connections getting cut off simultaniously.  The company
could hire incompetent engineering people, or get bought by somebody who
doesn't understand good network design, both of which have caused other
formerly good providers I've been paying attention to go down hill very
quickly.  Or, with a provider whose POPs are more interconnected with
themselves than InterNAP's are, a one or two line configuration screwup in
one router could take down large chunks of the network (although InterNAP's
architecture probably makes that significantly less likely).

Are any of these things likely to happen in this case on a regular basis? 
Probably not.  But getting redundant connectivity from different providers
and talking BGP over them is just basic good network design.  It's also easy
to see from the outside.  When you see somebody who isn't doing that,
generally they're cutting corners in many harder to see ways as well.
devnull
response 43 of 91: Mark Unseen   May 23 01:34 UTC 2000

OK, I'm willing to buy these arguments.

And certainly, a competent ISP really ought to have people who are capable
of dealing with setting up BGP4 anyway.
jared
response 44 of 91: Mark Unseen   Jun 12 17:53 UTC 2000

If there are network problems, I'm sure that Voyager will be contacted
about them.

Aside: the DSL line order is still being processed, but the ameritech
line has been ordered, but no due date is available yet.
jared
response 45 of 91: Mark Unseen   Jun 22 17:29 UTC 2000

That is still the case.  I've had us escalate with Covad three different times
now.  the "FOC" date was 6/9 and has long since passed.  I'm attempting
to get ISDN ready for you now.
jared
response 46 of 91: Mark Unseen   Jun 23 04:50 UTC 2000

Next BoD meeting, I should give a dsl update I suspect.
other
response 47 of 91: Mark Unseen   Jun 23 06:14 UTC 2000

Hopefully we'll have something in the way of an update somewhat before then...
jared
response 48 of 91: Mark Unseen   Jun 23 16:24 UTC 2000

The official issue is "problem obtaining line".

I'm on the phone with Covad right now attempting to get an update
on the order status.
other
response 49 of 91: Mark Unseen   Jun 23 16:38 UTC 2000

Thanks, Jared.  
jared
response 50 of 91: Mark Unseen   Jul 6 21:56 UTC 2000

Covad is still not giving a due date, and they are not able to provide
a line yet...

I've escalated the issue (again) in order to determine what can be done
to provide the DSL line.  Because of your short distance from the
Central Office, i would have never expected there to be any problems,
but I'm becoming amazed at the problems with getting your line.
 0-24   1-25   26-50   51-75   76-91      
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss