search

openBackhaul / ethernetContainer

Technology specific interface definition for an Ethernet Container
Apache License 2.0
1 stars 0 forks source link

ingress-policing-profile needs to be removed from both UML and YANG #39

Closed PrathibaJee closed 2 years ago

PrathibaJee commented 4 years ago

The ingress-policing-profile attribute in ethernet-container-configuration is not currently supported/implemented in vendor devices. Proposal :

  1. Need to remove the ingress-policing-profile from uml file.
  2. Need to generate new yang file based on the latest uml.

Note : Since its a leaf ref , in the uml class diagram we cannot able to view this attribute. But in the .uml file , this attribute will be mentioned starting with a underscore.

openBackhaul commented 3 years ago

Discussion on the DMIP call on 27th of May 2021: The referencing attribute would be required, if we would define a technology specific augmentation to the Profile class for Policing. It will be evaluated, whether such definition shall be elaborated.

openBackhaul commented 2 years ago

Checking internally resulted in: Currently not used at microwave, but scenarios are already under discussion.

Idea: Would it be possible to create an "empty" PolicingProfile, so the reference in the EthernetContainer can remain, but we get not delayed by defining the PolicingProfile in detail?

openBackhaul commented 2 years ago

Decision on the 5G-xhaul call on 23rd of March 2022:

The ethernet-container-configuration::ingress-policing-profile attribute shall not be deleted from the modelling. For avoiding the must statement at the leaf-ref to fail, at least a dummy module of the PolicingProfile shall be created.

openBackhaul commented 2 years ago

PolicingProfile modeling has been provide.

openBackhaul commented 2 years ago

Fixed with EthernetContainer_2.0.0-tsp.220405.1755.