The participants.html web page is out-of-date. Given this is a
volunteer-run exchange, I've done a bunch of updating work myself. (See
the attachment.) I believe I have everything current and complete,
except as noted below.
This originally started because I wanted looking glass addresses listed.
I've since changed my thinking on that. If you list a looking glass in
your
peeringdb.com entry,
bgp.he.net (to which we already link) picks
that up automatically. This saves us from having to maintain that data
on the MICE participants page.
Accordingly, I'd like to urge Visi to create a
peeringdb.com record and
list their Looking Glass URL. (No shaming implied... I don't have a
looking glass running... yet.)
Should the MICE AS have a
peeringdb.com entry? We could list the route
server there, for the same reason.
Is there value in linking to the respective
peeringdb.com links? If so,
should the anchor text be the carrier's name, or a new column?
We are still missing contacts for these networks:
South Dakota Networks
Dakota Carrier Network
Northern Lights GigaPoP
Compudyne
MyTelepath
Genesis Wireless/RevNetData
Jaguar Communications
NU Telecom
Dakota Carrier Network was assigned two IPv4 addresses, but only one
IPv6 address. I assume the IPv6 assignment was an oversight.
Is Hurricane Electric still planning to upgrade to 10Gig? I see they
have both 1Gig and 10Gig ports assigned.
Richard
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<participants.html>