%% You should probably cite rfc8415 instead of this I-D.
@techreport{ietf-dhc-rfc3315bis-08,
    number =    {draft-ietf-dhc-rfc3315bis-08},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-dhc-rfc3315bis/08/},
    author =    {Tomek Mrugalski and Marcin Siodelski and Bernie Volz and Andrew Yourtchenko and Michael Richardson and Sheng Jiang and Ted Lemon and Timothy Winters},
    title =     {{Dynamic Host Configuration Protocol for IPv6 (DHCPv6) bis}},
    pagetotal = 139,
    year =      2017,
    month =     may,
    day =       9,
    abstract =  {This document describes the Dynamic Host Configuration Protocol for IPv6 (DHCPv6): an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly, or in combination with stateful assignment of one or more IPv6 addresses and/or IPv6 prefixes. DHCPv6 can operate either in place of or in addition to stateless address autoconfiguration (SLAAC). This document updates the text from RFC3315, the original DHCPv6 specification, and incorporates prefix delegation (RFC3633), stateless DHCPv6 (RFC3736), an option to specify an upper bound for how long a client should wait before refreshing information (RFC4242), a mechanism for throttling DHCPv6 clients when DHCPv6 service is not available (RFC7083), and clarifies the interactions between modes of operation (RFC7550). As such, this document obsoletes RFC3315, RFC3633, RFC3736, RFC4242, RFC7083, and RFC7550.},
}