1 / 17

TEIN2 Engineering Design Update

TEIN2 Engineering Design Update. APAN Meeting, Taipei 25 th August 2005. TEIN2 Engineering Work. Discussion on needs for detailed technical design work kicked off at Singapore meeting in March First “Engineering Task Force” meeting held in Seoul in May

gage-gaines
Download Presentation

TEIN2 Engineering Design Update

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. TEIN2 Engineering Design Update APAN Meeting, Taipei 25th August 2005 APAN Meeting Taipei, 25 August 2005

  2. TEIN2 Engineering Work • Discussion on needs for detailed technical design work kicked off at Singapore meeting in March • First “Engineering Task Force” meeting held in Seoul in May • Discussed ToR and identified main pieces of work that needed to be completed during the remainder of 2005 • Core of “volunteers” identified during EngTF meeting • Tasked with drafting initial engineering design documents • Topology agreed upon during Tokyo meeting in July APAN Meeting Taipei, 25 August 2005

  3. Upfront Assumptions • Build & Operate a transit AS • So assume TEIN2 NRENs have own ASNs and IP blocks and can talk eBGP to TEIN2 • Provide multiple links to Europe (GÉANT2) • Plus seek transit arrangements • No commodity over (subsidised parts of) TEIN2 infrastructure • Seek equipment donation if possible • Meaning: one router for each POP • Approach has worked for EUMEDCONNECT & ALICE APAN Meeting Taipei, 25 August 2005

  4. Initial expectation APAN Meeting Taipei, 25 August 2005

  5. All prefixes tagged <XYZ:R&E_tag> advertised to TEIN2 NRENs TEIN2 AS XYZ • TEIN2 NREN advertises R&E-only prefixes • Filter put in place on TEIN2 router • Accepted prefixes tagged(e.g. with community <XYZ:R&E_tag>) High level TEIN2 Routing Plan (Connecting TEIN2 NRENs) eBGP peering eBGP peering eBGP peering T2 NREN T2 NREN T2 NREN APAN Meeting Taipei, 25 August 2005

  6. eBGP peering All prefixes tagged <XYZ:R&E_tag> advertised to GÉANT eBGP peering All prefixes tagged <XYZ:R&E_tag> advertised to TEIN2 NREN offering transit TEIN2 AS XYZ eBGP peering • All R&E prefixes advertised to TEIN2 • European (EU-NREN) prefixes preferred • All R&E prefixes advertised to TEIN2 • AP and NA prefixes preferred High level TEIN2 Routing Plan (Backhaul) T2 NREN Offering transit GÉANT eBGP peering eBGP peering eBGP peering T2 NREN T2 NREN Offering transit T2 NREN T2 NREN Back APAN Meeting Taipei, 25 August 2005

  7. Agreed Topology APAN Meeting Taipei, 25 August 2005

  8. JP CN Existing Link VN tba Links provided by NICT (JP) HK tba PH KR TH MY SG ID AU North America (via TransPAC2) EU 622 tba 622 Approved TEIN2 Topology (as of 8-8-05) 622 155 tba 45 622 EU 155 2 or 3 x 622 45 4 x 155 45 APAN Meeting Taipei, 25 August 2005

  9. TEIN2 AU KR Singapore POP Not yet fixed – one of many possibilities! STM-4c 4xSTM-1 to AU STM-4c to TEIN2-HK To GÉANT (Frankfurt) via SMW3 STM-4c Link to TEIN2-JP (NII) (capacity TBA) Link to JP (NICT) (details TBC) Links to TH (STM-1), MY (T3) & ID (T3) STM-4c STM-4c to KR APAN Meeting Taipei, 25 August 2005

  10. SG JP TEIN2 HK JP AS XYZ CN Routing (TEIN2+JP) I Originally envisaged one TEIN2 AS only! NICT “Access” links only (for NICT) AS 9355 APAN-JP AS 7660 SINET AS 2907 TEIN2-JP AS ABC NII-provided linksneed to be able toprovide backup forHK-SG link BGP loop detectionwould conspire to stopthis “backup transit” TEIN2-JP router must necessarily be in separate AS APAN Meeting Taipei, 25 August 2005

  11. SG JP HK JP CN Routing (TEIN2+JP) II 2 TEIN2 AS’s nowseems most expedientapproach NICT “Access” links only (for NICT) AS 9355 APAN-JP AS 7660 TEIN2-NORTH AS XYZ SINET AS 2907 TEIN2-JP AS ABC TEIN2-SOUTH AS ZYX Now a regular inter-domainrouting setup (with transit)should allow required backup TEIN2-JP router must necessarily be in separate AS APAN Meeting Taipei, 25 August 2005

  12. HK CN TEIN2-NORTH eBGP Peerings To GÉANT2 (UK)via Moscow CERNET APAN-JP AS 7660 Advertise all prefixes; accept based on IRR Advertise all prefixes; accept based on IRR;maybe locally prefersome prefixes and/oruse MEDs TEIN2-NORTH VNET TEIN2-JP To TEIN2-SOUTH (SG) APAN Meeting Taipei, 25 August 2005

  13. SG TEIN2-SOUTH eBGP Peerings To TEIN2-NORTH (HK) KOREN ThaiREN To GÉANT2 (DE) APAN-JP AS 7660 MYREN TEIN2-SOUTH TEIN2-JP Advertise all prefixes; accept based on IRR Advertise all prefixes; accept based on IRR;maybe locally prefersome prefixes and/oruse MEDs AARNet ITB APAN Meeting Taipei, 25 August 2005

  14. IP Addressing Plan • Needed to support application to APNIC for IP block • Skeleton plan in place; still needs expanding • Issues outstanding: • Who will make application? • NOC? APAN? DANTE? Other TEIN2 partner? • Assume that PI address space will be needed…? • Dual AS setup: assume that block will need to be split into two so that prefixes can be originated by each AS…? APAN Meeting Taipei, 25 August 2005

  15. Advanced IP Services • When will mcast & IPv6 service be required? • Offer strict “native-only” support? or • Offer support for interim tunnel-based solutions? • Allows support for users behind v4-only and/or unicast-only domains • Practical limitations required (down to operational and router performance issues) • Operate a “tunnel broker”??? • Leads to non-congruous routing architectures • Care needed! APAN Meeting Taipei, 25 August 2005

  16. Monitoring • DANTE is not expecting to deploy the same stats portal and back-end(s) as have been used for EUMEDCONNECT monitoring • Will be fully outsourced to TEIN2 NOC provider • See next presentation (Xing Li) APAN Meeting Taipei, 25 August 2005

  17. Thank You & Questions APAN Meeting Taipei, 25 August 2005

More Related