MANXIX RULES & REQUIREMENTS

Rules and Requirements

This document contains ManxIX's rules and regulations which members must follow. They should be read in conjunction with the Memorandum & Articles of Association which govern members' relationship with ManxIX and are available to members on request.

Organisational Requirements

  • Members must publish their contact information to whom requests for peering at ManxIX should be sent.
  • Members must subscribe at least one e-mail address to either members@manxix.im or announcements@manxix.im mailing lists.
  • Members must not carry out any illegal activity through ManxIX.
  • Members must not circulate correspondence on confidential ManxIX mailing lists or any other ManxIX confidential information to non-members.

Technical Requirements

  • Members must have an Autonomous System number registered with RIPE or other appropriate authority.
  • All networks announced at ManxIX must be registered with RIPE or other appropriate authority.
  • Members must not proxy-arp on any peering VLANs.
  • Members must only respond to ARP requests for addresses which they have been assigned.
  • Members must only present one source mac-address on any one physical connection they are connected to ManxIX via. (Aggregated LAG ports are considered to be one connection.)
  • Each member physical port (or LAG) must peer with the route collector.
  • Members should announce the same set of routes to the collector that would be advertised to a regular peer across ManxIX.
  • Members must ensure that their use of ManxIX is not detrimental to the use made by other Members.
  • Members must not install 'sniffers' or similar devices in an attempt to monitor traffic passing through ManxIX.
  • Cabling to ManxIX racks will only be run by contractors approved by ManxIX and always in accordance with the guidelines set by ManxIX.

Technical port and traffic requirements

Layer 1

ManxIX members must advise ManxIX of devices in the path between the ManxIX switch and the member’s Layer 3 terminating device, for example media converters, switches, or connections via third party ethernet providers (psuedowires).

Layer 2

All frames forwarded to a particular ManxIX port from a member must have the same source mac-address. On no account should BPDUs be forwarded to a ManxIX port. Members must ensure their equipment is configured in such a way that a frame received from a ManxIX port is never forwarded back to ManxIX. Interfaces must be configured in untagged access mode. No tagged traffic will be accepted.

< BACK TO MAIN PAGE