DHCPv4 Leasequery by relay agent remote ID
draft-kurapati-dhc-leasequery-by-remote-id-01

Document Type Replaced Internet-Draft (individual)
Authors Bharat Joshi  , D.T.V. Rao  , Pavan Kurapati 
Last updated 2008-06-16
Replaced by RFC 6148
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dhc-leasequery-by-remote-id
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kurapati-dhc-leasequery-by-remote-id-01.txt

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.

Authors

Bharat Joshi (bharat_joshi@infosys.com)
D.T.V. Rao (ramakrishnadtv@infosys.com)
Pavan Kurapati (pavan_kurapati@infosys.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)