IETF standard models

Framework

The Internet Engineering Task Force (IETF) creates standard models to support use cases in the northbound Interfaces (NBIs) of IP controllers. These models focus primarily on L2NM and L3NM network services, IETF network definitions, and IETF TE functions.

The NSP features an IETF framework that functions as a programmable northbound mediation layer, allowing for the import of IETF-based models into the NSP. CRUDL operations are automatically supported, with necessary invocations to NSP functions, as required. Customization is supported for overriding the CRUDL operations.

All IETF configurations are performed using the NSP RESTCONF API. Imported IETF service or network YANG models are exposed via the API, which is compliant with RESTCONF RFC 8040.

Architecture

The following diagram shows the architecture of the NSP's IETF framework.

View the figure

In order to use the NSP IETF framework, the Network Infrastructure Management and Service Activation and Configuration licensed packages must be part of your deployment. Additionally, several artifacts must be installed, including IETF artifacts, logical inventory adaptors, datasync mapping files, and predefined intent types. Documents delivered with these artifacts provide installation and compatibility information. These can be obtained from the Nokia Support Portal at the following locations:

  1. NSP/release/Adaptors/vendor — where vendor is the supported device type.

    NOTE: Customers should refer to the relevant adaptor documentation for more details about the adaptor suites. These documents are available from the Nokia Support Portal alongside the adaptor suites.

  2. NSP/release/Artifacts — This directory hosts artifacts available for production NSP deployments. It contains the predefined NSP service intents collection that is required for IETF services: NSP_Predefined_Service_Intents_release_version.zip. This directory also contains NSP ZTP intents, and device configuration intents, which are unrelated to the NSP IETF framework.

  3. NSP/release/Beta_Artifacts — This directory hosts artifacts that come with certain limitations. Most IETF artifacts can be found here, as well as the associated MoPs.

See the NSP Network Automation Guide for information about installing artifacts.

Topology

NSP supports the use of RESTCONF to retrieve IETF-compliant topology models, including layer 2 and 3 topology aspects, and traffic engineering topology aspects. This is in accordance with RFC8345, RFC8346, RFC8944, and draft-dbwb-opsawg-sap-02, and allows for the retrieval of service attachment points. IETF-compliant topology models are retrieved using the NSP's RESTCONF APIs. Visit the Network Developer Portal for more information.

Logical inventory

NSP supports the use of RESTCONF to retrieve IETF-compliant and OpenConfig-compliant logical interfaces, as defined by the TIP MUST IP SDN Controller NBI Technical requirements document. This is in accordance with RFC8345, RFC8528, and OpenConfig specifications. IETF-compliant logical inventory models are retrieved using the NSP's RESTCONF APIs. Visit the Network Developer Portal for more information.

Path control

NSP supports the use of RESTCONF to create, delete, update, and read IETF-compliant LSPs according to draft-ietf-teas-yang-te, including regular RSVP LSPs and PCC-Initiated RSVP/SR LSPs for deployment through NFM-P or MDM. The LSPs may be configured with a number of constraints - including hops and bandwidth - and may also be protected via redundancy. IETF-compliant LSPs are configured using the NSP RESTCONF API. Visit the Network Developer Portal for more information.

Services

NSP supports the use of RESTCONF to create, delete, update, and read IETF-compliant Layer 2 and Layer 3 services (L3 VPN and E-Line). IETF service models are stored and updated to reflect network changes. IETF service CRUD requests are translated prior to deployment. Additional services and service attributes can be added later via customization. IETF artifacts must be obtained from the Nokia Support Portal. IETF-compliant services are configured using the NSP's RESTCONF APIs and IETF models. Visit the Network Developer Portal for more information.