IETF Logo Mail Archive

Re: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022)

Susan Hares <shares@ndzh.com> Wed, 29 June 2022 21:28 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD7DEC15AD29 for <ippm@ietfa.amsl.com>; Wed, 29 Jun 2022 14:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 z2cvG6hyoN2E for <ippm@ietfa.amsl.com>; Wed, 29 Jun 2022 14:28:47 -0700 (PDT)
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2061.outbound.protection.outlook.com [40.107.223.61]) (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 7E41FC15AAF5 for <ippm@ietf.org>; Wed, 29 Jun 2022 14:28:47 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FTUxCHAie8hZUFLdriR0l8khR7a9t0WJh0acLlL9kuusHeuZKwiij1IHmt8KFta+Uha7g+IMCKPoKiCj8d+GaBNvXXki1fjYF1bMRQqmw7tA6D1I3opa2cmZ3u8KuA+aXQtuCbxP2WySzlds1ldiOUPTU+j0E1eLQAV2Z57BVyuXJeAuoSRiCbgh0Q80EUi7VK3m7DPcqM7ab4a8q5+0KOSijrijHcDfyqhi/nFQfheF6qaV3DuJx9ZMxCqyp/nD8Sw68u4wXsvPBCDNvyTifjgOOxSBpI1/xHmRyXsQYiVUphuLJfRCQZUqPoIae09LRamO0zk2gH3fVA4BySvlbQ==
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=BLXHJ1OSRvWrfq2uDmHy5gfxxC163zTlP62vgkv+ObI=; b=Dr4gybihfQwDp6TPp4bctRnQeOiFxtRwEZA16dgcDpqz47yGL2SvCtvtfnBo8O9rwd3Ih5CU4Jkuggmn1TVjEvJcCNA3PEnhLUdVqORzztbPvZ63NPeoSPjlrOm3sEwYtm3XHej+858Qp6qCHHbBvzLxWx+3s4tEDwryGn4mzrrKGtH8ddUYJI42JSFUGZj54oL7WXotmfZczhgubR1koGz+N2DhfhYAyilk9jXozAwXwNJOTN6dDW17U9a9DTDvfpT4ozpgC0rLH/+JO+p6CUsSZc3y1oQae9cVmk3LcQvqde4BcAzqD/tsNrE6Sv2y0HGAPaDmREHTaNdimBPT1Q==
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 DM6PR05CA0058.namprd05.prod.outlook.com (2603:10b6:5:335::27) by DM6PR08MB5225.namprd08.prod.outlook.com (2603:10b6:5:42::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5373.18; Wed, 29 Jun 2022 21:28:42 +0000
Received: from DM6NAM12FT049.eop-nam12.prod.protection.outlook.com (2603:10b6:5:335:cafe::2f) by DM6PR05CA0058.outlook.office365.com (2603:10b6:5:335::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5395.12 via Frontend Transport; Wed, 29 Jun 2022 21:28:42 +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.inkyphishfence.com;
Received: from obx.inkyphishfence.com (35.166.188.152) by DM6NAM12FT049.mail.protection.outlook.com (10.13.178.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5417.6 via Frontend Transport; Wed, 29 Jun 2022 21:28:42 +0000
Received: from NAM04-MW2-obe.outbound.protection.outlook.com (mail-mw2nam04lp2174.outbound.protection.outlook.com [104.47.73.174]) by obx-inbound.inkyphishfence.com (Postfix) with ESMTPS id 55C5117D454; Wed, 29 Jun 2022 21:28:41 +0000 (UTC)
Received: from BYAPR08MB4872.namprd08.prod.outlook.com (2603:10b6:a03:70::17) by SN6PR08MB4253.namprd08.prod.outlook.com (2603:10b6:805:34::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5373.18; Wed, 29 Jun 2022 21:28:38 +0000
Received: from BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::de0:4e0d:2268:73c3]) by BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::de0:4e0d:2268:73c3%5]) with mapi id 15.20.5395.014; Wed, 29 Jun 2022 21:28:38 +0000
From: Susan Hares <shares@ndzh.com>
To: "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
CC: "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022)
Thread-Index: AQHYi5ePy9TSDFzaHEueiiXwAWFDA61m5I3A
Date: Wed, 29 Jun 2022 21:28:37 +0000
Message-ID: <BYAPR08MB4872921388CFF8F234435865B3BB9@BYAPR08MB4872.namprd08.prod.outlook.com>
References: BYAPR08MB4872BA1F22EBD8F6788A4A89B3B49@BYAPR08MB4872.namprd08.prod.outlook.com <202206291706238457947@zte.com.cn>
In-Reply-To: <202206291706238457947@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-MS-Office365-Filtering-Correlation-Id: 9479207c-d055-4de3-91c4-08da5a16575f
x-ms-traffictypediagnostic: SN6PR08MB4253:EE_|DM6NAM12FT049:EE_|DM6PR08MB5225:EE_
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: s4KBjEkZtH5tBcejnSdtkryJTyIgEGfPtY+7x3egK5xQYV5/PEL4nUlCyGVOYcTcKLW+rWOd9dQrYl4OeTVo+gic3GRyIxBuMQn6fIePzR2jL4H9MeJkgnq69cq5SA8RTNLLjHZnIu1LH1gUkfWpzbVGPgllhgEWhh7gZZzQb6ia3RruII8q1jg2p01TgdwsRuOmZyeFPV+qTg3xnpVEJCwXrmrLQzFPm9G5CYjCATC2F/SzKWbnA6O751nFyhmzH3WlvgcNy2KbQWPSMeAydsIwXIjaa4FmdtHuD5vQ6tTWpcrAqWTESzT+mbTWaO6NiB/faneV4ukJdzhvay5S3KUNbi4KxPtVG6Mwlp2ZdEYsMrkEDJtKagp97f59JboTG4UGSq1nDKcz5B4vBswKFW3ReDxraZUkIzSVYSCOKtgeN0BqdllJGya2s2ItdbwFUThzh3WDq6TLqz2IqZ3jp6FAnAqpm64PP6OuZs6n0Nxd2J2yHN13wkfT3eMlYhS78UPvMmtlfGNt0gRhoYu1DfJMzXVoZp0LTBixJGYv2eVey3Qh/p11xwJ5bl7kwVI+pGwUErUXBQiYm9SvA+Aa2KB0L3NTxeJ4LO0AI5QKniXMqjRFYxrWENCbNvShYnpqM+LdmT5I74J6ZhpZg73MmbpQLKdW8N4X8IQqks4Ds1FFuFWWl49FTM2BB8afhU9V4TvxgR4QdsXrGy8MpXremxAu2beJWOBRzreV2BeRmRgF7uWy/dTmrtsBV8RKha4IuJStdjOGgWxEw10ZeZQZYy1lSGwPyAiMxD3+i0u9jV/R8Or84j/7l2QYJ1vQoTR0AC1U5UB58dR8tJjJ5bnfCP0MyMGc4Nw36WnBwc/6IQs=
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)(136003)(346002)(366004)(396003)(39830400003)(376002)(66556008)(66476007)(64756008)(186003)(86362001)(71200400001)(4326008)(66446008)(316002)(33656002)(5660300002)(6916009)(76116006)(52536014)(38070700005)(66946007)(122000001)(8676002)(8936002)(38100700002)(966005)(478600001)(53546011)(41300700001)(9686003)(7696005)(2906002)(55016003)(6506007)(83380400001)(166002)(26005); DIR:OUT; SFP:1101;
Content-Type: multipart/alternative; boundary="_000_BYAPR08MB4872921388CFF8F234435865B3BB9BYAPR08MB4872namp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR08MB4253
X-Inky-Outbound-Processed: True
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DM6NAM12FT049.eop-nam12.prod.protection.outlook.com
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id-Prvs: 835a6167-8ac1-4e71-e229-08da5a165484
X-IPW-GroupMember: False
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: lvkFu0GBAunDIu4Sr9A5m6/qWdaMbV+UQBkhFMpc6u2E00U8roAmciF9ZMN0g87f0lrpY8Y2sCtddy7JVH6sUiYNUUO8p9QndS/wYavYnD0b/hqj5p/pZjD/WpSLeXVNS//2b4oNLpGd9QJkKRXdY9rwbRuK764X8Km+E2nERaNcaFUMxDizH1xHd/aV8+Er7uQpuKRQJiB5TV0C3n3qK4rckIzVxnBuNvxahOPbU6hFe8yvnS58MYqcsN7S+wtXPaNfw7jsNwqjIaCemqqaDPl+3JIGXP4NdJblXfjIGfHA0aY2Fs3j3wnocZE3rljq/l8ZR52Pnj9xaKYBiqRh3JU5v1xO631WITtrQ+6mUzoGnjtJsOpnNn00Pfnhr8E8lkUGPF6JDGBcS24kWlsLi1vhRbW4U0WzVi3K2sv2g2tsMNaVxvc+t+LXblwI5vA/74CGWuGuhM+ZUbjfJxywfqzBbCzvBWn39p4GGSrPf+S7Hu6IkBAziw4xoT6s90w1KX4waXpsWxlKk9LY1wmuU5fz1N3s+usRcvtp/OUtpmkyHmbIfpPMo69V57J47o2dpJ18rJZCcGXUS8cNU9rFWwFlUov9PHiktSg7XMm6eogjacbrw6N6sQd6kFn7lSiS18D4pSuT5V01V3BaesVlWrhGq01g7V71sM6lGbngzIgp08M6+lwDy15Q0w/JazKao6l8tCCdey4bhTQGIZDQ+py10f/XBuKjEmsIf4ogA8zcAa68gZi0LSmXCa3D6fCSwy3IQ3eoVG0DAoUjxRrevu4JngbwbrQAWcJoNtsm8jklXUrXxMwDyONp/KVNzx7kBuqTGirpBiNAy8qu8mYeOg==
X-Forefront-Antispam-Report: CIP:35.166.188.152; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:obx.inkyphishfence.com; PTR:obx-outbound.inkyphishfence.com; CAT:NONE; SFS:(13230016)(39830400003)(346002)(376002)(136003)(396003)(46966006)(36840700001)(70206006)(33964004)(7636003)(41300700001)(6506007)(47076005)(70586007)(478600001)(6916009)(186003)(83380400001)(166002)(53546011)(336012)(36860700001)(8676002)(356005)(26005)(7696005)(8936002)(33656002)(52536014)(45080400002)(86362001)(4326008)(5660300002)(316002)(40480700001)(2906002)(9686003)(966005)(82310400005)(55016003); DIR:OUT; SFP:1101;
X-OriginatorOrg: ndzh.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Jun 2022 21:28:42.6445 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 9479207c-d055-4de3-91c4-08da5a16575f
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.inkyphishfence.com]
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM12FT049.eop-nam12.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR08MB5225
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/xSCJlKW_88Ksj_1fhOyH1igmGQc>
Subject: Re: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2022 21:28:51 -0000

