Just curious to know who's exchanging traffic at MAE NY? If I am to
believe what I see at www.mae.net, there's only two networks connected
there, which would make it a pretty ineffective exchange point. With
Pennsauken closed to new connections (anyone got extra rack space there?),
I'd like to investigate an alternative for that area.
Brian
The NY-IIX is beginning to become interesting, hosted by Telehouse at 25
Broadway.
10.160.32.198.IN-ADDR.ARPA domain name pointer nyiix1.wisper.net
11.160.32.198.IN-ADDR.ARPA domain name pointer iix-1.router.demon.net
12.160.32.198.IN-ADDR.ARPA domain name pointer iix.lightning.net
13.160.32.198.IN-ADDR.ARPA domain name pointer e1.nyc1gw1.us.insnet.net
14.160.32.198.IN-ADDR.ARPA domain name pointer nyc-2.nildram.net
15.160.32.198.IN-ADDR.ARPA domain name pointer IIX.TELEHOUSE1.NEW-YORK.NET
16.160.32.198.IN-ADDR.ARPA domain name pointer mori-e3.newyork.wirehub.net
17.160.32.198.IN-ADDR.ARPA domain name pointer gs0709-e0-0.tel.usa.quza.net
18.160.32.198.IN-ADDR.ARPA domain name pointer f1-1.gw3.nyc.globecomm.net
19.160.32.198.IN-ADDR.ARPA domain name pointer core0.nyiix.int-core.us.ipf.net
20.160.32.198.IN-ADDR.ARPA domain name pointer nac-nyiix-10Mb.nac.net
21.160.32.198.IN-ADDR.ARPA domain name pointer fddi-00.nyiix.us.internetfci.net
Lots of Euro-stuff.
Just curious to know who's exchanging traffic at MAE NY? If I am to
believe what I see at www.mae.net, there's only two networks connected
there, which would make it a pretty ineffective exchange point. With
Pennsauken closed to new connections (anyone got extra rack space there?),
I'd like to investigate an alternative for that area.Brian
---
Brian Horvitz
Shore.Net
Network Engineering
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
ISPF, The Forum for ISPs by ISPs. October 26-28, 1998, Atlanta, GA.
Three days of clues, news, and views from the industry's best and
brightest. http://www.ispf.com/ for information and registration.
Atheism is a non-prophet organization. I route, therefore I am.
Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member
Father of the Network and Head Bottle-Washer
Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834
Don't choose a spineless ISP; we have more backbone! http://www.nac.net
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
As another member of the IIX, I just wanna chime in...It's nice to be able to
exchange traffic without MFS. 
Reid
The NY-IIX is beginning to become interesting, hosted by Telehouse at 25
Broadway.10.160.32.198.IN-ADDR.ARPA domain name pointer nyiix1.wisper.net
11.160.32.198.IN-ADDR.ARPA domain name pointer iix-1.router.demon.net
12.160.32.198.IN-ADDR.ARPA domain name pointer iix.lightning.net
13.160.32.198.IN-ADDR.ARPA domain name pointer e1.nyc1gw1.us.insnet.net
14.160.32.198.IN-ADDR.ARPA domain name pointer nyc-2.nildram.net
15.160.32.198.IN-ADDR.ARPA domain name pointer IIX.TELEHOUSE1.NEW-YORK.NET
16.160.32.198.IN-ADDR.ARPA domain name pointer mori-e3.newyork.wirehub.net
17.160.32.198.IN-ADDR.ARPA domain name pointer gs0709-e0-0.tel.usa.quza.net
18.160.32.198.IN-ADDR.ARPA domain name pointer f1-1.gw3.nyc.globecomm.net
19.160.32.198.IN-ADDR.ARPA domain name pointer core0.nyiix.int-core.us.ipf.net
20.160.32.198.IN-ADDR.ARPA domain name pointer nac-nyiix-10Mb.nac.net
21.160.32.198.IN-ADDR.ARPA domain name pointer
As another member of the IIX, I just wanna chime in...It's nice to be able
to exchange traffic without MFS.
what's really nice is that they maintain mfs's high temperature standards
too. 
randy
Really?
core1.nyc>sho env all
Temperature readings:
chassis inlet measured at 26C/78F
chassis outlet 1 measured at 28C/82F
chassis outlet 2 measured at 35C/95F
chassis outlet 3 measured at 44C/111F
78F in my cabinet in the inlet seems reasonable to me.
Even my AGS is happy:
nyc7>sho env
Environmental controller firmware version 2.0
Serial number is 00230621, calibrated on 6-21-91, by technician jj
Internal temperature measured 25.4(C), shuts down at 43.0(C)
> As another member of the IIX, I just wanna chime in...It's nice to be able
> to exchange traffic without MFS.what's really nice is that they maintain mfs's high temperature standards
too.randy
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
ISPF, The Forum for ISPs by ISPs. October 26-28, 1998, Atlanta, GA.
Three days of clues, news, and views from the industry's best and
brightest. http://www.ispf.com/ for information and registration.
Atheism is a non-prophet organization. I route, therefore I am.
Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member
Father of the Network and Head Bottle-Washer
Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834
Don't choose a spineless ISP; we have more backbone! http://www.nac.net
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Well, I'm more than happy to avoid it altogether but, I want to have three
NAPs in my future, not just two. Unless of course, we can all get over
the "I'll peer at three NAPs or not at all" mentality (no Randy, that's
not directed at you, this just happens to be the one I replied to) that
many of us seem to have.
Brian
Well, I'm more than happy to avoid it altogether but, I want to have three
NAPs in my future, not just two. Unless of course, we can all get over
the "I'll peer at three NAPs or not at all" mentality
i should not speak for others, but i think that being at both coasts, with
sufficient bandwidth between to handle the potatoes, is more important than
at how many points one is present. most peers just don't want to haul your
traffic across the country on their nickel.
no Randy, that's not directed at you
hey, we're peering slu..., ooops, have enriched peering. 
randy
I should certainly agree. But, having been through this before, I know I
have to deal with silly policies which don't apply to all situations. My
traffic is entirely NE regional right now. I think I'm being a hell of a
sport by delivering it down to say MAE East and AADS or something like
that. When I have that established, and someone then comes back and tells
me that they won't peer just because I don't have a West coast presence, I
think that's rediculous.
Brian
I should certainly agree. But, having been through this before, I know I
have to deal with silly policies which don't apply to all situations. My
traffic is entirely NE regional right now.
i very much doubt this. your traffic is world-wide. the people who pay you
just happen to be only in the US NE. and this mis-conception is the basis
of your problem.
I think I'm being a hell of a sport by delivering it down to say MAE East
and AADS or something like that. When I have that established, and
someone then comes back and tells me that they won't peer just because I
don't have a West coast presence, I think that's rediculous.
the counter-argument would go something like this
so, you think it is fine for me to pay to carry your traffic across
the country.
then parallel logic says that we all should also think it fine if you
pay to carry our traffic across the country. please install a cross-
country link and peer on both coasts.
this is called hot potato, and is the general practice. check the meaning
of 'peer' in the dictionary.
i suspect that the airlines do not consider you 'a heck of a sport' because
you drove to the airport, and are 'ridiculous' enough to want to charge you
for a plane ticket to san francisco.
randy
Let's try to ignore my poor wording (like NE regional traffic) because we
both know what I'm talking about.
I guess the way people respond to this sort of thing depends on their
motivations. Since I'm in the business of providing a service, I want to
provide the best service possible to my customers. So, let's look at my
customer who wants to send a packet to your network. Right now, it leaves
my network, travels over one of the super-mega-conglomo backbone
providers which I'm connected to, and then gets to your network. Now, if
in the interest of bettering that, I throw a couple of T3s in to the NAPs
I can get to, and directly peer with your network in those places, we all
of a sudden have greatly increased performance in both directions. Thus,
I have happier customers. Now since on my network, inbound and outbound
traffic are almost the same, your customers should also enjoy the same
increased performance as mine. Also, by virtue of the fact that my only
"upstream" connections are in Boston, if you are peered with any of those
other providers, they will dump the packets onto your network as close to
Boston as they can. If I'm good enough to bring them half way across the
country, I'm doing you a favor while helping myself.
Brian
I guess the way people respond to this sort of thing depends on their
motivations. Since I'm in the business of providing a service, I want to
provide the best service possible to my customers. So, let's look at my
customer who wants to send a packet to your network. Right now, it leaves
my network, travels over one of the super-mega-conglomo backbone
providers which I'm connected to, and then gets to your network. Now, if
in the interest of bettering that, I throw a couple of T3s in to the NAPs
I can get to, and directly peer with your network in those places, we all
of a sudden have greatly increased performance in both directions. Thus,
I have happier customers. Now since on my network, inbound and outbound
traffic are almost the same, your customers should also enjoy the same
increased performance as mine.
only one problem. i am paying more than you. clearly this does not
disturb you. so, tell you what, you can meet folk at both coasts or pay
your upstream to get to them, and then we're all equal.
tanstaafl.
randy