Re: [dhcwg] One comment on draft-ietf-dhc-3315id-for-v4-05.txt
Andrea G Forte <andreaf@cs.columbia.edu> Thu, 10 November 2005 21:43 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaKCW-0003j6-9Y; Thu, 10 Nov 2005 16:43:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaKCU-0003ip-Ju for dhcwg@megatron.ietf.org; Thu, 10 Nov 2005 16:43:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17998 for <dhcwg@ietf.org>; Thu, 10 Nov 2005 16:42:50 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EaKSm-0005GD-TP for dhcwg@ietf.org; Thu, 10 Nov 2005 17:00:09 -0500
Received: from lion.cs.columbia.edu (IDENT:osiylyM5RMFSKntVw1b8xxihW41ol4mN@lion.cs.columbia.edu [128.59.16.120]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id jAALhAho010142 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 10 Nov 2005 16:43:11 -0500 (EST)
Received: from [128.59.19.228] (dhcp28.cs.columbia.edu [128.59.19.228]) by lion.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id jAALh7Iv031186; Thu, 10 Nov 2005 16:43:10 -0500
Message-ID: <4373BEE7.1000308@cs.columbia.edu>
Date: Thu, 10 Nov 2005 16:43:03 -0500
From: Andrea G Forte <andreaf@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] One comment on draft-ietf-dhc-3315id-for-v4-05.txt
References: <8E296595B6471A4689555D5D725EBB21D4275C@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB21D4275C@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
Cc: 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
Yes, I understand about IAID. I guess what I was trying to say is that we have to be careful at how the "multiple identities" problem is addressed as the DHCP server/client does not know how the user will use the different network interfaces. If I just want to switch between wired and wireless in the same subnet, having the same IP address for both interfaces might be a good idea (same identity and no intermittent connectivity), however if I want to use the two interfaces at the same time, then I need to have two different IP addresses. -Andrea Bernie Volz (volz) wrote: >That's why there is an Identity Association included. > >The DUID identifies the client (and it is one identity instead of many). > >The Identity Association is the second piece of the identity. So a >client that has multiple interfaces has (at least) a unique identity >association for each of those interfaces. (Client may have more identity >associations if they wanted multiple addresses PER interface.) > >- Bernie > > > >>-----Original Message----- >>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] >>On Behalf Of Andrea G Forte >>Sent: Thursday, November 10, 2005 3:55 PM >>To: dhcwg@ietf.org >>Subject: [dhcwg] One comment on draft-ietf-dhc-3315id-for-v4-05.txt >> >>I have not followed the exchange of comments regarding this draft, so >>please forgive me if this issue has already been discussed. >>However, one >>comment I have is that this draft seems to be useful only if >>I have more >>than one network card on the same subnet (the change of >>chassis and/or >>the change of NIC are less common especially nowadays with >>more and more >>devices with built-in wireless/wired ethernet). In many >>cases, wireless >>and wired networks belong to different subnets, in such a >>case we would >>still have different IPs on different NICs, so the client would still >>appear as it has intermittent connectivity when switching from one to >>the other. Furthermore, if we have the two cards (wireless >>and wired) on >>the same subnet, using the same IP address on both would >>create a lot of >>problems if (for whatever reason) I decide to use both of the >>cards at >>the same time. >> >>-Andrea >> >> >>_______________________________________________ >>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
- [dhcwg] One comment on draft-ietf-dhc-3315id-for-… Andrea G Forte
- RE: [dhcwg] One comment on draft-ietf-dhc-3315id-… Bernie Volz (volz)
- Re: [dhcwg] One comment on draft-ietf-dhc-3315id-… Andrea G Forte
- Re: [dhcwg] One comment on draft-ietf-dhc-3315id-… Ted Lemon
- Re: [dhcwg] One comment on draft-ietf-dhc-3315id-… Ted Lemon
- Re: [dhcwg] One comment on draft-ietf-dhc-3315id-… Andrea G Forte
- Re: [dhcwg] One comment on draft-ietf-dhc-3315id-… Ted Lemon
- Re: [dhcwg] One comment on draft-ietf-dhc-3315id-… David W. Hankins