[dhcwg] (no subject)

"CTO YAN Renxiang" <Renxiang.Yan@alcatel-sbell.com.cn> Wed, 14 July 2004 04:30 UTC

Received: from megatron.ietf.org (megatron.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14055; Wed, 14 Jul 2004 00:30:58 -0400 (EDT)
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkbJk-0000Au-Um; Wed, 14 Jul 2004 00:24:29 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkbAF-0001Mq-75 for dhcwg@megatron.ietf.org; Wed, 14 Jul 2004 00:14:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11422 for <dhcwg@ietf.org>; Wed, 14 Jul 2004 00:14:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkbAD-0003Ms-7o for dhcwg@ietf.org; Wed, 14 Jul 2004 00:14:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkaZ2-0004kE-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 23:36:14 -0400
Received: from [] (helo=asbmx.sbell.com.cn) by ietf-mx with esmtp (Exim 4.12) id 1Bka1T-0007FK-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 23:01:37 -0400
Received: from asbwebshld.sbell.com.cn (asbwebshld []) by asbmx.sbell.com.cn (8.12.10+Sun/8.12.3) with SMTP id i6E2udMK017966 for <dhcwg@ietf.org>; Wed, 14 Jul 2004 10:56:42 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ; Wed Jul 14 11:00:46 2004 +0800
Received: from BELLNET-MAIL3.sbell.com.cn ([]) by bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Wed, 14 Jul 2004 11:00:46 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Jul 2004 11:00:45 +0800
Message-ID: <8634B809B90D6E4AACA4AB0562A1F07205ED76@bellnet-mail3.sbell.com.cn>
Thread-Index: AcRpTsar2Adupie/SwKT86ndO464gA==
From: CTO YAN Renxiang <Renxiang.Yan@alcatel-sbell.com.cn>
To: volz@cisco.com
X-OriginalArrivalTime: 14 Jul 2004 03:00:46.0253 (UTC) FILETIME=[C25E1DD0:01C4694E]
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: dhcwg@ietf.org
Subject: [dhcwg] (no subject)
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: quoted-printable

Hi, Bernie,

I don't think domain name search list option defined in RFC3646 can transfer the DNS
zone suffix which is used by host to update the FQDN without any modification.

In section4 of RFC3646, it states:
"The Domain Search List option specifies the domain search list the client is to use when
resolving hostnames with DNS."

The initial purpose of domain search list option is hostname resolving, not domain name
update. Furthermore, the domain name listed in the Domain Search List option can be
different from the DNS zone suffix the client needed to update its domain name.

Even if Domain Search List option can be used in domain name update, we have to
define a mechanism to choose a correct domain name from domain search list.

To sum up, two choices exist to make it possible for IPv6 client to dynamically update its domain name:
1. define another option to transfer DNS zone suffix to client, which enables the client generates its FQDN,
as defined in http://www.ietf.org/internet-drafts/draft-yan-dhc-dhcpv6-opt-dnszone-00.txt.
2. define a mechanism to choose a domain name as DNS zone suffix from domain search list,
and use it to generate and update client's FQDN


P.S. In order to foster a discussion on this topic, I am CCing  this mail to DHC list,
I would be appreciated any value comments from experts in the list.

发件人: Bernie Volz [mailto:volz@cisco.com]
发送时间: 2004年7月13日 10:38
收件人: CTO YAN Renxiang
主题: RE: about your draft

The Client FQDN option sends the fully qualified domain name. There is no
indication of which is the host portion and which is the domain name. In
general, this really isn't that useful.

In DHCPv6, we already have the domain name search list option (see
http://www.ietf.org/rfc/rfc3646.txt). This is generally much more useful
than just the "domain name" and, in DHCPv4 it is generally the domain name
that is used as the default domain search list.

So, if a client receives the Client FQDN option with a fully qualified
domain name, it can figure out the host name portion by using the domain
search list, if it really cares. Or, it can do DNS lookups.

- Bernie

> -----Original Message-----
> From: CTO YAN Renxiang [mailto:Renxiang.Yan@alcatel-sbell.com.cn]
> Sent: Monday, July 12, 2004 8:38 PM
> To: Bernie Volz
> Subject: re: about your draft
> Hi, Bernie,
> In DHCPv4, the domain name is tranferred using option 15
> (domain name) defined in 2132. However, DHCPv6 does not
> defined such an option. How does your draft implement? could
> you explain in a bit detail?
> regards,
> -renxiang
> -----原始邮件-----
> 发件人: Bernie Volz [mailto:volz@cisco.com]
> 发送时间: 2004年7月12日 21:28
> 收件人: CTO YAN Renxiang
> 主题: RE: about your draft
> Hi:
> The draft should appear at the IETF web site shortly.
> Sometimes the announcement preceeds the upload to the web/ftp
> site(s), so give it a day or two and it should appear.
> The option is modeled after the DHCPv4 Client FQDN option.
> - Bernie
> > -----Original Message-----
> > From: CTO YAN Renxiang [mailto:Renxiang.Yan@alcatel-sbell.com.cn]
> > Sent: Sunday, July 11, 2004 11:35 PM
> > To: volz@cisco.com
> > Subject: about your draft
> >
> >
> > Hi Bernie,
> >
> > I found you will make presentation on 60th IETF meeting about
> > the DHCP FQDN option. I can't find the draft "The DHCPv6
> > Client FQDN Option" on website. Could you send me
> > the link?
> >
> > I wrote a draft  "DNS zone suffix option for DHCPv6" to allow
> > DHCPv6 server transfer the DNS zone suffix to DHCPv6 client.
> > I wonder there will be close relationship between our drafts,
> > so could you tell me how to tranfer the DNS suffix in your draft?
> >
> > Thank you!
> >
> > regards,
> > -Renxiang
> >
> cn 

dhcwg mailing list