Date: Sun, 25 Mar 2007 20:57:23 -0800 From: Tony Lum Subject: RE: SIX connection details Hi Chris/Troy, thanks you for the info. This is my letter to SIX for extension connection approval. Please post for comments and keep me posted of any questions needed my attention. " Pursuant to the SIX Switch Interconnection Policy obtained on July 24, 2006 from http://www.seattleix.net/rules.htm, Tony Lum of Cipherkey requests agreement from the SIX board to interconnect a Layer 2 device to the SIX fabric. The purpose of this connection will be to enable Layer 2 connectivity to the SIX exchange for Cipherkey, and other providers located in Vancouver, Canada in the future. This will be accomplished through a Gigabit Ethernet port attached to the exchange that does not have any MAC restrictions. The directly connected device, a Cisco Catalyst 6500/SUP2, will bridge participants in Vancouver, Canada over a Gigabit Ethernet link to a Cisco Catalyst 6500/SUP2 in Vancouver. Remote SIX port access speeds will be both Fast and Gigabit Ethernet, but packet forwarding to SIX participants will be provided on a VLAN configured for the purpose, as the 6500 device in Vancouver is used to provide other services to potential SIX participants, including local peering (which will be done over a different VLAN on the same trunk). Administrative control over all devices in the network will be held solely by personnel at Cipherkey. To ensure continued stability of the exchange, all trunk ports of the SIX remote switch will be filtered so as to only give access to approved SIX participants. Additionally, the VLAN itself will not be bridged to any other VLAN, and will have VLAN Access Control Lists setup with the following Cisco IOS command template on all involved switches: mac access-list extended SIXACL permit host A.A.A any permit any host A.A.A permit host B.B.B any permit any host B.B.B ! ! vlan access-map SIXMAP 10 match mac address SIXACL action forward ! Note that this configuration requires that remote peering participants provide Cipherkey with the MAC address of their peer, and packets to/from MAC addresses not within that list will not be forwarded. Care will be taken to ensure all remote peering participants meet all current and future SIX interconnection requirements. Today, only Cipherkey, Metrobridge, Data Fortress, and Skyway West are extension peers, and all are located in Vancouver, Canada. There is one exception: a subdivision of Metrobridge in Phoenix, AZ that would connect in Seattle directly to the Cipherkey 6509 there. " thanks tony