Technical Specifications

Ethernet Frame Format

AMR-IX requires that participants utilize only Ethernet Version 2, DIX Ethernet, or 802.3 framing for Ethernet frames transmitted across the IX switch fabric.

Ethernet Data Types

While the IX does not prohibit any Ethernet Data Type, 0x0800 (Internet Protocol version 4, or IPv4), 0x86dd (Internet Protocol version 6, or IPv6), and 0x0806 (Address Resolution Protocol, or ARP) are explicitly recognized as the Data Types most frequently used, and any others may be subject to special scrutiny by the Governing Board.

Maximum Transmission Unit

All Participants must explicitly set a Maximum Transmission Unit (MTU) of 9000 bytes on any interface facing AMR-IX switch fabric.

Broadcast Traffic

Broadcast traffic may not transmitted on AMR-IX switch fabric except for ARP, IPv6 Neighbor Solicitation, and as required for multicast transmission.

Participant Port Congestion Management

Because the commonly-used five-minute average traffic statistics mask congestion-causing microbursts of traffic, Participant ports peaking above 85% average utilization within any five-minute period in any three consecutive days shall receive additional or larger AMR-IX core switch ports as necessary to bring the peak utilization below the upgrade threshold, and the Participant shall be obligated to use those ports to increase interconnection bandwidth to their network at their own cost. Responsible Participants will proactively monitor traffic levels and anticipate the need for such upgrades.

If port congestion results in packet loss, the Governing Board may release this information in response to requests from other Participants. Members may gather statistics from their router's interface, but will not have access to the IX switch or interfaces.

MAC Address Limitation

Participants may utilize a single layer-2 MAC address to connect a single layer-3 router to each port or LAG group allocated to them by the Governing Board. Change of MAC address (such as due to the replacement of Participants’ router) may require explicit notification to the Governing Board. Any need for multiple MAC addresses on the same port or LAG group must be addressed through the Switch Fabric Extension policy.

Quarantine

Upon initial connection and subsequently if they deem necessary, the Governing Board may place a Participant’s port into a separate “quarantine” VLAN for diagnostic purposes or to verify policy-compliant operation.

Next Hop Self

In order to prevent the propagation of third-party routes, participants must set NEXT_HOP_SELF on all routes advertised through AMR-IX.

Public Autonomous System Numbers

Participants shall use public Autonomous System Numbers allocated uniquely to them by a Regional Internet Registry. Participants may not use private, reserved-range Autonomous System Numbers.

Routing Aggregation

Participants are encouraged to aggregate their IP prefix announcements into the fewest prefixes feasible, in accordance with best practices. Disaggregation for purposes of “traffic management” places a burden on peers and the rest of the network and creates a detrimental externality.

Prefixes Advertised

All IP prefixes advertised at AMR-IX must be delegated for unique use by a Regional Internet Registry, and the Participant advertising them must have the legal right to do so clearly conferred to them by the current registrant.

No Broadcast Protocols

In order to reduce unnecessary broadcast traffic, Participants must disable Interior Gateway Protocols, service discovery protocols, and other broadcast protocols toward AMR-IX. Participants must filter IP directed broadcast packets addressed to the IX broadcast addresses before they reach the IX peering subnets.

No Pointing default

Participants may not direct traffic to others unless it has been solicited via the routing announcement of a matching prefix directly to the Participant or via a commonly agreed-upon route server.

No Redistribution of the IXP Prefixes

Participants may not propagate the IXP IPv4 or IPv6 peering prefixes in any routing protocol. AMR-IX suggests that Participants set Next-Hop-Self towards peers within their own AS, in order to avoid having to carry the IXP prefixes as next-hops for their iBGP internal peers.

No Transit Through the Switch

While the Participants hope that AMR-IX will serve as a marketplace for diverse Internet services in AMR-IX, the IX switch fabric itself is a constrained and shared resource. In order to avoid a tragedy of the commons, the Participants agree to not provide IP transit service across the switch. Instead, IP transit services should be provided across other media, such as private crossconnects.

No Transport Through the Switch

Participants shall not routinely exchange traffic between ports under their own control.

Become a Member

Membership is open to any organization with an AS number and IP space