3 ms·

It's implied that the block is ONLY for traffic TO A FROM B; via R (router) (with R having the chance to aggregate? Maybe based on owning delivery paths that ar

It's implied that the block is ONLY for traffic TO A FROM B; via R (router) (with R having the chance to aggregate? Maybe based on owning delivery paths that are valid?). Full quote: "- Routers will accept a "shut up" request. If A wants to block B, it sends to a router on the path, the router pings A to validate the source, and then blocks traffic from B to A for a few minutes. This also contains DDOS attacks. Routers can forward "shut up" requests to the next router in the path, for further containment."

solatic 5y ago
This is slightly disingenuous. If I'm a router manufacturer, and there's a protocol that will tell me "peers such-and-such are troublemakers", and I get twenty such notifications from downstream that peer Foo is being a troublemaker, then I can automatically block all traffic from peer Foo (forget about what the protocol actually intended) and actually sell that as a security feature.