Transcript Netmod Netconf Data Modeling Sharon Chisholm Nortel

Netmod
Netconf Data Modeling
Sharon Chisholm
Nortel
[email protected]
Outline






Netmod Coordinates
Netconf Layers
Status
Scope
Netconf Family of Specifications
Next Steps
Netmod Coordinates

Website
• http://standards.nortelnetworks.com/netconf/
• Instructions on how to join mailing list,
archive, documents of interest

Mailing list
• separate list for data modeling specific
discussions
Netconf Layers
(4)
(3)
(2)
(1)
+-------------+
|
Content
|
+-------------+
|
+-------------+
| Operations |
+-------------+
|
+-------------+
|
RPC
|
+-------------+
|
+-------------+
| Application |
|
Protocol |
+-------------+
+-----------------------------+
|
Configuration data
|
+-----------------------------+
|
+-----------------------------+
| <get-config>, <edit-config> |
+-----------------------------+
|
+-----------------------------+
|
<rpc>, <rpc-reply>
|
+-----------------------------+
|
+-----------------------------+
|
BEEP, SSH, SSL, console
|
|
|
+-----------------------------+
Netmod
Status




BOF at IETF 60
Given guidance to reduce scope ...
Several Internet Drafts
Consolidated input into ‘Framework for
Netconf Data Models’
• http://www.ietf.org/internet-drafts/draftchisholm-netconf-model-01.txt
Scope



Select a single existing data definition language for netconf
content with emphasis placed on existing well-established
solutions.
Identify requirements and best practice for defining
•
•
•
•
•
•
•
•
•
Access control
Compliance
Versioning & backwards compatibility
naming
How to define relationships between elements
Design pattern for defining status, statistics and configuration
information
Notifications
Error Handling
Element Descriptions
Proof of concept data model definition
Netconf Family of Specifications
Netconf 1.0 (protocol, transports)
Netmod Framework
Netconf Protocol Extensions
IETF 62
Next Steps


Netmod editing session today at 1pm, meeting
at the bulletin board
Because
•
•

There doesn’t appear sufficient work for two working
groups.
Some problems such as security (access controll, etc)
and Notifications will span both protocol and data
model specification
Propose rather than creating a netmod working
group, we add it to the netconf charter