From michael@stroeder.com Sun May 3 07:01:27 2009 Return-Path: X-Original-To: ldapext@core3.amsl.com Delivered-To: ldapext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87D6D28C238 for ; Sun, 3 May 2009 07:01:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.147 X-Spam-Level: X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D18NOkhp0sUj for ; Sun, 3 May 2009 07:01:26 -0700 (PDT) Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) by core3.amsl.com (Postfix) with ESMTP id 9391328C108 for ; Sun, 3 May 2009 07:01:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by srv1.stroeder.com (Postfix) with ESMTP id 059364E168 for ; Sun, 3 May 2009 16:02:07 +0200 (CEST) X-Virus-Scanned: amavisd-new at stroeder.com Received: from srv1.stroeder.com ([127.0.0.1]) by localhost (srv1.stroeder.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPWkb0vNUzpO for ; Sun, 3 May 2009 16:01:58 +0200 (CEST) Received: from [10.1.0.2] (unknown [10.1.0.2]) by srv1.stroeder.com (Postfix) with ESMTP id D012F4E156 for ; Sun, 3 May 2009 16:01:57 +0200 (CEST) Message-ID: <49FDA400.10701@stroeder.com> Date: Sun, 03 May 2009 16:02:40 +0200 From: =?ISO-8859-1?Q?Michael_Str=F6der?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090402 SeaMonkey/1.1.16 MIME-Version: 1.0 To: ldapext@ietf.org References: <49C497F9.7010200@zioup.com> <49C870C6.4010803@zioup.com> <49C966C7.6060200@isode.com> <49CB0F22.6090902@zioup.com> <49CB853C.10108@zioup.com> In-Reply-To: <49CB853C.10108@zioup.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [ldapext] UTF-8 full support in LDIF / LDIF v2 X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 May 2009 14:01:27 -0000 Yves Dorfsman wrote: > Jim Willeke wrote: > >> Is the suggestion to utilize and indicator similar to the HTTP charset >> parameter (Content-Type: text/html; charset=utf-8) ? > > I don't think we ever got it that well defined, but I guess, yes this > would be one way of doing it. I'd prefer not to mix protocol specs here. The above key-word "Content-Type:" is used in HTTP and MIME headers. IMO there's no need to address that in the LDIF spec. One could suggest that content type should be set to Content-Type: application/directory; charset=utf-8 if the LDIF is encapsulated in MIME. But that's not part of LDIF itself. Ciao, Michael. From yves@zioup.com Thu May 7 14:26:43 2009 Return-Path: X-Original-To: ldapext@core3.amsl.com Delivered-To: ldapext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA58F3A6C02 for ; Thu, 7 May 2009 14:26:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.528 X-Spam-Level: X-Spam-Status: No, score=-1.528 tagged_above=-999 required=5 tests=[AWL=-0.940, BAYES_20=-0.74, SARE_SUB_ENC_UTF8=0.152] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFxHs5kah1lH for ; Thu, 7 May 2009 14:26:42 -0700 (PDT) Received: from idcmail-mo1so.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by core3.amsl.com (Postfix) with ESMTP id 0ADA03A68CF for ; Thu, 7 May 2009 14:26:33 -0700 (PDT) Received: from pd2ml1so-ssvc.prod.shaw.ca ([10.0.141.139]) by pd2mo1so-svcs.prod.shaw.ca with ESMTP; 07 May 2009 14:52:11 -0600 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=0 a=J6b0bBEkAAAA:8 a=DLutBw_bHfo3EEt_4TYA:9 a=oXMuVnJpUcHzKlupH28A:7 a=v4gLypJbTqHuETTUVOnOk5QjI_AA:4 a=WPV3hXSGBlIA:10 a=Cguc0gE-TcEA:10 Received: from s0106003018a62844.cg.shawcable.net (HELO home.zioup.com) ([68.147.37.46]) by pd2ml1so-dmz.prod.shaw.ca with ESMTP; 07 May 2009 14:52:11 -0600 Received: from [192.168.2.33] (nyksae.zioup.net [192.168.2.33]) by home.zioup.com (Postfix) with ESMTP id 18FB9350BF for ; Thu, 7 May 2009 14:52:11 -0600 (MDT) Message-ID: <4A0349FA.80001@zioup.com> Date: Thu, 07 May 2009 14:52:10 -0600 From: Yves Dorfsman User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: ldapext@ietf.org References: <49C497F9.7010200@zioup.com> <49C870C6.4010803@zioup.com> <49C966C7.6060200@isode.com> <49CB0F22.6090902@zioup.com> <49CB853C.10108@zioup.com> <49FDA400.10701@stroeder.com> In-Reply-To: <49FDA400.10701@stroeder.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [ldapext] UTF-8 full support in LDIF / LDIF v2 X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 21:26:43 -0000 Michael Ströder wrote: > Yves Dorfsman wrote: >> Jim Willeke wrote: >> >>> Is the suggestion to utilize and indicator similar to the HTTP charset >>> parameter (Content-Type: text/html; charset=utf-8) ? >> I don't think we ever got it that well defined, but I guess, yes this >> would be one way of doing it. > > I'd prefer not to mix protocol specs here. The above key-word > "Content-Type:" is used in HTTP and MIME headers. IMO there's no need to > address that in the LDIF spec. One could suggest that content type > should be set to > > Content-Type: application/directory; charset=utf-8 > > if the LDIF is encapsulated in MIME. But that's not part of LDIF itself. > Michael: Thanks for re-starting this thread. Some of Steven Legg's comment got me stuck, and then my priorities got shifted (looking for new contracts). I'll carry the thread following up on Steven's messages. -- Yves. http://www.sollers.ca/