RE: [dhcwg] dhcpv6 'zone suffix' option
"Bernie Volz" <volz@cisco.com> Wed, 10 November 2004 18:55 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 NAA12826; Wed, 10 Nov 2004 13:55:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxUj-0005ZN-BD; Wed, 10 Nov 2004 13:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxOr-0004XP-2u for dhcwg@megatron.ietf.org; Wed, 10 Nov 2004 13:40:57 -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 NAA11034 for <dhcwg@ietf.org>; Wed, 10 Nov 2004 13:40:55 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRxPq-0001P9-MR for dhcwg@ietf.org; Wed, 10 Nov 2004 13:41:59 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 10 Nov 2004 14:05:21 -0500
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iAAIeMR5007020; Wed, 10 Nov 2004 13:40:23 -0500 (EST)
Received: from volzw2k (dhcp-10-86-160-58.cisco.com [10.86.160.58]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMY19729; Wed, 10 Nov 2004 13:40:21 -0500 (EST)
From: Bernie Volz <volz@cisco.com>
To: 'Ted Lemon' <Ted.Lemon@nominum.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] dhcpv6 'zone suffix' option
Date: Wed, 10 Nov 2004 13:40:21 -0500
Organization: Cisco
Message-ID: <001a01c4c754$bbbecb00$a8412ca1@amer.cisco.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, Build 10.0.6626
In-Reply-To: <3517ADF8-3345-11D9-AA52-000A95D6A618@nominum.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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
Fine by me. I'll double check but I don't believe that I mentioned stateful in the current draft. > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > On Behalf Of Ted Lemon > Sent: Wednesday, November 10, 2004 1:21 PM > To: <dhcwg@ietf.org> <dhcwg@ietf.org> > Subject: Re: [dhcwg] dhcpv6 'zone suffix' option > > > 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 > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhcpv6 'zone suffix' option Mark Stapp
- Re: [dhcwg] dhcpv6 'zone suffix' option Ted Lemon
- RE: [dhcwg] dhcpv6 'zone suffix' option Bernie Volz
- Re: [dhcwg] dhcpv6 'zone suffix' option Ted Lemon
- RE: [dhcwg] dhcpv6 'zone suffix' option Bernie Volz
- [dhcwg] dhcpv6 source address selection policy op… (Tomohiro -INSTALLER- Fujisaki/藤崎 智宏 )
- Re: [dhcwg] dhcpv6 'zone suffix' option Ted Lemon
- RE: [dhcwg] dhcpv6 'zone suffix' option Bernie Volz
- re: [dhcwg] dhcpv6 'zone suffix' option CTO YAN Renxiang
- RE: [dhcwg] dhcpv6 'zone suffix' option Bernie Volz
- RE: [dhcwg] dhcpv6 'zone suffix' option CTO YAN Renxiang
- Re: [dhcwg] dhcpv6 'zone suffix' option Joe Quanaim
- RE: [dhcwg] dhcpv6 'zone suffix' option CTO YAN Renxiang
- re: [dhcwg] dhcpv6 'zone suffix' option CTO YAN Renxiang
- [dhcwg] dhcpv6 'zone suffix' option CTO YAN Renxiang
- RE: [dhcwg] dhcpv6 'zone suffix' option Bernie Volz