[dhcwg] Conflicting information regarding DHCP options 82 and 83.
Van Aken Dirk <VanAkenD@thmulti.com> Tue, 08 October 2002 21:00 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00781 for <dhcwg-archive@odin.ietf.org>; Tue, 8 Oct 2002 17:00:26 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g98L26Z30922 for dhcwg-archive@odin.ietf.org; Tue, 8 Oct 2002 17:02:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98L26v30919 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 8 Oct 2002 17:02:06 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00764 for <dhcwg-web-archive@ietf.org>; Tue, 8 Oct 2002 16:59:55 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Kxrv30225; Tue, 8 Oct 2002 16:59:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g978S7v04198 for <dhcwg@optimus.ietf.org>; Mon, 7 Oct 2002 04:28:07 -0400
Received: from ns1.thmulti.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10485 for <dhcwg@ietf.org>; Mon, 7 Oct 2002 04:25:47 -0400 (EDT)
Received: from smtprelay2.thmulti.com (smtprelay2 [141.11.195.242]) by ns1.thmulti.com (8.9.3/8.9.1) with ESMTP id KAA27758 for <dhcwg@ietf.org>; Mon, 7 Oct 2002 10:27:45 +0200 (MET DST)
Received: from parexch3.paris.thmulti.com (localhost [127.0.0.1]) by smtprelay2.thmulti.com (8.9.3/8.9.1) with ESMTP id KAA01182 for <dhcwg@ietf.org>; Mon, 7 Oct 2002 10:27:44 +0200 (MET DST)
Received: by parexch3 with Internet Mail Service (5.5.2653.19) id <SYZH5SL5>; Mon, 7 Oct 2002 10:27:44 +0200
Message-ID: <421CB3B9B2D2F645B548D213C0A90E5583F8B9@edgmsmsg01.eu.thmulti.com>
From: Van Aken Dirk <VanAkenD@thmulti.com>
To: "'dhcwg@ietf.org'" <dhcwg@ietf.org>
Cc: Dedecker Hans <DedeckerH@thmulti.com>, Dekeyser Miek <DekeyserM@thmulti.com>
Date: Mon, 07 Oct 2002 10:27:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [dhcwg] Conflicting information regarding DHCP options 82 and 83.
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 DHCP Working Group, I have some conflicting information regarding the DHCP options defined below. i.e. On the IANA bootp-dhcp parameter list ( http://www.iana.org/assignments/bootp-dhcp-parameters ) I see the following options: 82 Agent Circuit ID N Agent Circuit ID 83 Agent Remote ID N Agent Remote ID On the other hand RFC3046 mentions the following": >>>> 2.0 Relay Agent Information Option This document defines a new DHCP Option called the Relay Agent Information Option. It is a "container" option for specific agent- supplied sub-options. The format of the Relay Agent Information option is: Code Len Agent Information Field +------+------+------+------+------+------+--...-+------+ | 82 | N | i1 | i2 | i3 | i4 | | iN | +------+------+------+------+------+------+--...-+------+ The length N gives the total number of octets in the Agent Information Field. The Agent Information field consists of a sequence of SubOpt/Length/Value tuples for each sub-option, encoded in the following manner: SubOpt Len Sub-option Value +------+------+------+------+------+------+--...-+------+ | 1 | N | s1 | s2 | s3 | s4 | | sN | +------+------+------+------+------+------+--...-+------+ SubOpt Len Sub-option Value +------+------+------+------+------+------+--...-+------+ | 2 | N | i1 | i2 | i3 | i4 | | iN | +------+------+------+------+------+------+--...-+------+ No "pad" sub-option is defined, and the Information field shall NOT be terminated with a 255 sub-option. The length N of the DHCP Agent Information Option shall include all bytes of the sub-option code/length/value tuples. Since at least one sub-option must be defined, the minimum Relay Agent Information length is two (2). The length N of the sub-options shall be the number of octets in only that sub-option's value field. A sub-option length may be zero. The sub-options need not appear in sub-option code order. The initial assignment of DHCP Relay Agent Sub-options is as follows: DHCP Agent Sub-Option Description Sub-option Code --------------- ---------------------- 1 Agent Circuit ID Sub-option 2 Agent Remote ID Sub-option >>>> So I wonder now if DHCP option 82 refers to the DHCP Relay Information option for which there are defined two sub-options (1: Agent Circuit ID Sub-option and 2: Agent Remote ID Sub-option"). Or do I misunderstand something here ? Thanks in advance - Dirk Dirk Van Aken THOMSON multimedia Broadband Belgium NV System Architect Prins Boudewijnlaan 47, Tel. : 03/443.65.08 2650 Edegem Fax.: 03/443.66.32 Belgium vanakend@thmulti.com _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Conflicting information regarding DHCP op… Van Aken Dirk
- RE: [dhcwg] Conflicting information regarding DHC… Kostur, Andre
- RE: [dhcwg] Conflicting information regarding DHC… Woundy, Richard
- RE: [dhcwg] Conflicting information regarding DHC… John Schnizlein
- RE: [dhcwg] Conflicting information regarding DHC… Bernie Volz (EUD)
- RE: [dhcwg] Conflicting information regarding DHC… Ralph Droms
- RE: [dhcwg] Conflicting information regarding DHC… Bernie Volz (EUD)