Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F3-WG-Issue-7: Compatibility of BGP-CT and BGP-CAR to SR-PCE (Shraddha Hegde) #12

Closed
sa1231-coder opened this issue Feb 2, 2023 · 5 comments

Comments

@sa1231-coder
Copy link
Collaborator

• CT: Consider how CT implements or interoperates with all the constructs in RFC 9256. Provide a short section in your document regarding support.
• CT: Describe the limits of any community, extended community, wide-community regarding color when interacting with CT’s mapping community.
• CAR: Consider how CAR implements or interoperates with all the constructs in RFC9256. CAR: Provide a short section in your document regarding support.
• CAR: Describe the limits of any community, extended community or wide-community regarding color. Describe how any of these limits interact with LCM.

@sa1231-coder
Copy link
Collaborator Author

CAR is inherently compatible with SR-PCE. It uses the identical ‘Color’ construct for both service steering (Color-ExtComm), and for routing (CAR routes & LCM). Section 1.2 illustrates the seamless compatibility. CAR does not require separate mapping communities or number spaces that need to be mapped to the color.

CAR also does not preclude any typical BGP attributes based route-policies from being used to augment routing. There are no specific constraints w.r.t CAR.

@suehares
Copy link
Collaborator

suehares commented Mar 3, 2023

This issue had two points:
1. Consider how CAR implements or interoperates with all the constructs in RFC9256.
Please provide a short section on support. Your section 1.2 provides a good illustration, but it does not cover if "all the constructs of RFC9256" are supported.

If you believe you support "all the constructs in RFC9256", please ask Bruno or Joel for a review of your document (-01.txt) to see it supports "all constructs". If you wish to constrain the CAR support to a subset of the RFC9256 constructs, please add a paragraph.

2. CAR: Describe the limits of any community, extended community or wide-community regarding color. Describe how any of these limits interact with LCM.

I do not see where you provide me with an answer the second sub-issue above.

@suehares suehares reopened this Mar 3, 2023
@suehares
Copy link
Collaborator

suehares commented Jun 1, 2023

Section 3 contains the definition support for RFC9256.

@suehares
Copy link
Collaborator

suehares commented Jun 1, 2023

You do not support RFC 9012 Color SubTLV.
You do support Color in NLRI and Extended Communities (RFC9012).

Wide color community - Sue will research where it is mentioned. We will consider this closed if there are no wide community with color From Robert Raszuk.

@suehares
Copy link
Collaborator

No wide community color pointed to by Robert or other respondents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants