[Idr] Re: Suggestion for the service metadata draft//Re: I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt

"duzongpeng@foxmail.com" <duzongpeng@foxmail.com> Thu, 04 July 2024 01:38 UTC

Return-Path: <duzongpeng@foxmail.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 8B182C1CAE8C for <idr@ietfa.amsl.com>; Wed, 3 Jul 2024 18:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.841
X-Spam-Level:
X-Spam-Status: No, score=0.841 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 i9EdBKjBvsuE for <idr@ietfa.amsl.com>; Wed, 3 Jul 2024 18:38:22 -0700 (PDT)
Received: from out203-205-251-27.mail.qq.com (out203-205-251-27.mail.qq.com [203.205.251.27]) (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 8A25DC1D52F3 for <idr@ietf.org>; Wed, 3 Jul 2024 18:38:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1720057097; bh=/Ib3BPJWFPiobMy5u+t2B8AA3OmSnKPySQao9Q8wPlo=; h=Date:From:To:Cc:Subject:References; b=nLdebl5EWevZSgBt2X/0u2ZJVLOo9z8fyq2A1E+y1VniA6bv2q0YavqYrr+3v3Azt aXhrXLwOrESmHGexYVY8WyA9ww8OlE1hTna9qYVLQyyzofwuG2ieV4ZvSC/aKb+m3m kOUSVZ7t4BU529aAKicqgGxCG+SAUExpy0QHrM1I=
Received: from cmcc-PC ([103.35.105.43]) by newxmesmtplogicsvrszb9-1.qq.com (NewEsmtp) with SMTP id 98F81A21; Thu, 04 Jul 2024 09:38:15 +0800
X-QQ-mid: xmsmtpt1720057095tvv9vdfuh
Message-ID: <tencent_D07F51DFE51750003E05EC9C7C3B6D9D6A08@qq.com>
X-QQ-XMAILINFO: NMGzQWUSIfvTxThjb6sY1jTLDlb6OWOpfhE97IB/lEkR7NCfxLbSSSf7PLmYOP LaxRX4P0tkeKUWrKEgGFHMvaHsPKx9IW5SRGyaUcDDfalmro8JIstSaXilU0r07DAo48WT1+KHhY ncq3WKYIQURpE5JPQnhPZG3GkFbgknmzI2wrZrrFBE3ER8qr6pqQp7erpsaB2EG/crp58Ne2ZTpu rVBguDZVCS7lfwIHx95vBJ1UVbeIN2n+SUSI1ARKTuMrNAB6l2JhXqDMG974l7dA1+/e7SQ9HDwS kl5I045fiFpX5E3hlyaMUcZu4MJEYcqPV3TOHFvb/RTX7Q+zoJfwYwG3gkqQbv98qBzRxVadP1lE Ag0rmEJe5kq2/kjodSSHU8XYsgiLSP9xAbVMUGFxISPx1C+a/FzrudsZye2nymhRWzLpGbrYesED 7Y4mxoBe/V/EZ2puQDpfTKo59DrNKmCrrOK84aFGB0sFaR9p8hsXAQykHNdCjj/Xr/KtNnb5i4ZG qeiIbhPR2jIWQGWtO+Bj6Bp9HNygoFckGerfSaiIAzjw+3dP4Sjo2V1LJ4s0KcVSHn2g4iThSF4i Z3ndFjQUJzz1p8VYgyhPS+XmDNLhPxN+iPE0vXjj370gGa3UDCFwiJaVfiWyiBciX3//gpXNGzll DtXEBJ/nqtrlJsJO1EZkG/Ju2pOxt9BqCZpHawiup9pR0OTR2RGrotPtv4ZT06a/02PmnF+WtsfW HQ5sT8nmWpXtcrKAInak8gvTAsfMuLUAnUfXgLdPHIEffVE2mujE30BH1nG2t3pt2JYz2rJv3S32 zHpF+Cr0DwzBFsDUfH8uBcnNXas5HRwQ+/zujKve1Wz4iJkBTlMr7cCZVoo3SbYVcOoh39u/r6Yf Rq/Qj2pD8IbDw3KS9aS6URx9irN9Ywri1AlnVW0zE5bLbTJvaLOgA/GzXTJlN2n/3JUc7RSvMxs2 q4p5NLeFP1k4KsckUtXeDj7FZ6q93Jg8JjIFpLu6Yg9OJVRePFQwnOuBMBW8OAoAUWKBC4uAXbg1 nTzqLfPw==
X-QQ-XMRINFO: OWPUhxQsoeAVDbp3OJHYyFg=
Date: Thu, 04 Jul 2024 09:38:16 +0800
From: "duzongpeng@foxmail.com" <duzongpeng@foxmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>, Chengli <c.l@huawei.com>
References: <171926035861.192.16829707527682361901@dt-datatracker-5864469bc9-n5hqk>, <tencent_84E4E52A50163E58EC397C676D3C6A345108@qq.com>, <CO1PR13MB492067A20667845596A482FB85D32@CO1PR13MB4920.namprd13.prod.outlook.com>
X-Priority: 3
X-GUID: 02A840AA-2FC0-4954-915D-FBA9B541F09A
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.259[cn]
Mime-Version: 1.0
X-OQ-MSGID: <2024070409381626154012@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart513645744433_=----"
Message-ID-Hash: R652CJR3VJIZJ6NODWZIQ63CZA2N67DY
X-Message-ID-Hash: R652CJR3VJIZJ6NODWZIQ63CZA2N67DY
X-MailFrom: duzongpeng@foxmail.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: "idr@ietf. org" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: Suggestion for the service metadata draft//Re: I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/guGbSYMgD1L-8kk9HIcXz-zjZwc>
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, Linda and ChengLi

    Thanks for the response. 

    I also have some other concerns about the draft. 

    About the section 4.5, perhaps we can consider to add the jitter information as well.  

    For example, we can add a flag to indicate a jitter value is also attached.

    
    For the algorithm in section 5.2, it is about the detailed realization inside the equipment, perhaps we do not need to mention it in the draft.

Best Regards
Zongpeng Du



duzongpeng@foxmail.com & duzongpeng@chinamobile.com 
 
From: Linda Dunbar
Date: 2024-07-02 01:08
To: duzongpeng@foxmail.com; Chengli
CC: idr@ietf. org
Subject: RE: Suggestion for the serice metadata draft//Re: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt
Zong Peng, 
 
Thank you very much for the suggestions. 
 
Please see below for the detailed resolutions. 
 
Linda
 
From: duzongpeng@foxmail.com <duzongpeng@foxmail.com> 
Sent: Thursday, June 27, 2024 7:58 PM
To: Linda Dunbar <linda.dunbar@futurewei.com>; Chengli <c.l@huawei.com>
Cc: idr@ietf. org <idr@ietf.org>
Subject: Suggestion for the serice metadata draft//Re: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt
 
Hi, Linda
 
    I have a suggestion for the draft. 


[1]. https://datatracker.ietf.org/doc/html/draft-ietf-idr-5g-edge-service-metadata-19#section-4.7
 
    In the section 4.7, a untilzation sub-TLV is described. It describes the Utilization, i.e., how much of this capacity is currently being consumed.
 
    However, I suggest to change it to the available capacity, i.e., how much of this capacity is currently available for future usage.  In fact, it can be calculated out from the Utilization TLV by using the total capacity minus the Utilized capacity. 

    After the modification, the total capacity in section 4.6 can be used as the weight for load balancing, which is relatively static; similarly, the available capacity can also be used as the weight for load balancing, which is relatively dynamic. Which one would be used on the Ingress (decision point) is the decided by the Ingress itself. 


    The modification can reduce the minus process.

[Linda] How about changing the title of section 4.7 to “Service-Oriented Available Resource Sub-TLV"?
We can use the Flag P (single bit) to indicate the value field. When it
          is set to 1, it indicates the value is the Service-Oriented
          Available Resource in percentage. When the "P" flag is set to 0, the
          value in this Sub-TLV is the abstract value of the available
          resource.
 
Thanks, Linda


Best Regards
Zongpeng Du
 


duzongpeng@foxmail.com & duzongpeng@chinamobile.com 
 
From: internet-drafts
Date: 2024-06-25 04:19
To: i-d-announce@ietf.org
CC: idr
Subject: [Idr] I-D Action: draft-ietf-idr-5g-edge-service-metadata-19.txt
Internet-Draft draft-ietf-idr-5g-edge-service-metadata-19.txt is now
available. It is a work item of the Inter-Domain Routing (IDR) WG of the IETF.
 
   Title:   BGP Extension for 5G Edge Service Metadata
   Authors: Linda Dunbar
            Kausik Majumdar
            Cheng Li
            Gyan Mishra
            Zongpeng Du
   Name:    draft-ietf-idr-5g-edge-service-metadata-19.txt
   Pages:   28
   Dates:   2024-06-24
 
Abstract:
 
   This draft describes a new Metadata Path Attribute and some Sub-TLVs
   for egress routers to advertise the Metadata about the attached edge
   services (ES).  The edge service Metadata can be used by the ingress
   routers in the 5G Local Data Network to make path selections not only
   based on the routing cost but also the running environment of the
   edge services.  The goal is to improve latency and performance for 5G
   edge services.
 
   The extension enables an edge service at one specific location to be
   more preferred than the others with the same IP address (ANYCAST) to
   receive data flow from a specific source, like a specific User
   Equipment (UE).
 
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-5g-edge-service-metadata/
 
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-5g-edge-service-metadata-19
 
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-5g-edge-service-metadata-19
 
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
 
 
_______________________________________________
Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org