Rules

Rules & Regulations
This document contains IX Brighton Ltd (IXB)’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 IXB and are available to members on request.

Organisational Requirements

  • Members must publish their contact information to whom requests for peering at IXB should be sent.
  • Members must subscribe at least one e-mail address to either members@ixbrighton.net or announce@ixbrighton.net mailing lists
    Members must not carry out any illegal activity through IXB.
    Members must not circulate correspondence on confidential IXB mailing lists or any other IXB 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 IXB 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 port they are connected to IXB
  • Each member physical port (or LAG) must peer with the route collector on at least one of the public peering VLANs
  • Each public peering VLAN active on each member port must have a peering with the route collector
  • Members should announce the same set of routes to the collector that would be advertised to a regular peer across IXB.
  • Members must ensure that their use of IXB 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 IXB.
  • Cabling to IXB racks will only be run by contractors approved by IXB and always in accordance with the guidelines set by IXB and BDX.

Technical port and traffic requirements
Layer 1
IXB members must advise IXB of devices in the path between the IXB switch and the members Layer3 terminating device, for example media converters, or connections via third party ethernet providers (psuedowires).

Layer 2
All frames forwarded to a particular IXB port from a member must have the same source mac-address.
On no account should BPDUs be forwarded to a IXB port.

Members must ensure their equipment is configured in such a way that a frame received from a IXB port is never forwarded back to IXB

  • Member ports are configured as either single VLAN or multi VLAN ports Single VLAN ports
  • This is the default configuration
  • Port will be native in VLAN4

Multi VLAN ports

  • This is available on request, when participation in multiple VLANs is required
  • Members must choose between having either i) All VLANs – including VLAN 4, will be 802.1q tagged. or ii) The untagged VLAN will be VLAN 4, other VLANs are 802.1q tagged (ethertype 0x8100)
  • The member equipment must be capable of containing traffic sent to the member ports to only the VLANs the member is participating in, this excludes many Cisco desktop switches from being connected to multi VLAN ports, as they have no way to contain VLAN1 and VLAN1002-1005 traffic
  • The public peering VLANs and permitted ethertypes

VLAN 4 – IXB main peering LAN
0x0800 (IPv4) – must have a unicast destination mac
0x0806 (ARP) – must only reply to ARP requests for their assigned IPs on the peering lan
0x86dd (IPv6)