Re: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)

This adoption call is closed.   The IDR chairs will announce the results on 9/10/2022.

Cheers, Sue Hares

From: Linda Dunbar <linda.dunbar@futurewei.com>
Sent: Monday, August 22, 2022 7:06 PM
To: Dhruv Dhody <dhruv.ietf@gmail.com>; Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Subject: RE: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)

Dhruv, Thank you very much for the comments. Resolution to your comments are inserted below. Linda  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌
External (linda.dunbar@futurewei.com<mailto:linda.dunbar@futurewei.com>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzY2ZTNhZTlhYjgwYjM5M2IxOTEwZmE0NmU5YWFkMTVjLzE2NjEyMDk1ODQuNzM=#key=1a771b79c4c5929fc44b49d687176fb1>  FAQ<https://www.inky.com/banner-faq>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Dhruv,

Thank you very much for the comments.
Resolution to your comments are inserted below.

Linda

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Dhruv Dhody
Sent: Monday, August 22, 2022 8:49 AM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Cc: idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)

Hi WG,

I support WG adoption of this draft. Please find some comments for the considerations for the authors - all of them can be handled post adoption.

  *   Document abstract consider AppMetaData to be well-known, it would be better if a sentence is added first on what is AppMetaData in the context of BGP.

[Linda] Add this sentence in the Introduction to explain what AppMetaData mean in the document:

“The AppMetaData in this document refer to edge services’ site capacity, the site preference, and the load index, that are further explained in Section 3.”

  *   Abstract and Introduction says 3 new subTLVs but no context of where those subTLVs are present. They are mentioned later on in section 3.

[Linda] added the reference to Section 3 in the Introduction section.

  *   Section 3, adding description for metrics would be nice (or provide references)

[Linda] Added the following reference:

“[5G-EC-Metrics] has an example algorithm to compute the weighted path cost based on the AppMetaData carried by the sub-TLVs specified in this document.”

  *   Section 3.1.2 and 3.1.3 has useful information, but it is not clear how it is linked to AppMetaData.

[Linda] It is linked to the cost computed by the AppMetaData values. Cleaned out the text that was left over from splitting some content to another draft:  https://datatracker.ietf.org/doc/draft-dunbar-idr-5g-edge-compute-bgp-usage/<https://shared.outlook.inky.com/link?domain=datatracker.ietf.org&t=h.eJxVjkEOgjAQRa9iurYtFamUlVeZMkMhKpBhGhONd5fGlduX_17-W2W-q-6gRpF166xFEBCG_kZsJpLBLJwsLr1FhkE05jkC6wlZN0kTJtL98lizkI5p1XmDRFYdD-pWojPJrruqaX1wJ7uNwLRdZ3yNZres91QDBYhtFetQRxdcNcDZ7wjQNb113rtTFZr2bC51qVKp3qcZwfyeXIcsmelJUymWCZbJP_18ASxhSbo.MEQCICED0OsyFzHdXX_5FSBci_wuGSjc6vilvhsbg0nilV_QAiAipdc6fqU9vPy_9m46lr50qcxbuqODvWZQ88rKQfA4Og>

  *   Section 4.3, add a unit for Measure Period time

[Linda] In Seconds. Add.

  *   Manageability and Security are key for this work, and thus considerations for both should be added soon

[Linda] Add the following for the Manageability Consideration section:

“ The AppMetaData described in this document are only intended for propagating between Ingress and egress routers of one single BGP domain, i.e., the 5G Local Data Networks, which is a limited domain with edge services a few hops away from the ingress nodes. Only selective services by UEs are considered as 5G Edge Services. The 5G LDN is usually managed by one operator, even though the routers can be by different vendors.”

Add the following for the Security Consideration section:

“The proposed AppMetaData sub-TLVs are advertised within the trusted domain of 5G LDN’s ingress and egress routers. There are no extra security threats compared with iBGP.”
Nits

  *   s/subTLVs/sub-TLVs/

[Linda] changed to sub-TLVs

  *   Expand on first use - UE, CPE

[Linda] done.

  *   Section 3.1.1 calls the plugin as “load
Compute Engine” where as Section 5 calls it “Cost Compute Engine” - are they same or different things?
[Linda] Thanks for catching this.