Xiao:

Thank you for your feedback regarding this draft.
I need clarification on your feedback.

The introduction of draft-wang-idr-bgp-ifit-capabilities-05.txt
states IFIT is an abbreviation used by their draft as
denoted in their abstract:

   “This document defines extensions to BGP [RFC4271] to advertise the
   In-situ Flow Information Telemetry (IFIT) capabilities.”

Since this abbreviation is shared with:
draft-ietf-idr-sr-policy-ifit-03 (ready for WG LC) in
their abstract:

    “In-situ Flow Information Telemetry
   (IFIT) refers to network OAM data plane on-path telemetry techniques,
   in particular the most popular are In-situ OAM (IOAM) and Alternate
   Marking.”

Are you objecting to their abbreviation or the terms behind the
abbreviation?

2.  Would you please provide additional details on the overlap between
draft-wang-idr-bgp-ifit-cpabilities-05.txt and
draft-ietf-ippm-ioam-conf-state.

Thank you Susan Hares

From: xiao.min2@zte.com.cn <xiao.min2@zte.com.cn>
Sent: Wednesday, June 29, 2022 5:06 AM
To: Susan Hares <shares@ndzh.com>
Cc: ippm@ietf.org
Subject: Re: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022)

Hi Susan, Thank you for this notice, very helpful. I have two concerns as follow: 1. As far as I know, iFIT is not a standardized term defined in any IPPM RFC or WG draft, however iFIT includes Altern
External (xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tL2VmZGIyZWVlMGI0MmJlYmU2YTM2Y2JmMDVlM2Y3ZGEyLzE2NTY0OTM2MDEuOA==#key=62294ccb93526bd5bdf8fef445f3cf59>  FAQ<https://www.inky.com/banner-faq>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>


Hi Susan,



Thank you for this notice, very helpful.

I have two concerns as follow:

1. As far as I know, iFIT is not a standardized term defined in any IPPM RFC or WG draft, however iFIT includes Alternate Marking and In-situ OAM which both are defined in IPPM. I'm not sure it's appropriate, that looks out of order to me. The right order IMHO is to define iFIT in IPPM first (if necessary), and then to define protocol extensions (e.g. BGP extensions) to support iFIT.

2. In IPPM there is draft-ietf-ippm-ioam-conf-state that achieves the similar function intended by draft-wang-idr-ifit-capabilities, the two documents looks overlapping to some extent.



Best Regards,

Xiao Min

------------------Original------------------

From: SusanHares <shares@ndzh.com<mailto:shares@ndzh.com>>

To: ippm@ietf.org<mailto:ippm@ietf.org> <ippm@ietf.org<mailto:ippm@ietf.org>>;

Date: 2022年06月24日 23:29

Subject: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022)

