RFC 6148 on DHCPv4 Lease Query by Relay Agent Remote ID
rfc-editor@rfc-editor.org Tue, 01 March 2011 02:48 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 189A93A6C80; Mon, 28 Feb 2011 18:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.167
X-Spam-Level:
X-Spam-Status: No, score=-102.167 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UD-YfKZxkz0l; Mon, 28 Feb 2011 18:48:05 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 4E1B23A6C6F; Mon, 28 Feb 2011 18:48:05 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 74DA9E0736; Mon, 28 Feb 2011 18:49:07 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6148 on DHCPv4 Lease Query by Relay Agent Remote ID
From: rfc-editor@rfc-editor.org
Message-Id: <20110301024907.74DA9E0736@rfc-editor.org>
Date: Mon, 28 Feb 2011 18:49:07 -0800
Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 02:48:06 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6148
Title: DHCPv4 Lease Query by Relay
Agent Remote ID
Author: P. Kurapati, R. Desetti,
B. Joshi
Status: Standards Track
Stream: IETF
Date: February 2011
Mailbox: kurapati@juniper.net,
ramakrishnadtv@infosys.com,
bharat_joshi@infosys.com
Pages: 13
Characters: 26185
Updates: RFC4388
I-D Tag: draft-ietf-dhc-leasequery-by-remote-id-09.txt
URL: http://www.rfc-editor.org/rfc/rfc6148.txt
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.
[STANDARDS-TRACK]
This document is a product of the Dynamic Host Configuration Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements. Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC