Identifier at the original management interface to be mapped

[openBackhaul]

The name attribute at the LTP class shall also contain an instance documenting the identifier as it is used on the vendors own management interface for identifying the same logical interface. The field shall always be filled.

logical-termination-point :: name :: value-name: "ltpName"
logical-termination-point :: name :: value: "" (empty String as a default)

Example:
{
"uuid": "ETH-765.2.5",
"name": [
{
"value-name": "ltpName",
"value": "WAN:2/5"
},
{
"value-name": "externalLabel",
"value": "LAN5"
}
]
},

[demx8as6]

Please see similar information for "externalLabel":

TransmitterEquipment_1.0.0-tsp.200715.1225+spec.1.pdf

see chapter 9

9 Information ControlConstruct and LogicalTerminationPoint

(27) While creating an instance of ControlConstruct or LogicalTerminationPoint, an instance of the
NameAndValue datatype at the name attribute, which is inherited from the GlobalClass, shall be automatically
created and filled with valueName:“externalLabel” and value: “”(empty String).

(28) After rebooting, the interface (e.g. mediator) the last configured value shall be represented again.

[demx8as6]

Decision made at the 5G-xhaul call on Wednesday 26th of January 2022

The following new sentence should be added to chapter 9 of TransmitterEquipment document at the position of sentence (28). The existing (28) becomes (29) and so on.

(28') While creating an instance of the LogicalTerminationPoint, an additional instance of the NameAndValue datatype shall be created at the name attribute.
valueName attribute shall be filled with:“ltpName”.
value attribute shall automatically be filled with a string that contains the logical- or physical interface name as it is represented at the vendor's own management interface e.g. ltpName = “LAN 1/2/1”.
Both attributes (valueName and value) shall refuse configuration attempts, even if this is neither modelled in the YANG, nor expressed in the comments of the attributes.

[openBackhaul]

Please find the LtpAugment Issue#5 proposing a more explicit and cleaner modelling.

[openBackhaul]

This issue got obsolete due to later decision in ltpAugment issue#5.
It has been closed without any action.