NSP technology standards
Industry standards and open-standard interfaces
The NSP incorporates industry standards and open-standard interfaces that allow interoperation with other network monitoring and management systems. The following table lists and describes the technology standards and interfaces that are represented in the NSP system design.
Table A-1: Industry standards consulted in NSP design
|
Standard or interface |
Description |
|---|---|
|
draft-alvarez-pce-path-profiles-04 |
PCE path profiles |
|
draft-dbwb-opsawg-sap-02 |
A network YANG model for Service Access Points (SAPs) |
|
draft-ietf-i2rs-yang-network-topo-20 |
A data model for network topologies |
|
draft-ietf-idr-bgp-ls-segment-routing-ext-16 |
BGP link-state extensions for segment routing |
|
draft-ietf-idr-bgp-ls-segment-routing-msd-09 |
Signaling MSD using BGP-LS |
|
draft-ietf-isis-mi-02 |
IS-IS Multi-Instance |
|
draft-ietf-isis-segment-routing-extensions-04 |
IS-IS extensions for segment routing |
|
draft-ietf-opsawg-l2nm |
A YANG network data model for layer 2 VPN network |
|
draft-ietf-ospf-segment-routing-extensions-04 |
OSPF extensions for segment routing |
|
draft-ietf-pce-segment-routing-08 |
PCEP extensions for segment routing |
|
draft-ietf-pce-stateful-pce-14 |
PCEP extensions for stateful PCE |
|
draft-ietf-teas-yang-te-29 |
A YANG data model for traffic engineering tunnels and interfaces |
|
Keycloak |
Version 21.1.1 |
|
ONF TR-547-TAPI v2.1.3 |
Reference Implementation Agreement |
|
OpenFlow |
OpenFlow Switch Specification version 1.3.1 |
|
REST |
Representational State Transfer |
|
RFC 3986 |
URI Generic Syntax |
|
RFC 4655 |
Path Computation Element (PCE) based architecture |
|
RFC 5101 |
Specification of the IP Flow Information Export (IPFIX) Protocol for the exchange of IP traffic flow information |
|
RFC 5102 |
Information model for IP flow information export |
|
RFC 5440 |
Path Computation Element Communication Protocol (PCEP) |
|
RFC 5575 |
Dissemination of flow specification rules |
|
RFC 6020 |
YANG data modelling language for NETCONF |
|
RFC 6021 |
Common YANG data types |
|
RFC 6087 |
Guidelines for YANG Documents |
|
RFC 6241 |
Network configuration protocol (NETCONF) |
|
RFC 6242 |
NETCONF over SSH |
|
RFC 6991 |
Common YANG data types |
|
RFC 7223 |
A YANG data model for interface management |
|
RFC 7224 |
IANA interface type YANG model |
|
RFC 7420 |
PCEP Management Information Base (MIB) model |
|
RFC 7231 |
HTTP/1.1 Semantics and Content |
|
RFC 7752 |
North-bound distribution of link-state and Traffic Engineering (TE) information using BGP |
|
RFC 7950 |
YANG 1.1 |
|
RFC 7951 |
JSON encoding of data modelled with YANG |
|
RFC 7952 |
Defining and Using Meta Data with YANG |
|
RFC 8040 |
RESTCONF |
|
RFC 8072 |
YANG patch media type |
|
RFC 8281 |
PCEP extensions for PCE-initiated LSP setup in a stateful PCE model |
|
RFC 8321 |
PCEP extensions for stateful PCE |
|
RFC 8345 |
A YANG data model for network topologies |
|
REF 8346 |
A YANG data model for layer 3 topologies |
|
RFC 8476 |
Signaling MSD using OSPF (node MSD) |
|
RFC 8491 |
Signaling MSD using IS-IS (node MSD) |
|
RFC 8525 |
YANG Library |
|
RFC 8528 |
YANG schema mount |
|
RFC 8665 |
OSPF extensions for Segment Routing |
|
RFC 8667 |
IS-IS extensions for Segment Routing |
|
RFC 8776 |
Common YANG data types for traffic engineering |
|
RFC 8944 |
A YANG data model for layer 2 network topologies |
|
RFC 9181 |
A common YANG data model for layer 2 and layer 3 VPNs |
|
RFC 9182 |
A YANG network data model for layer 3 VPNs |