Request for message handling flow
Can we have, in the ARM or a KB: a description/diagram of the logical route taken by packets from ingress to egress or drop.
Where/how client classification gets done
- are different types of packets handled differently (request, renew, inform, discovery)
- Where/how subnet selection gets done, with and without shared networks
- When/how reservations are found (whether in-pool or global)
We have discussed needing something like this several times and haven't done it because it is difficult - but it would be helpful to support, and also to users.
Do we have a way to test this - generate a request from a specific client, with specified options in the request, and determine the subnet selection and options in the response is correct? If so, maybe describing how that test works might help generate the diagram desired?