Last Call: <draft-ietf-dhc-client-id-06.txt> (Client Identifier Option in DHCP Server Replies) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 03 October 2012 20:44 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1167A1F0425; Wed, 3 Oct 2012 13:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.522
X-Spam-Level:
X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJsdDPy9BYgs; Wed, 3 Oct 2012 13:44:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 925A921F84EB; Wed, 3 Oct 2012 13:44:55 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dhc-client-id-06.txt> (Client Identifier Option in DHCP Server Replies) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121003204455.25643.52075.idtracker@ietfa.amsl.com>
Date: Wed, 03 Oct 2012 13:44:55 -0700
Cc: dhcwg@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 03 Oct 2012 20:44:56 -0000
The IESG has received a request from the Dynamic Host Configuration WG (dhc) to consider the following document: - 'Client Identifier Option in DHCP Server Replies' <draft-ietf-dhc-client-id-06.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2012-10-17. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document updates RFC2131 [RFC2131]. The changes to [RFC2131] defined in this draft clarifies the use of 'client identifier' option by the DHCP servers. The clarification addresses the issues arising out of the point specified by [RFC2131] that the server 'MUST NOT' return client identifier' option to the client. Requirements The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-dhc-client-id/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-dhc-client-id/ballot/ No IPR declarations have been submitted directly on this I-D.