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

Jon Saperia <saperia@jdscons.com> Wed, 06 June 2007 12:52 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 1Hvuzv-0004wR-Kt; Wed, 06 Jun 2007 08:52:23 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43) id 1Hvuzu-0004wM-5w for ops-nm-confirm+ok@megatron.ietf.org; Wed, 06 Jun 2007 08:52:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvuzt-0004wE-Sn for ops-nm@ietf.org; Wed, 06 Jun 2007 08:52:21 -0400
Received: from rs32.luxsci.com ([65.61.166.73]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvuzs-0002jo-Ie for ops-nm@ietf.org; Wed, 06 Jun 2007 08:52:21 -0400
Received: from [192.168.5.101] (static-72-93-205-34.bstnma.fios.verizon.net [72.93.205.34]) (authenticated bits=0) by rs32.luxsci.com (8.13.1/8.13.7) with ESMTP id l56CqEiu007224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 6 Jun 2007 07:52:14 -0500
Message-ID: <4666ADF5.8010008@jdscons.com>
Date: Wed, 06 Jun 2007 08:52:05 -0400
From: Jon Saperia <saperia@jdscons.com>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.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>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A040D8023@307622ANEX5.global.avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
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

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

Romascanu, Dan (Dan) wrote:
>  
>  
>  
>  
>
>
> ________________________________
>
> 	From: Jon Saperia [mailto:saperia@jdscons.com] 
> 	
>
> 			XML-based management leverages lessons learned
> from the WWW. 
> 			While document-based rather than command-based,
> tasks can 
> 			often be grouped into a document-type interface,
> such as a 
> 			web page. With automated translation from XML
> into HTML (and 
> 			related technologies), we can work on developing
>
> 			task-based-document NM interfaces. 
> 			
> 			I think we need to spend more time thinking
> about operator 
> 			use-cases, not just technical designs of SMIs. I
> think it 
> 			would help to start thinking in terms of modular
> data models 
> 			similar to MIB modules, not just a <running>
> config,  but we 
> 			need to develop an SMI that helps to
> differentiate config and 
> 			state info, which SMIv2 doesn't do, Maybe all we
> need to do 
> 			is recommend that MIB modules have separate
> subtrees for 
> 			config and for state, much as we now recommend
> separate 
> 			subtrees for objects and notifications. 
> 			    
>
> 		
> 		Maybe, but at this point in time all the base of
> standard MIB modules is
> 		not designed this way. What are we going to do, re-write
> these MIB
> 		modules, or part of them? This does not seem an
> achievable task. 
> 		  
>
>
> 	I have seen a couple of references in the discussion to State
> and netconf.  Can we be more specific about what we mean by state here.
> Configuration state?  When I think of other types of state such as
> operational state or quality state I think of either read MIB objects or
> notifications (traps/informs).
> 	[DR]  
> 	[DR] My interpretation was state as in state of the system which
> is the super-set of configuration state, but not limited to
> configuration state. It is David however who introduced the term in the
> thread, so I would rather have him answer. 
> 	 
> 	Dan
> 	 
> 	
> 	
>
>
>   

-- 
Jon Saperia
(cell) 617-201-2655
(Eve.) 978-461-0264



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