IETF Logo Mail Archive

Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal

Andy Bierman <ietf@andybierman.com> Wed, 06 June 2007 16:06 UTC

Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvy1r-0007Gl-Tx; Wed, 06 Jun 2007 12:06:35 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43) id 1Hvy1q-0007Gg-4w for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 12:06:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvy1p-0007GX-Ri for ops-nm@ietf.org; Wed, 06 Jun 2007 12:06:33 -0400
Received: from smtp107.sbc.mail.mud.yahoo.com ([68.142.198.206]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hvy1o-0008E2-ID for ops-nm@ietf.org; Wed, 06 Jun 2007 12:06:33 -0400
Received: (qmail 77092 invoked from network); 6 Jun 2007 16:06:32 -0000
Received: from unknown (HELO ?127.0.0.1?) (andybierman@att.net@76.195.156.84 with plain) by smtp107.sbc.mail.mud.yahoo.com with SMTP; 6 Jun 2007 16:06:31 -0000
X-YMail-OSG: 7.xlxTYVM1kOt9MKMrB65pjXFrvQpPvrA_rS1HtNsEB9PkMk
Message-ID: <4666DB53.5040700@andybierman.com>
Date: Wed, 06 Jun 2007 09:05:39 -0700
From: Andy Bierman <ietf@andybierman.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jon Saperia <saperia@jdscons.com>
Subject: Re: [OPS-AREA] RE: [OPS-NM] Comments on XSDMI BoF proposal
References: <4664489B.1000406@andybierman.com> <02c901c7a7aa$ab924fc0$0600a8c0@china.huawei.com> <EDC652A26FB23C4EB6384A4584434A040D7E8D@307622ANEX5.global.avaya.com> <466686FF.3090906@jdscons.com> <EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com> <4666ADF5.8010008@jdscons.com>
In-Reply-To: <4666ADF5.8010008@jdscons.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Ops-Nm <ops-nm@ietf.org>
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Jon Saperia wrote:
> Thanks for the clarification, lets see what Dave says.  If it is as you 
> say, then I would say what is the justification for introducing 
> duplication of information?

What duplication are you talking about?

BTW, I do not agree with the RFC 4741 definition of config
because it is incomplete.

I use a very NETCONF-centric definition, with 3 states:

   config: Persistent Configuration
           * saved in NV-storage
           * included in <get-config>, <edit-config>, <copy-config>

   tconfig: Transient Configuration (e.g., per-session configuration)
           * not saved in NV-storage
           * included in <get-config>, <edit-config>, <copy-config>

   state: Non-Configuration Data
           * not saved in NV-storage
           * not included in <get-config>, <edit-config>, <copy-config>


> /jon


Andy


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm

v2.23.0 | Report a Bug | By Email