BIND 10 #2657: BIND10 Guide update: DHCPv6 options

[BIND 10 Development]

#2657: BIND10 Guide update: DHCPv6 options
-------------------------------------+-------------------------------------
            Reporter:  tomek         |                        Owner:
                Type:  task          |  marcin
            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 stephen):

 * owner:  stephen => marcin


Comment:

 Reviewed commit 1e2111996aa44a583fcdf0997a6aa170542f3ea2.

 I've made a number of edits - correcting typos etc, but also rewriting
 some paragraphs to make them (what I think) is clearer.  I've concentrated
 on the DHCPv4 sections, but some changes may need to be propagated to the
 V6 part of the guide.

 In addition, there are several issues:

 '''Table 17.1'''[[BR]]
 The "Array" field of the "routers" (code 3) line was empty.  I assumed
 that "routers" is an array, so have filled it in as "true".

 '''Section 17.4'''
 I've altered the text a bit here.  However, missing in the description of
 the first set of commands is the meaning of the files "array", "record-
 types" and "encapsulate".  Even if you say they should be left blank, they
 should be mentioned.

 '''Section 17.5'''[[BR]]
 There seems to be confusion between the name "vendor-encapsulated-options"
 and "vendor-ops" in the third example (Although I've modified the text,
 the name needs to be sorted out.)

 We also need to explain here why we are using this space (i.e. that we are
 talking about sub-options conveyed in a vendor option.)

 I've put what I think is the explanation for setting a value for option
 43.  This needs to be check.



 '''17.6 Nested DHCPv4 options (custom option spaces)'''[[BR]]
 The first paragraph here confuses me - if we need to define a vendor space
 so that we can use a new numbering scheme for options, what did we do in
 the last section (where we used vendor-encapsulated options)?

 When we define the DHCPv4 option "container" with code 222, the example
 sets the data type as uint16.  Is this correct?

 I've added a paragraph to the end of this section stating that the dummy
 values set for "container" are ignored.  Is this correct?  And will this
 restriction be removed in the future (i.e. should we add a "note"
 element?).

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