%% You should probably cite draft-ietf-dhc-leasequery-by-remote-id instead of this I-D.
@techreport{kurapati-dhc-leasequery-by-remote-id-01,
    number =    {draft-kurapati-dhc-leasequery-by-remote-id-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kurapati-dhc-leasequery-by-remote-id/01/},
    author =    {Bharat Joshi and D.T.V. Ramakrishna Rao and Pavan Kurapati},
    title =     {{DHCPv4 Leasequery by relay agent remote ID}},
    pagetotal = 26,
    year =      2008,
    month =     jun,
    day =       16,
    abstract =  {Some Relay Agents extract lease information from the DHCP message exchanged between the client and DHCP server. This lease information is used by relay agents for various purposes like antispoofing, prevention of flooding. RFC 4388 defines a mechanism for relay agents to retrieve the lease information from the DHCP server as and when this information is lost. Existing leasequery mechanism is data driven which means that a relay agent can initiate the leasequery only when it starts receiving data from/to the clients. In certain scenarios, this model is not scalable. This document first looks at issues in existing mechanism and then proposes a new query type, query by remote ID, to address these issues.},
}