Re: [Idr] Part 2 of CAR/CT Adoption call (7/6 to 7/20) - Adoption of draft-dskc-bess-bgp-car-05.txt and draft-kaliraj-idr-bgp-classful-transport-planes-17.txt

["MEANS, ISRAEL L" <[e-mail]>]

Hi Sue,
I endorse the adoption of CT.
While both CAR and CT address color as a reflection of intent the operational approaches are distinct.   With CT existing network constructs such as RD, RT and RTC are leveraged reducing the operational learning curve for MPLS VPN network operators.  We also find that CT simplifies operations of network structures that include SR and non-SR implementations under a single administrative authority.  CT provides an operationally simple approach that facilitates the creation of seamless end-to-end intent-based paths over networks with diverse protocols (example: SR vs RVSP-TE).
CAR and CT are functionality similar therefore I support moving forward with a single draft.
Regards,
Israel


From: "[e-mail]" <[e-mail]> on behalf of Susan Hares <[e-mail]>
Date: Wednesday, July 6, 2022 at 11:17 AM
To: "[e-mail]" <[e-mail]>
Subject: [Idr] Part 2 of CAR/CT Adoption call (7/6 to 7/20) - Adoption of draft-dskc-bess-bgp-car-05.txt and draft-kaliraj-idr-bgp-classful-transport-planes-17.txt

This begins a 2-week WG Adoption call (7/6/2022 to 7/20/2022) for the following drafts:

  *   draft-dskc-bess-bgp-car-05.txt

(https://datatracker.ietf.org/doc/draft-dskc-bess-bgp-car/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-dskc-bess-bgp-car/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hG9R00Cy$>)

  *   draft-kaliraj-idr-bgp-classful-transport-planes-17.txt

(https://datatracker.ietf.org/doc/draft-kaliraj-idr-bgp-classful-transport-planes/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-kaliraj-idr-bgp-classful-transport-planes/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hFCXsCU4$>)
The associated drafts may be useful in your consideration.
CAR:

  *   draft-ietf-spring-segment-routing-policy-22

https://datatracker.ietf.org/doc/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hNRKF1IE$> draft-ietf-spring-segment-routing-policy/



  *   draft-ietf-idr-segment-routing-te-policy-18

https://datatracker.ietf.org/doc/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hNRKF1IE$> draft-ietf-idr-segment-routing-te-policy/



  *   draft-dskc-bess-bgp-car-problem-statement-05.txt

https://datatracker.ietf.org/doc/draft-dskc-bess-bgp-car-problem-statement/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-dskc-bess-bgp-car-problem-statement/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hGXPnQsq$>
CT

  *   draft-hegde-spring-mpls-seamless-sr-06.txt

https://datatracker.ietf.org/doc/draft-hegde-spring-mpls-seamless-sr/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-hegde-spring-mpls-seamless-sr/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hCo_5m8U$>



  *   draft-kaliraj-idr-multinexthop-attribute-02.txt

(https://datatracker.ietf.org/doc/draft-kaliraj-idr-multinexthop-attribute/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-kaliraj-idr-multinexthop-attribute/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hCvtdNX9$>)



  *   draft-kaliraj-bess-bgp-sig-private-mpls-labels-04

(https://datatracker.ietf.org/doc/draft-kaliraj-bess-bgp-sig-private-mpls-labels/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-kaliraj-bess-bgp-sig-private-mpls-labels/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hDK0qtXc$>)


You may discuss adoption of one or both the main drafts (CAR or Classful-Transport (CT)) in your response, and the associate drafts.
A few caveats on your discussion:

  1.  Please do not worry whether the drafts belong in BESS or IDR.

Both BESS and IDR work on creating relevant quality standards in BGP,

and the chairs will work this out.



  1.  The IDR has spent time over 2020-2022 discussing these drafts.

For background information, see the following links below.

You can refer to these previous presentations or email discussions in your responses.



  1.  Please constrain your discussion to whether these drafts should be adopted.

I’ve started another email thread on whether path establishment/distribution

for a color (aka QOS/SLA/Transport Class) should be done via a

specific BGP route (i.e., per-color NLRI) rather than as per-color attributes on a route.
https://mailarchive.ietf.org/arch/msg/idr/FhoK04HsSy9tR7ioV7AD0Vv6Ir4/<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/idr/FhoK04HsSy9tR7ioV7AD0Vv6Ir4/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hL6niiHw$>

Questions (to consider) for these drafts:
Jeff Haas (IDR Co-chair) posted a summary on March 21, 2022 that for
route resolution and route origination/propagation, BGP-CAR and BGP-CT are functionally identical,
but operationally different.
    ( https://mailarchive.ietf.org/arch/msg/idr/e69NRd9i2aG0WUxFkShEfQHZsHo/<https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/idr/e69NRd9i2aG0WUxFkShEfQHZsHo/__;!!BhdT!irHYzdbvJQnVPsgA1gXerUMv3VyCPRTUmjtsZlQSnQcnhYWYH2C8hYRWRlZil1MU5pn5hDWYPAPD$>

  1.  Do you agree or disagree that these two drafts are functionally identical?
  2.  If you agree, should we have just one draft or do the operational difference encourage us to have two drafts?
  3.  If you disagree, do the functional differences encourage us to have one or two drafts adopted?