Framework for Netconf Data Models Netmod BOF – IETF 60

1. Framework for Netconf Data ModelsNetmod BOF – IETF 60 Sharon Chisholm – schishol@nortelnetworks,com

2. Outline • Netconf Layering • Building Blocks for Content • Strategy • Considerations for Interoperability • Considerations for Extensibility • Considerations for Parsability • Considerations for Usability

3. Netconf Layering Layer Example +-------------+ +-----------------------------+ | Content | | Configuration data | +-------------+ +-----------------------------+ | | +-------------+ +-----------------------------+ | Operations | | <get-config>, <edit-config> | +-------------+ +-----------------------------+ | | +-------------+ +-----------------------------+ | RPC | | <rpc>, <rpc-reply> | +-------------+ +-----------------------------+ | | +-------------+ +-----------------------------+ | Application | | BEEP, SSH, SSL, console | | Protocol | | | +-------------+ +-----------------------------+

4. Building Blocks for Content Tools for Creating Content W3C XML Schema Framework for Netconf Data Models ‘SMI for Netconf’ Meta-model or Information Model Netconf Data Types Content Standard Data Models Proprietary Data Models

5. Strategy • Applicable to all content – IETF & Proprietary • Leverage existing technology • Prioritize on delivering the ‘Framework’ Document • Capture requirements without rat holing • Framework • We focus syntax restrictions on those that enable interoperability, implementability, parsability, backwards compatibility, readability, and other 'bilities' as required. • We should do a gap analysis compared to existing W3C XML methods and only innovate as necessary. We should be careful to not create CLRs. • We should capture both our use of W3C XML methods to meeting specific requirements as well as out own innovations • We should evaluate our innovations for possible inclusion back into W3C XML specifications

6. Considerations for Interoperability • Data Modeling Language • XML Schema • Conformance • Under discussion (other than per element) • Versioning • The XML Schema version attribute will be used to signify version • Backwards Compatibility • Under Discussion • Object Granularity & Access control • Under Discussion

7. Considerations for Extensibility • Data Types • One per XSD • Let’s not define too many almost identical types • Elements and Attributes • Attributes should have Metadata, not data • Consider the Lack of Extensibility of Attributes • Other Extensibility Considerations • Defining new data types allows extension • The advice about the ‘any’ element might need to be revistited

8. Considerations for Parseability • Well-formed XML • No DTDs • Avoid Mixed Content • Use an Explicit Namespace on Attributes • Use Container Elements for Lists

9. Considerations for Usability • Naming • Proper Tag Names • Error Handling • Design Considerations • Under Discussion • Schema Documentation • Use documentation tag

10. New Topics • Containers versus the data • Under Discussion

11. Next Steps • Find additional editors • Resolve areas with no proposed solution • Identify additional must cover areas • Update draft