Bridge port update - 11

Added changes in ethernet module for handling the #bridge #port level #admin #flag for #TC #mapping. The port level TC mapping flag will #enable or #disable the #CoS to #traffic-class #mapping #configuration on the port.  The TC mapping will enable to map CoS on frames to a traffic-class. The mapped traffic class will be used for effective #QoS treatment on the frame. By default, all CoS values are mapped to traffic-class '0' and #best-effort ( #BE ) treatment is provided.

#Ethernet update 103 ...
[commit 03441757f7fe2a998152a2bc396906fcb9493f66]

Bridge port update - 10

Added changes in ethernet module for handling the #bridge #port level #admin #flag for #CoS #mapping. The port level CoS mapping flag will #enable or #disable the #CoS #mapping #configuration on the port.  The CoS remapping will enable to map CoS on frames to a different CoS value. The remapped CoS will be used for effective #QoS treatment on the frame. By default, for a frame the ingress CoS is considered as the #effective #CoS for QoS handling.

#Ethernet update 102 ...
[commit 7dcac8d2f88c5ca6ed45be6d2b0ff8d0e7a1cbd6]

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]

Bridge CoS update - 3

Added optimizations for #port #level #access #priority #remapping configuration on customer bridges. This will reduce the memory requirement for supporting access priority remapping configuration. The access priority remapping will enable to map #customer #CoS on frames to a different CoS value at the customer domain border, while sending data to the provider network. This is useful when the #SLA with the #provider #network requires specific kind of CoS mapping for required QoS treatment. The remapped CoS will be used int the provider network for effective #QoS treatment on the frame. By default, for a frame the egress CoS is send unaltered.

#Ethernet update 67 ...
[commit 927d1b2c75c52888f6a251138ed93a9e58c914a6]

Bridge CoS update - 2

Added optimizations for  #port #level #effective ( #remapped ) #CoS to #traffic-class #mapping in ethernet module. The optimization reduces memory used for maintaining this configuration in ethernet module. The traffic-class decides the #QoS treatment for ethernet frames. The remapped CoS which was deduced from the ingress CoS is used for deciding the traffic-class to be applied. By default - without any configuration present, all CoS values are mapped to same default traffic-class 0.

#Ethernet update 63 ...
[commit e21c37a8db62c1e13e5ae10c0074fe68585bc654]

Bridge CoS update

Added corrections for #general #bridge #port #CoS #configuration in ethernet module. The general configuration controls the default CoS applied on frames, number of traffic classes supported, PCP row to be used for remarking of frames, etc ...

Added optimizations for #port #level #CoS #remapping configuration. This will reduce the memory requirement for supporting CoS remapping configuration. The CoS remapping will enable to map CoS on frames to a different CoS value. The remapped CoS will be used for effective #QoS treatment on the frame. By default, for a frame the ingress CoS is considered as the #effective #CoS for QoS handling.

#Ethernet update 61 ...
[commit 45523fe6405229f8f91f0bd77771646acbb9ce85]