|
|
|
Optimizing Internet |
|
In Mongolia |
|
|
|
|
|
The Internet is a great tool |
|
If the tool doesn’t work well, we must fix the
tool or replace it |
|
The evolution of inter-networks turns back to
the local environment |
|
The intent is to create a utility meeting the
needs of Mongolia’s entire community |
|
Government |
|
Business |
|
Education |
|
Society |
|
Entertainment |
|
|
|
|
|
|
Starts with basic connectivity |
|
One or more networks connect to the Internet |
|
Mongolia ISPs pay all |
|
International leased capacity |
|
Ports on Tier ½ routers |
|
Volume sensitive billing |
|
The more successful you are – the faster you run
into financial difficulty |
|
|
|
|
|
|
|
|
|
|
Mongolia –to- Mongolia traffic |
|
Two satellite hops (1200ms +) |
|
Congestion on inbound links |
|
Local traffic dropped outside of Mongolia |
|
Intra-Mongolia performance Unacceptable |
|
Cost of higher capacity ports at Tier ½ |
|
Cost of capacity on international links |
|
|
|
|
Hosting local content in US/Intl |
|
Reluctant to build business process into
Internet environment |
|
|
|
|
|
Mongolia Internet community does not have rapid
organic growth |
|
Revenue leaves Mongolia for international
hosting providers |
|
Advanced models of Internet based business and
community growth delayed |
|
Business to Consumer |
|
Business to Business |
|
Government to Business/Consumer |
|
|
|
|
|
|
National Internet traffic stays local |
|
ISPs do not pay Tier 1/2 to carry Mongolian
originating and terminating traffic |
|
Businesses with primary Mongolia target markets
do not need to host their content outside of Mongolia |
|
B2B and supply chains can emerge when economy
and market is ready |
|
|
|
|
|
National content cache |
|
All ISPs have access to the same routes |
|
Bandwidth costs can turn back into local
business and value added service |
|
Obvious need to address competitive
considerations and content ownership questions |
|
|
|
|
|
|
|
Confirm facility location, management, and
prepare location to implement M-IX |
|
Receive equipment |
|
Routers on order |
|
Additional servers when needed by implementation
plan |
|
Modems on order |
|
Arrange local access lines for M-IX |
|
Determine if ISP community has any
considerations on design, location, operation, features, or implementation
of the M-IX |
|
Actual design plan, as it is, should be
available via the M-IX website |
|
http://www.pacific-tier.com/mix/mix.htm |
|
Agree on membership terms |
|
Membership criteria |
|
Membership dues/costs |
|
M-IX infrastructure cost recovery |
|
Service level agreements |
|
|
|
|
|
|
|
ISP Provided Access The ISP connects their
equipment directly onto the IX switch via 100BaseT Fast Ethernet. ISP will
provide all equipment and connectivity.
ISP is colocated with M-IX (ISP A) |
|
Dedicated IX Switch Access: The ISP connects
their equipment onto the IX switch via an SDSL/HDSL/ATM circuit at
10/100BaseT. The ISP router should have a 10/100BaseT Ethernet Port to
terminate traffic from the IX. (ISP B) |
|
Dedicated IX Router Access: The ISP connects
their equipment over a dedicated circuit onto a MIX managed router. The ISP
router should have a high speed V.35 serial port available for connecting
to the CSU/DSU provided by the telco. (ISP B) |
|
Managed IX Access: MIX will provide a router on
both sides of the dedicated circuit to provide managed IX access. The ISP
should have an available Ethernet port and IP address on their Network.
(ISP C) |
|
|
|
|
|
|
|
Dynamic Routing. Dynamic Routing Protocols allows the network to automatically
re-route during network outages, and is strongly recommended for IX route
exchanges. |
|
BGPv4 is the de-facto inter-domain routing
protocol used by ISPs around the world. BGP allows advanced route filtering
capabilities that can protect the ISP network stability that is not
available with other traditional IGP routing protocols, such as RIP and
OSPF. |
|
As MIX has not been assigned an official
Autonomous System Number (ASN), we will use the IANA assigned private
network ASN (AS 65001-65535). IX participants may peer directly with each
other to exchange routes, but is recommended to peer with the MIX router to
receive routes from participants not using BGP. |
|
As most ISPs in Mongolia do not currently have
the software and hardware required for BGP peering, RIPv2 has been selected
as an alternative mechanism to exchange routing information on the IX.
Routes learned from the IX should be redistributed into the ISP’s IGP. |
|
Static Routing.
IX participants may choose to use static routing, although this may
cause a “black hole” during network outages. |
|
|
|
|
|
|
|
Route Announcements |
|
MIX will only accept and redistribute registered
routes from member ISPs |
|
Member ISPs are strongly recommended to install
an inbound filter list on their router to ensure false routing information
is not inserted into their routing tables |
|
Customers are also strongly advised to install
an outbound filter list, so they do not announce the IX routes to the
Internet, or Internet routes to the IX, particularly if they are using a
dynamic routing protocol to their upstream provider |
|
Packet Filtering |
|
MIX should not filter traffic between MIX
participants |
|
If MIX participants are concerned about other
participants using their network as the default gateway to the Internet,
they are recommended to install a filter list on their IX interface to
restrict traffic |
|
|
|
|
|
|
Performance increase for Mongolia-Mongolia
traffic should get much better |
|
Performance on non-Mongolia traffic should show
a modest improvement |
|
The next generation of network integration into
B2B, B2C, education, and government will have a better chance to emerge and
grow |
|
Notes