XML MIB Modules draftstephanopsxmlmibmoduletemplate00

1
XML MIB Modules draft-stephan-ops-xml-mib-module-
template-00
68th IETF Meeting March 2007 OPS area mini-bof
Emile Stephan
2
Agenda

• Problem statements
• Experimentation with PCE WG MIB
• Benefits of standard XSL transformation
• Proposal

3
Problem statements 1/3

• MIB module editing in XML
• Currently MIB editing under xml2rfc in ltartworkgt
  (to be renamed lthardworkgt? )
• Not respectful of RFC2629 ltartworkgt content
  should be limited to one page
• A non sense to edit manually in ltartworkgt
• Need Editing directly in XML using standard XML
  template
• Save time for MIB editor MIB doctor
• and provide a trajectory for sharing SMI
  definition with other datamodels
• Datamodels sharing
• Currently IETF management framework doesn't
  propose anything for sharing MIB items
  definitions with other IETF network management
  data model such as Netconf.
• More and more appendixes carries XML datamodel
  without any guidance from IETF.
• Normative status of these appendixes become more
  and more unclear.
• Need share XML MIB object definitions
• Developpement
• Waste of Time doubling data model interface
  instance, tests
• Difficult to spec consolidation function relying
  on objects instances from different datamodel
• Operation
• Double poling, tricky consolidation

4
Problem statements 2/3Managing evolution

• Internet network management protocols
• Historically
• SpecifiedMIB/SNMP unspecifiedCLI, ftp..()
• Currently many Std protocols and few nm
  datamodels
• SNMP, COPS, Netconf, IPFIX
• SNMP is massively deployed for a while.
• SMI is still the centrality for fully specified
  network management interfaces
• W3C XML suite is replacing proprietary mgmg
  interfaces protocol
• XML based NM protocols don't have any nm
  interface data models
• untying NM interface spec protocol
• currently
• ASN.1 with SMI/ASN.1 and SNMP/ASN.1 BER
• XML Netconf protocol in XML, datamodel in XML
• Need
• ASN.1 BER XML are not the centrality for
  protocol encoding
• XML by essence is not bandwidth optimized
• Need of a standard XSL specification for
  transforming SMI NM interfaces in data models and
  protocols considered

5
Problem statements 3/3 Missing point

• Share MIB specifications with other data models
• Solution Through a XSL transformation spec

XML MIB module
XSL
SMI
XML Schema
Data models
ASN.1 X208
protocols
SNMP
NETCONF
presentation
XML
ASN.1 BER X209
SSH
SOAP
transport

6
Experimentation with PCE-DISC-MIB 1/4

• Manageability sections in PCE WG docs
• WG documents specify monitoring reqs.
• Editing draft-ietf-pce-disc-mib-02.xml
• Edited using xml2rfc-xxe
• Text section from David draft
• MIB objects definition written in XML
• XSD4MIB.xsl
• From the xml MIB to the schema of MIB
• PCE-DISC-STD-MIB.xsd PCE-DISC-STD-MIBsmi.xsd

7
Experimentation with PCE-DISC-MIB
Editing 2/4
Regular text editor
XXE gui
8
Experimentation with PCE DISC MIB 3/4

• XSL transformation spec for Sharing MIB types,
  objects verbs with other data models

draft-ietf-pce-disc-mib-02.xml
XSD4MIB.xsl transformation
Imports TC
Tables Notifications
Scalars, fields Entry
PCE-DISC-STD-MIB.xsd
PCE-DISC-STD-MIBsmi.xsd
PCE-DISC-STD-MIBverbs.xsd
9
PCE WG experimentation 4/4sum up

• xsd4Mib.xsl
• Indraft-ietf-pce-disc-mib-02.xml
• Out
• PCE-DISC-STD-MIB.xsd
• PCE-DISC-STD-MIBsmi.xsd
• Retro Compatibility
• Xml2rfc, smilint
• draft-ietf-pce-disc-mib-02.txt

10
Benefits 1/4

• Standardization process
• Operation
• Coupling with high level business apps

11
Benefits 2/4 Standardization process

• xsd4Mib.xsl document
• a spec of the tool in a std language and the tool
• Capitalize on manageability sections
• Not dedicated to MIB SNMP
• Cross referencing between NM languages
• Editors
• Faster Editing and more popular
• MIB Review
• Embedded SMI checking
• RW items in sec section, import, lint, compliance
  
• automatic framework section update // xml2rfc
• Avoid non standard XSD appendix in I-D

12
Benefits 3/4 Operation

• Operation consistency
• Std cross referencing among datamodels
• Ex provisioning in unspec XML and monitoring in
  SNMP
• a Mib object instance ??sth?? from XML world
• Space saving
• Avoid duplication of the same data
• Business
• Seamless connection with high level apps

13
Proposal 1/5 minimize efforts duplication
multiplication

• Edit IETF MIB draft in XML
• Standardize XSL translator of XML MIB
• Prepare derivation of this XSL
• Usage

14
Proposal 2/5 IETF MIB draft Editing in XML

• RFC2629
• Add 'smi' Attribute to 'list' element and
  reserved SMI keywords
• Reserved the value 'mibmodule' for 'anchor'
  attribute of section 'Element'
• Specify a XML template for each SMI macro
• Insert them in a model of xml mib module draft to
  be published and/or in xml2rfc-xxe edition panel

Import Identity Scalar Field Table Record notifica
tion
15
Proposal 3/5 Standard XSL translator for XML MIB

• Standardize
• xsd4Mib.xsl for producing
• Schema of the import of a XML MIB module
• Schema of the objects of a XML MIB module
• Schema of the verbs of a XML MIB module
• A single XML schema of well known TCs
• MIB items namespaces and import

16
Proposal 4/5 Same XSL base among datamodels

• Share the XSL as the base for translation towards
  non or specific XML datamodel

ietf-doc-mib-module.xml
Base XSL input
specific XSL output transformation

Datamodel1
Specific XML apps
17
Proposal 5/5 Limits initial usage

• Netconf SOAP operation with MIB verbs