Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 28: FUNCTIONAL NETWORK PROGRAMABILITY CONCEPTS (Application…
CHAPTER 28:
FUNCTIONAL NETWORK PROGRAMABILITY CONCEPTS
Application Programming Interface (API)
Software mechanisms to communicate with applications and other software
Northbound API
From network controller to management software
Southbound API
From management software to individual devices
Representational State Transfer (REST) APIs
HTTP methods to gather and manipulate data
GET, POST, PUT, PATCH, DELETE
CRUD:
Create, Read, Update, Delete
Collections:
Group of API Calls
Data Formats (Encoding)
Extensible Markup Language (XML)
<tag>Value</tag>
JavaScript Object Notation (JSON)
{ "key": "value" ,"key2": "value2"}
HTTP Codes
200: OK
201: Created
400: Bad Request
401: Unauthorized
403: Forbidden
404: Not Found
Data Models
Describe whatever can be configured, monitored or executed in a device
Yet Another Next Generation (YANG)
RFC 6020
Tree structure with configuration data and state information.
A
leaf
node contains simple data like an integer or a string.
A
container
node is used to group related nodes in a subtree.
A
list
defines a sequence of list entries.
Network Configuration (NETCONF)
RFC6241
Protocol that uses the YANG data models to communicate with the various devices on the network
Operations:
<get>, <get-config>, <edit-config>, <copy-config>, <delete-config>
RESTCONF
RFC8040
Provides RESTful API experience