1 / 8

APAN Design and Operation Memo - Bandwidth Allocation and Network Updates

This report provides information on the bandwidth allocation and network updates for APAN members. It includes details on link information, expected dates, and remarks for each network. The report also discusses the design and operation of APAN, including agreed diagrams, naming conventions, and future plans for differentiated services. Additionally, it addresses the initial bandwidth allocation and issues to be considered for introducing differentiated services. It concludes with details on server operation responsibilities.

waltermyers
Download Presentation

APAN Design and Operation Memo - Bandwidth Allocation and Network Updates

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NOC Report Seoul 1998.07.03 Kazunori Konishi NOC Director of APAN-JP Consortium konishi@jp.apan.net http://www.jp.apan.net

  2. APAN 98.07.03 CA STA MPT KR US JP EU MPT CN SG HK AU ID AI3 MITI PH TH MAFF ME

  3. Link Information Link Bandwidth(Mbps) Expected Date Remarks --------------------------------------------------------------------------------------- JP - US 35 =>70(ATM) 1998.7 => .11 IMnet(7.5M now) JP - AU 1.5 (FR) now RWCP/ACSys JP - HK 1.5 now AI3/HKUST JP - ID 1.5 now AI3/ITB JP - KR 2 =>8(ATM) now =>’99 APII-APAN JP - PH 0.77 (FR) now MAFFIN/PHNET JP - SG 2 =>8(ATM) now APII/SREN JP - TH 2 now SINET/NECTEC 1.5 now AI3/AIT KR - SG 2 ‘99 APII KR - US 20 =>45 now =>’99 Pubnet SG - US 14 now SingAREN

  4. APAN Design & Operation • * Design & Operation Memo has been discussed. • - Diagram between vBNS and Tokyo-XP was agreed. • - Naming convention was agreed: • tpr-tokyo = TransPAC router at Tokyo • - APAN member networks should relay commodity • traffic via their own commodity links to USA. • - tpr-tokyo will peer with tpr-startap with iBGP. • - Differenciated service will be experimented asap.

  5. APAN Design & Operation(Cont’d) • - Diagram including KR & SG has been drawn. • - VCI convention has been defined. • - Commercial ISP can’t access APAN cache servers • before confirming the safety of the links. • - Monthly report will be edited by IU with the help of • NOC team, based on the traffic data stored at each • XP servers. • - Annual report will be edited by IU with the help of • Secretariat/NOC teams.

  6. Initial Bandwidth Allocation • 98.7 (34M) 98.11(70M) • ------------------------------------------------------------------ • IPv4 & Mbone 15 - 30 • Cache 6 6 • ESnet -- 15 • NREN -- -- • IPv6 1.5 1.5 • Reserved 10 20 • (demo & experiment)

  7. APAN Design & Operation(Cont’d) • * Issues • - The procedure to introduce Differenciated Services should be proposed by Allen Robel. Local experiments should be well done prior to the introduction. • - Measurement tools commonly used should be proposed by Measurement WG. • - Collaboration tools commonly used should be decided by NOC. • - Design & Operation Memo including diagrams will • be made public on the Web of Tokyo NOC.

  8. Who will operate Servers? • * Basic Servers : NOC • * Cache: Cache WG • * Mbone: NOC & Mcast WG • * Demo: NOC at experimental phase • User Support Group at production phase • * Archive: Digital Library Group • * Donation & Content: For further study • * Shigeki Goto will be in charge of Content/Demo.

More Related