NYIIX-Requirements-Wavy-Lines-Graphic

NYIIX REQUIREMENTS

Ensuring a Stable Environment for All Peering Members

To ensure the NYIIX exchanges will provide stable and reliable service, TELEHOUSE must insist that all members follow the requirements described below.

TELEHOUSE reserves the right to disable ports that violate the requirements.

JOIN NYIIX TODAY!

NYIIX Allowed Traffic

1. Physical Layer

Ethernet interfaces attached to the NYIIX shall be explicitly configured with duplex and speed and shall not be auto-sensing.

2. MAC Layer

Frames forwarded to the NYIIX ports shall have one of the following ethertypes:

  • 0x0800 – IPv4
  • 0x0806 – ARP
  • 0x86dd – IPv6

Only one MAC source address shall be used on each port allocated to you on the NYIIX.

  • Members shall not connect equipment with MAC-layer switching or bridging capabilities to more than one port on the NYIIX/LAIIX.
  • Member shall not connect equipment with MAC-layer switching or bridging capabilities if member opt for trunk configuration (Etherchannel) or 802.3ad configuration. Trunk configuration shall be granted only for Layer 3 equipment.
  • Member shall disclose the configuration of equipment with MAC-layer switching or bridging capabilities if the equipment has/will have private connections to other NYIIX members in order to verify that there is/will be no possible MAC-layer loop.
  • Frames forwarded to the NYIIX ports shall not be addressed to a multicast or broadcast MAC destination address except as follows or unless otherwise designated for multicast use by TELEHOUSE.
    • ARP
    • IPv6 ND

Traffic for link-local protocols shall not be forwarded to the NYIIX ports except for the following:

  • ARP
  • IPv6 ND

Link-local protocols include but are not limited to:

  • IRDP
  • ICMP redirects
  • IEEE802 Spanning Tree
  • Vendor proprietary protocols (e.g. CDP, EDP, MOP, DTP)
  • Interior routing protocol broadcasts (e.g. OSPF, ISIS, IGRP, EIGRP)
  • BOOTP/DHCP
  • Member must disable Proxy ARP on all interfaces connected to the NYIIX.
  • All interfaces on member’s equipment that are connected to the NYIIX shall only use those VLAN tags assigned by TELEHOUSE in conformance with the IEEE 802.1q standard if the VLAN tags are needed.

3. IP Layer

• All IP interfaces on member’s equipment that are connected to the NYIIX shall only use IP addresses assigned by TELEHOUSE (IPv4, IPv6)  for NYIIX.

• Each IP interface on member’s equipment that are connected to the NYIIX must have network masks set to include the entire NYIIX as specified by TELEHOUSE (IPv4) and (IPv6).

• All exchange of routes across the NYIIX network shall be via BGP4(+).

• Each member must have a unique Autonomous System number (ASN) assigned by the ICANN-designated Regional Internet Registry.

• IP address spaces assigned to the NYIIX/LAIIX peering LAN shall not be advertised to other networks without explicit permission of the NYIIX/LAIIX.

4. Broadcast/Multicast

Members shall keep the amount of broadcast and multicast to a minimum. Members shall not ping or keep BGP sessions with non-existing members.

5. Connection to the production switch

• Members shall not be connected to the production switch until the technical requirements specified above are met.

• In the event that Member changes the configuration of the equipment attached to the NYIIX, TELEHOUSE may repeat the activation procedure to see if the Member meets the technical requirements specified above.

These requirements are put in place to minimize the risk of potential instability to the peering environment

No-export of NYIIX peering LAN

IP address space assigned to NYIIX Peering LANs shall not be advertised to other networks without explicit permission of Telehouse America.

Learn More About NYIIX Requirements and Join Today.

Enter your email to get in touch or find out more.

  • When submitting your email address you will be contacted by our marketing team to discuss your interest in our services. Your information will be used and protected as outlined in our Privacy Policy.
  • This field is for validation purposes and should be left unchanged.