PIT Miami LATAM Interconnection HUB

Technical Info

Traffic guidelines on the peering LAN.

The peering LAN is reserved for exchange traffic and control traffic required for peering. Participants are expected to keep the fabric stable, predictable and secure.

TopologyDistributed Layer 2 exchange fabric. Interface and CablingSupported optics and handoffs. Traffic GuidelinesAllowed traffic and operational expectations. Route ServerBIRD 2 multilateral peering details.

Allowed Traffic

  • IPv4 and IPv6 unicast traffic exchanged between consenting peers.
  • ARP and IPv6 Neighbor Discovery required for the peering LAN.
  • BGP sessions with bilateral peers and optional route servers.
  • Operational testing traffic coordinated with PIT Miami when needed.

Not Allowed

  • Traffic that disrupts IXP stability, including floods or attacks.
  • Spoofed source addresses, unauthorized prefixes or route leaks.
  • Layer 2 protocols not required for peering, such as STP, LLDP or CDP.
  • DHCP, non-peering multicast, unsolicited broadcast or non-IP payloads.

Operational expectations.

  • Maintain accurate IRR records and use RPKI where available.
  • Announce only authorized, publicly routable prefixes.
  • Keep technical and NOC contacts current for incident response.
  • Coordinate maintenance or unusual testing with PIT Miami operations.