ANI IX - Delhi

Joining any ANI IX India Internet Exchange is straightforward. We keep the tactic simple and legal to urge started with our Peering Services. You merely need to submit the duly filled, signed & stamped copy of ANI IX Customer Agreement. Remaining documents might be used for your references. If you've more query regarding procedures and documentation get in-tuned with us. Apart from providing Public Peering ports, ANI-IX is additionally very supportive in getting our members optimal routing and peering relations over that port. ANI IX aims to make sure the Members reliable and uninterrupted Service also on limit the risks of deliberate or accidental mistakes, defective equipment or lack of speed of certain Member to reflect the standard of the others. According to this subsequent restrictions and rules apply:

MAC Layer

1. ANI IX PHYSICAL INTERFACES and MEMBERS PHYSICAL INTERFACES shall add full-duplex regime.
2. Frames forwarded to ANI IX ports shall have one among subsequent ethertypes: – 0x0800 – IPv4
– 0x0806 – ARP
– 0x86dd – IPv6
and restricts all other ethertypes. 3. just one MAC address is allowed on a service port and every one traffic originating from this port should accompany an equivalent source MAC address, otherwise traffic are becoming to be discarded. In case of VLAN Interconnect service, we allow one MAC address per VLAN ID.
4. Frames forwarded to ANI IX ports shall not be addressed to a multicast or broadcast MAC destination address except as follows: – broadcast ARP (Address Resolution Protocol) packages
– multicast IPv6 Neighbor Discovery (ND) packages
5. Maximum broadcast packages forwarded from the MEMBER’S equipment must not exceed 50 (fifty) in number per second per PHYSICAL INTERFACE.
6. Members shall not announce to the ROUTE SERVERS IP address space reserved for personal networks (Private IPs).
7. Members shall not announce to the ROUTE SERVERS AS numbers reserved for personal use (Private AS).
8. The Member must aggregate as far as possible the announced prefixes (MEMBER ADDRESS SPACE).
The smallest block of IP address allowed to be announced is /24 (256 IP addresses). It is shall to not use Spanning Tree Protocol enabled on a port connected to ANI-IX It is not allowed to use proxy ARP enabled on a router port connected to ANI-IX. NOTE: don't advertise the whole routing table to us, we'd like your DNS IP Pools and user IP Pools only!
9. ANI IX can limit the general public PEERING traffic in both directions (source and destination), when source or destination IP address space is not the space of the announced prefixes by the Member to route servers
10. For the aim of monitoring on ANI IX site, Members shouldn't forbid ICMP (Internet Control Message Protocol) communication from/to ANI IX IP address space.
11. ANI IX has implemented Quarantine VLAN. Аll new ports are placed in their own separate VLAN, in conjunction with a monitor port.

IP Layer

1. Interfaces connected to ANI IX ports shall not use IP addresses (IPv4 and IPv6) and netmasks assigned to them by ANI IX.
2. IP packets addressed to ANI IX Peering LAN’s directed broadcast address shall not be automatically forwarded to ANI IX ports.
3. IP address space assigned to ANI IX Peering LANs shall not be advertised to other networks.

IP Traffic Exchange

IP traffic should be exchanged between ANI IX members using BGP protocol by subsequent ways:
1. Using Route Servers (RS) – two RSs for redundancy and resilience.
2. Bilateral BGP sessions between ANI IX Members / Content providers with theirs mutual agreements.

Route Servers Peering Policies

1. Disabling first AS check
The Route Servers don't have their AS first within the AS_PATH. In some cases you'd possibly got to disable the primary AS sign up your BGP configuration.
– On Cisco routers please specify ‘no bgp enforce-first-as’ or ‘bgp enforce-first-as disable’ to disable the enforcement.
–Need to specify ‘undo check-first-as’ to disable the enforcement On Huawei routers .
2. Autonomous System Number (ASN)
ANI IX supports both 16-bit and 32-bit AS numbers.
3. Incoming Prefixes Sanitization
The ANI IX route servers implement very basic incoming filters for personal ASNs and prefixes received from clients. ANI IX BLOCKs private ASNs, RFC1918 ranges, bogon prefixes and thus the default route. All members to ANI IX route servers can use communities to manage incoming and outgoing information. In reference to the incoming traffic (which announces are accepted) the control is within the client – he can filter which of them of the received from RS announces he will accept. ANI IX RSs remove its own AS from the route, which can make them seem directly connected without a necessary BGP session between them. With the assistance of BGP Community ANI IX member may decide who he wants to “give” the traffic to subsequent BGP Community is maintained for each announced prefix. ANI IX implements N:M filtering supported standard community strings. only 4 bytes is supported by standard BGP communities , this only works for 2-byte ASNs and peers with 2-byte ASNs.