On Fri, Jul 29, 2022 at 3:53 PM Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>> wrote:
This begins a 3 week WG Adoption call for
draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt
https://datatracker.ietf.org/doc/draft-dunbar-idr-5g-edge-compute-app-meta-data/<https://shared.outlook.inky.com/link?domain=nam11.safelinks.protection.outlook.com&t=h.eJxVUU1v2zAM_SuFAec0O_qwZbtAsCZpsrltDgPapNhNtqjYcSJ5slxjHfbfJ6WXFaAo8Yl8JPH-BKM5B7c3QWNtP9zO54pfMI4HLuHcqm6Ie6Mt1LbVKtajPWvdxbW-zL-6ssW1JqTLkGydCW65NbzuwMQtWBlrc_Swrr03XNpIjKriJmqFidJjBOIIkSPrRwsR7_voApZHnsYVzPy9QGmYrRF2zk0jePxBECZIjnY0MEHrp3HfMqNEVCjBhUwTIhBgwlEueJ4kKa0h8zQSIJeScFqRBOG8qLOUcizStMASRO1SfCPkDqNZwbKMIsxoQTGhzIEvqlN6Uu71fNj21befQ0VFDr8fDuVJt7t1Mj2dltPuftk-rR9-eGxPzuPuvfTx6rktWdnhhh8mH7_u1yXbKRTSe0dIEfJtP2w2XFff2awot6d6Mzxq21wmUoZkdXlxbjtkFiPofmn6-l3tN6v-0aEbRzUzMIB5A7FAwZeboPPCKrBOCIzSnBWYzIeGu6Q7Jd6bq5CMAeVQ8CpHldu1wgVGkifMQVzgtJ5jxjBBRZoncUY9K3jW_-W4-ySGTxE-5TP69x8rrL_S.MEUCIGNwyy6D3ySWS-2SSK8HlI95-mVj14gjdezrpWDTAdyJAiEAlbW7ROe0YNSkj-ZIEU3DuduXy3wTTjqOidZquqzNi_g>

This draft proposes a new SubTLV (AppMetaData)
for the BGP Tunnel Encapsulation Attribute [RFC9012]
that indicates the running status and environment of directly
attached 5G Edge Computing (EC) instances.

The AppMetaData can be used by routers in the
5G Local Data Network to make path selection
not only based on the routing distance but also the running
environment of the destinations. The goal is to improve
latency and performance for 5G EC services.

In your discussion of this adoption call, please consider
these questions:

1) The addition of this type of information to tunnels
is useful for inter-domain routing within 5G networks?

Yes!

2) What type of additional load this data to
Basic Tunnel encapsulation [RFC9012]?

For example is the load placed by this draft equal or
Less than the SR routing additions from
such as draft-ietf-idr-segment-routing-te-policy?

More details in managebility consideration should be added for this!

3) Will the addition of this information aid
Routing in 5G networks?

Yes!

Thanks!
Dhruv

Cheers, Sue Hares

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr<https://shared.outlook.inky.com/link?domain=nam11.safelinks.protection.outlook.com&t=h.eJxVUV1r4zAQ_CvF4Dwdtr4s24VwTRN6uDRwgTYpeZMsqVbsSDlZPtMe999PSl-usBK7s7MzSPsnmdyQ3N4knfeX8TbPDTtDmI1MyUGbfswuznrZem1NZic_WNtnrT3n38PY8jqT4lWKHkLM85xp6VVm3Vsoz0wPZ2ZCNujRa6NsSLVwC8E8W4IiLdcAhivYCJaJyXDmUgLU5CcnZ6mjTWirEiPBAYG1KggSQELEQCVYRUiBW1lGGSVlpRRimCMCYFW3ZYEZFEVRQyVFGyjRCIRDcVnTssQAUgKqMkgE8MX0xs4mZM-Hhwv_cRw5FpV8fzw0J6u3azI_nVbzdrPST-vHXcT2aJi2H02s7591Q5seduwwx_p1v27o1oAUb4IgBiDafsZivD59v4HNyl3OM3__-WuTovvuzeD-lYfvEZYe_XE3khOpcRdax86hXZBaODlK91uKJUi-3SR93JiRPvw0BEVFa4jysWOBdGfER3fdEKUSM1kzXgGOa8xhDYFihAaICVi0OaQUIlAXFclKHFVlVP1_HXdflhEpIlK-on__AU_wsng.MEUCIQCnu3V-LBdTAeOQzFbOHZbTWEDk-fp7fObJMbo56807RQIgS5SsV2wLaiuUdz5sApmc-NC2pnKKJY-13nxEIzoWILQ>