2017-11-21 LSST use of ESnet Meeting notes

Brainstorm connection options:
JB: PW proposed 3 options.  
3 Options are described in PW’s LSST-LHN ESnet colab meeting notes, and copied here:
Toward the end of October Matt, Jeronimo and Paul exchanged email brainstorming some ideas

1. Connect two router or switch ports to two client ports on the ESnet Ciena system.Each port would take a different path to Chicago and hand off the NCSA a client port. ESnet doesn't have built-in optical protection.
2. Connect a single router or switch port or dwdm client port to the ESnet Atlanta router and use a VPLS circuit to Chicago with a VPLS backup path and fast-reroute or something similar handing off a vlan to NCSA on their ESnet connection.
3. This is here just for trying to be complete. Establish BGP peering with the LSST router into a L3VPN within ESnet and have NCSA peer with the L3VPN. Traffic would route over the general IP network and around failures with everything else.

JB: need dedicated network services, not a pseudo wire.  
JB: what can I do to help?
PW: Referring to logical network diagram, not sure what circle means on the two paths from Atlanta to Chicago.
JB: Circle means protection at the optical layer?  Circle means two diverse paths.  AmLight will connect to ESnet transponders.  Ignore circle for now.
PW: ESnet does not provide optical protection.  Transport is what ESnet will provide.  ESnet does not need to provide protection.  
JB: Create a p2p link at the optical layer.  LSST NET will notify ESnet if link goes down.
JB: When there’s a connection at Atlanta, can first activate at 10G.  Circuit from Atlanta will come after connection from Boca Raton to Atlanta is established.
It does not make sense to provision dedicated 10G for transport.  
PW: a 10G routed port can be provided for fy19.
JK: Dedicated path diverse links not needed until 2021.
JB: Will write all this down into a tech document.  
JK: In addition to technical document, an Implementation plan and cost for what tech doc says.

Instrumenting the network paths:
JK: Other network segments, instrumenting with pS and using MADDash.  If we asked for this capability for the Atl to Chic segments, will that present any kinds of issues?
PW: available now through ESnet portal.  Will want this capability in 2021.  
JK: not specifically called out in the request.  REquest can be revised if necessary.  
JB: Addressing to wrong group.  From ESnet, the network service will be only optical layer.  They will not be able to test.
The LSST network will instrument the path, alongside the other active equipment.

Collocation:
JI: In Atlanta, can ESnet provide collo, or do we need to request from data center operator?  
PW: ESnet shares colo with I2.  ESnet would not be able to provide colo. 
600 W Chicago: available cabinets in the cage. 
JK: NCSA has multiple locations in Chicago.  Do green and red paths in diagram show up in the same or different locations in Chicago?
How does NCSA connect to Chicago for path diversity?
MK: NCSA peers with ESnet at 600 West and 710 Lakeshore Dri.  Connections are two optically diverse paths up to Chicago
JB: in those locations can you provide colocation?  
MK: probably not.  600 space is limited.  710 might be more flexible.  At 710 NCSA does not control those racks. 
JI: suggested PW take an action on the colo