Protocol Action: 'DHCPv4 Relay Agent Flags Suboption' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Mon, 25 June 2007 20:10 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2utJ-0000JX-7C; Mon, 25 Jun 2007 16:10:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I2utG-00008q-Sa; Mon, 25 Jun 2007 16:10:26 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2utG-0003fu-Hh; Mon, 25 Jun 2007 16:10:26 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5947C26E72; Mon, 25 Jun 2007 20:10:26 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I2utG-0006uM-8h; Mon, 25 Jun 2007 16:10:26 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I2utG-0006uM-8h@stiedprstage1.ietf.org>
Date: Mon, 25 Jun 2007 16:10:26 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <dhc-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, iana@iana.org, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'DHCPv4 Relay Agent Flags Suboption' to Proposed Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
The IESG has approved the following document: - 'DHCPv4 Relay Agent Flags Suboption ' <draft-ietf-dhc-relay-agent-flags-03.txt> as a Proposed Standard This document is the product of the Dynamic Host Configuration Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-agent-flags-03.txt Technical Summary The document specifies a relay agent suboption that a relay agent must include in the relay agent information option. The suboption contains flags that an agent can use to provide the server information about a client that would otherwise not be available to the server. This document also specifies one flag for this option to tell the server whether the client messages was sent as unicast or broadcast. This flag is useful when server override as specified in draft-ietf-dhc-server-override-04 is used. Working Group Summary An issue with server override and server not being able to know whether the client message was unicast or broadcast (to distinguish between renew and rebind) was brought up in response to IETF last call of draft-ietf-dhc-server-override-03 in February 2006. After discussions in the wg in February and March it was concluded that some relay agent sub-option was needed for this. This draft was adopted as a wg item after verifying consensus on the wg mailing list in June 2006. WGLC was done in September 2006. Several people supported this document and none were against. There were some editorial comments. This new revision has been changed to accomodate those comments. Protocol Quality The protocol specified in this document specifies a new DHCPv4 relay agent suboption. The specification of this protocol is pretty simple, and should be trivial to implement. Jari Arkko has reviewed this specification for the IESG. Thomas Narten has reviewed this specification for the IP Directorate. Note to RFC Editor Please expand the acronym DHCP on its first use in the title and in the abstract. In the last line of the first paragraph of the Introduction, the period should go after the references: OLD: DHCP Server. [RFC2131] [RFC2132] [RFC3046] NEW: DHCP Server [RFC2131] [RFC2132] [RFC3046]. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce