On Wed, 9 Jun 2021, Dave Taht wrote:

> … and a meeting with some starlink execs at 11AM today.

Nice!

The solution space you're working on ("one device knows its next-hop speed 
and adjacent device needs to know this") is applicable to for instance 
cable, DSL, PON, wifi etc.

I seem to remember there has been work in BBF to have the BNG know the 
sync-up speed of DSL in order to do proper buffering, what you need to do 
is to come from "the other end".

Would be nice if there was a generic mechanism for this but since several 
of these devices use L2 I think it'd have to be something LLDP like (also 
on L2).

Dave, how often does information regarding rate/scheduler need to be 
distributed from the scheduling node to the node that is trying to not use 
the upstream buffer? I presume this is in the 0.1 to 1s range, because the 
scheduler might change quite frequently and substantially?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se