1. http://standards.nortelnetworks.com/netconf/ PG 1 Framework for Netconf Data Models Netmod BOF – IETF 60 Sharon Chisholm – schishol@nortelnetworks,com

2. PG 2 schishol@nortelnetworks.com Netconf Layering Building Blocks for Content Strategy Considerations for Interoperability Considerations for Extensibility Considerations for Parsability Considerations for Usability Outline

3. PG 3 schishol@nortelnetworks.com Netconf Layering Layer Example +-------------+ +-----------------------------+ | Content | | Configuration data | +-------------+ +-----------------------------+ | | +-------------+ +-----------------------------+ | Operations | |, | +-------------+ +-----------------------------+ | | +-------------+ +-----------------------------+ | RPC | |, | +-------------+ +-----------------------------+ | | +-------------+ +-----------------------------+ | Application | | BEEP, SSH, SSL, console | | Protocol | | | +-------------+ +-----------------------------+

4. PG 4 schishol@nortelnetworks.com Building Blocks for Content Framework for Netconf Data Models ‘SMI for Netconf’ W3C XML Schema Netconf Data Types Meta-model or Information Model Standard Data ModelsProprietary Data Models Content Tools for CreatingContent

5. PG 5 schishol@nortelnetworks.com 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. PG 6 schishol@nortelnetworks.com 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. PG 7 schishol@nortelnetworks.com 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. PG 8 schishol@nortelnetworks.com Considerations for Parseability Well-formed XML No DTDs Avoid Mixed Content Use an Explicit Namespace on Attributes Use Container Elements for Lists

9. PG 9 schishol@nortelnetworks.com Considerations for Usability Naming Proper Tag Names Error Handling Design Considerations Under Discussion Schema Documentation Use documentation tag

10. PG 10 schishol@nortelnetworks.com New Topics Containers versus the data Under Discussion

11. PG 11 schishol@nortelnetworks.com Next Steps Find additional editors Resolve areas with no proposed solution Identify additional must cover areas Update draft

12. PG 12 schishol@nortelnetworks.com