@techreport{itsumo-drcp-01,
    number =    {draft-itsumo-drcp-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-itsumo-drcp/01/},
    author =    {Anthony McAuley and Sunil H. Madhani and Dr. Yasuro Shobatake},
    title =     {{Dynamic Registration and Configuration Protocol (DRCP)}},
    pagetotal = 15,
    year =      2000,
    month =     jul,
    day =       24,
    abstract =  {The Dynamic Host Configuration Protocol (DHCP) provides a framework for passing configuration information to hosts {[}DHC{]}. DHCP was, however, designed for hosts on a fixed LAN, not for nodes roaming among commercial wireless networks. A Mobile IP {[}MIP{]} Foreign Agent gives some powerful plug and play capability for roaming hosts, especially when combined with some recent proposals {[}e.g., MIPA, MIPC, MIPD, MIPN, HAW, CEL, TIA{]}. Mobile IP functionality, however is not always needed and for some dynamic networks it may be undesirable to use Foreign Agents. This draft proposes a lightweight dynamic configuration protocol, called the Dynamic Registration and Configuration Protocol (DRCP). DRCP borrows heavily from DHCP and can switch to using DHCP protocol if only DHCP servers are present in the network; but adds features critical to roaming users. Most importantly, DRCP allows rapid configuration by moving address consistency checking from the critical path. Other new features allow: a) clients to know when to get a new address independent of the layer-2 access technology, b) efficient use of scarce wireless bandwidth, c) clients to be routers, d) dynamic addition or deletion of address pools to any DRCP node, and e) message exchange without broadcast.},
}