[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Charter items
In this particular priority order:
1) SMI
Name convention (Ethernet0/0, or slot="Ethernet0", port="0", etc)
common data type (interface, ipv4addr (or ipaddrv4, ipaddressv4),
counter, integer, string, etc.)
tag convention (object tag, attribute tag, etc.)
2) Minimum common schema (MIB?)
3) Security
But let's focus on current draft first.
--
Weijing Chen
SBC Technology Resources
9505 Arboretum Blvd.
Austin, TX 78759
512 372 5710
wchen@tri.sbc.com
-----Original Message-----
From: Ron Bonica [mailto:Ronald.P.Bonica@wcom.com]
Sent: Friday, March 28, 2003 9:36 AM
To: xmlconf@ops.ietf.org
Subject: Charter items
Folks,
Draft-enns-xmlconf-spec-00.txt give us an excellant start. It seems that
three more work items are before us. These are:
1) adopt or create a structure of management information (as did RFC 1155)
2) codify some very basic management information (as did RFC 1213)
3) define a security model and invite security experts to crawl all over it
Comments?
===========================================
Ronald P. Bonica Ph: 703 886 1681
vBNS Engineering page: 1 888 268 8021
Ashburn, Va.
===========================================
"We are not on Earth to guard a museum, but
to cultivate a flourishing garden of life."
-- Angelo Giuseppe Roncalli
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>
--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>