1. N ETWORK C ONFIGURATION Prepared by: Menna Hamza Mohamad Hesham Mona Abdel Mageed Yasmine Shaker

2. A GENDA OPS NetConfig Work Group NetConfig Protocol XML Detour Definitions Protocol Layers Protocol Main Scenario Basic Operations Filters Example Partial Lock RPC With Default Capability TLS

3. OPERATIONS AND MANAGEMENT AREA Area Workgroups Examples: Adslmib : ADSL MIB Adslmib Capwap : Control And Provisioning of Wireless Access Points. Capwap Bmwg : Benchmarking Methodology Bmwg Dime : Diameter Maintenance and Extensions Dime Netconf : Network Configuration Netconf

4. NETCONF WORKING GROUP The NETCONF Working Group is chartered to produce a protocol suitable for network configuration. required characteristics includes: Differentiate between configuration data and non- configuration data. Extensible. Integration with user authentication methods. Integration with configuration database systems. Wide configuration transactions with features such as locking and rollback capability.

5. N ET C ONFIG P ROTOCOL The protocol provides mechanism to transfer and manipulate configuration data in a network device It uses an Extensible Markup Language (XML)- based data encoding for the configuration data and the protocol messages. The NETCONF protocol operations are realized on top of a simple Remote Procedure Call (RPC) layer.

6. XML D ETOUR XML Why XML? XSD and Schemas Xpath XML Node XML Sub Tree Example

7. XML E XAMPLE root superuser Charlie Root 1 Value of Xpath (top/users/user/name)

8. D EFINITIONS Application / client Server / Device Data Store / Configuration file Capabilities

9. P ROTOCOL L AYERS Configuration Data Status Data? Content ….. Operation RPC SSL, SSH, BEEP, console Transport Protocol

10. A way for both client and server to announce there existence It also serves as an announcement of session ID as well as supported features !!! Extendible protocol means that there is no guarantee that the server and client support the same set features. Base capability must be supported How to handle different set of features?

11. S ERVE M E The client the needed advertised capabilities requests to the Server. The Server processes the requests on a FIFO basis (Pipe Line) The Server sends Required Data/ request status to the client How to associate a request with a reply? Client closes the session or Server terminates session due to timeout

12. RPC F OR L IFE Client Requests are RPC calls The data store is conceptually a list of XML namespaces The RPC manipulates these XML namespaces Changes to the XML name spaces are mapped by the device to actual changes in it’s internal configuration (registers, etc..) Server reply contains requested XML data, errors, warnings and optionally execution success feedback

13. B ASIC O PERATIONS Get get get-config Manipulate edit-config copy-config delete-config Parallel access control Lock unlock End session close-session kill-session

14. RPC BLOCKS

15. F ILTERS What’s a filter Using a filter Demo

16. <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> root

17. <rpc-reply message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> root superuser Charlie Root 1

18. E XTENDED C APABILITIES C ASE S TUDTIES Partial lock With default Capabilities

19. P ARTIAL L OCK RPC Describes the lock and unlock operations on parts of configuration data stores using XPath filtering mechanisms Definition of Terms Scope of the lock Protected area

20. P ARTIAL L OCKING C APABILITY Usage Scenarios Multiple managers with overlapping sections Multiple managers, distinct management areas New Operations

21. o Locking a node protects the node itself and the complete sub-tree under the node o The XPath expressions are evaluated only once at lock time o NETCONF server that supports partial locking MUST be able to grant multiple simultaneous partial locks to a single NETCONF session. o Failure o Global lock o Already locked o User does not have access rights

22. ( CTD.) RPC Call Parameters Filter (Lock) ID (Unlock) Deadlock Avoidance RPC Reply Positive (Lock ID in case of lock) Negative

23. W ITH DEFAULT CAPABILITY It’s just a new XML child element added to the method-name element. part of the configuration data is not set by the NETCONF client, but rather a default value is used. Some times NETCONF client has a prior knowledge about this default data, so the NETCONF server does not need to send it to the client. In other situations the NETCONF client will need this data so it must be sent at the NETCONF messages.

24. R EPORTING MODES report-all: All default data is always reported. trim: Values are not reported if they match the default. explicit: Default data is not reported except explicitly set default data.

25. NETCONF OVER TLS Configuration exchange must be secure. TLS Provide support for certificate-based mutual authentication. TLS is application-protocol-independent. How NETCONF can be used within a TLS session?

26. NETCONF OVER TLS Connection Initiation ClientHello message Handshake Start Exchange XML Connection Closure Agent (NETCO NF) Server (TLS) Manger (NETCO NF) Client (TLS )

27. NETCONF OVER TLS Endpoint Authentication and Identification Server Identity 1. The server hostname 2. Matching is case-insensitive. 3. A "*" wildcard character. 4. multiple names is acceptable. Client Identity

28. Q UESTIONS

29. C ONTANCTS Group Mail : 4-team-Group@yahoogroups.com4-team-Group@yahoogroups.com Menna Hamza: hamza.menna@gmail.comhamza.menna@gmail.com Mohamad Hesham : iris_lastdance@yahoo.comiris_lastdance@yahoo.com Mona AbdelMageed : monaabdelmageed@yahoo.commonaabdelmageed@yahoo.com Yasmine Sahker : engineer.jessy@yahoo.comengineer.jessy@yahoo.com