All Rights Reserved Copyright © 2007,Hitachi.Ltd. VLAN data model for NETCONF ( draft-iijima-ngo-vlandatamodel-00) Thursday, March 22, 2007 Tomoyuki Iijima, Kunihiko Toumura, Hideki Okita (Hitachi Central Research Lab) Yoshifumi Atarashi, Hiroyasu Kimura (Alaxala Networks) 68 th IETF meeting NGO BoF

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -2- Proposed goals for NGO WG Investigate NETCONF architecture which can collaborate with other operation sub-systems and application systems. Publish guidelines for NETCONF application developers. Publish data model over NETCONF to exchange configuration data between NETCONF applications and network devices.

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -3- NETCONF data model NETCONF standardization process has almost finished. To discuss NETCONF data model, NGO (NETCONF Goes On) BoF was established after the 67 th meeting. SSH, SOAP, BEEP, Configuration data Transport Protocol RPC Operations Content NETCONF layer Modeling has not been done. RFC4741 RFC4742, 4743, 4744

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -4- Benefits of NETCONF data model Interoperability –Vendors can exchange NETCONF message based on the defined data model. Extensibility –If data modeling is done visually, it is easy to grasp the structure and relations of each configuration data, which makes it easier to append a new configuration data to the existing data model.

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -5- Things to be considered regarding data model interoperability Rough data model is enough –You can transform data model into another one, thanks to the features of XML technology. XML schema XSLT Standardized XML parser available Future extensibility has to be taken into account –There should be no compatibility problem by future extension.

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -6- Network functions to be modeled We extracted network functions to be modeled from a typical network. Internet ISP Enterprise network Filtering (ACL) VRRP VLAN Filtering (ACL) Routing Filtering (ACL) Routing Home

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -7- Configuration data required to be incorporated We incorporated following configuration data into each network function’s data model. FunctionConfiguration data VLANVLAN ID, VLAN name, etc. Filtering (Access Control List) Source IP addr, Destination IP addr, Source port, Destination port, etc. RouteDestination IP, Next hop address, etc. LinePort ID, Speed, Line name, PoE, etc. Link AggregationLink Aggregation, Group ID, port ID list, etc. NodeNode name, Location, etc.

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -8- VLAN’s UML class diagram Vlan - vlanid : short - vlanname : String - logicalIF : LogicalIF - assortmentPort : AssortmentPort TaggedPort - transtag : short ProtocolBasedPort - protocol : String[] MacBasedPort - macAddress : MacAddress[] IpSubnetPort - subNet : String[] UntaggedPort AssortmentPort - portid : String[] - type : String LogicalIF - IPV4Address : IPV4Address[] - IPV6Address : IPV6Address[} > IVlan - setLocator(Locator lctr) : void - getConfig() : short[] - getConfig(short id) : Vlan - getConfig(short[] ids) : Vlans - editConfigDelete(Vlan vlan) : void - editCOnfigMerge(Vlan vlan) : void IPV4Address - value : IPAddress IPV6Address - value : IPAddress association (has-a) inheritance (is-a) realization

All Rights Reserved Copyright © 2007,Hitachi.Ltd. -9- VLAN’s APIs generated from UML VariablesMethod VLAN IDsetVlanid(short vlanid) getVlanid() VLAN namesetVlanname(string vlanname) getVlanname() Tag VLANsetTaggedVlan(TaggedPort taggedPort) getTaggedVlan() Protocol VLANsetProtocolVlan(ProtocolBasedPort protocolBasedPort) getProtocolVlan() MAC VLANsetMacbasedVlan(MacbasedPort macBasedPort) getMacbasedVlan() Untagged VLANsetUntaggedVlan(UntaggedPort untaggedPort) getUntaggedVlan()

