1 / 8

Using XML Schema to define NETCONF Content

This paper explores using XML Schema to define content exchanged between NETCONF client and server, emphasizing modularity and data modeling considerations. The approach enables abundant tool usage and immediate implementation.

amim
Télécharger la présentation

Using XML Schema to define NETCONF Content

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using XML Schema to define NETCONF Content Sharon Chisholm schishol@nortel.com December 2007 IETF 70

  2. Background • Draft created to capture offline discussions about requirements and potential solutions for how to define NETCONF content • Current Version • http://www.ietf.org/internet-drafts/draft-chisholm-netconf-model-07.txt

  3. The approach • Requirements • Solution to define content to be exchanged between NETCONF client and NETCONF server. • Similar to what we required to define standard MIBs • Minus some things that don’t seem necessary anymore • Plus some additional meta data • Uses XML Schema, plus defines appInfo tags to fill in gaps • Enables use of abundant off the shelf tools • Allowed us to get started right away

  4. Areas of Requirements • Conformance • Fine Grain Conformance • Operations on managed objects . • Element Status • Additional Conformance Information • Backwards Compatibility • Versioning • Keys • Defining Relationships • Association Relationship • Defining Notification Event Messages • Considerations for Parse-ability • Well-formed XML • Naming • Error Messages • Schema Documentation • Specifying Statistics, Status and Configuration Information

  5. Modeling Considerations • Modularity • Data Types • Elements and Attributes • Naming implications of using XPATH • Proper Tag Names • Granularity of Data Model • Avoid Mixed Content

  6. Updates in -07 • Explained a few more benefits of the approach • Updated notification definition to align with Notification ID • Cleaned up examples to be more consistent and correct • Deleted the section which outlined specific NETCONF operations against the data model since it didn't seem to have much to do with this document. • General cleanup • Added an appendix talking about the potential for a mapping to Yang

  7. Requirements This list is not complete, but demonstrative of the analysis we should probably do

More Related