| link-id |
string |
An identifier for a link in a topology.
The identifier may be opaque.
The identifier SHOULD be chosen such that the same link in a
real network topology will always be identified through the
same identifier, even if the model is instantiated in separate
datastores. An implementation MAY choose to capture semantics
in the identifier, for example to indicate the type of link
and/or the type of topology that the link is a part of. |
| link-id |
string |
An identifier for a link in a topology.
The identifier may be opaque.
The identifier SHOULD be chosen such that the same link in a
real network topology will always be identified through the
same identifier, even if the model is instantiated in separate
datastores. An implementation MAY choose to capture semantics
in the identifier, for example to indicate the type of link
and/or the type of topology that the link is a part of. |
| link-ref |
leafref |
A type for an absolute reference a link instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.) |
| link-ref |
leafref |
A type for an absolute reference a link instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.) |
| node-id |
string |
An identifier for a node in a topology.
The identifier may be opaque.
The identifier SHOULD be chosen such that the same node in a
real network topology will always be identified through the
same identifier, even if the model is instantiated in separate
datastores. An implementation MAY choose to capture semantics
in the identifier, for example to indicate the type of node
and/or the type of topology that the node is a part of. |
| node-id |
string |
An identifier for a node in a topology.
The identifier may be opaque.
The identifier SHOULD be chosen such that the same node in a
real network topology will always be identified through the
same identifier, even if the model is instantiated in separate
datastores. An implementation MAY choose to capture semantics
in the identifier, for example to indicate the type of node
and/or the type of topology that the node is a part of. |
| node-ref |
leafref |
A type for an absolute reference to a node instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.) |
| node-ref |
leafref |
A type for an absolute reference to a node instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.) |
| topology-id |
string |
An identifier for a topology. |
| topology-id |
string |
An identifier for a topology. |
| topology-ref |
leafref |
A type for an absolute reference a topology instance. |
| topology-ref |
leafref |
A type for an absolute reference a topology instance. |
| tp-id |
string |
An identifier for termination points on a node.
The identifier may be opaque.
The identifier SHOULD be chosen such that the same TP in a
real network topology will always be identified through the
same identifier, even if the model is instantiated in separate
datastores. An implementation MAY choose to capture semantics
in the identifier, for example to indicate the type of TP
and/or the type of node and topology that the TP is a part of. |
| tp-id |
string |
An identifier for termination points on a node.
The identifier may be opaque.
The identifier SHOULD be chosen such that the same TP in a
real network topology will always be identified through the
same identifier, even if the model is instantiated in separate
datastores. An implementation MAY choose to capture semantics
in the identifier, for example to indicate the type of TP
and/or the type of node and topology that the TP is a part of. |
| tp-ref |
leafref |
A type for an absolute reference to a termination point.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.) |
| tp-ref |
leafref |
A type for an absolute reference to a termination point.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.) |