Re: [ldapext] New LDAPEXT charter

Chris Ridd <chris.ridd@forgerock.com> Thu, 19 November 2015 12:45 UTC

Return-Path: <chris.ridd@forgerock.com>
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 A3CA11ACEAE for <ldapext@ietfa.amsl.com>; Thu, 19 Nov 2015 04:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] 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 8Z-itZDM5_FZ for <ldapext@ietfa.amsl.com>; Thu, 19 Nov 2015 04:45:40 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C8281ACEAB for <ldapext@ietf.org>; Thu, 19 Nov 2015 04:45:39 -0800 (PST)
Received: by wmdw130 with SMTP id w130so238776693wmd.0 for <ldapext@ietf.org>; Thu, 19 Nov 2015 04:45:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forgerock.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nJyuAl7CFphHSxrS3pLisRmyGFxIGk2OnEe78YvPhEw=; b=XPuOr12ybXVsOYB/8U4ZHl7ZCiEOoQ5HhPeG2mpcnXWw3N38l9vOR0tPKsyoiDZdlK GUhSSweQH07wgX9E3WgphBHwGNutRZKcndtlY3OiZ+CTSnb41qgRhz8p0tVPIDHTVt84 YWZRr4t+chdqpquqLY8uZgzXwxd0npb2HOjpM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=nJyuAl7CFphHSxrS3pLisRmyGFxIGk2OnEe78YvPhEw=; b=kbPQSx1VrSlL+PL8Plc03VLUUtcmmO+z3Q57zVsFMyuwa9Fg15jeENL5JKIy+2kLVM yQ3Wn9EyMP3Hois16sCVK/kSEvoRA2Hh2kaHIjNzXLPvARcDnqWLdSI8plxGBolYpqNS 9032oAN9C3lBtmY/j/5fqVhI/I+an6601aNvv5p7m7lAto04U1LmsxFdP5l2HErpNEnf +NGxbrCDccVojwJjAiFf2HyXPKtbaYw+xkVjNUkw+2xNXK1wOtZ+1Hc+x6XINAD5wt1w MX3xOB7jCvRw81S3/fh9Fvnk0GR6dlSvL+3y/uap3YkVl8X7ZPlabdcQV7+tTdubUgww lzGQ==
X-Gm-Message-State: ALoCoQlVoRGegMBa0GAkHyim7VKIvUX/KgYNQfl8d15Jx1ic0RtH4rXDiV2LZ8gU0EIcrdzyXsYs
X-Received: by 10.28.89.129 with SMTP id n123mr2687259wmb.2.1447937137959; Thu, 19 Nov 2015 04:45:37 -0800 (PST)
Received: from ?IPv6:2001:470:1f09:8e7:31bf:60de:4dc0:8f52? ([2001:470:1f09:8e7:31bf:60de:4dc0:8f52]) by smtp.gmail.com with ESMTPSA id h7sm8171851wmf.0.2015.11.19.04.45.36 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 Nov 2015 04:45:36 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Chris Ridd <chris.ridd@forgerock.com>
X-Mailer: iPhone Mail (13B143)
In-Reply-To: <564DBFBF.1040707@proseconsulting.co.uk>
Date: Thu, 19 Nov 2015 12:45:36 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <293C3EB8-6D1B-426B-A01E-57F425F8EA21@forgerock.com>
References: <564CA0C0.9010400@proseconsulting.co.uk> <564CE3FD.2030704@stroeder.com> <564DBFBF.1040707@proseconsulting.co.uk>
To: Mark R Bannister <dbis@proseconsulting.co.uk>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/amduD8l0HlLrukymWLTF4S-YxQA>
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 12:45:41 -0000

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