[RFE] bgp-route-aggregation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Na Zhu |
Bug Description
[Existing problem]
Current BGP dynamic routing proposal [1]_ doesn't have support for route aggregation. Route aggregation could be extremely useful in reducing the size of the routing table and improves CPU utilization [2]_.
[Proposal]
- Add route-aggregation support to BGP dynamic routing.
[Benefits]
- Route aggregation is good as it reduces the size, and slows the growth, of the Internet routing table.
- Amount of resources (e.g., CPU and memory) required to process routing information is reduced and route calculation is sped up.
- Route flaps becomes limited in number
[What is the enhancement?]
- - Additional API, CLI and DB model will be added.
[Related information]
[1] Dynamic Advertising Routes for Public Ranges
https:/
[2] A Framework for Inter-Domain Route Aggregation
https:/
summary: |
- bgp-route-aggregation + [RFE] bgp-route-aggregation |
Changed in neutron: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in neutron: | |
assignee: | nobody → vikram.choudhary (vikschw) |
tags: |
added: l3-bgp removed: bgp |
tags: | removed: l3-ipam-dhcp |
Changed in neutron: | |
assignee: | nobody → Na Zhu (nazhu) |
Changed in neutron: | |
status: | Triaged → Confirmed |
tags: |
added: rfe-postponed removed: rfe |
The feature which this RFE depends on is not yet implemented.
It is valid as a feature request, but the requested feature can be implemented during the current proposed implementation.