Re: [Idr] WG LC for draft-ietf-idr-bgp-car-02 (7/10/2023 to 7/23/2023)

Robert:

At WG LC, we try to find sections of a draft that may be unclear to the expert reader.  So, the important question is what is unclear to an expert readers outside the authors.

A good focus is to determine what is unclear.  I have read and suggested changes.... but we need fresh eyes from people who examine -01.txt.

With you experience in working through this process, try to work through issues.

Sue

Sent via the Samsung Galaxy S23 Ultra 5G, an AT&T 5G smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>

Sent via the Samsung Galaxy S23 Ultra 5G, an AT&T 5G smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>

Sent via the Samsung Galaxy S23 Ultra 5G, an AT&T 5G smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Robert Raszuk <robert@raszuk.net>
Sent: Wednesday, July 19, 2023 4:01:34 PM
To: Kaliraj Vairavakkalai <kaliraj=40juniper.net@dmarc.ietf.org>
Cc: Dhananjaya Rao (dhrao) <dhrao=40cisco.com@dmarc.ietf.org>; Susan Hares <shares@ndzh.com>; Moshiko Nayman <mnayman@juniper.net>; idr@ietf.org <idr@ietf.org>; Ketan Talaulikar <ketant.ietf@gmail.com>
Subject: Re: [Idr] WG LC for draft-ietf-idr-bgp-car-02 (7/10/2023 to 7/23/2023)

Kaliraj & Sue, As I mentioned in my note my understanding is that CAR routes augment transport so are exclusive to next hop's color marking. You still need SAFI 1/1 and 1/128 or 2/1 and CAR SAFI would
External (robert@raszuk.net<mailto:robert@raszuk.net>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzE5OTRhYzE4MGQwNDA0MDFiMDJmZDJkYWMwNzA4OTAzLzE2ODk3OTY5NTAuNTI=#key=e5c3bb98edfaada57acbf979fd70130a>  FAQ<https://www.godaddy.com/help/report-email-with-advanced-email-security-40813>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Kaliraj & Sue,

As I mentioned in my note my understanding is that CAR routes augment transport so are exclusive to next hop's color marking.

You still need SAFI 1/1 and 1/128 or 2/1 and CAR SAFI would be just carrying colored next hops for those service SAFIs.

And CAR will not in any form or shape replace those. Interaction between services SAFIs and CAR SAFI is via next hop resolution.

That is why I asked in the former note where your assumption came from. Your quotes to some lines of the CAR draft are simply out of context as you need to put them into overall CAR intention and keep in mind that CAR is only transport augmentation.

Kind regards,
Robert

On Wed, Jul 19, 2023 at 12:32 PM Kaliraj Vairavakkalai <kaliraj=40juniper.net@dmarc.ietf.org<mailto:40juniper.net@dmarc.ietf.org>> wrote:

>“The CAR SAFI is intended to update the BGP transport functions in BGP-LU (applicable to just MPLS) for new transports (such as SRv6).  It maintains the exact flat routing semantics of BGP-LU/IP without any need for VPN-like import.”

     >>DR# Sure that would be fine.

Here you seem to agree with Sue that families using CAR SAFI are at transport-layer.

But then, you go on to say:

>> DR#.. BGP CAR can be enabled between PE-CE. To advertise the customer’s CAR routes between PEs, VPN CAR is required.

Do you see this usage of CAR and VPN-CAR families as a transport-layer of service-layer usage?

Also, section 8 or 10 lack procedures on how this usage interacts with existing AFI/SAFIs

(e.g., 1/1 or 1/128) that are deployed today on PE-CE or PE-PE sessions.

Thanks

Kaliraj

Juniper Business Use Only

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr<https://shared.outlook.inky.com/link?domain=www.ietf.org&t=h.eJxFjcsOgyAQRX-lYd0wA_XBuPJXULASFRrAmNj03yvdNHd3H-e-2R5X1t3YnPMrdQDHcXBn88RDfMKm3bppD6tL2fkpgDOR3W9sKQtv89URWKuGhIQ062hT78058zFsIIgqPQqFBqtLYkA5GWn0iC0qwgeIRlFLDdXIa1motlBjGGzMfdTp3Bd-fZTE_JK_9fkCwPo32w.MEUCIQCjiNY8xZFfoJqM3l_a-pevnDCNHOT58G0MDVDp11I3LAIgIl3DBL6-ASv1UexWwmFypDygyVrbDjA1JIY0PD5Uz1c>