[bind10-dev] Receptionist's guts

[JINMEI Tatuya / 神明達哉]

At Wed, 13 Mar 2013 09:38:11 +0100,
Michal 'vorner' Vaner <michal.vaner at nic.cz> wrote:

> As asked on the call yesterday, I'm sending what internal data structure and
> logic would the receptionist have.

Thanks, I think we can now move on to creating tickets.

Some quick comments and questions:

- are we going to update all of auth, resolver, xfrout, and ddns so
  that they can use the new internal socket?
- is my understanding correct that the receptionist is optional and
  both the current mode of operations and operation with the
  receptionist will coexist?
- we'll also have to pass the transport protocol (TCP/UDP)
- I'm not so confident about the overflow thing.  It's quite
  complicated, and its rationale (such as about soft vs hard) is not
  really clear to me, whether it's a random idea or has some
  concrete background.  Also, I think we'd basically say for really
  busy servers where such overflow could matter they should go without
  the receptionist, so it's not clear whether we really need
  sophisticated rate control; a naive but simple approach of dropping
  anything when busy may suffice.  A sophisticated flow control may be
  nicer, but I guess we can defer it.
- on a related note, assuming we don't expect an excellent level of
  performance, I don't see much benefit of handling the raw packet
  data.  parsing the header part with libdns++ will be more convenient
  and safer (and that part isn't really that expensive).

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.