All Rights Reserved Copyright © 2007,Hitachi.Ltd VLAN’s XML schema, xsd format (1/4) <xs:schema id="onapi-datamodel_1.1" targetNamespace="urn:net:alaxala:oan:onapi:commons:netmod:1.1" xmlns:ncp="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:xs=" xmlns:nm1_0="urn:net:alaxala:oan:onapi:commons:netmod:1.0" xmlns:nm1_1="urn:net:alaxala:oan:onapi:commons:netmod:1.1">

All Rights Reserved Copyright © 2007,Hitachi.Ltd VLAN’s XML schema, xsd format (2/4)

All Rights Reserved Copyright © 2007,Hitachi.Ltd VLAN’s XML schema, xsd format (3/4)

All Rights Reserved Copyright © 2007,Hitachi.Ltd VLAN’s XML schema, xsd format (4/4)

All Rights Reserved Copyright © 2007,Hitachi.Ltd Expected issue in the NGO WG Which schema should be used to express a data model? Assumptions –Expected target users of data model Network Operators Network Management System Developers Network Device Developers –Development efficiency is the most important point XML Development Environment Applicability to OOP concept

All Rights Reserved Copyright © 2007,Hitachi.Ltd Comparison between XSD and Relax NG Available XML Development Environment –Developers/Operators use XML API and do not directly treat raw XML data. (Raw XML data is an intermediate expression for them) –Major Development Environment in Web app. world seem to support W3C Schema, not RelaxNG. Applicability to OOP concept –OOP Language like C++ or Java is suitable for XML data processing. –JDK supports W3C Schema by default. W3C Schema (XSD)RelaxNG Environments.NET, Apache Xerces (JDK), libxml2 libxml2, relaxer Schema EditorVisual Studio, Eclipse, OxygenOxygen LanguageC/C++, Java, PerlC, Java Red: major development environments in the Web app. world

All Rights Reserved Copyright © 2007,Hitachi.Ltd NETCONF application example VLAN assignment app. for video streaming VLAN 100 Configuration application implementing VLAN APIs VLAN 100 assign by NETCONF request Operator using Configuration Application Video Server User A Port 0/7 Port VLAN NETCONF reply

All Rights Reserved Copyright © 2007,Hitachi.Ltd Implementation example public class AxConfig { private static short authedVlanId = 100; // … public boolean setPortVlan(int portNum) { // … try { Vlan vlan = new Vlan(); vlan.setVlanid(authedVlanId); UntaggedPort utport = new UntaggedPort(); StringBuffer sb = new StringBuffer("port 0/"); sb.append(portNum); String[] strs = { sb.toString() }; utport.setPortid(strs); vlan.setUntaggedPort(utport); vlanImpl.editConfigMerge(vlan); } catch (Exception e) { // … } 0100 VLAN0100 port 0/7 UNTAGGED_PORT What developers write:What goes on wire:

All Rights Reserved Copyright © 2007,Hitachi.Ltd Implementation Example (cont.) 0100 VLAN0100 port 0/7 UNTAGGED_PORT What goes on wire (magnified one )

All Rights Reserved Copyright © 2007,Hitachi.Ltd Proposal to INTAP/OSMIC We proposed our data model to INTAP/OSMIC and it was accepted as a reference data model. –INTAP (Interoperability Technology Association for Information Processing) Organization established by Japanese government. Promote progress of information technologies. –OSMIC (Open Systems Management Industry Collaboration) INTAP’s sub-committee. Implement and evaluate interoperability among implementations of multiple vendors.

All Rights Reserved Copyright © 2007,Hitachi.Ltd Conclusion We showed our VLAN data model as a reference in order to stimulate NETCONF data model discussion. We would like to request this I-D to be accepted as an informational I-D for a future scope of NGO WG. Let’s start NGO WG!!

All Rights Reserved Copyright © 2007,Hitachi.Ltd XML Tools References Language Specifications – – Development Environments – – –

All Rights Reserved Copyright © 2007,Hitachi.Ltd XML schema shown on designing tool

All Rights Reserved Copyright © 2007,Hitachi.Ltd WSDL shown on designing tool