DHCPv4 Lease Query by Relay Agent Remote ID
RFC 6148
| Document | Type |
RFC - Proposed Standard
(February 2011; No errata)
Updates RFC 4388
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-kurapati-dhc-leasequery-by-remote-id | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6148 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ralph Droms | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) P. Kurapati
Request for Comments: 6148 Juniper Networks
Updates: 4388 R. Desetti
Category: Standards Track B. Joshi
ISSN: 2070-1721 Infosys Technologies Ltd.
February 2011
DHCPv4 Lease Query by Relay Agent Remote ID
Abstract
Some relay agents extract lease information from the DHCP messages
exchanged between the client and DHCP server. This lease information
is used by relay agents for various purposes like antispoofing and
prevention of flooding. RFC 4388 defines a mechanism for relay
agents to retrieve the lease information from the DHCP server when
this information is lost. The existing lease query mechanism is
data-driven, which means that a relay agent can initiate the lease
query only when it starts receiving data to and from the clients. In
certain scenarios, this model is not scalable. This document first
looks at issues in the existing mechanism and then proposes a new
query type, query by Remote ID, to address these issues.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6148.
Kurapati, et al. Standards Track [Page 1]
RFC 6148 Query by Remote ID February 2011
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Kurapati, et al. Standards Track [Page 2]
RFC 6148 Query by Remote ID February 2011
Table of Contents
1. Introduction ....................................................3
2. Terminology .....................................................4
3. Motivation ......................................................6
4. Protocol Details ................................................7
4.1. Sending the DHCPLEASEQUERY Message .........................7
4.2. Responding to the DHCPLEASEQUERY Message ...................8
4.3. Building a DHCPLEASEACTIVE or DHCPLEASEUNKNOWN Message .....8
4.4. Determining the IP Address to Be Used in Response ..........9
4.5. Sending a DHCPLEASEACTIVE or DHCPLEASEUNKNOWN Message ......9
4.6. Receiving a DHCPLEASEACTIVE or DHCPLEASEUNKNOWN Message ....9
4.7. Receiving No Response to the DHCPLEASEQUERY Message .......10
4.8. Lease-Binding Data Storage Requirements ...................10
4.9. Using the DHCPLEASEQUERY Message with Multiple
DHCP Servers ..............................................10
5. RFC 4388 Considerations ........................................11
6. Security Considerations ........................................11
7. Acknowledgments ................................................11
8. References .....................................................12
8.1. Normative References ......................................12
8.2. Informative References ....................................12
Show full document text