Re: [ldapext] New LDAPEXT charter

Mark R Bannister <dbis@proseconsulting.co.uk> Thu, 19 November 2015 13:14 UTC

Return-Path: <dbis@proseconsulting.co.uk>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC711AD0C7 for <ldapext@ietfa.amsl.com>; Thu, 19 Nov 2015 05:14:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pdwllbv0EIUh for <ldapext@ietfa.amsl.com>; Thu, 19 Nov 2015 05:14:38 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.141]) by ietfa.amsl.com (Postfix) with ESMTP id 589421A6FDC for <ldapext@ietf.org>; Thu, 19 Nov 2015 05:14:38 -0800 (PST)
Received: from host86-148-222-229.range86-148.btcentralplus.com ([86.148.222.229] helo=[192.168.1.67]) by smtp06.mailcore.me with esmtpa (Exim 4.80.1) (envelope-from <dbis@proseconsulting.co.uk>) id 1ZzP2r-0003DZ-6Y; Thu, 19 Nov 2015 13:14:37 +0000
To: Chris Ridd <chris.ridd@forgerock.com>
References: <564CA0C0.9010400@proseconsulting.co.uk> <564CE3FD.2030704@stroeder.com> <564DBFBF.1040707@proseconsulting.co.uk> <293C3EB8-6D1B-426B-A01E-57F425F8EA21@forgerock.com>
From: Mark R Bannister <dbis@proseconsulting.co.uk>
Message-ID: <564DCB37.1030408@proseconsulting.co.uk>
Date: Thu, 19 Nov 2015 13:14:31 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <293C3EB8-6D1B-426B-A01E-57F425F8EA21@forgerock.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailcore-Auth: 12040446
X-Mailcore-Domain: 1286164
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/LPFOn1DtaBiaZgNb8OoQhFHw_cA>
Cc: ldapext <ldapext@ietf.org>, =?UTF-8?Q?Michael_Str=c3=b6der?= <michael@stroeder.com>
Subject: Re: [ldapext] New LDAPEXT charter
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 13:14:42 -0000

On 19/11/2015 12:45, Chris Ridd wrote:
> On 19 Nov 2015, at 12:25, Mark R Bannister <dbis@proseconsulting.co.uk> wrote:
>> 2. Is the bit I still don't understand.  Where is this rule written down?
> I believe this is currently described in RFC 6410.
>
> Chris

Excellent, thanks Chris, that's exactly what I'm looking for.

Mark.