_______________________________________________

ippm mailing list

ippm@ietf.org<mailto:ippm@ietf.org>

https://www.ietf.org/mailman/listinfo/ippm<https://shared.outlook.inky.com/link?domain=www.ietf.org&t=h.eJxNjMEOgyAQBX_FcG5YQKXWk78CstRNBYzQ2Nj031tuvb55M2_23Fc2NmwpZcsjwHEcnLB4nvY7BENrMBFWyoWiT0DbFtilYY-qRCy_kxT9oG9SQV7MjnmK7lz4nAKgd1YhorCdsmhRm1bP1oseW391RoHUve5urRaSDzWKNfoik3igqKazYO3wOVboKvybPl8h5TpL.MEYCIQCBnmd9-d0HffKOr6zNeEqTcGaHg3X2BaUIadZC0UxkCQIhAOQ8mnXEDUrE6p-fIacdpKujkPRZG8_vtdai1OrJZBAz>



Marcus, Tommy and ippm WG:

The IDR WG would like your feedback on two drafts in IDR:

1. draft-ietf-idr-sr-policy-ifit-03.txt – The IDR WG is planning WG LC on this draft in August.

2. draft-wang-idr-ifit-capabilities-05.tt – The IDR WG has consensus on adopting this draft.

Please let us know if you have any concerns regarding these drafts.

We note that these drafts reference:

1) draft-ietf-6man-ipv6-alt-mark

2) draft-ietf-ippm-ioam-data

3) draft-ietf-ippm-ioam-direct-export

4) draft-ietf-ippm-ioam-flags

5) draft-ietf-ippm-ioam-ipv6-options

Please let me know if you have any questions regarding these two drafts.

I am one of the IDR WG co-chairs and the shepherd for these two drafts.

You can reply to this thread or provide information to your WG chairs.

Cheers, Susan Hares

v2.23.0 | Report a Bug | By Email