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

"Steve Gonczi" <steve@relicore.com> Thu, 08 January 2004 20:51 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11618 for <dhcwg-archive@odin.ietf.org>; Thu, 8 Jan 2004 15:51:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aeh72-00061f-E0 for dhcwg-archive@odin.ietf.org; Thu, 08 Jan 2004 15:50:40 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i08KoeZ4023163 for dhcwg-archive@odin.ietf.org; Thu, 8 Jan 2004 15:50:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aeh72-00061W-Af for dhcwg-web-archive@optimus.ietf.org; Thu, 08 Jan 2004 15:50:40 -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 PAA11590 for <dhcwg-web-archive@ietf.org>; Thu, 8 Jan 2004 15:50:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aeh70-0005Sv-00 for dhcwg-web-archive@ietf.org; Thu, 08 Jan 2004 15:50:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aeh5I-0005ML-00 for dhcwg-web-archive@ietf.org; Thu, 08 Jan 2004 15:48:53 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aeh3V-0005FF-00 for dhcwg-web-archive@ietf.org; Thu, 08 Jan 2004 15:47:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aeh3U-0005Yf-9F; Thu, 08 Jan 2004 15:47:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aeh3I-0005Y5-Kz for dhcwg@optimus.ietf.org; Thu, 08 Jan 2004 15:46:48 -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 PAA11447 for <dhcwg@ietf.org>; Thu, 8 Jan 2004 15:46:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aeh3H-0005Dx-00 for dhcwg@ietf.org; Thu, 08 Jan 2004 15:46:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aeh1d-00057O-00 for dhcwg@ietf.org; Thu, 08 Jan 2004 15:45:06 -0500
Received: from ftp.relicore.com ([4.36.57.198]) by ietf-mx with esmtp (Exim 4.12) id 1Aeh0m-0004y3-00 for dhcwg@ietf.org; Thu, 08 Jan 2004 15:44:12 -0500
Received: from STEVEPC (ob.relicore.com [192.168.0.222]) by ftp.relicore.com (8.12.9/8.12.9) with SMTP id i08KMppu019600 for <dhcwg@ietf.org>; Thu, 8 Jan 2004 15:22:54 -0500 (EST)
From: Steve Gonczi <steve@relicore.com>
To: dhcwg@ietf.org
Subject: RE: [dhcwg] Request for review of 3315id draft...
Date: Thu, 08 Jan 2004 15:43:07 -0500
Message-ID: <BFELJLKGHEJOPOPGJBKKMEGACHAA.steve@relicore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <B7CE828D-4211-11D8-9200-000A95D9C74C@nominum.com>
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

I am begginnig to think this is a non-issue.

Given multiple ip-s per DNS name:
A) The client is be allowed to present one identity
(say, ID1) for more than one interfaces.

This would result in enforcing a "one active interface
at a time" behavior.
In a multi-server case, if a client tries to renew an 
IP address that a server  has no pool (or knowledge) of, 
the client gets NAK-d, and gets a new address. 
This results in the A record being overwritten 
both in case of solitary, or multiple DHCP servers. 

B) OTOH, a client is allowed to present a separate 
identity (say, ID1, ID2) for each interface.

This would result in multiple A records being maintained 
by either a solitary, or multiple DHCP servers.

The A record for ID1 gets created or deleted as ID1
acquires or releases the IP, and the same happens
for ID2.

In reality, (B) can not be distinguished from
a DNS round-robin server farm, where multiple
IP addreses, located on multiple, separate
servers are mapped to the same name via 
multiple A records.


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