[ipfix] FYI: IPFIX XML work (fwd)
Juergen Quittek <quittek@netlab.nec.de> Sun, 28 May 2006 23:24 UTC
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FkUcZ-0007IX-H8 for ipfix-archive@lists.ietf.org; Sun, 28 May 2006 19:24:31 -0400
Received: from mil.doit.wisc.edu ([128.104.31.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FkUcY-0004O5-64 for ipfix-archive@lists.ietf.org; Sun, 28 May 2006 19:24:31 -0400
Received: from majordomo by mil.doit.wisc.edu with local (Exim 3.13 #1) id 1FkUYa-0006Ea-00 for ipfix-list@mil.doit.wisc.edu; Sun, 28 May 2006 18:20:24 -0500
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by mil.doit.wisc.edu with esmtp (Exim 3.13 #1) id 1FkUYY-0006EL-00 for ipfix@net.doit.wisc.edu; Sun, 28 May 2006 18:20:22 -0500
Received: from [192.168.1.130] (HSI-KBW-085-216-002-068.hsi.kabelbw.de [85.216.2.68]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 4D8471BAC4D for <ipfix@net.doit.wisc.edu>; Mon, 29 May 2006 01:11:16 +0200 (CEST)
Date: Mon, 29 May 2006 01:20:17 +0200
From: Juergen Quittek <quittek@netlab.nec.de>
To: ipfix@net.doit.wisc.edu
Subject: [ipfix] FYI: IPFIX XML work (fwd)
Message-ID: <AEA80337B44EF41063F74206@[192.168.1.130]>
X-Mailer: Mulberry/3.1.6 (Mac OS X)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==========3B4054F599C905316AF2=========="
Precedence: bulk
Sender: majordomo listserver <majordomo@mil.doit.wisc.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Dear all,
FYI, the message below was posted last week on the NetConf mailing list.
Juergen
------------ Forwarded Message ------------
Date: Wednesday, Mai 24, 2006 09:45 h -0700
From: Andy Bierman <ietf@andybierman.com>
To: "Netconf (E-mail)" <netconf@ops.ietf.org>, Netconf Data Model Discussion <netconfmodel@lists.nortel.com>, Dan Romascanu <dromasca@avaya.com>
Subject: FYI: IPFIX XML work
Hi,
I think you should read Appendix A of the IPFIX Info Model draft:
http://www.ietf.org/internet-drafts/draft-ietf-ipfix-info-11.txt
IMO, it would be a *really* bad idea for every std NM protocol with
DM info (snmp, syslog, ipfix, netconf, ?) to invent their own
DM language, module & life-cycle system, access control model,
core info model, naming model, and on and on...
Dan, I think you should force the IPFIX WG to break out (at least)
the core set of 'XML Simple Types' from this document
and let all the OPS-NM WGs review it and add/change it.
Then it should be published as a PS RFC, and all XML DM work
in the IETF must use those data types, if they apply.
By the time one figures out the "free-for-all" approach doesn't work,
it is usually too late to fix it.
Andy
--
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/>
---------- End Forwarded Message ----------
--- Begin Message ---Hi, I think you should read Appendix A of the IPFIX Info Model draft: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-info-11.txt IMO, it would be a *really* bad idea for every std NM protocol with DM info (snmp, syslog, ipfix, netconf, ?) to invent their own DM language, module & life-cycle system, access control model, core info model, naming model, and on and on... Dan, I think you should force the IPFIX WG to break out (at least) the core set of 'XML Simple Types' from this document and let all the OPS-NM WGs review it and add/change it. Then it should be published as a PS RFC, and all XML DM work in the IETF must use those data types, if they apply. By the time one figures out the "free-for-all" approach doesn't work, it is usually too late to fix it. Andy -- 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/>--- End Message ---
- [ipfix] FYI: IPFIX XML work (fwd) Juergen Quittek