Subject: [Netconf] Fwd: New Version Notification for draft-mahesh-netconf-persistent-00.txt

From: Mahesh Jethanandani <[email-masked]>
Date: Mon, 27 Oct 2014 11:44:56 -0400

I had taken an action item during one of the interim meetings to come up with a draft to address support for commands such as ping and traceroute in a NETCONF setup.

This short draft takes a stab at defining the problem statement, a set of requirements and at least one solution. Should make for some easy reading.

Mahesh Jethanandani
[email-masked]

Begin forwarded message:

> From: [email-masked]
> Date: October 27, 2014 at 8:10:16 AM EDT
> To: "Mahesh Jethanandani" <[email-masked]>, Mahesh Jethanandani <[email-masked]>
> Subject: New Version Notification for draft-mahesh-netconf-persistent-00.txt
> 
> 
> A new version of I-D, draft-mahesh-netconf-persistent-00.txt
> has been successfully submitted by Mahesh Jethanandani and posted to the
> IETF repository.
> 
> Name:        draft-mahesh-netconf-persistent
> Revision:    00
> Title:        NETCONF and persistent responses
> Document date:    2014-10-27
> Group:        Individual Submission
> Pages:        4
> URL:            http://www.ietf.org/internet-drafts/draft-mahesh-netconf-persistent-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-mahesh-netconf-persistent/
> Htmlized:       http://tools.ietf.org/html/draft-mahesh-netconf-persistent-00
> 
> 
> Abstract:
>   This document outlines a solution for NETCONF operations that might
>   be initiated with a single request but require multiple responses to
>   be received, with an ability to terminate the operation at any time.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>