Internet2  ION  Service    Overview  and  Status  

Tom  Lehman  (USC/ISI)  

Internet2  ION  Service  •  ION  is  Internet2  instan=a=on  of  a  Dynamic  Circuit  Network  (DCN)  

•  Internet2  launched  the  ION  service  in  2009  –  ION  allows  for  the  provision  of  scheduled,  dedicated  capacity,  layer  2  (Ethernet  VLAN  framed)  connec=ons  

–  ION  is  a  produc=on  service  managed  by  the  Internet2  NOC  on  the  Internet2  network  backbone  

–  ION  circuits  are  provisioned  using  a  simple  and  secure  web-­‐based  interface  or  applica=on  signaling  

–  ION  circuit  setup  uses  the  DCN  SoMware  Suite    •  OSCARS,  DRAGON  soMware  •  perfSONAR  based  Topology,  Lookup,  and  Monitoring  services  

Internet2  ION  Service  •  Mul=ple  Domain  Deployments  and  InterDomain  Service  Provisioning  –  ION  speaks  the  InterDomain  Controller  Protocol  (IDCP)  (www.controlplane.net)  

–  IDCP  allows  for  a  mul=-­‐domain  interconnected  DCN  space  and  InterDomain  provisioning  

– This  interconnected  network  space  includes:  •  ESnet  Science  Data  Network  (SCN)    •  Mul=ple  regional  and  campus  networks  

•  USLHCNet  •  CalTech  •  JGN2  •  KOREN  •  Mul=ple  experimental  deployments  

Internet2  ION  Service  •  Internet2  ION  service  transi=oned  from  dedicated  network  built  atop  Ciena  CoreDirectors  to  Juniper  MX960s  (complete  as  of  July  6th,  2010)  – MPLS  transport  more  efficient  use  of  resources  – Bandwidth  reserved  for  circuit  instan=a=on  is  available  for  use  by  other  users  when  circuit  owner  not  u=lizing  circuit  for  transfer  

– Opportunity  to  provide  circuits  that  can  burst  above  their  requested  commit  rate,  if  sufficient  headroom  available  

Open  Source  DCN  SoMware  Suite  •  OSCARS  (IDC)  

– Open  source  project  development  is  led  by  ESnet  –  Internet2  is  a  major  contributor  

•  DRAGON  (DC)  – Open  source  project  maintained  by  USC  ISI  EAST  and  MAX  

•  Version  5.2  of  DCNSS  currently  deployed,  available  here:  –  haps://wiki.internet2.edu/confluence/display/DCNSS  

•  Java  Client  API  –  haps://wiki.internet2.edu/confluence/display/CPD/OSCARS+Client+Java+API    

OSCARS  

•  On-­‐demand  Secure  Circuits  and  Advance  Reserva=on  System  (OSCARS)  

•  DOE  Office  of  Science  and  ESnet  project    •  Co-­‐development  with  Internet2  •  Web  Service  based  provisioning  infrastructure,  which  includes  scheduling,  AAA  architecture  using  X.509  cer=ficates  

•  Extended  to  include  the  IDCP  •  www.es.net/oscars  

DRAGON  Project  

•  Dynamic  Resource  Alloca=on  via  GMPLS  Op=cal  Networks  (DRAGON)  

•  Adds  GMPLS  control  plane  to  non-­‐control  plane  enabled  network  elements,  like  Ethernet  switches  

•  NSF  Funded  Project    •  Maintained  by  USC/ISI  and  UMD/MAX  •  dragon.east.isi.edu  •  dragon.maxgigapop.net  

Topology  and  Lookup  Service  •  ION  Control  Plane  uses  PerfSonar  Topology  Service  and  LookUp  Service  

•  LookUp  Service  Service  – Provides  a  mapping  from  circuit  end  points  to  user  friendly  names  

•  Topology  Service  – Provides  an  infrastructure  from  which  to  retrieve  topologies  from  other  domains  

– U=lized  for  global  path  computa=on    

Dynamic  Network  Services  IntraDomain  

• Source  Address  • Des=na=on  Address  • Bandwidth  • VLAN  TAG  (untagged  |  any  |  tagged  |  tunnel)  • User  Iden=fica=on  (cer=ficate)  • Schedule  

Client  A  

Client  B  

Circuit  Request  

Layer2  Circuits  

Dynamically  Provisioned  Dedicated  Resource  Path  (“Circuit”)  

DCN  Enabled  Network  

IDC  

• api  can  run  on  the  client,  or  in  a  separate  machine,  or  from  a  web  browser  

XML  USER  API  

Actual  Network  Path  

MulFple  Signaling  Control  Plane  OpFons  

Dynamic  Network  Services-­‐InterDomain  •  No  difference  from  a  client  (user)  perspecFve  for  InterDomain  

