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

Ralph Droms <rdroms@cisco.com> Thu, 10 March 2005 03:00 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 WAA22060 for <dhcwg-web-archive@ietf.org>; Wed, 9 Mar 2005 22:00:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D9Dx9-0001tq-8o for dhcwg-web-archive@ietf.org; Wed, 09 Mar 2005 22:03:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9Dsl-00067t-03; Wed, 09 Mar 2005 21:58:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9Dsj-00067o-Ti for dhcwg@megatron.ietf.org; Wed, 09 Mar 2005 21:58:37 -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 VAA21719 for <dhcwg@ietf.org>; Wed, 9 Mar 2005 21:58:35 -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 1D9DvS-0001qs-Gi for dhcwg@ietf.org; Wed, 09 Mar 2005 22:01:26 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 09 Mar 2005 20:15:49 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,152,1107734400"; d="scan'208"; a="233364575:sNHT20569976"
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 j2A2wPuC016131; Wed, 9 Mar 2005 18:58:26 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn4-712.cisco.com [10.21.82.200]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id APR78771; Wed, 9 Mar 2005 21:58:23 -0500 (EST)
Message-Id: <4.3.2.7.2.20050309215651.02052d28@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 09 Mar 2005 21:58:19 -0500
To: Bernie Volz <volz@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: RE: [dhcwg] RFC2131 - option multiple times - which ones ?
In-Reply-To: <200503100247.APR78347@flask.cisco.com>
References: <20050310022155.GC44497@isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: 'Dhcwg' <dhcwg@ietf.org>
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: e8a67952aa972b528dd04570d58ad8fe

Bernie, David - the third paragraph of section 2.1 in RFC 3046 contains this
text:

    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.

which indicates to me that at most one relay agent option can appear in a
DHCP message.

- Ralph

At 09:47 PM 3/9/2005 -0500, Bernie Volz wrote:
>David:
>
>You're probably correct, but where is this stated? The text in RFC 3046
>implies that there can only be one relay agent option. Section 2.1.1 of RFC
>3046 indicates that only one relay agent option may be added. And, RFC 3396
>doesn't mention relay agent option as being special.
>
>- Bernie
>
> > -----Original Message-----
> > From: David W. Hankins [mailto:David_Hankins@isc.org]
> > Sent: Wednesday, March 09, 2005 9:22 PM
> > To: Bernie Volz
> > Cc: 'Grubmair Peter'; 'Dhcwg'
> > Subject: Re: [dhcwg] RFC2131 - option multiple times - which ones ?
> >
> > 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.
> >
> > --
> > David W. Hankins              "If you don't do it right the
> > first time,
> > Operations Engineer                   you'll just have to do
> > it again."
> > Internet Systems Consortium, Inc.             -- Jack T. Hankins
> >
>
>_______________________________________________
>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