Skip to content

Latest commit

 

History

History
14 lines (9 loc) · 954 Bytes

File metadata and controls

14 lines (9 loc) · 954 Bytes

Structure of OAM Paths

The requests for application management shall be as close as possible to those for device management.
Consequently, the OaM paths look and feel like a RESTCONF interface of a device as it is exposed at the controller NBI.

The structure of the classes and attributes is according to the ONF Core modelling.
The syntax is determined by the YANG and RESTCONF definitions.

The uppercase letters in the original class and attribute names of the ONF modelling are represented as hyphens and lowercase letters.
Module names must be inserted at the beginning of the path and wherever there is a transition between models in the path.
Variable components of the paths, such as UUIDs or LocalIDs, must be enclosed in curly brackets and defined in the parameter: statement.

OaM path segements