Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates
 64.233.162.236 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=Z9DtjEeI+InJiFWtTNQOH1KSEfTLo2Bl6Kv7QjdjvzGc4svj+C7P53LOjtfpKXbNh1rPcnJeaEy21+rts2vhsQ+QlWSJrFfWyh1h0rgXItSAMexFZGS100eJcJLD8zDrGpZ6tI/t7H8AoejZ9hvtFu74XjGUdDN4Gs4odeGV8qQ=
Message-ID: <a32f6b020706070823l4a8e8c80n3bf2940808ed9b8f@mail.gmail.com>
Date: Thu, 7 Jun 2007 17:23:55 +0200
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: Sandboxing undocumented protocols (was: Re: [Vote] Sandboxing
 DHCP protocol)
In-Reply-To: <466821C3.1060102@labeo.de>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_35549_33301255.1181229835686"
References: <a32f6b020706070812l7d08de1ck8c2f6ba63eea14d2@mail.gmail.com>
	 <466821C3.1060102@labeo.de>

------=_Part_35549_33301255.1181229835686
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 6/7/07, Stefan Zoerner <stefan@labeo.de> wrote:
>
> Alex Karasulu wrote:
> > Just changed the name so we can discuss the other services separately
> from
> > the vote thread.
> >
> > Note that I think we might want to leave NTP since it is complete from
> my
> > understanding but Enrique would know best.  Also NTP might be needed for
> > time synch for Kerberos which needs time synchronization to
> function.  DNS
> > is not needed but is somewhat complete?
>
> NTP is quite simple, so it should be quite easy to provide user
> documentation. There is already something available
>
> http://directory.apache.org/apacheds/1.5/ntp-protocol-provider.html
>
> I volunteer for a simple "Getting started" article about how to enable
> the protocol in the configuration and check with a client -- step by step.


Cool thanks Stefan.

Perhaps Enrique could you setup an integration test to make sure NTP
works when enabled in the server?

Alex

------=_Part_35549_33301255.1181229835686
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br><div><span class="gmail_quote">On 6/7/07, <b class="gmail_sendername">Stefan Zoerner</b> &lt;<a href="mailto:stefan@labeo.de">stefan@labeo.de</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alex Karasulu wrote:<br>&gt; Just changed the name so we can discuss the other services separately from<br>&gt; the vote thread.<br>&gt;<br>&gt; Note that I think we might want to leave NTP since it is complete from my<br>
&gt; understanding but Enrique would know best.&nbsp;&nbsp;Also NTP might be needed for<br>&gt; time synch for Kerberos which needs time synchronization to function.&nbsp;&nbsp;DNS<br>&gt; is not needed but is somewhat complete?<br><br>NTP is quite simple, so it should be quite easy to provide user
<br>documentation. There is already something available<br><br><a href="http://directory.apache.org/apacheds/1.5/ntp-protocol-provider.html">http://directory.apache.org/apacheds/1.5/ntp-protocol-provider.html</a><br><br>I volunteer for a simple &quot;Getting started&quot; article about how to enable
<br>the protocol in the configuration and check with a client -- step by step.</blockquote><div><br>Cool thanks Stefan. &nbsp; <br></div><br>Perhaps Enrique could you setup an integration test to make sure NTP <br>works when enabled in the server?
<br><br>Alex<br><br></div>

------=_Part_35549_33301255.1181229835686--