Time Capability in NETCONF
RFC 7758

Document Type RFC - Experimental (February 2016; No errata)
Last updated 2016-02-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd No shepherd assigned
Shepherd write-up Show (last changed 2015-08-31)
IESG IESG state RFC 7758 (Experimental)
Consensus Boilerplate Yes
Telechat date
Responsible AD Joel Jaeggli
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                        T. Mizrahi
Request for Comments: 7758                                      Y. Moses
Category: Experimental                                          Technion
ISSN: 2070-1721                                            February 2016

                       Time Capability in NETCONF

Abstract

   This document defines a capability-based extension to the Network
   Configuration Protocol (NETCONF) that allows time-triggered
   configuration and management operations.  This extension allows
   NETCONF clients to invoke configuration updates according to
   scheduled times and allows NETCONF servers to attach timestamps to
   the data they send to NETCONF clients.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7758.

Mizrahi & Moses               Experimental                      [Page 1]
RFC 7758               Time Capability in NETCONF          February 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Mizrahi & Moses               Experimental                      [Page 2]
RFC 7758               Time Capability in NETCONF          February 2016

Table of Contents

   1. Introduction ....................................................4
   2. Conventions Used in This Document ...............................4
      2.1. Key Words ..................................................4
      2.2. Abbreviations ..............................................5
      2.3. Terminology ................................................5
   3. Using Time in NETCONF ...........................................5
      3.1. The Time Capability in a Nutshell ..........................5
      3.2. Notifications and Cancellation Messages ....................7
      3.3. Synchronization Aspects ....................................9
      3.4. Scheduled Time Format .....................................10
      3.5. Scheduling Tolerance ......................................10
      3.6. Scheduling the Near vs. Far Future ........................11
      3.7. Time-Interval Format ......................................13
   4. Time Capability ................................................14
      4.1. Overview ..................................................14
      4.2. Dependencies ..............................................14
      4.3. Capability Identifier .....................................14
      4.4. New Operations ............................................14
      4.5. Modifications to Existing Operations ......................15
           4.5.1. Affected Operations ................................15
           4.5.2. Processing Scheduled Operations ....................16
      4.6. Interactions with Other Capabilities ......................16
   5. Examples .......................................................17
      5.1. <scheduled-time> Example ..................................17
      5.2. <get-time> Example ........................................18
      5.3. Error Example .............................................19
   6. Security Considerations ........................................19
      6.1. General Security Considerations ...........................19
      6.2. YANG Module Security Considerations .......................20
   7. IANA Considerations ............................................21
   8. References .....................................................22
Show full document text