Draft AUP

[Sematimba Noah K <ksemat@eahd.or.ug>]

Sorry I have taken too long with this. Anyway here comes the draft AUP that I 
promised. I have adapted it from a number of sources and thus it needs editing 
to fit our needs. Please read through and submnit your comments.

Technical Guidelines:
 

1.   Members may only connect equipment that is owned and operated by that 
member to the UIXP. Members may not connect equipment to the UIXP on behalf of 
third parties. 

2.   Members must only use IP addresses on the interface(s) of their router(s) 
connected to the UIXP allocated to them by the UIXP. 

3.   Members may only present a single MAC address to any individual UIXP port 
that is allocated to them. 

4. Subscribers will make use of a unique Autonomous System Number assigned by a 
suitable registration authority. As of this writing, the top-level registration 
authority in the world is the InterNIC. Details on obtaining an Autonomous 
System Number are available at the following URL: 
ftp://rs.internic.net/templates/asn-template.txt 

5.   Peering between Members' routers across the UIXP will be via BGP-4. 

6. Members shall not generate unnecessary route flap, or advertise 
unnecessarily specific routes in peering sessions with other Members across the 
UIXP. 

7.   Members may not advertise routes with a next-hop other than that of their 
own routers without the prior written permission of the advertised party, the 
advertisee, and the UIXP. 

8.   Members may not forward traffic across the UIXP unless either the traffic 
follows a route advertised in a peering session at the UIXP or where prior 
written permission of the Member to whom the traffic is forwarded has been 
given. 

9.   Members must, on all interfaces connected to the UIXP, disable: Proxy ARP, 
ICMP redirects, CDP, IRDP, Directed broadcasts, IEEE802 Spanning Tree, Interior 
routing protocol broadcasts, and all other MAC layer broadcasts except ARP. 

10. Members must, on all interfaces connected to the UIXP, disable any duplex, 
speed, or other link parameter auto-sensing.

11. Members shall not announce ("leak") prefixes including some or all of the 
UIXP peering LAN to other networks without explicit permission of the UIXP. 

12. Members must set net masks on all interfaces connected to the UIXP to 
include the entire UIXP peering LAN. 

13. Any equipment and/or cabling installed by a Member at the UIXP must be 
clearly labeled as belonging to the Member. 

14. Members will not touch equipment and/or cabling owned by other Members and 
installed at the UIXP or in the room containing the UIXP without the explicit 
permission of the Member who owns the equipment. 

15. Members will not install 'sniffers' to monitor traffic passing through the 
UIXP, except through their own ports. The UIXP may monitor any port but will 
keep any information gathered confidential, except where required by law or 
where the UIXP has determined a violation of this Memorandum of Understanding. 

16.Members will not circulate confidential correspondence on the UIXP mailing 
lists to non-Members. 
 
17. Members must ensure that their usage of the UIXP is not detrimental to the 
usage of the UIXP by other Members. 

18. Members may not connect more than two wide-area circuits to routers housed 
at the UIXP. This restriction may be overridden on a per-case basis at the 
discretion of the UIXP. 

19. Members may not directly connect customers who are not UIXP Members via 
circuits to their router housed in any UIXP rack. 

20. Members should not routinely use the UIXP for carrying traffic between 
their own routers.

21. Members will be required to install routers that support the full BGP-4 
standard. A list of recommended routers will be made available online.

22.The technical committee will set up certain monitoring features on the 
server at the UIXP.  Certain UIXP Members will be asked to have their ops 
departments monitor these features such that any problems can be referred to 
the UIXP technical support personnel as quickly as possible. 

23.Subscribers will use a standard framing mechanism. For Ethernet connections, 
the framing is specified in RFC 894. Reference URL: ftp://ftp.isi.edu/in-
notes/rfc894.txt 

24.Changes in this policy shall be made through a majority vote of the 
participants at any annual or special meetings. 



--------------------------------------------------------------------------------

Noah.

--
This is the techies mailing list. The list archives can be found at http://uixp.co.ug/archives .