Re: draft-shafer-netconf-syslog-00.txt

Phil Shafer <phil@juniper.net> Mon, 26 June 2006 21:24 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuyZc-0004oI-Ib for netconf-archive@lists.ietf.org; Mon, 26 Jun 2006 17:24:48 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuyZb-00084o-8o for netconf-archive@lists.ietf.org; Mon, 26 Jun 2006 17:24:48 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-netconf@ops.ietf.org>) id 1FuyWe-000JXG-8x for netconf-data@psg.com; Mon, 26 Jun 2006 21:21:44 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.1
Received: from [207.17.137.64] (helo=colo-dns-ext2.juniper.net) by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.60 (FreeBSD)) (envelope-from <phil@juniper.net>) id 1FuyWd-000JX1-NP for netconf@ops.ietf.org; Mon, 26 Jun 2006 21:21:43 +0000
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id k5QLLf1Z086144; Mon, 26 Jun 2006 14:21:41 -0700 (PDT) (envelope-from phil@juniper.net)
Received: from idle.juniper.net (leida.juniper.net [172.18.16.26]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k5QLLf584783; Mon, 26 Jun 2006 14:21:41 -0700 (PDT) (envelope-from phil@juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.12.6/8.11.3) with ESMTP id k5QLLewn055980; Mon, 26 Jun 2006 17:21:40 -0400 (EDT) (envelope-from phil@idle.juniper.net)
Message-Id: <200606262121.k5QLLewn055980@idle.juniper.net>
To: Balazs Lengyel <balazs.lengyel@ericsson.com>
cc: netconf@ops.ietf.org
Subject: Re: draft-shafer-netconf-syslog-00.txt
In-Reply-To: Your message of "Thu, 22 Jun 2006 11:55:04 +0200." <449A68F8.8010608@ericsson.com>
Date: Mon, 26 Jun 2006 17:21:40 -0400
From: Phil Shafer <phil@juniper.net>
Sender: owner-netconf@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

Balazs Lengyel writes:
>1) I want to fetch recorded data from yesterday 12:00Z till
>13:00Z. The draft doesn't seem
>to allow this as the stop time is already in the past. I would allow this!

The draft allows this; see 3.2.1.1 (Closing the Response).

>2) Same comments as for Sharon's draft:
>Use a data model for streams and use the get and edit-config
>operations instead of a custom operation for a small set of special
>(?) data. Even if streams can be defined in multiple ways
>(configuration, system default, etc.) they still can nicely be modeled
>as read-only data. 

System defaults aren't read-only data; see 1.3 in the netconf-prot
spec.

> > I'm not prepared to be the first lamb on that altar.  ;^)
>Someone has to be :-) otherwise NETCONF is dead already.

Nope, it's the opposite.  NETCONF is in its infancy.  The raw config
parts are starting to gel and get widely implemented but the role of
standard data models, how they are defined, where they fit, how and
when the translation between the standard and the device-specific
occurs, and what to do when things don't quite translate are all wide
open areas which need tons of work.

We should work to make our puppy grow up, but should continue to do
reasonable work in parallel to allow the growing pup is useful asap
for taming real world problems.

Thanks,
 Phil

--
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/>