Hi, Linda:

 

From: Linda Dunbar [mailto:[email protected]] 
Sent: Saturday, November 7, 2020 1:27 AM
To: Aijun Wang <[email protected]>; 'Acee Lindem (acee)' 
<[email protected]>; 'Peter Psenak' <[email protected]>; 'Jeff 
Tantsura' <[email protected]>; 'Yingzhen Qu' <[email protected]>; 
[email protected]; [email protected]
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

 

Aijun, 

 

I read through your draft, need to clarify a few things:

 

1.       Is your “Passive Link” same as the “Stub Link”? 

[WAJ] Yes.

2.       Are you suggesting that the “Passive Link” to be advertised less often 
than the regular LSA? 

[WAJ] No. It is same.

 

Thank you, 

 

Linda

 

From: Aijun Wang <[email protected] <mailto:[email protected]> 
> 
Sent: Thursday, November 5, 2020 7:35 PM
To: Linda Dunbar <[email protected] 
<mailto:[email protected]> >; 'Acee Lindem (acee)' <[email protected] 
<mailto:[email protected]> >; 'Peter Psenak' <[email protected] 
<mailto:[email protected]> >; 'Jeff Tantsura' 
<[email protected] <mailto:[email protected]> >; 'Yingzhen Qu' 
<[email protected] <mailto:[email protected]> >; [email protected] 
<mailto:[email protected]> ; [email protected] <mailto:[email protected]> 
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

 

Hi, Linda, Acee, Jeff and Peter:

 

>From this use case, together with another 
>draft(https://datatracker.ietf.org/doc/draft-wang-lsr-passive-interface-attribute/
> 
><https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-wang-lsr-passive-interface-attribute%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7Cf8b544146d184bfe98fa08d881f42cb5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637402233049926010%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=UUGE%2F6VXzQTnAYEqHq8y91zfRlorFitl9wpF5lqiSqI%3D&reserved=0>
> ) that we are proposing and discussing, as in 
>https://mailarchive.ietf.org/arch/msg/lsr/imojDOsS3W3B2H2SbmUT0QKjbxM/ 
><https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Flsr%2FimojDOsS3W3B2H2SbmUT0QKjbxM%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7Cf8b544146d184bfe98fa08d881f42cb5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637402233049926010%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=yYJ1hceIJEGByWaTha6PjowYkoa0Hbsn0Ekup2pRCpk%3D&reserved=0>
> 

It is more convincible to define one new top TLV, for example, Stub-Link TLV, 
to contain your current proposed sub-TLV, and other futures information.

 

The information contained within the Stub-Link TLV, will not participate the 
SPF calculation on each router.  

It is more clear than to put this information associated with the Prefix TLV.

 

 

Best Regards

 

Aijun Wang

China Telecom

 

 

From: [email protected] <mailto:[email protected]>  
[mailto:[email protected]] On Behalf Of Linda Dunbar
Sent: Friday, November 6, 2020 12:04 AM
To: Acee Lindem (acee) <[email protected] <mailto:[email protected]> >; Jeff Tantsura 
<[email protected] <mailto:[email protected]> >; Yingzhen Qu 
<[email protected] <mailto:[email protected]> >; [email protected] 
<mailto:[email protected]> ; [email protected] <mailto:[email protected]> 
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

 

Jeff and Acee, 

 

I understand that RFC8362 has specifies Extended Prefix TLV for IPv6.

 

Since there are two separate RFCs for the Extended Prefix TLV, one for IPv4 and 
another one for IPv6,  I was asking if the Sub-TLVs proposed for 5G Edge 
Computing needs to have two separate drafts: one for IPv4 and another one for 
IPv6?   Or just one draft to describe the extension to both RFCs? 

 

Your guidance is greatly appreciated. 

 

Linda

 

From: Acee Lindem (acee) <[email protected] <mailto:[email protected]> > 
Sent: Wednesday, November 4, 2020 6:42 PM
To: Jeff Tantsura <[email protected] <mailto:[email protected]> >; 
Yingzhen Qu <[email protected] <mailto:[email protected]> >; 
[email protected] <mailto:[email protected]> ; [email protected] 
<mailto:[email protected]> ; Linda Dunbar <[email protected] 
<mailto:[email protected]> >
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 <[email protected] <mailto:[email protected]> >
Date: Wednesday, November 4, 2020 at 6:16 PM
To: Acee Lindem <[email protected] <mailto:[email protected]> >, Yingzhen Qu 
<[email protected] <mailto:[email protected]> >, "[email protected] 
<mailto:[email protected]> " <[email protected] <mailto:[email protected]> >, 
"[email protected] <mailto:[email protected]> " <[email protected] 
<mailto:[email protected]> >, Linda Dunbar <[email protected] 
<mailto:[email protected]> >
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 <[email protected] 
<mailto:[email protected]> >, 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://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%7Cf8b544146d184bfe98fa08d881f42cb5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637402233049936011%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3zom9hRpZxml8ZcHRYSlvT%2B%2B8slMqI4Wkz8i%2Bsq%2F78o%3D&reserved=0>
 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) <[email protected] <mailto:[email protected]> >

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

To: Linda Dunbar <[email protected] 
<mailto:[email protected]> >; Yingzhen Qu <[email protected] 
<mailto:[email protected]> >; [email protected] <mailto:[email protected]> ; 
[email protected] <mailto:[email protected]> 

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:[email protected]> 
[email protected]>

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

To: Yingzhen Qu < <mailto:[email protected]> [email protected]>, " 
<mailto:[email protected]> [email protected]" < <mailto:[email protected]> [email protected]>, " 
<mailto:[email protected]> [email protected]" < 
<mailto:[email protected]> [email protected]>

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:[email protected]> [email protected]>

Resent-To: Yingzhen Qu < <mailto:[email protected]> 
[email protected]>, Acee Lindem < <mailto:[email protected]> 
[email protected]>, Christian Hopps < <mailto:[email protected]> [email protected]>

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%7Cf8b544146d184bfe98fa08d881f42cb5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637402233049946003%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=z51rG6ODVK7sj2xlLkn2utpzw1e0NbXhY%2BO8hDm%2F8hQ%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 <[email protected] <mailto:[email protected]> > On Behalf Of 
Yingzhen Qu

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

To: [email protected] <mailto:[email protected]> ; [email protected] 
<mailto:[email protected]> 

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:[email protected]> 
[email protected] 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

[email protected] <mailto:[email protected]> 

https://www.ietf.org/mailman/listinfo/lsr 
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr&data=04%7C01%7Clinda.dunbar%40futurewei.com%7Cf8b544146d184bfe98fa08d881f42cb5%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637402233049956004%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=s7uVUm1L5QDDsOZF6rZS6qg45fEHepOq8la9IJ4ejJo%3D&reserved=0>
 

_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to