Re: FW: [dhcwg] co-existence of temp and normal addresses
Thomas Narten <narten@us.ibm.com> Mon, 08 April 2002 18:37 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02176 for <dhcwg-archive@odin.ietf.org>; Mon, 8 Apr 2002 14:37:06 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA28712 for dhcwg-archive@odin.ietf.org; Mon, 8 Apr 2002 14:37:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24995; Mon, 8 Apr 2002 13:53:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24973 for <dhcwg@ns.ietf.org>; Mon, 8 Apr 2002 13:53:56 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (cm058.254.234.24.lvcm.com [24.234.254.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01166 for <dhcwg@ietf.org>; Mon, 8 Apr 2002 13:53:53 -0400 (EDT)
Received: from cichlid.adsl.duke.edu (narten@localhost) by cichlid.adsl.duke.edu (8.11.6/8.11.6) with ESMTP id g38E7vq05345; Mon, 8 Apr 2002 07:07:57 -0700
Message-Id: <200204081407.g38E7vq05345@cichlid.adsl.duke.edu>
To: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
cc: vijayak@india.hp.com, dhcwg@ietf.org
Subject: Re: FW: [dhcwg] co-existence of temp and normal addresses
In-Reply-To: Message from "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> of "Sun, 07 Apr 2002 22:35:58 CDT." <66F66129A77AD411B76200508B65AC69B4D1CA@EAMBUNT705>
Date: Mon, 08 Apr 2002 07:07:57 -0700
From: Thomas Narten <narten@us.ibm.com>
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
> Though I hate to do it because it reopens the discussions, if we > consider anything we shouldn't add more IA types. Instead, we should > redesign the IA option slightly and add a type field. The type field > (8 bit?) could have the following values: > 0 - "Normal" addresses > 1 - "Temporary" addresses I think these two may make sense. The reason is that temporary addresses are different than other addresses in *how* the client uses them. A client may want to use several at a time, or just one. It may want to extend the lease of one particular one (if the application continues to use it), etc. That is, temporary addresses really do have the potential for being used in application-specific manners. As an example (not that I necessarily agree with it), when temporary addresses were designed in the IPNg WG, there were some people that thought it should be possible to have a new address created whenever a new application started. Allowing the client to ask for "yet another new temporary address" (as opposed to "give me the temporary addresses I'm supposed to have")) would support this. > 2 - "DSTM" addresses (this replaces the DSTM option) > ... I can see the benfit here. Having a type makes sense in cases where identifying the type of address (i.e, how it will be used) is necessary to decide how to allocate and use it. Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- RE: [dhcwg] Changes to remove "client-link-local-… Bernie Volz (EUD)
- RE: [dhcwg] Changes to remove "client-link-local-… Bernie Volz (EUD)
- RE: [dhcwg] Changes to remove "client-link-local-… Bernie Volz (EUD)
- Re: [dhcwg] Changes to remove "client-link-local-… Josh Littlefield
- RE: [dhcwg] Changes to remove "client-link-local-… Ralph Droms
- RE: [dhcwg] Changes to remove "client-link-local-… Bernie Volz (EUD)
- Re: [dhcwg] Changes to remove "client-link-local-… Ralph Droms
- RE: [dhcwg] Changes to remove "client-link-local-… Bernie Volz (EUD)
- Re: [dhcwg] Changes to remove "client-link-local-… Ted Lemon
- RE: [dhcwg] Changes to remove "client-link-local-… Bernie Volz (EUD)
- RE: [dhcwg] Changes to remove "client-link-local-… Bernie Volz (EUD)
- Re: [dhcwg] Changes to remove "client-link-local-… Josh Littlefield
- Re: [dhcwg] Changes to remove "client-link-local-… Ted Lemon
- Re: [dhcwg] Changes to remove "client-link-local-… Ralph Droms
- Re: [dhcwg] client unicast/client unicast option Ted Lemon
- Re: [dhcwg] Incorporation of WG last call comment… Ted Lemon
- Re: [dhcwg] Assigning DHCPv6 option codes Thomas Narten
- Re: FW: [dhcwg] co-existence of temp and normal a… Thomas Narten
- Re: FW: [dhcwg] co-existence of temp and normal a… Thomas Narten
- Re: [dhcwg] dhcpv6-24: Rapid Commit Thomas Narten
- Re: [dhcwg] dhcpv6-24: movement detection and Con… Thomas Narten
- Re: [dhcwg] dhcpv6-24: movement detection and Con… Thomas Narten
- Re: [dhcwg] dhcpv6-24: use of anycast Thomas Narten
- Re: [dhcwg] dhcpv6-24: Interface-ID option Thomas Narten
- Re: [dhcwg] dhcpv6-24: Temporary addresses Thomas Narten
- Re: [dhcwg] dhcpv6-24: movement detection and Con… Thomas Narten
- Re: [dhcwg] dhcpv6-24: movement detection and Con… Ted Lemon
- Re: [dhcwg] DHCP Option for CableLabs Client Conf… Thomas Narten
- Re: [dhcwg] status of draft-ietf-dhc-agent-subnet… Thomas Narten
- Re: [dhcwg] Conflicting information regarding DHC… Thomas Narten
- Re: [dhcwg] RE: I-D ACTION:draft-droms-dhcp-relay… Thomas Narten