Re: [dhcwg] Re: UTF-8 issues (Re: Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs)
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 06 February 2006 20:02 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6CZ1-00018l-Or for dnsext-archive@megatron.ietf.org; Mon, 06 Feb 2006 15:02:19 -0500
Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17434 for <dnsext-archive@lists.ietf.org>; Mon, 6 Feb 2006 15:00:30 -0500 (EST)
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1F6CWe-000CjX-KB for namedroppers-data@psg.com; Mon, 06 Feb 2006 19:59:52 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.0
Received: from [131.112.32.132] (helo=necom830.hpcl.titech.ac.jp) by psg.com with smtp (Exim 4.60 (FreeBSD)) (envelope-from <mohta@necom830.hpcl.titech.ac.jp>) id 1F6CWb-000Cj9-8G for namedroppers@ops.ietf.org; Mon, 06 Feb 2006 19:59:49 +0000
Received: (qmail 48914 invoked from network); 6 Feb 2006 20:52:21 -0000
Received: from softbank219001188003.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.1.188.3) by necom830.hpcl.titech.ac.jp with SMTP; 6 Feb 2006 20:52:21 -0000
Message-ID: <43E7AAE2.6050108@necom830.hpcl.titech.ac.jp>
Date: Tue, 07 Feb 2006 05:00:34 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
CC: Mark Andrews <Mark_Andrews@isc.org>, Harald Tveit Alvestrand <harald@alvestrand.no>, Olaf Kolkman <olaf@nlnetlabs.nl>, namedroppers@ops.ietf.org, dhcwg <dhcwg@ietf.org>, Stig Venaas <Stig.Venaas@uninett.no>, "Ralph Droms (rdroms)" <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: UTF-8 issues (Re: Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs)
References: <8E296595B6471A4689555D5D725EBB21012DC25E@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB21012DC25E@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit
Bernie Volz (volz) wrote: > So, I think we want to drop or replace the LAST paragarph in section > 3.3.1 of draft-ietf-dhc-fqdn-option-11.txt. Sure. > Actually, I do now have a suggestion: > > Clients and servers SHOULD follow the character-set recommendations > of RFC 1035 section 2.3.1. However, implementers SHOULD also > be aware that some client software may use other character-sets. > This specification does not require support for any other > character-sets. > > If you don't like this, PLEASE SUGGEST ALTERNATIVE TEXT. We should also give reference to section 2.3.3. We don't have to say anything about "character-sets". So, the text could be: > Clients and servers SHOULD follow the character-set recommendations > of RFC 1035 section 2.3.1. However, implementers SHOULD also > be aware that some client software may "use the full binary octet > capabilities in names" as described in section 2.3.3 of RFC1035. Masataka Ohta -- to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/namedroppers/>
- RE: [dhcwg] Re: UTF-8 issues (Re: Open issues in … Harald Tveit Alvestrand
- Re: [dhcwg] Re: UTF-8 issues (Re: Open issues in … Masataka Ohta