Re: [dhcwg] Re: I-D: draft-volz-dhc-dhcpv6-fqdn-00.txt - NEED INPUT BEFORE REVISING DRAFT!

Joe Quanaim <jdq@lucent.com> Wed, 08 September 2004 12:30 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 IAA06251; Wed, 8 Sep 2004 08:30:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C51SN-0002SW-8t; Wed, 08 Sep 2004 08:21:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C51QS-00025R-6q for dhcwg@megatron.ietf.org; Wed, 08 Sep 2004 08:19:48 -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 IAA05420 for <dhcwg@ietf.org>; Wed, 8 Sep 2004 08:19:46 -0400 (EDT)
Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C51U5-0007aM-Bz for dhcwg@ietf.org; Wed, 08 Sep 2004 08:23:34 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10]) by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id i88CIULq021816; Wed, 8 Sep 2004 07:18:30 -0500 (CDT)
Received: from kraken.mh.lucent.com by homail.ho.lucent.com (8.11.7+Sun/EMS-1.5 sol2) id i88CITP01836; Wed, 8 Sep 2004 08:18:29 -0400 (EDT)
From: Joe Quanaim <jdq@lucent.com>
To: Bernie Volz <volz@cisco.com>, dhcwg@ietf.org, 'Ted Lemon' <mellon@nominum.com>
Subject: Re: [dhcwg] Re: I-D: draft-volz-dhc-dhcpv6-fqdn-00.txt - NEED INPUT BEFORE REVISING DRAFT!
Date: Wed, 08 Sep 2004 08:18:27 -0400
User-Agent: KMail/1.5.4
References: <002301c4951b$7d08c980$efa0560a@amer.cisco.com>
In-Reply-To: <002301c4951b$7d08c980$efa0560a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200409080818.28071.jdq@lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jdq@lucent.com
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
Content-Transfer-Encoding: 7bit

Bernie Volz wrote:
> Before I revise the draft, please let me know if you think it is worth
> doing. The choices are:
> 1. Allow only the simple case for now (ie, Client FQDN option in an IA_NA
> or IA_TA options field applies to all addresses in the IA). We can always
> add the complex case (using a bit) in the future.
> 2. Allow both the simple and more complex case (latter is as currently
> documented); we'd use a bit in the flags field to indicate whether the
> client supports the complex method and wants to use (server can support it
> or not). Default (bit not set) is simple-only.
> 3. Come up with a completely different approach the problem (ideas?).
> 4. Abandon this work (if there's no interest in it).

I think 1 is sufficient for now, but I would also accept 2.  I think 4 is not 
a good choice.  dns integration is a valuable differentiator between dhcp and 
slac.

Joe.


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