Re: [Idr] CAR vs CT observation/question ...

Susan Hares <shares@ndzh.com> Thu, 14 July 2022 20:23 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 330EEC16ECEB for <idr@ietfa.amsl.com>; Thu, 14 Jul 2022 13:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7I9VfGBjT-W for <idr@ietfa.amsl.com>; Thu, 14 Jul 2022 13:23:29 -0700 (PDT)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2070.outbound.protection.outlook.com [40.107.220.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B35F7C16ECDB for <idr@ietf.org>; Thu, 14 Jul 2022 13:23:29 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RSN10C5B/0vfQ4Ih6kSyeAss1gU/BG1GN+rNvl2iwitt3EIXKU9SY6MrQsaySJQ8nDjsefRrmwzmVBECdv7BKopzgxkeNiQ8gv3ejEZZYjaG9PLZWuOZAwnbj8Afu6RNnfkyqpaVkqGj3hGbgCMYAQxeU7y+mjPi1Xiltemge67eTloDIcdlHrv8IRRORCOTYgjT1ZZkI21WBDDhf3Bv1O8gPfj1vKLhISqjnqjYdKOPoAA1RKvPe/o+2NOHj1/kQBa8RQSv9wWIgoRCGGiZ4PiXEQdDItPOr7K2dExFYXRpGz3FKu+gkGDQK60zwNyR6OKgNs08C4jQBmNkVL7Z+g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=LrG3wNCpm2bVPhCm4nVfN7NLUn82ctGmdTLuDbfPlQQ=; b=SJWTit3x+0gTW3AEPvwuVMKrUxW1jWTnZCHZVpzbMDTgI0WhVGEWRGyj5hcvopyTAzWBq2eArQtAjNTGuFgoi5u7zhMKCsVAjlbjGt/cTzTvc/DP3RrB8yzBvULSYkHjHhA6KHt0SLM6X8sJ33fnUPyMB14/k7D2vndcF0SIj1rDXw5vl6NjMdOO1VFbCW2ebdfz+rcvGOvjmb76d3dfQo+oGLszbytt3gaCm67lh/bKcxXgV+JuyhheulaZ6/N+GXI6FI90zclbZJ9TLi1PWf/xQgVwiCyq6wH+ExLK362qVUo8W0jtXyYKavoC/ody6uea/ByxBGn2v+4k7eG3Fw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=fail (sender ip is 35.166.188.152) smtp.rcpttodomain=ietf.org smtp.mailfrom=ndzh.com; dmarc=none action=none header.from=ndzh.com; dkim=none (message not signed); arc=none
Received: from DS7PR03CA0286.namprd03.prod.outlook.com (2603:10b6:5:3ad::21) by SA1PR08MB7165.namprd08.prod.outlook.com (2603:10b6:806:184::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5438.14; Thu, 14 Jul 2022 20:23:24 +0000
Received: from DM6NAM12FT015.eop-nam12.prod.protection.outlook.com (2603:10b6:5:3ad:cafe::96) by DS7PR03CA0286.outlook.office365.com (2603:10b6:5:3ad::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5417.25 via Frontend Transport; Thu, 14 Jul 2022 20:23:23 +0000
X-MS-Exchange-Authentication-Results: spf=fail (sender IP is 35.166.188.152) smtp.mailfrom=ndzh.com; dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ndzh.com;
Received-SPF: Fail (protection.outlook.com: domain of ndzh.com does not designate 35.166.188.152 as permitted sender) receiver=protection.outlook.com; client-ip=35.166.188.152; helo=obx-outbound.inkyphishfence.com;
Received: from obx-outbound.inkyphishfence.com (35.166.188.152) by DM6NAM12FT015.mail.protection.outlook.com (10.13.179.131) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5458.5 via Frontend Transport; Thu, 14 Jul 2022 20:23:22 +0000
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12lp2173.outbound.protection.outlook.com [104.47.55.173]) by obx-inbound.inkyphishfence.com (Postfix) with ESMTPS id 05CCD17D46F; Thu, 14 Jul 2022 20:23:21 +0000 (UTC)
Received: from BYAPR08MB4872.namprd08.prod.outlook.com (2603:10b6:a03:70::17) by BY3PR08MB7172.namprd08.prod.outlook.com (2603:10b6:a03:355::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5438.12; Thu, 14 Jul 2022 20:23:19 +0000
Received: from BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::ddda:dd38:4ae:7188]) by BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::ddda:dd38:4ae:7188%5]) with mapi id 15.20.5417.026; Thu, 14 Jul 2022 20:23:19 +0000
From: Susan Hares <shares@ndzh.com>
To: Robert Raszuk <robert@raszuk.net>, Natrajan Venkataraman <natv@juniper.net>
CC: "idr@ietf. org" <idr@ietf.org>
Thread-Topic: [Idr] CAR vs CT observation/question ...
Thread-Index: AQHYl2BQ3fTSLVSrGEueXOc58Rgb+a1+SPgAgAACWoCAAAPYUA==
Date: Thu, 14 Jul 2022 20:23:19 +0000
Message-ID: <BYAPR08MB4872754113F66669FBE0A517B3889@BYAPR08MB4872.namprd08.prod.outlook.com>
References: <CAOj+MMFfwP2SW0d-RG_QiAjG8zL2mwVRcJUvUSip1JBYCtN-3g@mail.gmail.com> <BY3PR05MB805087D391A8ACE7126D3607D9889@BY3PR05MB8050.namprd05.prod.outlook.com> <CAOj+MMHEA4Gi12rPhtr1v5QuqJ+1fbBHsdx4WFLGOVYyj5-yCw@mail.gmail.com>
In-Reply-To: <CAOj+MMHEA4Gi12rPhtr1v5QuqJ+1fbBHsdx4WFLGOVYyj5-yCw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-MS-Office365-Filtering-Correlation-Id: 4f98b660-51ae-40ec-342b-08da65d6b310
x-ms-traffictypediagnostic: BY3PR08MB7172:EE_|DM6NAM12FT015:EE_|SA1PR08MB7165:EE_
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: QTIfnxi9LSdnOp6PZb3JrrW8vobTAgQBAXloGdQc98tUlmCO0JowZrJTE7uYlbgORR+zWcbxVm9mzD2exFGFVru4Ifnh9jY/QK/+NS993jFstDrN2YBkr98zeEYnV6p3Bl7Frqd74bwjH5aQR1KMKBhlLJNgjMey9Ed4PJLFAlDQ5rMXsrni0aaZ1x3S9UpCKYUEEEctqtfRi4KRjb3HdvQ/cYMuI7BAGRjNRLChu/eHYXydrZZlRwvuyoLbWXkzPqKHW5qkWzPB/mgUY5QkVe0gVNIsLaag8VNTXSDvjwj1HaNmhtqhkwuPzob+r1aUgUXLkUk97XFCiPUuelb13doWtVgv4e/Y269W8gQv+q79w3dVFlLzdcoT2aCVCjd+urwfrO9r1i5/9erfXpl7iZCvFfSo05r27tKOAvM3Y3qvKkg8h9UH/uoNiOiamdekPbYguXIihbN70Zw2Q81MyUDOE/T2fmWXqOPLMPqScP7PVQLmxn14rnacqebt2d39UWB9chpPHa9FEyOoeY7lfRs4P9bPNopiaK/iUFkXs+r3eM9U/WMYQ+klu/zZLX3Ds0nnU1od5W/N/zjX7eeiv11EcMhh3tB4hLFjWPJU783CGE3FSXrOX0GLMf8CLRwf93cDOF3uHVVjeXuXEphEFzbEjU8527nnzHBbq1LjTt+jgs+UxqTruHoL/Y6HstpUWSly9Qm/hx5dgAbmeUtPLwc5zXUMrcaqCVshAdYmgCEZjBADV50HvrufVCMNvjpeKmBLDQRriV+IMrO6pR2mLvMMcJJVeAHWSpLzftZYpH/YSvMzxOn7vACAvH8Ad3TXlt2W4Vf/dczePq7yL45q3BuL0JzdNaL0FKhuCjvF2CUwcRWGBwOVeVh1fgKWBbef
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR08MB4872.namprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230016)(366004)(346002)(396003)(136003)(39830400003)(376002)(110136005)(38100700002)(316002)(38070700005)(86362001)(166002)(83380400001)(33656002)(5660300002)(4326008)(2906002)(66556008)(66476007)(64756008)(66946007)(8676002)(8936002)(52536014)(122000001)(66446008)(76116006)(26005)(186003)(9686003)(7696005)(53546011)(6506007)(478600001)(55016003)(41300700001)(966005)(71200400001)(66574015); DIR:OUT; SFP:1101;
Content-Type: multipart/alternative; boundary="_000_BYAPR08MB4872754113F66669FBE0A517B3889BYAPR08MB4872namp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY3PR08MB7172
X-Inky-Outbound-Processed: True
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DM6NAM12FT015.eop-nam12.prod.protection.outlook.com
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id-Prvs: f8385a8c-4628-408f-8457-08da65d6b105
X-IPW-GroupMember: False
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: TaJPdFAT/idoE3Ikd30iUzD83GNi6McpoPPmQrKq6UqIB8p8LlPBxq8BfqplHet6F91tVFNxbYBo9h1qFQYhPyfpWn5NnzHVNX0hVUrg1+FqF6i/M2cd+mqPOkVfOm1vO59V2xghfKJsmXvLYcminWd+upSbiPuBDEU0hogfEkqJWJjiV234GxZsKfTpj5bmpjpVlQdO3TtyUsSq0g9i4kBTJpzJ0+gumM9XtfFFK/WVTjUeJpPbCfkrZzcdLxWOQS5o03Ngv/i4o9XmwGeHyDZAHjUe2LB3pANwTwJPA7211edaV/TLfvOtx4foJ+KRt71IgUenYAxzqGI802lkbwPMXF+gzH5eKzoIgZZuqoHXAd4GEN43+n3alIRkw7Ke4Oagz9uggvRx4CgLUZG7aSgLfIIDd8SX9JCKApk6g9J5km8YzRCk09NESHzOx/5e3aRV0UjEWyrDS33eQDw066RFj0c4JKHcFFR+KCBsvOm5vvLpfU+BPQYb3AoTg7n7ILhPBzkDxvMGmS1tyfAh18KL6gKT/FnQ7eMqQ683wke2jYw0IquaAvkbf2Po3MOkRd4B0xuXjN7LA6krtinj4GXg0vM9olvnXrr3tSa7gcCSHOgBpjpSg3VkSf7uyYVYzqsA09Qz/vPnqJgcI5iSuWaZIJ4rzuO+7lSUGic2fNL8VWZD8ynUkpCNH//2N8FtfMqZnnxuG5nmutBLi/dl666UVoN3+GLenJn7agly1eK7JpI3kwL3savYGOKADcpg/EhbFb5z9/64/INn9738IEk1uUwi2LhJrQ7DOR5uFIU5mhNkVDLpXa2LTQw8Xhps9LJ97REY161mCWVWqs39+W5+/rphU/yD8GoydeKsOvM=
X-Forefront-Antispam-Report: CIP:35.166.188.152; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:obx-outbound.inkyphishfence.com; PTR:obx-outbound.inkyphishfence.com; CAT:NONE; SFS:(13230016)(346002)(39830400003)(396003)(136003)(376002)(46966006)(36840700001)(52536014)(7596003)(5660300002)(2906002)(47076005)(186003)(86362001)(66574015)(83380400001)(336012)(7636003)(8936002)(55016003)(166002)(82310400005)(356005)(110136005)(33656002)(36860700001)(26005)(7696005)(6506007)(33964004)(4326008)(8676002)(478600001)(41300700001)(70206006)(53546011)(316002)(40480700001)(70586007)(966005)(9686003); DIR:OUT; SFP:1101;
X-OriginatorOrg: ndzh.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Jul 2022 20:23:22.6374 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 4f98b660-51ae-40ec-342b-08da65d6b310
X-MS-Exchange-CrossTenant-Id: d6c573f1-34ce-4e5a-8411-94cc752db3e5
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=d6c573f1-34ce-4e5a-8411-94cc752db3e5; Ip=[35.166.188.152]; Helo=[obx-outbound.inkyphishfence.com]
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM12FT015.eop-nam12.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA1PR08MB7165
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/dFkMRNpkExUr23dqCA0BMz39PgQ>
Subject: Re: [Idr] CAR vs CT observation/question ...
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2022 20:23:34 -0000

