BIND 10 #3007: Develop NameChangeRequest class

[BIND 10 Development]

#3007: Develop NameChangeRequest class
-------------------------------------+-------------------------------------
            Reporter:  tmark         |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  dhcp          |  Sprint-DHCP-20130620
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DHCP          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by tmark:

Old description:

> D2 Item# 2.1 Develop NameChangeRequest class:
> Define and implement the object, plus tests for serialization and
> de-serialization.  The class should support the (at least) following
> members:
>     a. FQDN - Fully qualified domain name (specified by the client or
> generated by the DHCP server).
>     b. IP Address - IPv4 or IPv6 address assigned to the lease.
>     c. DHCID - Unique client identifier generated by the DHCP server.
>     c. Type of Change - "Add" if the mapping is new or updated, or
> "Remove" to delete the mapping.
>     d. Forward Change Flag - If true the mapping change should be sent to
> the forward DNS server.
>     e. Reverse Change Flag - If true, the mapping change should be sent
> to the reverse DNS server.
>     f. Lease TTL - The lease duration.
>
>     Issue to resolve: Value to use for TTL?
>         a. Duration of the lease
>         b. Timestamp of Lease Expiration
>
> The initial implementation should support a wire format of JSON. The
> class interface should make it simple to extend or use other formats.

New description:

 D2 Item# 2.1 Develop !NameChangeRequest class:
 Define and implement the object, plus tests for serialization and
 de-serialization.  The class should support the (at least) following
 members:
     a. FQDN - Fully qualified domain name (specified by the client or
 generated by the DHCP server).
     b. IP Address - IPv4 or IPv6 address assigned to the lease.
     c. DHCID - Unique client identifier generated by the DHCP server.
     c. Type of Change - "Add" if the mapping is new or updated, or
 "Remove" to delete the mapping.
     d. Forward Change Flag - If true the mapping change should be sent to
 the forward DNS server.
     e. Reverse Change Flag - If true, the mapping change should be sent to
 the reverse DNS server.
     f. Lease TTL - The lease duration.

     Issue to resolve: Value to use for TTL?
         a. Duration of the lease
         b. Timestamp of Lease Expiration

 The initial implementation should support a wire format of JSON. The class
 interface should make it simple to extend or use other formats.

--

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