Madison Internet eXchange Peering Point - MadIX
UW-Madison DoIT Network Services established the MADison Internet eXchange (MadIX) in early 2000 as a means for local network providers to peer in Madison, WI.
|A provider can peer at MadIX at the following exchange points:||You can get connected to the exchange via the following institutions which have high speed circuit capability at 222 West Washington (preferred) or the UW Data Center:|
In order to join one of the MadIX locations for peering, the following is required of the ISP:
- A registered BGP Autonomous System number.
- Ethernet Connectivity into one of the locations listed above.
- Commitment to provide and update technical contact information.
Our v4 subnet is 126.96.36.199/27
Our v6 subnet is 2607:f388:0:2200::/64
Contact Network Services to become a MadIX member via Email. You will need to provide your AS Number, ISP name, Contact Phone Number and indicate which of the locations in the Overview section you want to peer at.
A mailing list has been set up for supporting NOC notifications, and populated with the support information below. Only the addresses subscribed to the list may post to the list. Usage of the list is restricted to outage and related notifications. This list is notfor peering coordination nor general-purpose discussion.
- Mailing list: madix-notifications at lists.wisc.edu
- To subscribe: join-madix-notifications at lists.wisc.edu
- To email the list maintainer: owner-madix-notifications at lists.wisc.edu
The following Table shows the current members and how to contact them to arrange peering:
|Name||BGP AS||V4||V4 mcast||V4 BFD||V6||V6 BFD||Peering Email||Peering Phone||Support Email||Support Phone|
note: serviced by AS3128.
Please peer with AS3128.
|TDS Telecom||4181||188.8.131.52||::email@example.com||Kevin Roberts 608-664-4690|
Brad Fick 608-664-4667
|SupraNet||4150||184.108.40.206||YES||YES||::5||YESfirstname.lastname@example.org||(608) email@example.com||(608) 836-0282|
|UW System Network||3128||220.127.116.11||YES||::3||YESfirstname.lastname@example.orgemail@example.com||608-263-4188|
|Netwurx||26785||18.104.22.168||YES||::4||Adam St. George|
|Mad City Broadband||5683||22.214.171.124||YES||::8||YESfirstname.lastname@example.org||(608) email@example.com||(608) 836-0282|
|Bug Tussel Wireless|
|(608) firstname.lastname@example.org||(920) 940-0001|
|Multicast Monitoring Port||126.96.36.199|| David Treptow|
|email@example.com||608-634-3136 Ext: 264|
|Hurricane Electric||6939||188.8.131.52||::Bfirstname.lastname@example.org||(510) email@example.com||(510) 580-4100|
|Akamai||via 2381||Contact firstname.lastname@example.org for details|
|Netflix||via 2381||Contact email@example.com for details|
Evaluation of Open-IX Technical Requirements
The Open-IX Association has put together a list of technical requirements to standardize IXP offerings.
The below table outlines a comparison of MadIX with these requirements.
|Public exchange vlan||Available!|
|Private vlan||Available! (just ask)|
|ethertype 0x0800||Yes, we allow legacy ethertypes.|
|ethertype 0x86dd||No problem.|
|ethertype 0x8606||Yes, we allow legacy ethertypes.|
|ipv4 multicast filtering||We can support v4 multicast, and we do IGMP & PIM snooping.|
|ipv6 multicast filtering||Not supported (yet). MLD snooping is not currently enabled.|
|customer demarc||The port on our switch at 222. The cabling is yours, but we prefer minimally to help dress the cables in the common area and into our cage. At the CS datacenter, the demarc is on your equipment (our a demarc panel you provide) and we will take it from there.|
|non-oversubscribed switching backplane||4500x|
|inter-switch congestion||There is a 20G etherchannel between the two switches which is congestion free.|
|inter-switch path diversity||The 20G etherchannel between the two switches is provisioned as a 10G on each side of UW's metro ring.|
|redundant power feeds||The switch at 222 has a minimum 4 hour of battery runtime, backed by a generator circuit provided from 5nines, and a building power source from Fiore. The UW CS datacenter has multiple power feeds backed by 30min of battery, n+1 natural gas generators with 2 days of diesel reserves on-site.|
|Measures implemented to overcome single component failures||See above. Let us know if you have any questions & we can try to clarify.|
|PI address space from an RIR||UW-Madison address space is currently in use. UW does not have plans to change this, but if you want to help MadIX acquire new space, then by all means let's get in touch.|
|Route server||None. You're on your own.|
|NOC contact information||See above contact info table. UW-Madison runs the IXP operations.|
|Service-affecting maintenance announcements||See above info on email notifications. UW-Madison's internal procedures call for a minimum of 2 business day notification on service affecting maintenance. In reality, we typically announce this much further in advance (plus we can negotiate the window).|
|Monitoring||The UW NOC monitors MadIX for performance degradation and service affecting events.|
|Procedure for performance degradation event notifications||In most cases the NOC typically will use the email list above. If something affects only one participant, then only they may be notified.|
|Participants & AS numbers||See above table.|
|Traffic statistics.||See above links. We have a total bit/sec summary as well as per-participant stats for various metrics.|
|Website where the Open-IX standards are addressed.||You are looking at it.|
|Entry in a directory||We are on PeeringDB here.|