Robert and Nats:

The new forum is posted at:
https://mailarchive.ietf.org/arch/msg/idr/3RH-Ra4igU4y0sVNC0WM4W0WM0Q/

Would you please pick up this interesting discussion and restart on this
3rd mail thread for the CAR – CT adoption call.   This new mail thread
has specific rules of discussion.

The IETF mailer seems to have munged Jeff’s review web pointer.
 Jeff’s summary can be found at:
https://mailarchive.ietf.org/arch/msg/idr/e69NRd9i2aG0WUxFkShEfQHZsHo/

Thanks for your passionate efforts!

Sue

From: Robert Raszuk <robert@raszuk.net>
Sent: Thursday, July 14, 2022 4:05 PM
To: Natrajan Venkataraman <natv@juniper.net>
Cc: idr@ietf. org <idr@ietf.org>; Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] CAR vs CT observation/question ...

Hi Natrajan, NV> The assumption that you are making about BGP-CT being a subset of BGP-CAR is neither correct nor backed by substantial technical evidence. When I stated that CT can be subset of CA
External (robert@raszuk.net<mailto:robert@raszuk.net>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzJiNjdmODFiNTRhZjI3NWMxOTQzMjk1MWQ3NDdiYjM2LzE2NTc4MjkxMzMuOTY=#key=80d464a9a914d7caea7cb7590edf8168>  FAQ<https://www.inky.com/banner-faq>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Hi Natrajan,

NV> The assumption that you are making about BGP-CT being a subset of BGP-CAR is neither correct nor backed by substantial technical evidence.

When I stated  that CT can be subset of CAR I did mean functionally. Do you dispute the fact that functionally both proposals are equivalent.

So the only significant difference voiced in almost all CT support emails was the fact that CT uses RD and VPN like encoding. Do you  also dispute that fact ?

So with both I do have an opinion that CAR's VPN mode can successfully meet expectations of those customers who feel much more comfortable with RD based encoding.

Many thx,
Robert





On Thu, Jul 14, 2022 at 9:57 PM Natrajan Venkataraman <natv@juniper.net<mailto:natv@juniper.net>> wrote:
Hi Robert,

Please find my answers inline marked with NV> below

Best,
-Nats-

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>
Date: Thursday, July 14, 2022 at 2:01 AM
To: idr@ietf. org <idr@ietf.org<mailto:idr@ietf.org>>, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Subject: [Idr] CAR vs CT observation/question ...
[External Email. Be cautious of content]

All,

Reading Sue's last email I can not resist asking one very basic but key question.

CT supporters love RD based information distribution schema. Yes, RD and VPN format has proven useful for a lot of services. But we are not stuck with it forever.

But as it is defined CAR does support VPN scoped distribution of transport colors with RDs.

So natural question pops:

Isn't CT just a subset of CAR ? If you like to use RD schema to distribute your classes of transport do it in the CAR VPN mode. Treat the Internet as a VPN if needed. Keep a broader solution to progress.

NV> The assumption that you are making about BGP-CT being a subset of BGP-CAR is neither correct nor backed by substantial technical evidence. I would like you to discuss technical viewpoints that you may have as part of Susan’s Part 3 (Q3) thread that is being scheduled. We will be more than happy to evaluate your comments in the context of that thread provided you present sound technical evidence.

Yes sure there are still encoding differences but what everybody supporting CT is saying is that what is convincing for them is the VPN model of distribution using RDs which CAR does support today (section 8 of draft-dskc-bess-bgp-car).

With that is this debate really needed ?

NV> This debate is needed because BGP-CT has proved that “all the use-cases” that apply to this problem space can be solved by leveraging existing BGP machinery that is available today with simple well-defined constructs. What is really the incentive to define something completely new like BGP-CAR to solve the same? In the networking world, anything brand-new is always seen as additional cost, sub-optimal ROI and takes time to mature.

The IDR chairs have come to an agreement that these two approaches are functionally identical. The only thing that needs to be affirmed is whether BGP-CAR brings something radically different with respect to

  *   Operational benefits
  *   Operational cost
  *   Training cost
  *   Ease of migration
  *   Ability to solve use-cases with an unified approach
  *   Overall efficiency in handling use-cases
  *   Optimal ROI
  *   Better scaling and performance
  *   Error Handling
  *   Maturation time
In exchange for adopting brand-new greenfield procedures that haven’t either stood the test of time or the scenarios available in the field.

Many thx,
Robert.



Juniper Business Use Only