DHCPv4 Lease Query by Relay Agent Remote ID

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>,
    dhc mailing list <dhcwg@ietf.org>,
    dhc chair <dhc-chairs@tools.ietf.org>
Subject: Protocol Action: 'DHCPv4 lease query by Relay Agent Remote ID' to Proposed Standard (draft-ietf-dhc-leasequery-by-remote-id-09.txt)

The IESG has approved the following document:
- 'DHCPv4 lease query by Relay Agent Remote ID'
  (draft-ietf-dhc-leasequery-by-remote-id-09.txt) as a Proposed Standard

This document is the product of the Dynamic Host Configuration Working

The IESG contact persons are Ralph Droms and Jari Arkko.

A URL of this Internet Draft is:

Technical Summary

   This document describes an extension to the DHCPLEASEQUERY exchange
   described in RFC4388.  The extension allows the querying agent to
   immediately refresh its cache after a reboot using information that
   is available to it (the remote id) rather than requiring it to make
   LEASEQUERY requests as a result of information gleaned from traffic
   over time.

Working Group Summary

   This document appeared in the working group at the beginning of
   2008.  There has been substantial review of this document.

Document Quality

   The document has undergone careful review, and the working group is
   satisfied with its quality.


   The document shepherd is Ted Lemon <mellon@nominum.com>.  Tthe
   responsible A-D is Ralph Droms <rdroms.ietf@gmail.com>.

RFC Editor Note

Please revise section 6, "Security Considerations," as follows:


   This document does not introduce any new security concerns beyond
   those specified in the original lease query protocol RFC 4388
   [RFC4388] specifications.


   This document inherits the security concerns present in the
   original lease query protocol RFC 4388 [RFC4388] specifications.

   This specification introduces one additional issue, beyond those
   described in RFC 4388. A query by remote-id will result in the
   server replying with a consolidated lease binding information. 
   Such a query, if done from an unauthorized source may lead to
   leak of lease binding information. It is critical to deploy
   authentication techniques mentioned in RFC 3118 to prevent such
   unauthorized lease queries.