search

ietf-wg-idr / draft-ietf-idr-bgp-ct

1 stars 2 forks source link

Section 7.3 #48

Closed suehares closed 5 months ago

suehares commented 6 months ago

16) Section 7.3.

The resolution scheme for a Transport Class RT with Transport Class ID "C1" contains TRDB for Transport Class with same ID. In cases where Transport Class "C1" tunnels are not available in a domain, the administrator MAY customize the resolution scheme to map to a different set of transport classes available in that domain. #Keyur: How does this work with section 4.3 where RT Constrain is enabled?
suehares commented 6 months ago

Kaliraj: RTC will work for both the TCs C1 and available-TC-ID. Because both those TCs are configured, RTC membership request will be advertised for both TC-RTs. Rules specified in RTC RFC apply for these cases also..

suehares commented 6 months ago

Sue: Kaliraj - please let me know what text in the draft you think specifies "RTC will work for both the TCs C1 and available-TC-ID. Because both those TCs are configured, RTC membership request will be advertised for both TC-RTs. Rules specified in RTC RFC apply for these cases also.."

suehares commented 6 months ago

Keyur comment #17 Section 7.3

RD is stripped by the ingress node from the BGP CT NLRI prefix RD:EP when a BGP CT route is added to a TRDB. So that service routes can resolve over this BGP CT tunnel route for EP. This step applies only if the Transport Class RT is received on a BGP route in address family with SAFI 76. #Keyur: Isn’t this an implementation specific text? **Kaliraj reponse:** No. TRDB only contains the IP prefix without RD. And these IP routes are used to resolve BGP NHs. So RD should not be there.
suehares commented 6 months ago

Kaliraj - Keyur is indicatig that the TRDB is not being standardized, but the BGP Update packets.
You are using the TRDB to explain the processing of the packet. What you are saying is that Route selection is based on IP prefix only.

This is my understanding. Is this correct?

kalirajv commented 6 months ago

Correct Sue. Besides update packets send, receive, It is also important to standardize how the route resolution works, to be able to guarantee end-to-end intent. This section mentions that toute's nexthop resolution happens based on IP-prefix only (RD stripped from BGP-CT routes).

kalirajv commented 5 months ago

16: Just like RTC routes are generated for each locally configured VRF, they are generated for each locally configured Transport-Class. Explained during discussion with Keyur, Sue on call.

17: Clarified text by replacing 'strip' with 'ignore'.