RFC 7758 on Time Capability in NETCONF

rfc-editor@rfc-editor.org Wed, 03 February 2016 01:59 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21AD01B3154 for <ietf-announce@ietfa.amsl.com>; Tue, 2 Feb 2016 17:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f4NsrTx7A7md for <ietf-announce@ietfa.amsl.com>; Tue, 2 Feb 2016 17:59:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64FA31B31A2 for <ietf-announce@ietf.org>; Tue, 2 Feb 2016 17:59:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4428B1804F4; Tue, 2 Feb 2016 17:58:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7758 on Time Capability in NETCONF
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160203015859.4428B1804F4@rfc-editor.org>
Date: Tue, 02 Feb 2016 17:58:59 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/-VTDR32fez_u_i1qV3REQv0221Q>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 01:59:19 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7758

        Title:      Time Capability in NETCONF 
        Author:     T. Mizrahi, Y. Moses
        Status:     Experimental
        Stream:     IETF
        Date:       February 2016
        Mailbox:    dew@tx.technion.ac.il, 
                    moses@ee.technion.ac.il
        Pages:      32
        Characters: 56330
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mm-netconf-time-capability-09.txt

        URL:        https://www.rfc-editor.org/info/rfc7758

        DOI:        http://dx.doi.org/10.17487/RFC7758

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.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC