Bridge port update - 9

Added back-end #update #routine for #extended #bridge #port parameter #admin #flags in ethernet module. This will control port level attributes like #CoS, #TC and #PCP #mapping, #service #UNI, #ENNI, #VUNI and #spanning-tree enable. These attributes are checked for their correctness and valid ones are updated in the back-end structures.

#Ethernet update 100 ...
[commit 91a48c92bcbc6075b151553d94996d83767c66bb]

Bridge port update - 8

Added #bridge #port #level #admin #flags #handler in ethernet module. These flags control parameters like #CoS, #TC and #PCP #mapping, #service #UNI, #ENNI, #VUNI and #spanning-tree operations on the respective port.

#Ethernet update 98 ...
[commit ee6173e7810d74df24ad7c9916c7f9e81bf330f2]

Bridge CoS update - 6

Added changes in ethernet module for traversing #port #level #service #access #priority #remapping configuration entries on provider bridges. The new changes enables to #traverse through the optimized configuration entries. The #agent #framework uses these for #GETNEXT functionality among the configuration entries.

#Ethernet update 74 ...
[commit da62efad1123bdbf472ceff31c9529ff49d28250]

Bridge CoS update - 4

Added optimizations for #port #level #service #access #priority #remapping configuration on provider bridges. This will reduce the memory requirement for supporting service access priority remapping configuration. The service access priority remapping will enable to map #customer #CoS on frames to a different CoS value at the provider network border - either on a customer edge port ( #CEP ) or a customer network port ( #CNP ) -, while receiving data from the customer network. This is useful to request priority handling of customer frames in the provider network. The remapped CoS will be used int the provider network for effective #QoS treatment on the frame. By default, for a frame the ingress CoS is used unaltered.

#Ethernet update 68 ...
[commit 416f683112105b43bdca799b83e8ed23f748a54e]