Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07475; Wed, 5 Sep 2001 11:25:00 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13444; Wed, 5 Sep 2001 11:24:34 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13418 for ; Wed, 5 Sep 2001 11:24:31 -0400 (EDT) Received: from imr2.ericy.com (imr2.ericy.com [12.34.240.68]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07357 for ; Wed, 5 Sep 2001 11:23:04 -0400 (EDT) Received: from mr7.exu.ericsson.se (mr7att.ericy.com [138.85.92.15]) by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id f85FNv520288 for ; Wed, 5 Sep 2001 10:23:57 -0500 (CDT) Received: from eamrcnt749 (eamrcnt749.exu.ericsson.se [138.85.133.47]) by mr7.exu.ericsson.se (8.11.3/8.11.3) with SMTP id f85FNv307597 for ; Wed, 5 Sep 2001 10:23:57 -0500 (CDT) Received: FROM eamrcnt760.exu.ericsson.se BY eamrcnt749 ; Wed Sep 05 10:23:56 2001 -0500 Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id ; Wed, 5 Sep 2001 10:23:56 -0500 Message-ID: <66F66129A77AD411B76200508B65AC697B3534@eambunt705.ena-east.ericsson.se> From: "Bernie Volz (EUD)" To: "'Thomas Narten'" Cc: dhcwg@ietf.org Subject: RE: [dhcwg] How to encode DNS labels in DHCP options Date: Wed, 5 Sep 2001 10:23:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1361E.C3436FE0" Sender: dhcwg-admin@ietf.org Errors-To: dhcwg-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: dhcwg@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1361E.C3436FE0 Content-Type: text/plain; charset="iso-8859-1" Well, how about many of the Microsoft clients? That is likely 10's or 100's of millions. - Bernie -----Original Message----- From: Thomas Narten [mailto:narten@raleigh.ibm.com] Sent: Wednesday, September 05, 2001 11:19 AM To: Bernie Volz (EUD) Cc: dhcwg@ietf.org Subject: Re: [dhcwg] How to encode DNS labels in DHCP options Bernie, > The problem is that the FQDN option is already in such wide > deployment with the ASCII encoding that it would be impossible to > ask that everyone change to using the new. Which clients implement this? I.e, if there are lots of clients sending this out to servers today, than the spec should document this so servers can respond appropriately (or at the very least, not choke). But it would be good to know the number of clients we are talking about. Thomas ------_=_NextPart_001_01C1361E.C3436FE0 Content-Type: text/html; charset="iso-8859-1" RE: [dhcwg] How to encode DNS labels in DHCP options

Well, how about many of the Microsoft clients? That is likely 10's or 100's of millions.

- Bernie

-----Original Message-----
From: Thomas Narten [mailto:narten@raleigh.ibm.com]
Sent: Wednesday, September 05, 2001 11:19 AM
To: Bernie Volz (EUD)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] How to encode DNS labels in DHCP options


Bernie,

> The problem is that the FQDN option is already in such wide
> deployment with the ASCII encoding that it would be impossible to
> ask that everyone change to using the new.

Which clients implement this? I.e, if there are lots of clients
sending this out to servers today, than the spec should document this
so servers can respond appropriately (or at the very least, not
choke). But it would be good to know the number of clients we are
talking about.

Thomas

------_=_NextPart_001_01C1361E.C3436FE0-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org http://www1.ietf.org/mailman/listinfo/dhcwg