[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Begin WG Last Call: draft-ietf-netconf-prot-04

To: "Rob Enns" <rpe@juniper.net>
Subject: Re: Begin WG Last Call: draft-ietf-netconf-prot-04
From: Wes Hardaker <wjhns1@hardakers.net>
Date: Tue, 30 Nov 2004 16:12:43 -0800
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "Andy Bierman" <abierman@cisco.com>, <netconf@ops.ietf.org>
In-reply-to: <062B922B6EC55149B5A267ECE78E5D4407877C28@photon.jnpr.net> (Rob Enns's message of "Tue, 30 Nov 2004 14:06:57 -0800")
Organization: Sparta
References: <062B922B6EC55149B5A267ECE78E5D4407877C28@photon.jnpr.net>
User-agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.4 (Security Through Obscurity, linux)

>>>>> On Tue, 30 Nov 2004 14:06:57 -0800, "Rob Enns" <rpe@juniper.net> said:

Rob> Note that the NETCONF protocol is concerned only with information
Rob> required to get the device into its desired running state.

As I mentioned in my comments.  This whole sentence is untrue.  You
already have operations that request state information.


-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>

References:
- RE: Begin WG Last Call: draft-ietf-netconf-prot-04
  - From: "Rob Enns" <rpe@juniper.net>

Prev by Date: RE: Begin WG Last Call: draft-ietf-netconf-prot-04
Next by Date: Re: Begin WG Last Call: draft-ietf-netconf-prot-04
Previous by thread: RE: Begin WG Last Call: draft-ietf-netconf-prot-04
Next by thread: Begin WG Last Call: draft-ietf-netconf-beep-02
Index(es):
- Date
- Thread