Re: [dhcwg] RFC2131 - option multiple times - which ones ?
John Schnizlein <jschnizl@cisco.com> Thu, 10 March 2005 02:58 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21667 for <dhcwg-web-archive@ietf.org>; Wed, 9 Mar 2005 21:58:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9Dv2-0001pH-W7 for dhcwg-web-archive@ietf.org; Wed, 09 Mar 2005 22:01:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9Dq4-0005yD-BC; Wed, 09 Mar 2005 21:55:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9Dq2-0005y8-VR for dhcwg@megatron.ietf.org; Wed, 09 Mar 2005 21:55:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21408 for <dhcwg@ietf.org>; Wed, 9 Mar 2005 21:55:48 -0500 (EST)
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9Dsl-0001l8-DN for dhcwg@ietf.org; Wed, 09 Mar 2005 21:58:39 -0500
Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 10 Mar 2005 04:16:53 +0100
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from [130.129.133.152] (che-vpn-cluster-2-142.cisco.com [10.86.242.142]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j2A2talu029531; Thu, 10 Mar 2005 03:55:37 +0100 (MET)
In-Reply-To: <20050310022155.GC44497@isc.org>
References: <4D50D5110555D5119F270800062B41650532ACFE@viee10pa.erd.siemens.at> <200503092245.APR63243@flask.cisco.com> <20050310022155.GC44497@isc.org>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <BAF3E74D-910F-11D9-BF03-00112473A260@cisco.com>
Content-Transfer-Encoding: 7bit
From: John Schnizlein <jschnizl@cisco.com>
Subject: Re: [dhcwg] RFC2131 - option multiple times - which ones ?
Date: Wed, 09 Mar 2005 20:54:33 -0600
To: "David W. Hankins" <David_Hankins@isc.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: 'Dhcwg' <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
I thought it was clear that the relay-agent information option could occur at most once. Where is the specification that the relay-agent information option can appear multiple times? Any such specification would seem to conflict with the following excerpts from RFC 3046. 2.1 Agent Operation ... A DHCP relay agent adding a Relay Agent Information field SHALL add it as the last option (but before 'End Option' 255, if present) in the DHCP options field of any recognized BOOTP or DHCP packet forwarded from a client to a server. ... A trusted circuit may contain a trusted downstream (closer to client) network element (bridge) between the relay agent and the client that MAY add a relay agent option but not set the giaddr field. In this case, the relay agent does NOT add a "second" relay agent option, but forwards the DHCP packet per normal DHCP relay agent operations, setting the giaddr field as it deems appropriate. On Mar 9, 2005, at 8:21 PM, David W. Hankins wrote: > On Wed, Mar 09, 2005 at 05:45:39PM -0500, Bernie Volz wrote: >> The idea was that MAYBE in the future, options might be defined that >> can >> appear multiple times and would not be concatented, but that hasn't >> been the >> case. > > except for the relay agent option, which can appear multiple times and > not > be concatenated. it's also a special case in other ways, which is why > it > can get away with that. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] RFC2131 - option multiple times - which o… Grubmair Peter
- RE: [dhcwg] RFC2131 - option multiple times - whi… Bernie Volz
- Re: [dhcwg] RFC2131 - option multiple times - whi… David W. Hankins
- RE: [dhcwg] RFC2131 - option multiple times - whi… Bernie Volz
- Re: [dhcwg] RFC2131 - option multiple times - whi… John Schnizlein
- RE: [dhcwg] RFC2131 - option multiple times - whi… Ralph Droms
- Re: [dhcwg] RFC2131 - option multiple times - whi… David W. Hankins
- [dhcwg] RFC2131 - option multiple times - which o… Grubmair Peter
- RE: [dhcwg] RFC2131 - option multiple times - whi… Bernie Volz
- Re: [dhcwg] RFC2131 - option multiple times - whi… David W. Hankins
- Re: [dhcwg] RFC2131 - option multiple times - whi… Ted Lemon