RE: [dhcwg] RFC2131 - option multiple times - which ones ?

"Bernie Volz" <volz@cisco.com> Fri, 11 March 2005 16:36 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 LAA11928 for <dhcwg-web-archive@ietf.org>; Fri, 11 Mar 2005 11:36:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9nAT-0004kb-QC for dhcwg-web-archive@ietf.org; Fri, 11 Mar 2005 11:39:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9n59-0001y5-Rs; Fri, 11 Mar 2005 11:33:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9n58-0001x8-EK for dhcwg@megatron.ietf.org; Fri, 11 Mar 2005 11:33:46 -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 LAA11714 for <dhcwg@ietf.org>; Fri, 11 Mar 2005 11:33:44 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9n89-0004cy-VJ for dhcwg@ietf.org; Fri, 11 Mar 2005 11:36:55 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 11 Mar 2005 09:50:45 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,157,1107734400"; d="scan'208"; a="233999128:sNHT21530700"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j2BGX3uC011445; Fri, 11 Mar 2005 08:33:04 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-2-38.cisco.com [10.86.242.38]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id APT02043; Fri, 11 Mar 2005 11:33:02 -0500 (EST)
Message-Id: <200503111633.APT02043@flask.cisco.com>
From: Bernie Volz <volz@cisco.com>
To: 'Grubmair Peter' <peter.grubmair@siemens.com>, 'Dhcwg' <dhcwg@ietf.org>
Subject: RE: [dhcwg] RFC2131 - option multiple times - which ones ?
Date: Fri, 11 Mar 2005 11:33:02 -0500
Organization: Cisco
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <4D50D5110555D5119F270800062B41650532AD00@viee10pa.erd.siemens.at>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcUmGxxCC/Dga+YrTdK80BrxzRJgEwAPFvYA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
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: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit

Don't forget RFC 3396:

Abstract

   This document specifies the processing rules for Dynamic Host
   Configuration Protocol (DHCPv4) options that appear multiple times in
   the same message.  Multiple instances of the same option are
   generated when an option exceeds 255 octets in size (the maximum size
   of a single option) or when an option needs to be split apart in
   order to take advantage of DHCP option overloading.  When multiple
   instances of the same option appear in the options, file and/or sname
   fields in a DHCP packet, the contents of these options are
   concatenated together to form a single option prior to processing.


There are no hints in 2131/2 about which options may or may not be "split".

The bottom line is avoid splitting options unless you have an explicit need,
such as outlined above in the 3396 abstract.

- Bernie



> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
> On Behalf Of Grubmair Peter
> Sent: Friday, March 11, 2005 4:12 AM
> To: Dhcwg (dhcwg@ietf.org)
> Subject: [dhcwg] RFC2131 - option multiple times - which ones ?
> 
>  Hi,
> Thank you for your replies.
> My question was much simpler:
>  RFC2131 says:
> 
>    The values to be passed in an 'option' tag may be too long 
> to fit in
>    the 255 octets available to a single option (e.g., a list 
> of routers
>    in a 'router' option [21]).  Options may appear only once, unless
>    otherwise specified in the options document.  The client 
> concatenates
>    the values of multiple instances of the same option into a single
>    parameter list for configuration.
> 
> I interpreted it like this:
>   The rule is, that a specific option may appear only once in
>   a dhcp message.
>   The exception from this rule is, that the option document 
> (RFC2132 or
> other)
>   tells , that the option may appear multiple times.
>   Then the multiple instances of the option have to be 
> concatenated into
>   one instance before interpretation.
> 
>   So I am missing in RFC2131 hints, which option may appear 
> multiple times
> and
>   therefore have to be concatenated during reception(e.g. 
> router option ?)
> 
>   I think all options using charackter strings or lists (of 
> ip addresses)
> may
>   be split during send and have to be concatenated during reception
>  , but RFC2132 tells nothing about this.
> 
> Best regards
>   Peter
> 
>   
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg