Re: [ldapext] why posixAccount MUST contain 'cn'?

Kurt Zeilenga <kurt.zeilenga@isode.com> Sun, 14 December 2014 16:43 UTC

Return-Path: <kurt.zeilenga@isode.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 C963B1A0100 for <ldapext@ietfa.amsl.com>; Sun, 14 Dec 2014 08:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level:
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 1TDqDg0InuMJ for <ldapext@ietfa.amsl.com>; Sun, 14 Dec 2014 08:43:26 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 271031A00F7 for <ldapext@ietf.org>; Sun, 14 Dec 2014 08:43:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1418575405; d=isode.com; s=selector; i=@isode.com; bh=ZfQsn+lQ92LQgR0ZNCejG5vD5uhSiqvj+kTSGhmpV3c=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=JBrxHxxS1VtGD7dEwLq7efeuKThOe5j1J18TzhLQFWwkhx6T2mXY3k6KWqq+Hk5UbiyfCJ Zxs19smMzdk79hT7t1PMZjCAKLOKZmUr95h2aiO0IYKX2kCmnIT5Pvc/1stbynJGvvaX+X uDecYdBhhjiFhzyKuvYRMvQLzwi2uHI=;
Received: from pagan.boolean.net ((unknown) [75.141.217.19]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <VI2-LABCky2j@waldorf.isode.com>; Sun, 14 Dec 2014 16:43:25 +0000
X-SMTP-Protocol-Errors: NORDNS PIPELINING
From: Kurt Zeilenga <kurt.zeilenga@isode.com>
In-Reply-To: <548DB67C.5060009@stroeder.com>
Date: Sun, 14 Dec 2014 08:43:19 -0800
Message-Id: <CF47C8D4-038D-4232-96F8-5EDE3A62C7D2@isode.com>
References: <548DB67C.5060009@stroeder.com>
To: =?utf-8?Q?Michael_Str=C3=B6der?= <michael@stroeder.com>
X-Mailer: Apple Mail (2.1993)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ldapext/4ByjK5XzmxLq9gBUGW3Vcwt5IfY
Cc: ldapext@ietf.org
Subject: Re: [ldapext] why posixAccount MUST contain 'cn'?
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: <http://www.ietf.org/mail-archive/web/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: Sun, 14 Dec 2014 16:43:27 -0000

> 
> 
> I'd be in favour of relaxing this to MAY cn in RFC2307bis.

See BCP 118 [RFC 4521], Section 5 concerning IETF rules for changing previously published schema definitions.