Public
Child pages
  • Technical Policy

Versions Compared

Old Version 4

changes.mady.by.user Nishal Goburdhan

Saved on

compared with

New Version Current

changes.mady.by.user Nishal Goburdhan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. BGP-4 or successor is used for peering and peers must set NEXT_HOP_SELF if advertising routes from other INX participants.
  2. Broadcast traffic may not delivered to the exchange, except as needed for normal operation and troubleshootingdebugging.
  3. We operate a Unicast unicast fabric;  multicast except for regular IPv6 operations is not permitted.
  4. Participants should ensure that only a single MAC address is visible via their ports, unless they are a reseller, and have made prior arrangements with the Ops team
  5. Mac addressed are hard-coded to peer ports.
  6. Participants may not point default or otherwise use another participant's resources without permission.
  7. Peering is bilateral with the exception of the route server serviceBGP Route Servers service.  Peers are encouraged to setup their own bilateral sessions where appropriate.
  8. Participants may not sniff traffic between other participants.
  9. No participant may have access to the SNMP community string strings for the INX switches unless cleared to do so by the INX management committee.
  10. Peer are expected to respond timeously to concerns raised by the Ops team.  Non response may result in ports being disabled.