vs  IntraDomain  

•  Issues  like  mulF-­‐domain  path  and  vlan  selecFon  get  worked  out  in  real  Fme  as  part  of  IDC  protocol  

RON Dynamic Infrastructure Ethernet VLAN

RON Dynamic Infrastructure Ethernet VLAN

Internet2 ION

1. Client Service Request 2. Resource Scheduling 5. Service Instantiation (as a result of Signaling)

A. Abstracted topology exchange (via PS Topology Service)

A A 2

2 1

USER API

XML

Multi-Domain Dynamically Provisioned Circuit

IDCP  Protocol  

•  InterDomain  Controller  Protocol  (IDCP)  –  Originally  developed  in  DICE  by  Internet2,  ESnet,  GEANT,  Caltech,  

others  

–  www.controlplane.net  –  hap://www.controlplane.net/idcp-­‐v1.1-­‐ogf/draM-­‐gwdi-­‐nsi-­‐idcp-­‐2010-­‐

sep-­‐01.doc  |  pdf  

•  OGF  Informa=onal  Document  approved  to  be  published:  –  IDCP  Specifica=on,  GFD-­‐I.170  

IDCP  Protocol,  Topology,  Lookup  Service  Integra=on  

OSCARS  Development  Ac=vi=es  

•  OSCARS  v5.3  – December  2010  

– VLAN  transla=on  to  facilitate  provisioning  to  connectors  with  limited  VLAN  ranges  available  

– Features  to  improve  failure  handling  

•  OSCARS  v6.0  – April  2011  – Major  re-­‐write  to  increase  modularity  and  facilitate  future  feature  set  extension  

– Hopefully  will  facilitate  others  joining  in  the  open  source  development  project  and  contribu=ng  code  

OSCARS  and  DRAGON  Configura=ons  •  OSCARS  includes  the  Web  Service  Infrastructure,  Client  API,    

IDCP,  and  Network  Control  Interface  

•  DRAGON  is  required  for  some  network  element  types  and  configuraFons  

Dynamic Network

USER API

XML

OSCARS

Client API

IDCP to other IDCs

Network Element Control – Vendor Native Protocol when possible, DRAGON when needed

Multiple Network Element Types and Configurations out there. From a Dynamic Network Control, DCNSS supports the following currently:

i) Router/MPLS based L2VPN, RSVP Signaling ii) Ethernet Over SONET, RSVP-like Signaling iii) Native Ethernet VLAN Control, no native Signaling Engine iv) Heterogeneous mix of any combination of the above v) Adding other network technologies and element types as needed.

DRAGON provides a GMPLS signaling environment to any network deployment which does not have a native signaling engine. This would include a network which is constructed of commodity Ethernet switches, or one which has a heterogeneous mix of vendors or network technologies. Currently supported list of elements: https://wiki.internet2.edu/confluence/display/DCNSS/DRAGON+Supported+Switches

Overtime the may integrate the DRAGON functions into the native OSCARS code base, so that there will be only one code base to maintain.

DCN  Global  FootPrint  

Dynamic  Circuit  Networking  -­‐  Research  •  Internet2  is  engaged  in  standardiza=on  effort  within  the  Open  Grid  

Forum  (OGF)  

–  NSI  WG  (network  service  interface  defini=on  and  protocol)  –  NML  WG  (topology  support  of  circuits  and  monitoring)  

–  NMC  WG  (performance  middleware)  

–  NM  WG  (measurement  defini=on)  

•  Internet2  is  engaged  in  GLIF  experimental  networks  –  perfSONAR  Demos  

–  Automated  GOLE  Demos  (working  with  FENIUS  effort)  

•  Internet2,  in  consulta=on  with  partners,  plans  to  evolve  working  IDC-­‐based  service  instances  over  =me  in  keeping  with  emerging  consensus  on  standards  and  best  prac=ces  within  the  OGF  and  GLIF  

Dynamic  Circuit  Networking  –  Service  Extension  

•  Internet2  would  like  to  con=nue  to  extend  dynamic  circuit  networking  services    (specifically  service  defini=ons  based  on  the  IDC  protocol)    –  US  regional  networks  –  US  campuses  

–  US-­‐funded  interna=onal  links  •  Three  NSF  awards  of  interest  

–  IRIS:  develop  perfSONAR-­‐ps  based  performance  monitoring  package  for  use  by  IRNC  PRONET  awardees  

–  DyGIR:  develop  OSCARS  (and  DRAGON)  based  dynamic  circuit  networking  package  for  use  by  IRNC  PRONET  awardees    

–  DYNES:  develop  OSCARS  (DRAGON)  and  perfSONAR-­‐ps  based  distributed  virtual  instrument  for  LHC  community  and  others  

End