APNIC 16 Home APNIC 16 Home
APNIC Home

 

SIG: IX

Wednesday 20 August 2003, Lotte Hotel, Jamsil - Seoul, Korea

Minutes

Meeting commenced: 11:10 am

Chair: Philip Smith

Co-chair: Che-Hoo Cheng

The Chair introduced the SIG and explained the agenda.

Contents
  1. Review of previous open action items
  2. IXes in South Asia
  3. JPNAP
  4. Progress report - IIX
  5. DIX-IE
  6. Modified APNIC policy for Internet Exchange Point assignment
  7. Current open action items
  1. Review of previous open action items
  2. Philip Smith, Cisco

    Presentation [pdf]

    • Action ix-15-001 update: No comments on the draft charter were received. The charter for this IX SIG has now been accepted as "The IX SIG provides a forum for sharing information about the status and activities of Internet eXchange (IX) points in the Asia Pacific region".
    • Action ix-15-002 update: Che-Hoo Cheng has been elected as Co-chair of the IX SIG.

    Top

  3. IXes in South Asia
  4. Gaurab Raj Upadhaya, Nepal Internet Exchange

    Presentation [ppt | pdf]

    The presenter provided an overview of the status of Internet Exchanges in South Asia.

    In Afghanistan, it is hard to determine how many links are in the country. Regulation activities are now underway for national and international ISPs. There are 200 cyber cafes in Kabul, generally using V-SAT. Most private ISPs are customers of larger ISPs in Pakistan. It was noted that MOIC and AFGNIC are considering initiating an IX.

    In Bangladesh, there are more than 100 ISPs, many are small neighbourhood businesses getting bandwidth from bigger providers. The BDIX project has been funded by UNDP to include the 20 largest ISPs in 2003. Wireless connectivity will be used initially due to the difficult regulatory regime, but this is considered to be a temporary solution. In July 2003, the first IX workshop was held with 35 participants. More IXP workshops are scheduled for later in 2003.

    In Bhutan, there is only one ISP, with 10,000 access accounts, 40-50,000 users. It uses satellite connectivity.

    In India, NIXI is government funded, non-profit, with cooperation from ISPs. There are plans to establish IXes in Delhi, Mumbai, Chennai, and Kolkata. The Delhi location has been selected and commenced with eight ISPs in July. The NIXI mandates peering, but discussions are continuing. The NIXI project has been increasing awareness in the industry.

    In Maldives, there is one ISP, using VSAT connectivity and no local IXes. There are some interesting experiments to provide wireless connectivity to various islands, however, there are now some moves to consider underwater fibre.

    In Nepal, the npIX continues. All six ISPs have now been migrated to BGP. Traffic is growing at 10-15 percent. There is a plan to interconnect the two switches in September 2003. Non-ISPs are now being included, such as the University and other agencies with their own satellite links.

    In Pakistan, a Pakistan Internet Exchange is a transit selling exchange for the PCTL but is not a real peering exchange. ISPs are now allowed to have an independent gateway, but this has not yet been taken up by many. The government does content filtering. There has been a new telecom policy announced recently which may improve the environment. The IX formation has been hindered by poor connectivity and lack of knowledge, but some ISPs are now interested in going forward.

    In Sri Lanka, LISPA-IX is the longest operating IX in South Asia, operated by the local ISP association. This is still using static routes, but has plans to migrate to BGP soon. They are expecting a significant traffic increase soon due to regulatory changes.

    Questions and discussion

    • None

    Action items

    • None

    Top

  5. JPNAP
  6. Toshinori Ishii, Internet Multifeed

    Presentation [pdf]

    The presenter provided an overview of the JPNAP service. JPNAP is a commercial IX in Japan operated by Multifeed.

    JPNAP Tokyo is Ethernet based Layer 2 IX. It is a distributed service for the Tokyo metropolitan area. Its traffic volume has been increasing rapidly, peaking at 26.5 Gbps.

    JPNAP has been supporting 10GbE since January 2003.

    JPNAP Osaka is not connected with JPNAP Tokyo. It was established for redundancy in case of disaster in Tokyo. It too has seen increased traffic volume.

    JPNAP6 Tokyo has supported IPv6 since June 2002, currently serving 10 customers, although traffic volume is still low.

    Questions and discussion

    • None

    Action items

    • None

    Top

  7. Progress report - IIX
  8. Ahmad Alkazimy, APJII

    Presentation [ppt | pdf]

    The presenter provided an overview and status report of IIX activities in Indonesia. IIX currently has three nodes. It is Layer 2 and 3 infrastructure. IIX has 70 members, connecting via IPv4.

    IIX announces 1600 lines. 84 percent of members now use BGP.

    IIX recently received an allocation from APNIC, and renumbering took two months.

    IIX now supports IPv6 and will provide IPv6 connectivity to members. There are implementation problems related to limited knowledge among members of IPv6 policy and issues.

    A private AS implementation plan is now underway for members that will be connected to IIX using singlehomed connections.

    APJII encourages more IPv6 knowledge building and invites greater industry support for IPv6 testing.

    Questions and discussion

    • There was a discussion of the reasons for using private AS numbers. It was explained that this was due to some technical problems and a lack of knowledge of BGP. However, it was noted from the floor that private AS numbers may not help with the perceived technical problems and may introduce some additional problems. There was also a suggestion that there may be a misunderstanding of the APNIC policy. It was clarified that using a public AS number to connect to an IXP would satisfy the APNIC policy.
    • There were several recommendations from the floor that it would be better to use BGP rather than static routes, and public ASNs rather than private ASNs.
    • It was recommended that APNIC should clarify the guidelines for the ASN policy.

    Action items

    • Action ix-16-001: APNIC Secretariat should clarify the guidelines for the ASN policy in relation to multihoming.

    Top

  9. DIX-IE
  10. Akira Kato, WIDE Project

    Presentation [pdf]

    NSPIXP-2 has been renamed to DIX-IE. It is a distributed IX in EDO.

    The project to create a layer 2 extension of NSPIXP-2 commenced in mid-2002.

    The presenter provided an overview of the architecture of the IX and discussed traffic volume, which currently has peaked at approximately 15Gbps. He also described the work to provide remote access via MPLS, in a joint effort with Japan Telecom.

    Questions and discussion

    • There was a discussion about how peering is planned to be done in MPLS. There was also a discussion about the use of BGP to send labels.

    Action items

    • None

    Top

  11. Modified APNIC policy for Internet Exchange Point assignment
  12. Bill Woodcock, PCH

    The presenter explained the proposal to be made in the Address Policy SIG to modify the APNIC IXP policy. The proposal is to provide an updated definition of IXPs, to recommend simultaneous IPv4 and IPv6 assignments, to remove the block on routing IXP assignments, and to waive assignment fees for qualifying not-for-profit IXPs. (For full details of the proposals, refer to the minutes of the Address Policy SIG.)

    Questions and discussion

    • There was a discussion about whether or not hosts should be allowed on the subnet assigned under this policy.
    • There were also discussions of the fee and membership level implications.
    • There were general discussions in relation to how the IXes should obtain ASNs.
    • There was a question relating to existing holders of IPv4 and IPv6 IXP assignments. It was noted that this policy would not require these IXPs to renumber to ensure matching numbers.

    Top

    Meeting closed: 12:40 pm

    Minuted by: Gerard Ross

    Current open action items
    • Action ix-16-001: APNIC Secretariat should clarify the guidelines for the ASN policy in relation to multihoming.

    Minutes

 

APNIC 16 hosted by
KRNIC
Last modified: Monday, 19-Jul-2004 10:38:13 EST | © 1999 - 2020 APNIC Pty. Ltd.
Contact us | Privacy statement