IETF Logo Mail Archive

Re: [dhcwg] Request for review of 3315id draft...

Ted Lemon <mellon@nominum.com> Thu, 08 January 2004 21:29 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12593 for <dhcwg-archive@odin.ietf.org>; Thu, 8 Jan 2004 16:29:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AehiQ-00075n-F1 for dhcwg-archive@odin.ietf.org; Thu, 08 Jan 2004 16:29:18 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i08LTIGW027257 for dhcwg-archive@odin.ietf.org; Thu, 8 Jan 2004 16:29:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AehiQ-00075Y-8k for dhcwg-web-archive@optimus.ietf.org; Thu, 08 Jan 2004 16:29:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12574 for <dhcwg-web-archive@ietf.org>; Thu, 8 Jan 2004 16:29:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AehiJ-0007Pr-00 for dhcwg-web-archive@ietf.org; Thu, 08 Jan 2004 16:29:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AehcA-00078V-00 for dhcwg-web-archive@ietf.org; Thu, 08 Jan 2004 16:22:51 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AehWr-0006pY-00 for dhcwg-web-archive@ietf.org; Thu, 08 Jan 2004 16:17:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AehWX-0006rS-22; Thu, 08 Jan 2004 16:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AehW5-0006pt-4x for dhcwg@optimus.ietf.org; Thu, 08 Jan 2004 16:16:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12307 for <dhcwg@ietf.org>; Thu, 8 Jan 2004 16:16:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AehVt-0006lg-00 for dhcwg@ietf.org; Thu, 08 Jan 2004 16:16:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AehTA-0006a0-00 for dhcwg@ietf.org; Thu, 08 Jan 2004 16:13:32 -0500
Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx with esmtp (Exim 4.12) id 1AehM8-0006DN-00 for dhcwg@ietf.org; Thu, 08 Jan 2004 16:06:16 -0500
Received: from [81.200.65.85] (dhcp-85.wl.nominum.com [81.200.65.85]) by toccata.fugue.com (Postfix) with ESMTP id D8E901B200C; Thu, 8 Jan 2004 15:00:19 -0600 (CST)
In-Reply-To: <BFELJLKGHEJOPOPGJBKKMEGACHAA.steve@relicore.com>
References: <BFELJLKGHEJOPOPGJBKKMEGACHAA.steve@relicore.com>
Mime-Version: 1.0 (Apple Message framework v609)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <6D318406-421E-11D8-98A2-000A95D9C74C@nominum.com>
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
From: Ted Lemon <mellon@nominum.com>
Subject: Re: [dhcwg] Request for review of 3315id draft...
Date: Thu, 08 Jan 2004 13:05:45 -0800
To: Steve Gonczi <steve@relicore.com>
X-Mailer: Apple Mail (2.609)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Jan 8, 2004, at 12:43 PM, Steve Gonczi wrote:

Be careful, Steve.   I think you're conflating the client identifier 
and the client hostname, and they're two separate things.   If the 
client sends a different ID and a different hostname on each interface, 
there's no problem.   If it sends the same ID and hostname on each 
interface, there may be a problem.   If it sends different ID and the 
same hostname on each interface, there's a problem.

This would all be greatly simplified by simply requiring that the 
client do its own update, but we really aren't in a position to do 
that.


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

v2.23.0 | Report a Bug | By Email