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

[Vasilenko Eduard <[e-mail]>]

The bottleneck is typically in the opposite direction: from BRAS to CPE. QoS is needed here.

CPE could do FQ-CODEL (almost per-flow) in the direction of WIFI - it is enough. CPE is software, very flexible.

Congestion Control is alway interacrtion of CC on hosts with AQM on routers. If router send more information by AQM, then host could do the job better. I did beleive it is the intention, No?
Ed/
From:Watson Ladd <[e-mail]<mailto:[e-mail]>>
To:Vasilenko Eduard <[e-mail]<mailto:[e-mail]>>
Cc:mohamed.boucadair <[e-mail]<mailto:[e-mail]>>;Michael Richardson <[e-mail]<mailto:[e-mail]>>;scone <[e-mail]<mailto:[e-mail]>>
Date:2024-11-25 17:52:55
Subject:Re: [Scone] Re: Number of sessions is needed for the SCOPE

The whole point as I understood it was to express the limits that are
enforced. The flow transits the enforcement point, and whatever
enforcement logic it supports should be expressable.

The other wrinkle is isn't about "bottleneck schedulers" but rather
artificial rate limiting put on to manage overall traffic demand short
of congestion control. So it could be CPE enforcing while the actual
limit is at some uplink. The CPE can obviously devote more resources
to tracking individual flows.

On Mon, Nov 25, 2024 at 2:38 AM Vasilenko Eduard
<vasilenko.eduard=[e-mail]> wrote:
>
> I do have a research project now where we hope to achieve "active flow number" signaling from switches. But it is so much a corner case (with a huge number of assumptions/restrictions) that it does not make sense to discuss.
>
> In the terminology of IETF, flows are available on so-called "middleboxes". Hence, not only the "service side".
> I did look "router", "switch", "middlebox" in the charter - found nothing.
> Hence, developing a solution that would work only for "middleboxes" looks fine - it is compliant with the charter.
> Ed/
> -----Original Message-----
> From: [e-mail] <[e-mail]>
> Sent: Monday, November 25, 2024 09:59
> To: Vasilenko Eduard <[e-mail]>; Michael Richardson <[e-mail]>
> Cc: [e-mail]
> Subject: RE: [Scone] Re: Number of sessions is needed for the SCOPE
>
> Hi Eduard, all,
>
> Not sure how this can be set/implemented by a router (especially that flows are dynamic) nor how this can be useful for hosts.
>
> Also, I'm not aware of any router that provides such knob or a mechanism to export it. Do you have any to share? Thanks.
>
> I'm aware of platforms that deal with some flow-based rate-limiting, but those are more suitable on the service side (and **not relevant** for the scone target). See, e.g., [1]. But even for those, the parameters are similar to what is described in the current blob.
>
> Cheers,
> Med
>
> [1] https://www.juniper.net/documentation/us/en/software/session-smart-router/docs/config_rate_limiting/
>
> > -----Message d'origine-----
> > De : Vasilenko Eduard
> > <vasilenko.eduard=[e-mail]>
> > Envoyé : lundi 25 novembre 2024 07:26
> > À : Michael Richardson <[e-mail]> Cc : [e-mail]
> > Objet : [Scone] Re: Number of sessions is needed for the SCOPE
> >
> >
> > a) is not useful for host,
> > Hence, b)
> > Ed/
> > -----Original Message-----
> > From: Michael Richardson <[e-mail]>
> > Sent: Friday, November 22, 2024 20:05
> > To: Vasilenko Eduard <[e-mail]>
> > Cc: [e-mail]
> > Subject: Re: [Scone] Number of sessions is needed for the SCOPE
> >
> > Vasilenko Eduard <vasilenko.eduard=[e-mail]>
> > wrote:
> >     > IMHO: it is better to include "the number of sessions" in the
> > SCOPE specification.
> >
> > Does the router report:
> >
> > a) I can support N flows of X Mb/s.
> > -or-
> > b) Your flow is the N'th I'm forwarding at X Mb/s.
> >
> >
> > --
> > Michael Richardson <[e-mail]>   . o O ( IPv6 IøT
> > consulting )
> >            Sandelman Software Works Inc, Ottawa and Worldwide
> >
> >
> >
> >
> > _______________________________________________
> > Scone mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> ____________________________________________________________________________________________________________
> 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.
> _______________________________________________
> Scone mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]



--
Astra mortemque praestare gradatim