Re: [dhcwg] dhcpv6 'zone suffix' option

Ted Lemon <Ted.Lemon@nominum.com> Wed, 10 November 2004 18:34 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 NAA10430; Wed, 10 Nov 2004 13:34:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxFV-00029W-3L; Wed, 10 Nov 2004 13:31:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRx60-00082i-LM for dhcwg@megatron.ietf.org; Wed, 10 Nov 2004 13:21:28 -0500
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 NAA08306 for <dhcwg@ietf.org>; Wed, 10 Nov 2004 13:21:25 -0500 (EST)
Received: from shell-ng.nominum.com ([81.200.64.181]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRx70-0000j8-K7 for dhcwg@ietf.org; Wed, 10 Nov 2004 13:22:31 -0500
Received: from [130.129.131.238] (unknown [130.129.131.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id 1538656881 for <dhcwg@ietf.org>; Wed, 10 Nov 2004 10:20:43 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <000501c4c737$c8b832a0$a8412ca1@amer.cisco.com>
References: <000501c4c737$c8b832a0$a8412ca1@amer.cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <3517ADF8-3345-11D9-AA52-000A95D6A618@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] dhcpv6 'zone suffix' option
Date: Wed, 10 Nov 2004 13:20:32 -0500
To: "<dhcwg@ietf.org> <dhcwg@ietf.org>" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

On Nov 10, 2004, at 10:13 AM, Bernie Volz wrote:
> By putting it in the IA_* options, we're restricting it to stateful 
> (PD or
> NA) but I don't think that's an issue (especially if we don't use it to
> communicate the zone name).

I would encourage you not to put any language in the draft that 
explicitly refers to stateful versus not stateful.   I think it's 
likely that we will want to support dynamic DNS updates with the 
Information Request message using the FQDN option.   In this case, the 
client would have to send an IA option, in order to identify it for the 
purposes of doing the DNS update.   So if you don't explicitly say 
anything about stateful vs. non-stateful, we don't need to update your 
draft when we write a draft explaining how to do updates with stateless 
DHCPv6.


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