[dhcwg] ID's: DHCP Discovery Extensions / Interface Information Option

"Rentschler, Markus" <mrentsch@nt.hirschmann.de> Mon, 03 November 2003 10:46 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27055 for <dhcwg-archive@odin.ietf.org>; Mon, 3 Nov 2003 05:46:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGcDm-0005Xy-4z for dhcwg-archive@odin.ietf.org; Mon, 03 Nov 2003 05:46:09 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3Ak6gR021316 for dhcwg-archive@odin.ietf.org; Mon, 3 Nov 2003 05:46:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGcDm-0005Xj-0c for dhcwg-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 05:46:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27012 for <dhcwg-web-archive@ietf.org>; Mon, 3 Nov 2003 05:45:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGcDi-0003YI-00 for dhcwg-web-archive@ietf.org; Mon, 03 Nov 2003 05:46:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGcDh-0003YF-00 for dhcwg-web-archive@ietf.org; Mon, 03 Nov 2003 05:46:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGcDh-0005VE-7l; Mon, 03 Nov 2003 05:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGcD9-0005UQ-0W for dhcwg@optimus.ietf.org; Mon, 03 Nov 2003 05:45:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27006 for <dhcwg@ietf.org>; Mon, 3 Nov 2003 05:45:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGcD5-0003Y2-00 for dhcwg@ietf.org; Mon, 03 Nov 2003 05:45:23 -0500
Received: from nt.hirschmann.de ([149.218.112.4] helo=hirschmann.de) by ietf-mx with esmtp (Exim 4.12) id 1AGcD3-0003W5-00 for dhcwg@ietf.org; Mon, 03 Nov 2003 05:45:21 -0500
Received: from merkur.hirschmann.de ([149.218.20.87]) by gw.hirschmann.de with ESMTP id <119041>; Mon, 3 Nov 2003 11:37:54 +0100
Received: by merkur.hirschmann.de with Internet Mail Service (5.5.2655.55) id <WAPLPW80>; Mon, 3 Nov 2003 11:41:42 +0100
Message-ID: <DD24B3AA7EFE0D47BD09F5809C0D5D8A03A8CB3D@merkur.hirschmann.de>
From: "Rentschler, Markus" <mrentsch@nt.hirschmann.de>
To: dhcwg@ietf.org
Date: Mon, 03 Nov 2003 11:41:33 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C3A1F7.0C32B670"
Subject: [dhcwg] ID's: DHCP Discovery Extensions / Interface Information Option
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Hello DHC-WG,

I seem to have missed the deadline for ID submission, but need some
criticism/feedback on the issues described in the enclosed drafts. Please
read through the documents and let me know your comments.

The abstracts of these drafts are given here:

-- DHCP Discovery Extensions --

   This draft defines simple protocol enhancements to DHCP so that it
   can be used for the following applications:

   - Discovery of clients in the network
   - DHCP server redundancy
   - Server-initiated configuration of clients

   The discovery mechanism described here is built upon and coexists
   with BOOTP according to RFC 1542 and DHCP according to RFC 2131 
   and RFC 3203.
   It allows server-initiated communication to specific or all clients 
   in the network, using the DHCP packet format. Other DHCP servers
   in the network can be provided with information about all
   existing client configurations and will therefore be able to take
   over if the main server fails.

 <<draft-rentschler-dhc-discovery-00.txt>> 



-- DHCP Interface Information Option --

   This draft defines a new option to inform the server about
   the client's physical interface it is connected to.
   This information may be used together with the relay agent 
   information option (RFC 3046) for the purpose of topology 
   recognition.

 <<draft-rentschler-dhc-interface-opt-00.txt>> 



Best Regards,
           Markus Rentschler