RE: [Policy] draft-reyes-policy-core-ext-schema-01.txt
"Pana, Mircea" <mpana@metasolv.com> Fri, 07 March 2003 23:17 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 SAA13588 for <policy-archive@odin.ietf.org>; Fri, 7 Mar 2003 18:17:23 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h27NT5d24695 for policy-archive@odin.ietf.org; Fri, 7 Mar 2003 18:29:05 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NNBO24265; Fri, 7 Mar 2003 18:23:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h27NF2O23899 for <policy@optimus.ietf.org>; Fri, 7 Mar 2003 18:15:02 -0500
Received: from srvmaddog.metasolv.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12174 for <policy@ietf.org>; Fri, 7 Mar 2003 18:02:49 -0500 (EST)
Received: by mail.metasolv.com with Internet Mail Service (5.5.2655.55) id <GP7N51BS>; Fri, 7 Mar 2003 17:08:04 -0600
Message-ID: <A33EE5A81E634B488B099FD31F65196153CBD7@SRVOTEMAIL>
From: "Pana, Mircea" <mpana@metasolv.com>
To: "'Larry S. Bartz'" <lbartz@parnelli.indy.cr.irs.gov>
Cc: policy@ietf.org
Subject: RE: [Policy] draft-reyes-policy-core-ext-schema-01.txt
Date: Fri, 07 Mar 2003 17:05:37 -0600
X-MS-TNEF-Correlator: <A33EE5A81E634B488B099FD31F65196153CBD7@SRVOTEMAIL>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C2E4FE.10C99E30"
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>
> I question whether it is absolutely necessary to mark the several > components from PCLS as "OBSOLETE". I realize that PCIMe describes > these as "deprecated". But the "OBSOLETE" designation is harsh. It > implies that a Directory implementation may not simultaneously > support both PCLS and PCELS. I don't see any naming clashes between > PCLS and PCELS, so why mark the PCLS components as OBSOLETE? You are right, it is not *absolutely* necessary to mark the deprecated schema items as "OBSOLETE". The "OBSOLETE" mechanism has been chosen as a way to formalize the restriction for PCELS information trees not to (SHOULD NOT) contain any of the deprecated PCLS items. In other words, PCELS and PCLS information trees SHOULD be disjunctive. This restriction originates from the desire to avoid backward compatibility issues for PCELS-only compliant applications ;-) PCLS schema items marked as "OBSOLETE" in subschema subentries governing specific PCELS administrative areas indicate that instances of such schema items are to be ignored. Implementations that do not support subschema subentries and specific administrative areas may ignore the "OBSOLETE" statements in the schema definitions but should have these restrictions enforced by other means. Regards, Mircea.
- [Policy] draft-reyes-policy-core-ext-schema-01.txt Pana, Mircea
- Re: [Policy] draft-reyes-policy-core-ext-schema-0… Larry S. Bartz
- RE: [Policy] draft-reyes-policy-core-ext-schema-0… Pana, Mircea
- RE: [Policy] draft-reyes-policy-core-ext-schema-0… Kurt D. Zeilenga
- RE: [Policy] draft-reyes-policy-core-ext-schema-0… Pana, Mircea
- RE: [Policy] draft-reyes-policy-core-ext-schema-0… Kurt D. Zeilenga