IETF Logo Mail Archive

[dhcwg] dhcpv6 'zone suffix' option

"CTO YAN Renxiang" <Renxiang.Yan@alcatel-sbell.com.cn> Mon, 13 December 2004 13:48 UTC

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 IAA08786 for <dhcwg-web-archive@ietf.org>; Mon, 13 Dec 2004 08:48:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdqgN-00069N-72 for dhcwg-web-archive@ietf.org; Mon, 13 Dec 2004 08:56:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdqOD-0004us-I0; Mon, 13 Dec 2004 08:37:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdqCG-0007lt-J8 for dhcwg@megatron.ietf.org; Mon, 13 Dec 2004 08:25:04 -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 IAA06283 for <dhcwg@ietf.org>; Mon, 13 Dec 2004 08:25:03 -0500 (EST)
Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdqK3-0005UB-HG for dhcwg@ietf.org; Mon, 13 Dec 2004 08:33:09 -0500
Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38]) by asbmx.sbell.com.cn (8.12.10+Sun/8.12.3) with SMTP id iBDDJ5hi024722 for <dhcwg@ietf.org>; Mon, 13 Dec 2004 21:19:11 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Mon Dec 13 21:24:11 2004 +0800
Received: from BELLNET-MAIL3.sbell.com.cn ([172.24.208.23]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Mon, 13 Dec 2004 21:24:11 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: [dhcwg] dhcpv6 'zone suffix' option
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Mon, 13 Dec 2004 21:24:11 +0800
Message-ID: <8634B809B90D6E4AACA4AB0562A1F07205EDF2@bellnet-mail3.sbell.com.cn>
Thread-Topic: [dhcwg] dhcpv6 'zone suffix' option
Thread-Index: AcThFwiCWtu1C0NbSHylSZjXzoHTVw==
From: CTO YAN Renxiang <Renxiang.Yan@alcatel-sbell.com.cn>
To: dhcwg@ietf.org
X-OriginalArrivalTime: 13 Dec 2004 13:24:11.0952 (UTC) FILETIME=[08B0D300:01C4E117]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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>
Content-Type: multipart/mixed; boundary="===============1711700359=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88

Hi, all,

I've submitted the new version of the draft to the mailing list for some days, by now, no feedback received. 

I believe the questions raised in the 61th meeting have been clarified in the new draft. The main concern is the security. 

In version1, we gave an example, in which user updates DNS RR in DNS server. in fact, this example have no direct relationship with the options proposed in the draft. The idea in the draft only proposes a method to configure the zone suffix.  It does not concern who performs DNS update. In versioin2, we clarify this issue to avoid the misunderstanding. Moreover, after discussion,  Volz and I agree to attach the "zone suffix" option with IA_PD option.

 Does anyone have other opinions about that?  Please give me the comments, good or bad.

Thank you!

-Yan 


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

v2.30.2 | Report a Bug | By Email | System Status