BIND 10 #2642: Update DHCP documentation in BIND 10 guide

[BIND 10 Development]

#2642: Update DHCP documentation in BIND 10 guide
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:
                Type:  task          |  stephen
            Priority:  medium        |                       Status:
           Component:                |  reviewing
  documentation                      |                    Milestone:
            Keywords:                |  Sprint-DHCP-20130122
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by tomek):

 * owner:  tomek => stephen


Comment:

 Replying to [comment:7 stephen]:
 > > There are no option examples for DHCPv4. We definitely need some!
 > Awaiting Marcin's input here...
 Let this not block this ticket. Marcin can provide his input on a separate
 ticket.

 > > Does this make sense anymore? bind10 is started as root, and so are
 all its daemons. It was useful remark when b10-dhcp6 was stand-alone.
 > I've removed this, although I think we need to discuss privilege with
 the DNS team: do we use the privileged socket creator to open the
 privileged ports?
 No, we don't.

 > '''Section 18.2'''[[BR]]
 > > Second listing has some values for v6 database name and user, but the
 v4 counterpart does not. I think it would be easier to deploy if we had
 defined some defaults. I understand the dangers of having default password
 set, but still these are early days, so tradeoff for easier deployment
 outweights security concerns.
 > The listing has been changed.  As to a default password, I don't think
 it would be useful: the creation of the MySQL database and authorization
 of the username under which it is accessed is wholly under control of the
 user.  The aim is to get the information in the BIND 10 configuration
 matching that entered when the database and the database user were
 created.
 Ok.

 > > Third bullet suggest an ugly kludge for working around the problems in
 session control. With Marcin's fixes (or bit cleaner workarounds, as the
 underlying issue in session control object are not fixed) in #2637, this
 should be removed.
 > I think this limitation is still here.  Let's not this and check when we
 do the testing.
 Ok.

 > > There is no chapter about libdhcpsrv.
 > I don't think there should be - it is internal to BIND 10 and not
 designed for external use.
 Ok. It makese sense - dhcpsrv can be considered an internal part of our
 daemons.

 It seems that there are things that can be still improved in the
 documentation, but we don't have to do everything in one step. I think the
 ticket is ready for merge.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2642#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development