TED update - 21: optimizing standard TE-Link component link entries

Optimized the variables used in TE-Link #component-link entries and #component-link #bandwidth entries in TED module. The #variable #size used for storing the #bandwidth information has been reduced - in the #component-link entry the #max-reservable-bandwidth keeps maximum available bandwidth on the component-link, also the component-link bandwidth entries keep 8 separate entries on each component-link to keep the current #unreserved-bandwidth available for each of the 8 #priority values on the component-link. The #max-reservable-bandwidth is a configurable parameter by the operator, but the #unreserved-bandwidth is dynamic value currently set on the component-link.

#TED update 21 ...
[commit 39d7d5a691043d8a624faa35a69770e0dd3fc37c] (https://github.com/nes-repo/NES-Open-Switch/commit/39d7d5a691043d8a624faa35a69770e0dd3fc37c)

TED update - 19: adding new TE-Link reservation priority based index

Added #new #priority #based #indexing on the #TE-Link #reservations in the TED module. This will enable to #query TE-Link reservations #based on their #priority. This will be useful when #preemptable #bandwidth has to be calculated from the existing reservations on a TE-Link. When preemption is enabled and #unreserved #bandwidth is not being available, some of the existing #lower #priority reservations will be released and used to fulfill the current requirement.

#TED update 19 ...
[commit f24555b15e06dc91475482fcb6e58debc0680760] (https://github.com/nes-repo/NES-Open-Switch/commit/f24555b15e06dc91475482fcb6e58debc0680760)

TED update - 13: optimizing TE-Link link-reservation entries

#Optimized #TE-Link #link-reservation entries in TED module. The #reservation #priority has been added to the link-reservation entries, so that #preemption feature can be optimally implemented for #path #computation procedures. The #link-reservation #index has been made #compact by removing the 4 integer indexes and #replaced them with a #generic 16 byte #wide #index. This helps to keep traffic-engineering module to be less specific to the MPLS framework, as the generic index can be used from other modules as well. Also this makes link-reservation database more easily usable. The #preemption is used for #high #priority #path #setup #requests in the #traffic-engineering module. Preemption is used when #resource #crunch is experienced on a TE-Link for these requests. The #previously placed #low #priority resource #reservations will reused for performing current high priority request. The existing low priority reservations of will be either #teared #down or #moved to a different TE-Link. The bandwidth that got available from handling the low priority reservations will be used for current high priority path setup request.

#TED update 13 ...
[commit dcc8fa6c7a1eeddf3954da8671719bdb4ed62d25] (https://github.com/nes-repo/NES-Open-Switch/commit/dcc8fa6c7a1eeddf3954da8671719bdb4ed62d25)

TED update - 12: optimizing TE-Link switching-capability (ISCD) entries and adjustment-capability (IACD) entries

#Optimized #TE-Link #switching-capability ( #ISCD ) entries and #adjustment-capability ( #IACD ) entries in TED module. The TE-Link switching-capability and adjustment-capability #configuration entries has been made #compact #by making the #bandwidth to #64-bit #fixed size #format. The generic variable size format for these parameters takes quite some memory space. The #switching-capability and #adjustment-capability #configuration for TE-Link #component-links also has been #compacted in the same way. The #switching-capability configuration has #max-lsp-bandwidth for each of the 8 #priority values and fixing them to 64-bit will get ride of the 8 size fields of these parameters reducing the memory size. The #max-lsp-bandwidth is kept in #64-bit #floating-point #format which is always exist as a fixed format. The #adjustment-capability configuration as well has 8 #max-lsp-bandwidth fields for each #priority values, this too has been optimized in the same way.

#TED update 12 ...
[commit 31ff9d5adba547ada03c7c10996ae817f3ff97c1] (https://github.com/nes-repo/NES-Open-Switch/commit/31ff9d5adba547ada03c7c10996ae817f3ff97c1)

TED update - 11: renaming standard TE-Link switching-capability (ISCD) entries

#Renamed #standard #TE-Link #switching-capability ( #ISCD ) entries in TED module. The TE-Link switching-capability configuration entries has been made straight forward by correcting it's name. The TE-Link switching-capability entries contain #attributes like #min-lsp-bandwidth, #max-lsp-bandwidth for each #priority, #interface #MTU, SONET / SDH type, etc ... The switching-capability entries are identified by their #switching-type and #LSP-encoding types. The same information has been updated for the counter parts from the #component-links as well.

#TED update 11 ...
[commit 51fd4675bdbdfe0983f6bb82406b5a7d00e6c150] (https://github.com/nes-repo/NES-Open-Switch/commit/51fd4675bdbdfe0983f6bb82406b5a7d00e6c150)

TED update - 5: adding TE-Link adjustment capability parameters

Added new #adjustment-capability ( #IACD ) information both #on #TE-Link and the individual #component-link level s in TED module. The adjustment-capability enables to capture the #capability and #capacity of each node to #perform #media #conversion #between it's #TE-Links ( #Ethernet-to-SDH, #Ethernet-to-OTN, #OTN-to-WDM, etc ... ). The adjustment-capability indicated as the #higher and #lower #layer #switching-type and #LSP-encoding #of a possible #media #conversion and #bandwidth capacity is indicated per #priority. When a node has different types of - media - TE-Links and it is possible to forward data-stream between these links the internal capacity of the node to perform this conversion is indicated as adjustment-capability.

#TED update 5 ...
[commit 7e2c2086756a59df15b2f5303b205e3da3cafce6] (https://github.com/nes-repo/NES-Open-Switch/commit/7e2c2086756a59df15b2f5303b205e3da3cafce6)

Bridge port update - 12: PCP encoding/decoding admin flag

Added changes in ethernet module for handling the #bridge #port level #admin #flag for #PCP #mapping. The port level PCP mapping flag will #enable or #disable the PCP encoding/decoding #configuration on the port.  This flag will enable #port level #priority #code #point ( #PCP ) #encoding configuration entries and #decoding configuration entries on provider bridges. By default, #CoS and #DEI values as per the translation tables defined in #802-1Q-2011 will be used which can be further fine tuned by the operator.

#Ethernet update 105 ...
[commit 73db4c6913e89424c654ca7fa99fb36137ab9fb2]

Bridge CoS update - 15

Added changes in ethernet module for traversing #port #level #priority #code #point ( #PCP ) #encoding configuration 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 96 ...
[commit 31263afc3940867eeefa3770f9b4dfe2ae855fd0]

Bridge CoS update - 14

Added optimizations for #port #level #priority #code #point ( #PCP ) #encoding configuration on provider bridges. This will enable to access the optimized encoding configuration entries from the agent framework. These will be used for #GET, #GETNEXT and #SET operations from the agent.

#Ethernet update 95 ...
[commit c0ca95073029d941effab715ff3cf476976ef3b8]

Bridge CoS update - 13

Added changes in ethernet module for initializing #port #level #priority #code #point ( #PCP ) #encoding configuration entries and #decoding configuration entries on provider bridges. These changes will initialize the configuration entries with default #CoS and #DEI values as per the translation tables defined in #802-1Q-2011. By default the ingress frame CoS is used unaltered.

#Ethernet update 94 ...
[commit 252dcb6d8f6c9b3c2a3e3393cc78dfd898305b97]

Bridge CoS update - 12

Created default tables in ethernet module for #port #level #priority #code #point ( #PCP ) #encoding / #decoding configuration on #provider #bridges ( #PB ). These tables will help to fill PCP encoding / decoding configuration with their initial values. The default table will ensure that ingress CoS is used unaltered and egress CoS is also conveyed unaltered.

#Ethernet update 87 ...
[commit b6c38d7c64f29ecadec9743a092946f773566f9d]

Bridge CoS update - 11

Added changes in ethernet module for traversing #port #level #priority #code #point ( #PCP ) #decoding configuration 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 86 ...
[commit 4e61fd0cd564328a3fbdaa7dfd0fc02f9d5a11af]

Bridge CoS update - 10

Added changes in ethernet module for traversing #port #level #access #priority #remapping configuration. 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 82 ...
[commit ef219b5ee6c0ebdb066c920e1b11fc02a5197154]

Bridge CoS update - 7

Added optimizations for #port #level #priority #code #point ( #PCP ) #decoding configuration on provider bridges. This will reduce the memory requirement for supporting PCP decoding configuration. The configuration will decide the effective #CoS and #drop #eligibility ( #DEI ) of the incoming frame based on ingress CoS. Based on the priority code point row selected in the PCP table on the port, the CoS and DEI decoded on the frames will change. By default, for a frame the ingress CoS is used unaltered.

#Ethernet update 77 ...
[commit 1232c133519a37001035c506fb9f9984f9b86234]

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 - 5

Added optimizations for #port #level #priority #code #point ( #PCP ) #encoding configuration on provider bridges. This will reduce the memory requirement for supporting PCP encoding configuration. The configuration will decide the CoS encoded on the outgoing frames, based on the #customer #CoS and #drop #eligibility ( #DEI ) of the frame. Based on the priority code point row selected in the PCP table on the port, the CoS encoded on the frames will change. By default, for a frame the egress CoS is used unaltered.

#Ethernet update 70 ...
[commit fb4bcfd54d7dd6e5eb271db8419f0580f248a6a1]

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]