IETF Logo Mail Archive

RE: [Policy] draft-reyes-policy-core-ext-schema-01.txt

"Pana, Mircea" <mpana@metasolv.com> Wed, 23 April 2003 19:03 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01017 for <policy-archive@odin.ietf.org>; Wed, 23 Apr 2003 15:03:17 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3NJFRl20395 for policy-archive@odin.ietf.org; Wed, 23 Apr 2003 15:15:27 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3NJBU820212; Wed, 23 Apr 2003 15:11:30 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3NJAP820152 for <policy@optimus.ietf.org>; Wed, 23 Apr 2003 15:10:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00670 for <policy@ietf.org>; Wed, 23 Apr 2003 14:57:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 198PTQ-0006Sk-00 for policy@ietf.org; Wed, 23 Apr 2003 15:00:04 -0400
Received: from [66.46.208.99] (helo=srvotgfi.metasolv.com) by ietf-mx with esmtp (Exim 4.12) id 198PTQ-0006Sd-00 for policy@ietf.org; Wed, 23 Apr 2003 15:00:04 -0400
Received: from SRVOTEMAIL.metasolv.com ([10.13.1.25]) by srvotgfi.metasolv.com with Microsoft SMTPSVC(5.0.2172.1); Wed, 23 Apr 2003 15:02:26 -0400
Received: by SRVOTEMAIL.metasolv.com with Internet Mail Service (5.5.2653.19) id <20V95SQL>; Wed, 23 Apr 2003 14:54:57 -0400
Message-ID: <A33EE5A81E634B488B099FD31F65196153CC29@SRVOTEMAIL.metasolv.com>
From: "Pana, Mircea" <mpana@metasolv.com>
To: "'Kurt D. Zeilenga'" <Kurt@OpenLDAP.org>, policy@ietf.org
Subject: RE: [Policy] draft-reyes-policy-core-ext-schema-01.txt
Date: Wed, 23 Apr 2003 14:54:52 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-OriginalArrivalTime: 23 Apr 2003 19:02:26.0485 (UTC) FILETIME=[E152CE50:01C309CA]
Sender: policy-admin@ietf.org
Errors-To: policy-admin@ietf.org
X-BeenThere: policy@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/policy>, <mailto:policy-request@ietf.org?subject=unsubscribe>
List-Id: Policy Framework <policy.ietf.org>
List-Post: <mailto:policy@ietf.org>
List-Help: <mailto:policy-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/policy>, <mailto:policy-request@ietf.org?subject=subscribe>

Kurt,

Thank you for the clarification. The intent was to indicate (& emphasize)
the fact that items of the previously defined schema are no longer used.
Alternate schema items are provided by the
draft-reyes-policy-core-ext-schema specification.

Is there a formal mechanism that specifications can use to indicate the
deprecation of LDAP schema items?

Thanks,
Mircea.
  

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Tuesday, April 22, 2003 8:48 PM
To: policy@ietf.org
Subject: RE: [Policy] draft-reyes-policy-core-ext-schema-01.txt


In regards to the use of OBSOLETE keyword, please note that
this is NOT a mechanism for specifications to indicate that
a particular schema item is deprecated, but a mechanism for
directory administrators to mark schema as inactive in the
subschema.  See draft-ietf-ldapbis-models (or X.501(93)).

Kurt

_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy
_______________________________________________
Policy mailing list
Policy@ietf.org
https://www1.ietf.org/mailman/listinfo/policy

v2.23.0 | Report a Bug | By Email