[BGPCEP-627] draft-ietf-spring-segment-routing-central-epe-10 - Egress peer engineering PCEP Created: 06/Feb/17 Updated: 16/Nov/21 |
|
| Status: | Confirmed |
| Project: | bgpcep |
| Component/s: | PCEP |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Bijan Rofoee | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
Segment routing with egress peer engineering: Opendaylight supports creating segments based on two SIDs of node id and link adjacency id. However peerset id is not supported which is essential for enabling egress engineering between ASs. In the BGP yang model there is a EPE support which sends the information the controller through LS, following a issue raised before. However could not find similar one in PCEP which I assume is for programming the segment. So either PCEP or flowspec need to be used for this purpose. please see this: thanks |