1. Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science On Time Inder Monga, ESnet

2. Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science How to think about Service Time? The notion of “Time” should be consistent within a “Service Definition” Can specify new “Service Definitions” and standardize them For example, within Connection Service, Advanced Reservation Service (ARS) SD - Start Time = time when service is expected to be available - End Time = time when service is expected to be torn down Immediate Provisioning Service (IPS) SD - Start Time = Now, implies as soon as network is provisioned - End Time = time when service is expected to be torn down. Persistent Infrastructure Service SD - No End time For both the situations above, the Start/End time should be within the Service Parameters rather than common parameters AND, they have specific meanings within the context

3. Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Automated vs Manual Provisioning For ARS, Start Time is when the facility is available for “service” In Automated provisioning, - The connection is setup by the network - The network uses the guard time to reserve the resources and determine when to initiate its own provisioning - Connection available for service by “Start Time” In Manual Provisioning, - Onus of initiating the provisioning on the user. - Facility available for provisioning at “Start Time” - User can query the network for guard times and create “start time” accordingly. - The reservation does not go away if provisioning message does not come at Start time.

4. Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science “Time” is a service specific thing The role of “Time” within NSI “Timeouts” – messages are not received within a certain delta - Not dependent on absolute time, but delta - Assumption that each device has a reasonably accurate clock - Need to account for reasonable in-flight times “Time Synchronization” – already specified, recommended - Any service that supports advance reservation must maintain its own real-time clock and it is necessary for the requester and provider clocks to be synchronized to a mutually acceptable granularity “Service Time” - Manifests itself as “Reserved time”, “Start time + duration”, “Start/End time” etc.