[Scone] Re: Number of sessions is needed for the SCOPE

[[e-mail]]

Hi Eduard,

Can you please clarify which spec are you referring to? (as there is no “the SCONE specification”)

Thanks.

Cheers,
Med

De : Vasilenko Eduard <vasilenko.eduard=[e-mail]>
Envoyé : vendredi 22 novembre 2024 14:10
À : [e-mail]
Objet : [Scone] Number of sessions is needed for the SCOPE

Hi Experts,
IMHO: you are missing the critical parameter in the SCONE specification: the number of sessions on the bottleneck scheduler (it looks like the scheduler is called “flow policy” in the draft).

Per-flow performance is not possible for hardware routers and switches – it is too expensive, hardware routers are 3x cheaper, switches are 5x cheaper compared to flow-based devices (FW, IPS, DPI, LB, etc).

Per-scheduler performance (possible for routers and switches) is useless without knowing how many flows are sharing it. It is a divider to understand what is possible to push for the particular flow on the host.

Of course, it is a big challenge to how hardware routers or switches would calculate the number of sessions. But better to push the problem out of SCOPE territory.
It would be possible to say: “SCOPE will be ready when the hardware router would be ready”. (if ever)

IMHO: it is better to include “the number of sessions” in the SCOPE specification.

PS: Software routers are typically multi-functional our days (IPS, DPI, and everything else on board), flow-based forwarding is possible.
Moreover, all 3GPP wireless IP forwarding is based on software only – no acceleration has been done for 3GPP.
Unfortunately, fixed broadband is based on BRAS/BNG which is actually a hardware router – it could not be flow-based.

Best Regards
Eduard Vasilenko
Senior Architect
Network Algorithm Laboratory
Tel: [phone]

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.