[BGPCEP-255] Support for non-MP advertisements Created: 01/Jul/15 Updated: 03/Mar/19 Resolved: 05/Dec/15 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Bugzilla Migration |
| Type: | Bug | ||
| Reporter: | Dana Kutenicsova | Assignee: | Milos Fabian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3919 |
| Description |
|
If peering with a client that does not support MP, the advertisement is still done using MP_REACH (even for ipv4 routes) meaning the client will ignore them. Fix will probably need a little redesign, as the information about supported capabilities is not available at the time of creating Update messages. |
| Comments |
| Comment by Claudio David Gasparini [ 03/Jul/15 ] |
| Comment by Milos Fabian [ 26/Nov/15 ] |
|
-the bug fix needs to be revised |
| Comment by Milos Fabian [ 27/Nov/15 ] |
| Comment by Milos Fabian [ 01/Dec/15 ] |
|
Lithium cherry-picks: Wait until stable/lithium get "unlocked" |