%% You should probably cite draft-gandhewar-dhc-relay-initiated-release-01 instead of this revision.
@techreport{gandhewar-dhc-relay-initiated-release-00,
    number =    {draft-gandhewar-dhc-relay-initiated-release-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-gandhewar-dhc-relay-initiated-release/00/},
    author =    {Sunil M Gandhewar},
    title =     {{DHCP Relay Initiated Release}},
    pagetotal = 10,
    year =      2015,
    month =     jun,
    day =       29,
    abstract =  {The Dynamic Host Configuration Protocol (DHCP) is initiated by a DHCP client. A DHCP server can force DHCP client to send DHCPRENEW by sending a DHCPFORCERENEW message. There may be multiple DHCP network devices connected in between a DHCP client and a server, each one reserving resources for the DHCP client. There are no DHCP messages that a relay can initiate in order to control the client binding. A DHCP client may not always send a DHCPRELEASE message when it no longer needs the IP address. This document specifies a way to request release message to be initiated by an intermediate DHCP network device, e.g. DHCP relay, on behalf of DHCP client. This helps relinquish network resources sooner than the lease expiration time.},
}