[Idr] Re: [CATS & IDR] Discussing the distribution of service metrics via BGP[draft-lin-idr-distribute-service-metri]

linchangwang <linchangwang.04414@h3c.com> Fri, 07 June 2024 08:36 UTC

Return-Path: <linchangwang.04414@h3c.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 D6F1AC1D4A6E; Fri, 7 Jun 2024 01:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 OkYJUszMMSBJ; Fri, 7 Jun 2024 01:36:22 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (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 086E4C18DB80; Fri, 7 Jun 2024 01:36:14 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 4578Zmuc063777; Fri, 7 Jun 2024 16:35:48 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX10-BJD.srv.huawei-3com.com (unknown [10.153.34.12]) by mail.maildlp.com (Postfix) with ESMTP id 0EECA2004BAA; Fri, 7 Jun 2024 16:39:19 +0800 (CST)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) by DAG6EX10-BJD.srv.huawei-3com.com (10.153.34.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Fri, 7 Jun 2024 16:35:50 +0800
Received: from DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738]) by DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738%17]) with mapi id 15.02.1258.027; Fri, 7 Jun 2024 16:35:50 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Robert Raszuk <robert@raszuk.net>
Thread-Topic: [Idr] [CATS & IDR] Discussing the distribution of service metrics via BGP[draft-lin-idr-distribute-service-metri]
Thread-Index: Adq4nKslDPQoanK2R4qPV9o8iFJwwA==
Date: Fri, 07 Jun 2024 08:35:50 +0000
Message-ID: <515c3f147d31406ab6827c33a23bfbc0@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.76.156]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_515c3f147d31406ab6827c33a23bfbc0h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 4578Zmuc063777
Message-ID-Hash: DTIFW7VAYHMZT7Q3VUVX5MGFXWC6ATQU
X-Message-ID-Hash: DTIFW7VAYHMZT7Q3VUVX5MGFXWC6ATQU
X-MailFrom: linchangwang.04414@h3c.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: cats <cats@ietf.org>, "cats-chairs@ietf.org" <cats-chairs@ietf.org>, "idr@ietf.org" <idr@ietf.org>, idr-chairs <idr-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: [CATS & IDR] Discussing the distribution of service metrics via BGP[draft-lin-idr-distribute-service-metri]
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Vwu6z275RE2CqQVcyg7qLBAReRk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hi Robert,

       Thanks for the review and comments,  I will prepare a new revision to address them.
       Please check inline below for responses with Changwang.

Thanks,
Changwang


发件人: Robert Raszuk <robert@raszuk.net>
发送时间: 2024年6月6日 18:09
收件人: linchangwang (RD) <linchangwang.04414@h3c.com>
抄送: cats <cats@ietf.org>; cats-chairs@ietf.org; idr@ietf.org; idr-chairs <idr-chairs@ietf.org>
主题: Re: [Idr] [CATS & IDR] Discussing the distribution of service metrics via BGP[draft-lin-idr-distribute-service-metri]

Dear Authors of  draft-lin-idr-distribute-service-metric<https://datatracker.ietf.org/doc/draft-lin-idr-distribute-service-metric/>,

I have read your proposal with interest.

I have a few comments on it.

#1 Fundamental - The document as written today is not scalable. However if you just slightly modify the proposal and insert in between Subscriber and Publisher a regular Route Reflector or Route Server I do believe we will start to have a solid base for discussion.

Changwang > Thank you, I will update the explanation of Route Reflector or Route Server in the next release.

#2 Editorial - There are a number of terms in this document which should be renamed to better reflect their role. Example: "Register Route" advertisement should be renamed to "Service Metric Advertisement" or something that is not a synonym of Subscribe Route.

Changwang > Thank you for the suggestion, I will update the description in the next version.

In general IMO we should discourage advertising service metrics using BGP. I understand that as we have TCP sessions we are loading BGP more and more simply for convenience. BGP is a "spray and pray" protocol. Not a pub/sub bus.

Changwang >  BGP is evolving due to the reliability and scalability of TCP. It has seen significant advancements in the announcement of routing information, north-south interfaces for controllers, EVPN, MVPN, and other areas. As BGP address families continue to evolve, mechanisms such as MVPN and RT-Filter have emerged, incorporating features like request and interaction, as well as active filtering. The description of pub/sub here may be inaccurate; in reality, it is a form of dynamic filtering mechanism. This feature for the distribution of service metrics is optional and will be updated in subsequent versions.


So at very minimum a section in this document should discuss alternative options to distribute service metrics to RRs/Controllers and highlight why using BGP would be superior.

Changwang >  Thank you for the suggestion. I will include additional descriptions and comparative analysis in the next version.

Kind regards,
Robert


On Thu, Jun 6, 2024 at 11:11 AM linchangwang <linchangwang.04414@h3c.com<mailto:linchangwang.04414@h3c.com>> wrote:
Hi Wg,

Link: https://datatracker.ietf.org/doc/html/draft-lin-idr-distribute-service-metric-02

This document is based on the extension address families of BGP for distributing the computing metrics of CATS.
It primarily focuses on the following aspects:

1. Transmitting computing metrics information through the new BGP extension address families to ensure isolation from the routing information of other existing address families.
  This approach can enhance the performance of computing routing while minimizing the impact on existing address families.

2. Implementing dynamic subscriptions of corresponding computing metrics through BGP-extended routes based on the on-demand concept to mitigate the repercussions of periodic computing metrics updates.

3. Defining computing metrics information in the new NLRI of BGP, rather than in the attributes of BGP. This enhances the efficiency of computing routing transmission and processing, and overall performance.

4. Normalizing computing metrics measurement information.

We welcome any comments and discussions.

Thank you!

Thanks,
Changwang


-----邮件原件-----
发件人: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
发送时间: 2024年6月6日 13:22
收件人: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
主题: I-D Action: draft-lin-idr-distribute-service-metric-02.txt

Internet-Draft draft-lin-idr-distribute-service-metric-02.txt is now available.

   Title:   Distribute Service Metric By BGP
   Authors: Changwang Lin
            Huijuan Yao
   Name:    draft-lin-idr-distribute-service-metric-02.txt
   Pages:   20
   Dates:   2024-06-05

Abstract:

   When calculating the path selection for service traffic, it is
   important to consider not only network metrics, but also the impact
   of service Metric. Therefore, it is necessary to transmit service
   Metric information from the server site to the user access site, in
   order to facilitate path selection for service traffic at the access
   router.

   This document describes an approach for using the BGP Control Plane
   to steer traffic based on a set of metrics that reflect the
   underlying network conditions and other service-specific state
   collected from available service locations.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-lin-idr-distribute-service-metric/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-lin-idr-distribute-service-metric-02

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-lin-idr-distribute-service-metric-02

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list -- i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> To unsubscribe send an email to i-d-announce-leave@ietf.org<mailto:i-d-announce-leave@ietf.org>
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!
_______________________________________________
Idr mailing list -- idr@ietf.org<mailto:idr@ietf.org>
To unsubscribe send an email to idr-leave@ietf.org<mailto:idr-leave@ietf.org>