Time Capability in NETCONF
draft-mm-netconf-time-capability-03
http://tools.ietf.org/html/draft-mm-netconf-time-capability
Tal Mizrahi, Yoram Moses
Technion – Israel Institute of Technology
NETCONF, IETF Meeting, March 2015
Time Capability in NETCONF
1
Overview
• This draft defines the time capability.
• Allows time-triggered RPCs.
• Client can attach a scheduled time of execution to
RPCs.
• Server can attach timestamp to RPC reply.
• Very powerful tool for various network configuration
scenarios.
• We defined a similar extension to the OpenFlow
protocol. It is now in OpenFlow 1.5.0 and in the
OpenFlow 1.3.x extension package.
Time Capability in NETCONF
2
Example: Network-wide Commit
All-or-none commit:
• Client sends ‘commit at time T’ to n servers
• A client that receives an error message from some server sends
cancellation messages to all
• In the absence of cancellation, the n switches commit at time T
• Client sends <commit>,
scheduled to time T
• All servers commit at T±δ
• δ is the scheduling accuracy
Client
Server 1
Server 2
...
Server n
Time Capability in NETCONF
3
Scheduled Operations
• RPC may include <scheduled-time> element.
Ts
server executes
operation at Ts.
server
Time
RPC
(with
<scheduled-time> Ts)
client
Time Capability in NETCONF
4
Reporting the Execution time
• RPC may include a <get-time> element.
 RPC reply includes <execution-time>.
server executes
operation at Te.
Te
server
Time
RPC
(with <get-time>)
RPC reply
(with <executiontime> Te)
client
Time Capability in NETCONF
5
Scheduling and Reporting
• RPC may include both <get-time> and <scheduled-time>.
• Client receives feedback about whether the operation was
executed as scheduled.
server executes
operation at Te.
Ts Te
server
Time
RPC
(with <scheduledtime> and <get-time>)
RPC reply
(with <executiontime> Te)
client
Time Capability in NETCONF
6
History of this Draft
• July 2013 – draft 00
• July 2013 – presented in IETF 87, Berlin
• Jan 2014 – draft 01
– Incorporated a lot of feedback from the WG
• Dec 2015 – draft 03 (current draft)
– We believe we addressed all the issues raised on the
mailing list.
• Next step: consider WG adoption
Time Capability in NETCONF
7
THANKS !
Time Capability in NETCONF
8
References
[1] T. Mizrahi, O. Rottenstreich, Y. Moses, "TimeFlip: Scheduling Network Updates with Timestampbased TCAM Ranges", INFOCOM, 2015.
http://tx.technion.ac.il/~dew/TimeFlipINFOCOM.pdf
[2] T. Mizrahi, Y. Moses, "Time-based Updates in Software Defined Networks", the second workshop on
hot topics in software defined networks (HotSDN), 2013.
http://tx.technion.ac.il/~dew/TimeSDN.pdf
[3] T. Mizrahi, Y. Moses, "On the Necessity of Time-based Updates in SDN", in the Open Networking
Summit (ONS), 2014.
http://tx.technion.ac.il/~dew/ONS-Time.pdf
[4] T. Mizrahi, Y. Moses, “Time Capability in NETCONF", draft-mm-netconf-time-capability, work in
progress, 2014.
https://tools.ietf.org/html/draft-mm-netconf-time-capability
[5] Open Networking Foundation, OpenFlow switch specification, Version 1.5.0, 2015.
https://www.opennetworking.org/images/stories/downloads/sdn-resources/onfspecifications/openflow/openflow-switch-v1.5.0.noipr.pdf
[6] Open Networking Foundation, OpenFlow extensions 1.3.x package 2, 2015.
https://www.opennetworking.org/images/stories/downloads/sdn-resources/onfspecifications/openflow/openflow-extensions-1.3.x-pack2-noipr.zip
Time Capability in NETCONF
9