[Srcomp] Additional requirements

["[e-mail]" <[e-mail]>]

Hi，all
Since I joined the maillist late and missed the early discussion of the requirements, I add several additional requirements to the datasheet sent by Weiqiang. Pls be kindely requested to check them.

Thanks
Chongfeng

From: Henderickx, Wim (Nokia - BE/Antwerp)
Date: 2020-08-14 02:59
To: Ron Bonica; Darren Dukes (ddukes); [e-mail]
Subject: Re: [Srcomp] REQ-7-27-SVC-SCALE-00
Why don’t we create 2 requirements.
1 with 20 bit for local significant allocation and a 2nd for 24 bit with global allocation.
 
I believe we should decouple ourselves in req. from the way solutions are proposed.
 
From: Ron Bonica <[e-mail]>
Date: Thursday, 13 August 2020 at 16:14
To: Darren Dukes <[e-mail]>, "Henderickx, Wim (Nokia - BE/Antwerp)" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: RE: REQ-7-27-SVC-SCALE-00
 
Darren,
 
If all of the proposed compression mechanism maintained a strict separation between traffic engineering and services, I would agree with you. But they don’t.
 
                                                      Ron
 
 
 
Juniper Business Use Only
From: Darren Dukes (ddukes) <[e-mail]> 
Sent: Wednesday, August 12, 2020 8:51 AM
To: Henderickx, Wim (Nokia - BE/Antwerp) <[e-mail]>; Ron Bonica <[e-mail]>; [e-mail]
Subject: Re: REQ-7-27-SVC-SCALE-00
 
[External Email. Be cautious of content]
 
Hi Wim and Ron, I'm a bit concerned that over-specification of scale requirements goes beyond SR compression and into general requirements for an SR instantiation and the myriad services it supports.
 
Darren


From: Srcomp <[e-mail]> on behalf of Henderickx, Wim (Nokia - BE/Antwerp) <[e-mail]>
Sent: Wednesday, August 12, 2020 12:02 AM
To: Ron Bonica <[e-mail]>; [e-mail] <[e-mail]>
Subject: Re: [Srcomp] REQ-7-27-SVC-SCALE-00 
 
See if we believe 24 bit is needed let’s do it, but I didn’t want to over specify. Also if we do local significant assignment we have a massive scale even with 20 bit.
If we all believe 24 bit is the way to go I will update the requirement.
 
From: Ron Bonica <[e-mail]>
Date: Tuesday, 11 August 2020 at 16:04
To: "Henderickx, Wim (Nokia - BE/Antwerp)" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: RE: REQ-7-27-SVC-SCALE-00
 
Wim,
 
I don’t know of any deployments that scale larger than 1 million. However, if we want to replace VXLAN, we need to be as capable as VXLAN.
 
                                                                             Ron
 
 
 
Juniper Business Use Only
From: Henderickx, Wim (Nokia - BE/Antwerp) <[e-mail]> 
Sent: Tuesday, August 11, 2020 1:20 AM
To: Ron Bonica <[e-mail]>; [e-mail]
Subject: Re: REQ-7-27-SVC-SCALE-00
 
[External Email. Be cautious of content]
 
I don’t know only use case which comes to 16M so far, I know 1 deployment which is getting close to 1M, this is why I suggested at least 20 bit. If we know deployments that need this scale would be good to know, but if you have local significant usage this would be 20 bit * # devices. So network wide this is massive.
 
From: Ron Bonica <[e-mail]>
Date: Monday, 10 August 2020 at 17:12
To: "Henderickx, Wim (Nokia - BE/Antwerp)" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: RE: REQ-7-27-SVC-SCALE-00
 
Folks,
 
Do we have general consensus that we want the compression mechanism to replace the EVPN VXLAN header? If so, the VNI in the VXLAN header is 24-bits long. So, the Service Scale requirement should be 2**24 (i.e., 16.7 million).
 
                                                                                                                             Ron
 
 
 
 
Juniper Business Use Only
From: Henderickx, Wim (Nokia - BE/Antwerp) <[e-mail]> 
Sent: Tuesday, July 28, 2020 4:41 PM
To: Ron Bonica <[e-mail]>; [e-mail]
Subject: Re: REQ-7-27-SVC-SCALE-00
 
[External Email. Be cautious of content]
 
I said more then >16bit and 1Million was something I know someone deployed. So I would say lets list what we have as a customer requirement somehow 
 
From: Ron Bonica <[e-mail]>
Date: Tuesday, 28 July 2020 at 21:07
To: "Henderickx, Wim (Nokia - BE/Antwerp)" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: RE: REQ-7-27-SVC-SCALE-00
 
Wim,
 
Two to the sixteenth power is only 65k. If you want to support 1 million services, you need 20 bits, not 16.
 
The EVPN VNI is 24-bits long. Given that EVPN is a fastest growing VPN service, I suggest that we may actually need 24 bits.
 
                                                                                                               Ron
 
 
 
Juniper Business Use Only
From: Srcomp <[e-mail]> On Behalf Of Henderickx, Wim (Nokia - BE/Antwerp)
Sent: Monday, July 27, 2020 12:17 PM
To: [e-mail]
Subject: Re: [Srcomp] REQ-7-27-SVC-SCALE-00
 
[External Email. Be cautious of content]
 
 
 
From: "Henderickx, Wim (Nokia - BE/Antwerp)" <[e-mail]>
Date: Monday, 27 July 2020 at 18:07
To: "[e-mail]" <[e-mail]>
Subject: REQ-7-27-SVC-SCALE-00
 
Short Name: Service scale
 
Description: The compression mechanism must support > 1Million services (>16bit)
 
Rationale: Some network operators deploy networks which requires > 500K services.
 
Metric: The compression mechanism allows to work in an environment that support this scalability.