Re: [Lsr] Question on using OSFPv2 extended Prefix TLV as the OSPF extension for 5G Edge Computing (was RE: IETF 109 LSR Presentation Slot Requests

Aijun Wang <wangaijun@tsinghua.org.cn> Wed, 16 December 2020 03:44 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E873A0E60; Tue, 15 Dec 2020 19:44:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.795
X-Spam-Level:
X-Spam-Status: No, score=-1.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u1vKW78b0nys; Tue, 15 Dec 2020 19:44:38 -0800 (PST)
Received: from mail-m127101.qiye.163.com (mail-m127101.qiye.163.com [115.236.127.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 939513A0E59; Tue, 15 Dec 2020 19:44:35 -0800 (PST)
Received: from DESKTOP2IOH5QC (unknown [219.142.69.75]) by mail-m127101.qiye.163.com (Hmail) with ESMTPA id 9FF1047F40; Wed, 16 Dec 2020 11:44:31 +0800 (CST)
From: "Aijun Wang" <wangaijun@tsinghua.org.cn>
To: "'Acee Lindem \(acee\)'" <acee=40cisco.com@dmarc.ietf.org>, "'Jeff Tantsura'" <jefftant.ietf@gmail.com>, "'Yingzhen Qu'" <yingzhen.ietf@gmail.com>, <lsr@ietf.org>, <lsr-chairs@ietf.org>, "'Linda Dunbar'" <linda.dunbar@futurewei.com>
References: <SN6PR13MB2334FB60B2DEF450A621C01285EF0@SN6PR13MB2334.namprd13.prod.outlook.com> <9af88324-b117-4272-b21d-29002f9183fd@Spark> <75281559-0A10-4F81-B358-AAE2CBA0DE2B@cisco.com>
In-Reply-To: <75281559-0A10-4F81-B358-AAE2CBA0DE2B@cisco.com>
Date: Wed, 16 Dec 2020 11:44:31 +0800
Message-ID: <000901d6d35d$c35e3a40$4a1aaec0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01D6D3A0.D1843960"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQD2J7U/Llv21jdkogB4O2EIjUtqHQNgqO6mAg0tJwerjve6cA==
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZS1VLWVdZKFlBSkxLS0o3V1ktWUFJV1 kPCRoVCBIfWUFZTxpNS0hPSE5JSkxNVkpNS0NLQktJTElLS09VEwETFhoSFyQUDg9ZV1kWGg8SFR 0UWUFZT0tIVUpKS09ISFVLWQY+
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Kww6Djo4DT8KIikKMjQ4OU9O Nx8KCjpVSlVKTUtDS0JLSUxJT0JDVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQU1MSUxONwY+
X-HM-Tid: 0a7669a6407a9865kuuu9ff1047f40
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/0J5PsbMsPwoJqvMNEJVVS8CCQOk>
Subject: Re: [Lsr] Question on using OSFPv2 extended Prefix TLV as the OSPF extension for 5G Edge Computing (was RE: IETF 109 LSR Presentation Slot Requests
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2020 03:44:42 -0000

Hi, Acee and Linda:

 

The mentioned information in this draft are more related to the links that connect the server to the edge router, than to the prefix of the app server.

For example, the “Capacity Index”, “Preference Index” are all related to the site, not the prefix. 

And, for “Load Measurement”, it is not enough to detect only the load to the server, but omits the load status of the link that connected the servers.

We should also considering the future possible extension, such as the bandwidth reservation on these links to the App server etc.

 

In conclusion, associate these attributes to the link is more reasonable than to the prefix.

Such links are another typical use case of passive/stub link within the network.

 

 

Best Regards

 

Aijun Wang

China Telecom

 

From: lsr-bounces@ietf.org <lsr-bounces@ietf.org> On Behalf Of Acee Lindem (acee)
Sent: Thursday, November 5, 2020 8:42 AM
To: Jeff Tantsura <jefftant.ietf@gmail.com>om>; Yingzhen Qu <yingzhen.ietf@gmail.com>om>; lsr@ietf.org; lsr-chairs@ietf.org; Linda Dunbar <linda.dunbar@futurewei.com>
Subject: Re: [Lsr] Question on using OSFPv2 extended Prefix TLV as the OSPF extension for 5G Edge Computing (was RE: IETF 109 LSR Presentation Slot Requests

 

Exactly. 

Thanks,
Acee

 

From: Jeff Tantsura <jefftant.ietf@gmail.com <mailto:jefftant.ietf@gmail.com> >
Date: Wednesday, November 4, 2020 at 6:16 PM
To: Acee Lindem <acee@cisco.com <mailto:acee@cisco.com> >, Yingzhen Qu <yingzhen.ietf@gmail.com <mailto:yingzhen.ietf@gmail.com> >, "lsr@ietf.org <mailto:lsr@ietf.org> " <lsr@ietf.org <mailto:lsr@ietf.org> >, "lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org> " <lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org> >, Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com> >
Subject: Re: [Lsr] Question on using OSFPv2 extended Prefix TLV as the OSPF extension for 5G Edge Computing (was RE: IETF 109 LSR Presentation Slot Requests

 

For OSPFv3 use E-LSAs (RFC8362)

 

Cheers, 

Jeff

On Nov 4, 2020, 2:44 PM -0800, Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com> >, wrote:

Acee,

 

Thank you very much for suggesting using the Prefix TLV for carry the Running Status and environment of 5G Edge Computing servers.

 

In a nutshell, the  <https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/> https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/ proposes the extension to LSA that can carry the three SubTLVs that are used to represent the Running Status and Environment information of the 5G Edge Computing Servers attached to the router:

 

 • Load measurement sub-TLV 

 • Capacity Index  Sub-TLV                            

 • Preference Index  Sub-TLV                                                   

 

Several sections of the draft are devoted to describe what those measurement are and why need them for 5G Edge Computing, which may have made it not so straightforward when reading in a rush.

 

The Goal of the OSPF extension is to carry those Sub-TLVs in the router’s LSA to be advertised to other routers in the 5G Local Data Network.

 

If using your suggested RFC7684 OSPFv2 Extended Prefix TLV, the extension does seem easier and cleaner:

 

We can have:

 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Type                          | Length                        |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Route Type    | Prefix Length | AF            | Flags         |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

| Address Prefix (variable)                                     |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  

| Load Measurement Sub-TLV                                      |

~                                                               ~

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  

| capacity Index Sub-TLV                                        |

~                                                               ~

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  

| Site Preference Sub-TLV                                       |

~                                                               ~  

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  

 

 

RFC7684 only has the Extended Prefix TLV for IPv4. If the App Server addresses are in IPv6, should we specify the extension to RFC8362 in the same draft? Or define a new AF type for the same extension to RFC7684?

 

Your guidance is greatly appreciated.

 

Thank you very much.

 

Linda Dunbar

 

 

From: Acee Lindem (acee) <acee@cisco.com <mailto:acee@cisco.com> >

Sent: Tuesday, November 3, 2020 1:38 PM

To: Linda Dunbar <linda.dunbar@futurewei.com <mailto:linda.dunbar@futurewei.com> >; Yingzhen Qu <yingzhen.ietf@gmail.com <mailto:yingzhen.ietf@gmail.com> >; lsr@ietf.org <mailto:lsr@ietf.org> ; lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org> 

Subject: Re: Need 10 minute slot to discuss OSPF extension for 5G Edge Computing (was RE: [Lsr] IETF 109 LSR Presentation Slot Requests

 

We have a pretty full schedule and we add you as optional. I took a look at the draft and it is all over the place right now with standardization requested for one solution but 3 separate solutions partially specified. It could benefit from some WG mailing list discussion prior to a 10 minute presentation where we wouldn’t have time to discuss the many issues.

 

One major issue is that you should be extending RFC 7684 rather than RFC 3630 and it seems you these app-server selection metrics should be associated with a prefix and NOT a stub link (i.e., the application server address).

 

I’ll try to read it in more depth before IETF 109.

 

Thanks,

Acee

 

From: Linda Dunbar < <mailto:linda.dunbar@futurewei.com> linda.dunbar@futurewei.com>

Date: Monday, November 2, 2020 at 10:12 PM

To: Yingzhen Qu < <mailto:yingzhen.ietf@gmail.com> yingzhen.ietf@gmail.com>gt;, " <mailto:lsr@ietf.org> lsr@ietf.org" < <mailto:lsr@ietf.org> lsr@ietf.org>gt;, " <mailto:lsr-chairs@ietf.org> lsr-chairs@ietf.org" < <mailto:lsr-chairs@ietf.org> lsr-chairs@ietf.org>

Subject: Need 10 minute slot to discuss OSPF extension for 5G Edge Computing (was RE: [Lsr] IETF 109 LSR Presentation Slot Requests

Resent-From: < <mailto:alias-bounces@ietf.org> alias-bounces@ietf.org>

Resent-To: Yingzhen Qu < <mailto:yingzhen.ietf@gmail.com> yingzhen.ietf@gmail.com>gt;, Acee Lindem < <mailto:acee@cisco.com> acee@cisco.com>gt;, Christian Hopps < <mailto:chopps@chopps.org> chopps@chopps.org>

Resent-Date: Monday, November 2, 2020 at 10:12 PM

 

LSR Chairs, YingZhen,

 

Can you give us 10 minute slot to present this new draft:

https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/ <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-dunbar-lsr-5g-edge-compute-ospf-ext%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C83f990f38fe14407efe208d880300245%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637400290992237706%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CooHUjUYe%2BePz9rwBZe0orzPqku%2BoSL%2FrMVVa%2Fl2uIc%3D&reserved=0> 

 

This draft describes an OSPF extension that can distribute the 5G Edge Computing App running status and environment, so that other routers in the 5G Local Data Network can make intelligent decision on optimizing forwarding of flows from UEs. The goal is to improve latency and performance for 5G Edge Computing services.

 

Thank you very much,

 

Linda Dunbar

 

From: Lsr <lsr-bounces@ietf.org <mailto:lsr-bounces@ietf.org> > On Behalf Of Yingzhen Qu

Sent: Monday, October 19, 2020 3:52 PM

To: lsr@ietf.org <mailto:lsr@ietf.org> ; lsr-chairs@ietf.org <mailto:lsr-chairs@ietf.org> 

Subject: [Lsr] IETF 109 LSR Presentation Slot Requests

 

Hi all, 

 

We're now accepting agenda requests for the LSR Working Grouping meeting IETF 109. Please send your requests to  <mailto:lsr-chairs@ietf.org> lsr-chairs@ietf.org indicating draft name, speaker, and desired duration (covering presentation and discussion). 

 

LSR session is scheduled on Monday, Nov 16, 12:00-14:00 ICT.

 

Thanks,

Yingzhen

_______________________________________________

Lsr mailing list

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

https://www.ietf.org/mailman/listinfo/lsr