Mixnet: Packet delay in mix node #49
Conversation
youngjoon-lee
force-pushed
the
mixnode-delay
branch
from
787d63c
to
6a849c4
Compare
| def start( | ||
| self, | ||
| delay_rate_per_min: int, | ||
| inbound_socket: PacketQueue, | ||
| outbound_socket: PacketPayloadQueue, | ||
| ) -> MixNodeRunner: | ||
| thread = MixNodeRunner( | ||
| self.encryption_private_key, | ||
| delay_rate_per_min, | ||
| inbound_socket, | ||
| outbound_socket, | ||
| ) | ||
| thread.daemon = True | ||
| thread.start() | ||
| return thread |
There was a problem hiding this comment.
Nitpick: could this be async instead?
There was a problem hiding this comment.
Yes, we can use async, but I'm thinking if it would be not readable for someone who is not familar with async programming.
Also in previous PRs I remember to see some async code, we should choose one style
I haven't used async code in this repo. But, let me translate this into async. If it doesn't look complicated, we can go with async because it's much easier to approximate M/M/∞ queue using async rather than sync.
There was a problem hiding this comment.
I haven't used async code in this repo. But, hm, let me translate this into async. If it doesn't look complicated, we can go with async because it's much easier to approximate M/M/∞ queue using async rather than sync.
It is not necessary!, we can go ahead with this.
This PR covers the specification of packet delay in mix nodes: https://www.notion.so/Mixnet-Specification-807b624444a54a4b88afa1cc80e100c2?pvs=4#15ccbb03a44f42658ea67a33527ecea2.
In summary,$\lambda$ , the mix node should be implementation to approximate a M/M/∞ queue with packet delays that follow an exponential distribution $\mu$ . With this setup, the packet emission rate of a mix node must be $\lambda$ , and the mean number of packets being processed by a mix node at any time must be $\lambda/\mu$ .
assuming that the packet receiving rate of a mix node follows a Poisson distribution
A unit test checks these properties.