Evolution  of  the  Internet2  Network

John  Hicks,  jhicks@internet2.eduSAACC

Topics:

• Current  transition  of  the  network  – Short  term• SDN  Support• Long  term  evolution  of  the  network• Research  facilitation• Continued  participation  in  GNA  activities

CURRENT  TRANSITION  OF  THE  NETWORK  – SHORT  TERM

[  4 ]

2016-­‐2017  Target  areas

Core  Network:Move  to  single  vendor  platform  based  on  MPLS  (2016  – 2017)

Capacity:Improve  analytics;  perform  first  wave  of  upgradesLeverage  DCI  at  key  interconnect  locations

Optical:Auditing  and  Compliance

[  5 ]

2016-­‐2017  CORE  Network  Program:  Requirements

• All  Services  at  all  nodes  – AL3S  (R&E,  TRCPS,  LHCONE,  other  L3VPNs)  – AL2S  (L2VPN,  VPLS,  Advanced  L2-­‐CCC)

• Allow  for  Explicit  Path  Selection• Restore  to  Primary  by  Default• Edge  interface  support  all  services  on  a  single  port• Multipoint  (VPLS,  default  MAC-­‐Address  Table  Limits)• Path  Exposure  (Traceroute,  MPLS  Ping)• IPv6• Multicast  (ASM  &  SSM)

[  6 ]

2016-­‐2017  CORE  Network  Program

Consolidated AL2S/AL3S/TRCPS

J

J

J

J J

J

J J

JJ

J

J

JJ

J

J

J

J

JJ

J

J

J

J

J

J

JJ

J

J

J

JJ

J

J

J

JNEWY1118TH

NEWY32AOA

HART2

BOSTALBA

CLEV

PITTASHB

RALE

WASH

CHAR

PHILINDI

LOUI

CINC

STAR

EQCH

CHIC

KANS

SAIN

COLU4

TULS

NASH

ATLA

JACK

BATO

JCSN

DALL

DALL3

HOUS

HOUH

MINN

MISS2

SEAT

LACY

PORT

EUGE

BOIS

SACR

SUNN

PAIX

LOSA

WILCSAND

SANL

PHOE TUCS

SALT

DENV

PUEB

ALBU

ELPA SANA

RENO

LASV

J

J

J

J J TELX

Optical Add/Drop, no L2/L3

J R&E/TRCPS VRFs and OpenFlow

J OpenFlow only

J TRCPS VRF only

J Juniper MX960

J R&E/TRCPS VRF only

[  7 ]

Current  Status• Transition  of  all  vlans to  MPLS  is  completed  as  of  8-­‐15-­‐17.– Total  of    vlans transitioned  in  stages  was  890.– Took  about  40  hours  total

• The  process  occurred  over  7  nights.  No  single  vlan took  more  then  a  minute  or  so.

• No  substantive  issues  came  up  during  this  process.

SDN  SUPPORT

• 8  sites,  national  footprint• Each  site  contains:– Dell  Server– Corsa Switch–Multiple  10GE  interconnects  provided  via  AL2S

– 10GE  AL2S  port  for  onramp/offramp

[  9 ]

What  it  looks  like 3 Degree SDN Overlay Site

Overlay SDN Corsa DP2xxx

AL2S Juniper MX960

Internal Management

Network

Virtual Switch Virtual Switch

SDN Server Dell 630

controller VM controller VM

10G

10G 10G 10G 10G

1G

1G

1G

WAN

100G 100G 100G

2c 2d 2e 2f

2a

3b 3c 3d 3e

3g 3h 3i

1b 1c

2b

3f

10G

1a

3a

• AL2S  circuits  interconnect  sites,  circuits  follow  physical  infrastructure

• Each  slice  gets  its  own  set  of  logical  circuits

• To  the  control  plane,  these  look  just  like  direct  10GE  adjacencies

• Each  slice  has  its  own  dedicated  management  network.

[  10 ]

What  it  looks  like  (2)

LONG  TERM  EVOLUTION  OF  THE  NETWORK

Framing• Community  investment  -­‐ not  just  backbone  -­‐ and  not  normal  refresh

• Not  “what  Internet2  should  do”  but  “how  can  we  work  differently  together”• Target  for  capital  investment  is  2+  years  out

• Practically  -­‐ looking  at  technology  that  is  not  yet  ready  for  prime  time  today• We  should  take  the  time  to  more  efficiently  make  shared  investments  where  practical

• Re-­‐emphasize  our  commitment  to  our  research  support  missions• Tailor  services  and  infrastructure  to  do  so  in  a  more  integrated  fashion

• Workforce  impact  -­‐ skills,  processes,  etc.• This  is  an  overarching  issue

• This  is  not  a  firm  plan  -­‐ we  need  input  and  collaboration• Not  everyone  will  be  ready  to  engage  day  one• Maintain  community  mindset  -­‐ all  can  join  and  benefit  when  ready

Key  principles

• Developed  from  requirements  gathering  process– Ecosystem  -­‐ planning,  service  development  and  investment  should  proceed  in  an  integrated  fashion  amongst  ecosystem  members  (campuses,  regionals,  NRENs,  etc.)

– Experimentation  -­‐ development  of  the  integrated  infrastructure  (ecosystem)  should  take  place  as  a  community-­‐wide  continuous  development  process

– End  User  Experience  -­‐ Follow  leading  use  cases  and  examples  that  enhance  the  user’s  end  to  end  experience

• Points  to  the  need  for  coordinated,  community  experimentation  efforts

GNA  

GNA  • Currently  in  the  process  of  developing  GNA  2.0  standards.• GNA  tech  is  co-­‐chaired  by  Dale  Finkelson and  Erik-­‐Jan  Bos• Many  people  from  the  community  are  engaged  in  the  current  activities,  these  include:– Enhanced  measurement/monitoring– Work  on  End-­‐to-­‐End  capabilities– Agreements  on  baseline  services  and  functionalities– Potential  use  of  NFV  tools– Non-­‐networking  capabilities– Security  and  Authentication

• More  information  on  the  GNA  activities  will  be  forthcoming  from  Erik-­‐Jan  and  Dale  Finkelson.