# Re: AF\_BUS socket address family

- From: David Miller \<davem@davemloft.net\>
- Date: 2012-07-01 21:45:48 
- List: netdev
- Page: https://ratatoskr.run/netdev/2012/07/3887314
- Thread: https://ratatoskr.run/netdev/2012/06/3886804/t.md

```text
From: Alan Cox <redacted>
Date: Sun, 1 Jul 2012 15:16:59 +0100

>> The issue is that what to do when a receiver goes deaf is a policy
>> issue.
> 
> Something all these protocols alredy recognize and have done for years.
> The real issue for AF_BUS versus the current slow AF_UNIX approach is
> that you really need to know *who* is blocked up.
> 
> That's no different to UDP multicast and needing to know how errored the
> frame.

And the policy on what to do about such UDP multicast errors is in
userspace, which is precisely my point.
```