Last update: 22-Jan-2018
These Technical Requirements (TR) define the ways in which you may or may not make use of the MMIX services. This document will be regularly reviewed and revised in the light of operational experience to ensure maximum protection of service to MMIX members.
- Ethernet interfaces attached to MMIX ports shall be explicitly configured with duplex, speed and other configuration settings. And it shall not be auto-sensing.
- Only specified ethertypes are allowed on the MMIX VLANs. The policy is enforced with a VACL configured on the MMIX switches.
- The following ethertypes are allowed:
- 0x0800: IPv4
- 0x0806: ARP
- 0x86dd: IPv6
- Frames with any other ethertypes are dropped on MMIX switch ingress.
- All frames of a service forwarded to an individual MMIX port shall have the same source MAC address.
- Interfaces connected to MMIX ports shall only use IP addresses and netmasks (prefix lengths) assigned to them by MMIX. In particular:
- IPv6 addresses (link & global scope) shall be explicitly configured and not auto-configured
- IPv6 site-local addresses shall not be used
- Standard IP MTU size = 1500
- All exchange of routes across the MMIX network shall be via BGP4(+).
- AS numbers used in BGP4(+) sessions across the MMIX network shall not be from range reserved for private use.
- All routes advertised shall be aggregated as far as possible.
- IP address space assigned to MMIX peering LAN shall not be advertised to other networks without explicit permission of MMIX.
- All routes to be advertised in a peering session across MMIX shall be registered in the APNIC or other public routing registry.
- Traffic shall only be forwarded to a MMIX member when permission has been given by the receiving member either:
- by advertising a route across the MMIX network (directly or via the route server)
- or explicitly in writing
- Traffic shall not be routinely exchanged between two MMIX ports owned by the same MMIX member.