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

John Strassner <John.Strassner@intelliden.com> Mon, 15 September 2003 13:16 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27714 for <policy-archive@odin.ietf.org>; Mon, 15 Sep 2003 09:16:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ytD7-00073F-E3 for policy-archive@odin.ietf.org; Mon, 15 Sep 2003 09:16:11 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8FDG9Bk026960 for policy-archive@odin.ietf.org; Mon, 15 Sep 2003 09:16:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ytD1-0006xG-2c; Mon, 15 Sep 2003 09:16:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ytCJ-0006ro-25 for policy@optimus.ietf.org; Mon, 15 Sep 2003 09:15:19 -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 JAA27659 for <policy@ietf.org>; Mon, 15 Sep 2003 09:15:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ytCH-000556-00 for policy@ietf.org; Mon, 15 Sep 2003 09:15:17 -0400
Received: from cosium01.intelliden.net ([12.41.186.248]) by ietf-mx with esmtp (Exim 4.12) id 19ytCG-00051S-00 for policy@ietf.org; Mon, 15 Sep 2003 09:15:16 -0400
Received: by cosium01.intelliden.net with Internet Mail Service (5.5.2653.19) id <SSQBPLA5>; Mon, 15 Sep 2003 07:14:39 -0600
Message-ID: <AE723009E85E224CB00132C7FF0B34E1720709@cosium02.intelliden.net>
From: John Strassner <John.Strassner@intelliden.com>
To: "Larry S. Bartz" <lbartz@parnelli.indy.cr.irs.gov>, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: policy@ietf.org
Subject: RE: [Policy] Re: draft-reyes-policy-core-ext-schema-03.txt
Date: Mon, 15 Sep 2003 07:14:30 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C37B8B.4C0A4D40"
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've been away for awhile, but am commenting because Bert asked for comments
from the original authors.

I agree with Larry and Ryan. There is no technical justification for
deprecating these classes. In rereading the draft, I would go further and
state that there some of the restructuring may not be a good idea; however,
I want to reread this one last time and then I will provide detailed
comments.

Finally, Kurt is absolutely correct - deprecation is inappropriate in an
LDAP schema standards document.

regards,
John

John C. Strassner
Chief Strategy Officer
Intelliden Inc.
90 South Cascade Avenue
Colorado Springs, CO  80906  USA
phone:  +1.791.785.0648
  fax:     +1.719.785.0644
email:    john.strassner@intelliden.com


> -----Original Message-----
> From: Larry S. Bartz [mailto:lbartz@parnelli.indy.cr.irs.gov]
> Sent: Friday, August 29, 2003 3:24 PM
> To: Wijnen, Bert (Bert)
> Cc: policy@ietf.org
> Subject: Re: [Policy] Re: draft-reyes-policy-core-ext-schema-03.txt
> 
> Wijnen, Bert (Bert) wrote, On 08/29/03 10:14:
> > What an underwhelming interest in this document.
> >
> > When I start reading it, I see in the abstract:
> >    This document defines a number of changes and extensions to
> the
> >    Policy Core LDAP Schema [PCLS] based on the specifications of
> the
> >    Policy Core Information Model Extensions [PCIM_EXT]. The
> changes
> >    include additional object classes previously not covered,
> deprecation
> >    of some object classes and changes to the object class
> hierarchy
> >    defined in [PCLS].
> >
> > And so I immediately wonder... is it really OK that this document
> > deprecates some object classes ??
> >
> > Possibly so... but I'd like to hear some of the PCIM, PCIM-EXT
> and
> > PCLS authors/ediotrs to explicitly say so. PLEASE!
> >
> > Thanks,
> > Bert
> 
> 
> I argued several months ago that it is actually unnecessary to
> deprecate any of PCLS's information components. There are no
> naming clashes with PCLS components. The proposed deprecation
> only insures that PCLS and this schema will not be able to
> co-exist in the same Directory implementations. This is counter
> to the spirit of "extension". It casts a negative light on an
> elegant and highly serviceable information model and schema
> definition.
> 
> Further, another commenter (I believe it was Kurt Zielenga)
> asserted
> that the specification of deprecation is inappropriate in a schema
> standards document. Rather, deprecation is to be asserted by
> Directory service implementers in the course of managing instances
> of the Directory service.
> 
> --
> --
> #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> ::::|
> # Larry Bartz
> #
> #  voice (317) 226-7060
> #  FAX   (317) 226-6378
> #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> ::::|
> 
> 
> _______________________________________________
> Policy mailing list
> Policy@ietf.org
> https://www1.ietf.org/mailman/listinfo/policy