[BGPCEP-913] Path Computation Segment Routing NAI is not conform Created: 09/Jul/20 Updated: 17/Jul/20 Resolved: 17/Jul/20 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | None |
| Affects Version/s: | Magnesium |
| Fix Version/s: | Aluminium, Magnesium SR2 |
| Type: | Bug | Priority: | High |
| Reporter: | Olivier Dugeon | Assignee: | Olivier Dugeon |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Path Computation used in conjunction to PcInit message produce a NAI which is not supported by Cisco & Juniper routers. Indeed, the produce NAI is based on Node-SID + Router-ID while router expected a NAI based on Adjacecy-SID and interface address. This type of Node-SID NAI is only pertinent for loose path computation while Adjacency NAI is suitable for strict path computation. However, routers are expected a strict path. |