[dhcwg] EXTENDED Last Call: <draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04.txt> (Client Link-layer Address Option in DHCPv6) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Thu, 14 February 2013 21:39 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2183721F86C0; Thu, 14 Feb 2013 13:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level:
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, 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 abJnIYEYVTOs; Thu, 14 Feb 2013 13:39:48 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144A021F890E; Thu, 14 Feb 2013 13:39:48 -0800 (PST)
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>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130214213948.11955.3082.idtracker@ietfa.amsl.com>
Date: Thu, 14 Feb 2013 13:39:48 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] EXTENDED Last Call: <draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04.txt> (Client Link-layer Address Option in DHCPv6) to Proposed Standard
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2013 21:39:50 -0000
The IESG has received a request from the Dynamic Host Configuration WG (dhc) to consider the following document: - 'Client Link-layer Address Option in DHCPv6' <draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04.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 2013-02-28. 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. Note that this is an extension of the IETF last call that was originally announced on 2013-02-04. The IETF last call has been extended because of IPR disclosure 1710, which was published in reference to draft-halwasia-dhc-dhcpv6-hardware-addr-opt-00.txt. Because draft-halwasia-dhc-dhcpv6-hardware-addr-opt-00.txt is a predecessor to draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04.txt, IPR disclosure 1710 should be considered in this IETF last call. Abstract This document specifies the format and mechanism that is to be used for encoding client link-layer address in DHCPv6 Relay-Forward messages by defining a new DHCPv6 Client Link-layer Address option. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt/ballot/ IPR disclosure 1710 may be relevant to this document.