Re: [dhcwg] Re: one more comment about the lifetime option

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Sat, 04 September 2004 06:26 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27832; Sat, 4 Sep 2004 02:26:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3Txu-0007O8-Pn; Sat, 04 Sep 2004 02:23:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3TuY-0005lm-Dw for dhcwg@megatron.ietf.org; Sat, 04 Sep 2004 02:20:30 -0400
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 CAA27354 for <dhcwg@ietf.org>; Sat, 4 Sep 2004 02:20:29 -0400 (EDT)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3TxI-0002S9-2j for dhcwg@ietf.org; Sat, 04 Sep 2004 02:23:21 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:545c:249b:d371:bb2c]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 7F7291525D; Sat, 4 Sep 2004 15:20:26 +0900 (JST)
Date: Sat, 04 Sep 2004 15:20:27 +0900
Message-ID: <y7vpt521ro4.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp>
To: Stig Venaas <Stig.Venaas@uninett.no>
Subject: Re: [dhcwg] Re: one more comment about the lifetime option
In-Reply-To: <20040903075617.GA22032@sverresborg.uninett.no>
References: <y7vy8jt3u2u.wl@ocean.jinmei.org> <000701c490ea$db453770$6501a8c0@amer.cisco.com> <y7vacw75081.wl@ocean.jinmei.org> <20040903075617.GA22032@sverresborg.uninett.no>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, "'Ted Lemon'" <mellon@nominum.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

>>>>> On Fri, 3 Sep 2004 09:56:17 +0200, 
>>>>> Stig Venaas <Stig.Venaas@uninett.no> said:

>> Ah, okay, I was wrong.  The authentication option is a variable-length
>> option but does not take a sub-option according to RFC3315.
>> 
>> > But in any case, its no big deal to specify that the option is restricted to
>> > the message level.
>> 
>> That's correct.  But at the same time, I believe we all agree that
>> there is no reason to allow the lifetime (or refresh timer) option
>> appearing as a sub-option.

> Yes, I don't mind adding some wording to the fact. It's against the
> whole idea to use it as a sub-option.

> I must say though that I'm a little bit surprised this came up. I'm
> not that into the world of DHCP, but I don't recall seeing specs for
> other options saying this, and I had thought that they should only
> be used as sub-options if specified as such. Or is the idea that in
> general, any option could be used as a sub-option?

I think your understanding is basically correct.  RFC3315 says in
Section 22 that:

   Unless otherwise noted, each option may appear only in the options
   area of a DHCP message and may appear only once.

The term "options area" does not seem to be officially defined in the
RFC, but it should be natural to interpret this to mean areas which
are not a sub-option of a separate option.

But at the same time, the RFC explicitly mentions the default
restriction in some places.  For example, in Section 22.5 it says:

   An IA_TA option may only appear in the options area of a DHCP
   message.

And,

> I think though that the IRT (lifetime) option might appear to make
> sense as a sub-option, while many other options pretty obviously
> don't make sense. So I'm happy to add the wording, just to avoid
> possible misuse.

this is exactly my point.

 I believe it depends on whether we want to avoid possible misuse
 explicitly.  And then it depends on how we asses the possibility of
 the misuse.  Of course, the sense on this may vary among people (so I
 won't push my preference).  But if we recall that we are talking
 about this in the context where we are trying to add a note that a
 single IRT (or lifetime) optin should be common for all possible
 information resources, I personally think it's reasonable to add an
 explicit note here.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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