1 / 6

Proposal: A new LHCONE core architecture

Proposal: A new LHCONE core architecture. Gerben van Malenstein Amsterdam, the Netherlands – December 1-2, 2011 LHCONE Architecture WG. Approach. Current LHCONE implementation hard to debug, needs re-design to be future-proof Discussion SURFnet, SARA NRG, NL-T1

ciaran-davenport
Download Presentation

Proposal: A new LHCONE core architecture

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. Proposal: A new LHCONE core architecture Gerben van Malenstein Amsterdam, the Netherlands – December 1-2, 2011LHCONE Architecture WG

  2. Approach • Current LHCONE implementation hard to debug, needs re-design to be future-proof • Discussion SURFnet, SARA NRG, NL-T1 • This presentation based on proposal sent to LHCONE architecture working group mailing list: 2 proposals, 1 appendix • Timelines also TBD, proposals are on a 2+ year timeline

  3. Appendix –Not a proposal! • Not adding anything essentially new to the existing IP interconnectivity of the current networks • Because of routers present inside the LHCONE core, (new) tiers will not benefit from the lowest equipment cost, compared to a layer 2 solution

  4. Scenario A • Ethernet domain using the IEEE 802.1aq (Shortest Path Bridging) protocol or the TRILL (Transparent Interconnect of Lots of Links) protocol, possibly implemented through OpenFlow; Ethernet OAM available • Needs feasibility study, research (see Worddoc sent to the list), milestones

  5. Scenario B • Multiple domains that are connected to each other by Ethernet connections. On top of this infrastructure, dynamic VLANs enable point-to-point connections on a per-VLAN basis • Network Service Interface (NSI) through Network Service Agent(s) (NSA)

  6. Thank you! Gerben van Malenstein gerben.vanmalenstein@surfnet.nl

More Related