From mailnull@www1.ietf.org Mon Mar 3 12:32:34 2003 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 MAA04157 for ; Mon, 3 Mar 2003 12:32:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h23HgcM07678 for policy-archive@odin.ietf.org; Mon, 3 Mar 2003 12:42:38 -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 h23Ha1p06403; Mon, 3 Mar 2003 12:36:01 -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 h23HYMp06161 for ; Mon, 3 Mar 2003 12:34:22 -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 MAA03861 for ; Mon, 3 Mar 2003 12:23:48 -0500 (EST) Received: by mail.metasolv.com with Internet Mail Service (5.5.2655.55) id <1F9L3WD9>; Mon, 3 Mar 2003 11:28:51 -0600 Message-ID: From: "Pana, Mircea" To: policy@ietf.org Date: Mon, 3 Mar 2003 11:26:30 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E1AA.079A0720" Subject: [Policy] draft-reyes-policy-core-ext-schema-01.txt 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: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2E1AA.079A0720 Content-Type: text/plain; charset="iso-8859-1" We have recently submitted a revision of PCELS (LDAP schema mapping for PCIMe). The document is now available as: http://www.ietf.org/internet-drafts/draft-reyes-policy-core-ext-schema-01.tx t Mircea. ------_=_NextPart_001_01C2E1AA.079A0720 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable draft-reyes-policy-core-ext-schema-01.txt

We have recently submitted a revision of PCELS (LDAP = schema mapping for PCIMe).
The document is now available as:
http://www.ietf.org/internet-drafts/draft-reyes-policy= -core-ext-schema-01.txt

Mircea.

------_=_NextPart_001_01C2E1AA.079A0720-- _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From mailnull@www1.ietf.org Tue Mar 4 08:47:33 2003 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 IAA20889 for ; Tue, 4 Mar 2003 08:47:32 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h24Dw1n05364 for policy-archive@odin.ietf.org; Tue, 4 Mar 2003 08:58:01 -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 h24Dq0p05068; Tue, 4 Mar 2003 08:52:00 -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 h24Do8p05010 for ; Tue, 4 Mar 2003 08:50:08 -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 IAA20520 for ; Tue, 4 Mar 2003 08:39:08 -0500 (EST) Received: by mail.metasolv.com with Internet Mail Service (5.5.2655.55) id <1F9LPH2B>; Tue, 4 Mar 2003 07:44:13 -0600 Message-ID: From: "Pana, Mircea" To: "'larry.bartz@irs.gov'" Cc: policy@ietf.org Subject: RE: [Policy] I-D ACTION:draft-bartz-lsb-policy-rule-components-00 .txt Date: Tue, 4 Mar 2003 07:41:54 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E253.D1B3CE20" 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: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2E253.D1B3CE20 Content-Type: text/plain; charset="iso-8859-1" Larry, Some long due comments on LSBPRC: - Section 1. (Introduction) positions the paper as means for the implementation of policies in Expert Systems. Details, concrete applicability statements and examples would be very helpful. - Section 2 (Model): It is not obvious how LSBPRC extends the PCIM/PCIMe model. A list and diagram(s) of the new classes and attributes would be useful - it would also be useful to see the model and schema inheritance hierarchies and the model-schema mapping. Regards, Mircea. -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, December 11, 2002 8:12 AM Cc: policy@ietf.org Subject: [Policy] I-D ACTION:draft-bartz-lsb-policy-rule-components-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Logically Succinct Basic Policy Rule Components Author(s) : L. Bartz Filename : draft-bartz-lsb-policy-rule-components-00.txt Pages : 46 Date : 2002-12-9 Logically Succinct Basic Policy Rule Components (LSBPRC) provides model extensions to the Policy Core Information Model (PCIM) and implementable extensions to the Policy Core LDAP Schema (PCLS) in which the logic of conditions and actions can be succinctly expressed and explicitly interpreted. LSBPRC offers a direct and invariant connection between the rule designer's intention and the rule interpreter's evaluation of the rulebase. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-bartz-lsb-policy-rule-components-0 0.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-bartz-lsb-policy-rule-components-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-bartz-lsb-policy-rule-components-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_001_01C2E253.D1B3CE20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [Policy] I-D = ACTION:draft-bartz-lsb-policy-rule-components-00.txt

Larry,

Some long due comments on LSBPRC:

- Section 1. (Introduction) positions the paper as = means for the implementation of policies in Expert Systems. Details, = concrete applicability statements and examples would be very = helpful.

- Section 2 (Model): It is not obvious how LSBPRC = extends the PCIM/PCIMe model. A list and diagram(s) of the new classes = and attributes would be useful

- it would also be useful to see the model and schema = inheritance hierarchies and the model-schema mapping.

Regards,
Mircea.



-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org= ]
Sent: Wednesday, December 11, 2002 8:12 AM
Cc: policy@ietf.org
Subject: [Policy] I-D
ACTION:draft-bartz-lsb-policy-rule-components-00.txt


A New Internet-Draft is available from the on-line = Internet-Drafts directories.


        Title           : = Logically Succinct Basic Policy Rule Components
        Author(s)       : L. = Bartz
        Filename        : = draft-bartz-lsb-policy-rule-components-00.txt
        Pages           : = 46
        Date    =         : 2002-12-9
       =20
Logically Succinct Basic Policy Rule Components = (LSBPRC) provides
model extensions to the Policy Core Information = Model (PCIM) and
implementable extensions to the Policy Core LDAP = Schema (PCLS) in
which the logic of conditions and actions can be = succinctly expressed
and explicitly interpreted. LSBPRC offers a direct = and invariant
connection between the rule designer's intention and = the rule
interpreter's evaluation of the rulebase.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bartz-lsb-po= licy-rule-components-00.txt

To remove yourself from the IETF Announcement list, = send a message to
ietf-announce-request with the word unsubscribe in = the body of the message.

Internet-Drafts are also available by anonymous FTP. = Login with the username
"anonymous" and a password of your e-mail = address. After logging in,
type "cd internet-drafts" and then
        "get = draft-bartz-lsb-policy-rule-components-00.txt".

A list of Internet-Drafts directories can be found = in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by = e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE = /internet-drafts/draft-bartz-lsb-policy-rule-components-00.txt".
       =20
NOTE:   The mail server at ietf.org can = return the document in
        MIME-encoded form by using the "mpack" = utility.  To use this
        feature, = insert the command "ENCODING mime" before the = "FILE"
        command.  To decode the response(s), you will need = "munpack" or
        a = MIME-compliant mail reader.  Different MIME-compliant mail = readers
        exhibit = different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have = been split
        up into = multiple messages), so check your local documentation on
        how to = manipulate these messages.
        =        =20
        =        =20
Below is the data which will enable a MIME compliant = mail reader
implementation to automatically retrieve the ASCII = version of the
Internet-Draft.

------_=_NextPart_001_01C2E253.D1B3CE20-- _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From mailnull@www1.ietf.org Tue Mar 4 11:53:19 2003 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 LAA00902 for ; Tue, 4 Mar 2003 11:53:19 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h24H3qI20793 for policy-archive@odin.ietf.org; Tue, 4 Mar 2003 12:03:52 -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 h24Gvhp20041; Tue, 4 Mar 2003 11:57:43 -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 h24Guap19903 for ; Tue, 4 Mar 2003 11:56:36 -0500 Received: from mx-relay21.treas.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00128 for ; Tue, 4 Mar 2003 11:45:31 -0500 (EST) Received: from TIAS24.net.treas.gov (tias24.treas.gov [199.196.132.24]) by mx-relay21.treas.gov (8.12.8/8.12.8) with SMTP id h24GYoUX027521; Tue, 4 Mar 2003 11:34:50 -0500 (EST) Received: from no.name.available by TIAS24.net.treas.gov via smtpd (for [199.196.132.5]) with SMTP; 4 Mar 2003 16:47:33 UT Received: from irsbd2.net.treas.gov (localhost [127.0.0.1]) by mailhub-23.net.treas.gov (8.12.8/8.12.8) with ESMTP id h24GlRcd020587; Tue, 4 Mar 2003 11:47:27 -0500 (EST) Received: from no.name.available by irsbd2.net.treas.gov via smtpd (for mailhub.net.treas.gov [10.13.252.13]) with ESMTP; Tue, 4 Mar 2003 11:47:27 -0500 Received: from parnelli.indy.cr.irs.gov (localhost.localdomain [127.0.0.1]) by mears.indy.cr.irs.gov (8.11.6/8.11.6) with ESMTP id h24GlQH22220; Tue, 4 Mar 2003 11:47:26 -0500 Message-ID: <3E64D89E.7030701@parnelli.indy.cr.irs.gov> Date: Tue, 04 Mar 2003 11:47:26 -0500 From: "Larry S. Bartz" Organization: Internal Revenue Service User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Pana, Mircea" CC: policy@ietf.org Subject: Re: [Policy] I-D ACTION:draft-bartz-lsb-policy-rule-components-00 .txt References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Thanks, Mircea. I will address these issues in my "01" version of the draft, which I expect to publish within a month. Larry Pana, Mircea wrote, On 03/04/2003 08:41 AM: > Larry, > > Some long due comments on LSBPRC: > > - Section 1. (Introduction) positions the paper as means for the > implementation of policies in Expert Systems. Details, concrete > applicability statements and examples would be very helpful. I attempted to indicate that Expert Systems serves as a model of "best practices" for LSBPRC, while at the same time asserting that Expert Systems are not necessarily the omly target for implementation and use of the model. I'll try a a little harder to make those points more obvious in "01". > > - Section 2 (Model): It is not obvious how LSBPRC extends the PCIM/PCIMe > model. A list and diagram(s) of the new classes and attributes would be > useful Yes, you're right, absolutely. I intend to include UML-like schematics and objectclass inheritance diagrams similar to those of the PCIM and PCLS documents. > > - it would also be useful to see the model and schema inheritance > hierarchies and the model-schema mapping. As above. > > Regards, > Mircea. > > > > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Wednesday, December 11, 2002 8:12 AM > Cc: policy@ietf.org > Subject: [Policy] I-D > ACTION:draft-bartz-lsb-policy-rule-components-00.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Logically Succinct Basic Policy Rule Components > Author(s) : L. Bartz > Filename : draft-bartz-lsb-policy-rule-components-00.txt > Pages : 46 > Date : 2002-12-9 > > Logically Succinct Basic Policy Rule Components (LSBPRC) provides > model extensions to the Policy Core Information Model (PCIM) and > implementable extensions to the Policy Core LDAP Schema (PCLS) in > which the logic of conditions and actions can be succinctly expressed > and explicitly interpreted. LSBPRC offers a direct and invariant > connection between the rule designer's intention and the rule > interpreter's evaluation of the rulebase. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-bartz-lsb-policy-rule-components-00.txt > > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body of the message. > > Internet-Drafts are also available by anonymous FTP. Login with the > username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-bartz-lsb-policy-rule-components-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE > /internet-drafts/draft-bartz-lsb-policy-rule-components-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail > readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From mailnull@www1.ietf.org Thu Mar 6 15:35:59 2003 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 PAA11585 for ; Thu, 6 Mar 2003 15:35:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h26Kl8R12611 for policy-archive@odin.ietf.org; Thu, 6 Mar 2003 15:47:08 -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 h26Kf6O12317; Thu, 6 Mar 2003 15:41:06 -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 h26KO0O10487 for ; Thu, 6 Mar 2003 15:24:00 -0500 Received: from mx-relay1.net.treas.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10728 for ; Thu, 6 Mar 2003 15:12:18 -0500 (EST) Received: from tias5.treas.gov (tias-gw5.treas.gov [199.196.144.15]) by mx-relay1.net.treas.gov (8.12.8/8.12.8) with SMTP id h26KEN94002923; Thu, 6 Mar 2003 15:14:23 -0500 (EST) Received: from mailhub.net.treas.gov by tias5.treas.gov via smtpd (for mx-relay.treas.gov [199.196.144.5]) with SMTP; 6 Mar 2003 20:14:23 UT Received: from irsbd3.net.treas.gov (localhost [127.0.0.1]) by mailhub-4.net.treas.gov (8.12.8/8.12.8) with ESMTP id h26KEH8B026237; Thu, 6 Mar 2003 15:14:17 -0500 (EST) Received: from no.name.available by irsbd3.net.treas.gov via smtpd (for mailhub.net.treas.gov [10.7.14.14]) with ESMTP; Thu, 6 Mar 2003 15:14:17 -0500 Received: from parnelli.indy.cr.irs.gov (localhost.localdomain [127.0.0.1]) by mears.indy.cr.irs.gov (8.11.6/8.11.6) with ESMTP id h26KEGH01737; Thu, 6 Mar 2003 15:14:16 -0500 Message-ID: <3E67AC18.3050406@parnelli.indy.cr.irs.gov> Date: Thu, 06 Mar 2003 15:14:16 -0500 From: "Larry S. Bartz" Organization: Internal Revenue Service User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Pana, Mircea" CC: policy@ietf.org Subject: Re: [Policy] draft-reyes-policy-core-ext-schema-01.txt References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Pana, Mircea wrote, On 03/03/2003 12:26 PM: > We have recently submitted a revision of PCELS (LDAP schema mapping for > PCIMe). > The document is now available as: > http://www.ietf.org/internet-drafts/draft-reyes-policy-core-ext-schema-01.txt > > > Mircea. > The authors have done good work to improve the draft from its previous version. In particular the ABNF descriptions of the LDAP information components is much improved. I question whether it is absolutely neccessary 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? -- -- #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::| # Larry Bartz | | # lbartz@parnelli.indy.cr.irs.gov | Ooo, ooo, | # | Ooo, ooo, oooooo! | # | I've got a gnu attitude! | # voice (317) 226-7060 | | # FAX (317) 226-6378 | | #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::| _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From mailnull@www1.ietf.org Thu Mar 6 16:29:33 2003 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 QAA13481 for ; Thu, 6 Mar 2003 16:29:33 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h26Leio17181 for policy-archive@odin.ietf.org; Thu, 6 Mar 2003 16:40:44 -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 h26LYnO15933; Thu, 6 Mar 2003 16:34:49 -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 h26LT1O15541 for ; Thu, 6 Mar 2003 16:29:01 -0500 Received: from mx-relay21.treas.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12871 for ; Thu, 6 Mar 2003 16:17:19 -0500 (EST) Received: from TIAS24.net.treas.gov (tias24.treas.gov [199.196.132.24]) by mx-relay21.treas.gov (8.12.8/8.12.8) with SMTP id h26L6aUX014863; Thu, 6 Mar 2003 16:06:37 -0500 (EST) Received: from no.name.available by TIAS24.net.treas.gov via smtpd (for [199.196.132.5]) with SMTP; 6 Mar 2003 21:19:21 UT Received: from irsbd3.net.treas.gov (localhost [127.0.0.1]) by mailhub-21.net.treas.gov (8.12.8/8.12.8) with ESMTP id h26LJF8r029395; Thu, 6 Mar 2003 16:19:16 -0500 (EST) Received: from no.name.available by irsbd3.net.treas.gov via smtpd (for mailhub.net.treas.gov [10.13.252.11]) with ESMTP; Thu, 6 Mar 2003 16:19:16 -0500 Received: from parnelli.indy.cr.irs.gov (localhost.localdomain [127.0.0.1]) by mears.indy.cr.irs.gov (8.11.6/8.11.6) with ESMTP id h26LJFH01948; Thu, 6 Mar 2003 16:19:15 -0500 Message-ID: <3E67BB53.4000209@parnelli.indy.cr.irs.gov> Date: Thu, 06 Mar 2003 16:19:15 -0500 From: "Larry S. Bartz" Organization: Internal Revenue Service User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David McTavish , policy@ietf.org Subject: Re: [Policy] java-implementation Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit David McTavish wrote, on Wed, 18 Dec 2002 14:28:05 -0500: > I was hoping that someone would be interested enough to look at the > attached java-based source files to give me an idea of whether my > interpretation of what the PCIM model is supposed to be is correct. > I have found that the model proposed in the draft is fairly > understandable, but there are some minor inconsistencies with how > conditions and actions are handled/implemented. > > Anyway, please feel free to use these files in any form if it would > help bring this proposal into a finalized standard. > > d. > David, My comments are long overdue, for which I apologize. In my own defense, I didn't immediately recognize the potential utility of your work. Now that I've rested a few times, I'm seeing lots of potential uses. Your org.ietf.pcim package appears to be a sound foundation for others to implement, extend, and accessorize to meet Policy manipulation and interpretation requirements. I have looked for, but have not been able to detect, what you have characterized as "minor inconsistencies with how conditions and actions are handled/implemented." Can you elaborate? At what point(s) in which source file(s) are these inconsistencies manifested? David, I'm no lawyer. But I believe that the copyright notice which is incorporated in each of your package's source files is logically inconsistent with the package name "org.ietf.pcim", and with your assertion that we should "feel free to use these files in any form...". Would you consider republishing your work with one of the more liberal and more open copyright statements, such as GPL, LGPL, BSD or similar? It is entirely appropriate to identify yourself and your employer in each of your source files, to establish authorship. But if I understand your intent correctly, a more explicit invitation to romp and play is warranted. Thanks, -- -- #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::| # Larry Bartz | | # lbartz@parnelli.indy.cr.irs.gov | Ooo, ooo, | # | Ooo, ooo, oooooo! | # | I've got a gnu attitude! | # voice (317) 226-7060 | | # FAX (317) 226-6378 | | #::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::| _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From mailnull@www1.ietf.org Fri Mar 7 18:17:23 2003 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 ; 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 ; 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 ; Fri, 7 Mar 2003 18:02:49 -0500 (EST) Received: by mail.metasolv.com with Internet Mail Service (5.5.2655.55) id ; Fri, 7 Mar 2003 17:08:04 -0600 Message-ID: From: "Pana, Mircea" To: "'Larry S. Bartz'" Cc: policy@ietf.org Subject: RE: [Policy] draft-reyes-policy-core-ext-schema-01.txt Date: Fri, 7 Mar 2003 17:05:37 -0600 X-MS-TNEF-Correlator: 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: , List-Id: Policy Framework List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C2E4FE.10C99E30 Content-Type: text/plain > 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. ------_=_NextPart_000_01C2E4FE.10C99E30 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+IgUXAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQWAAwAOAAAA0wcDAAcAEQAFACUABQAkAQEggAMADgAAANMHAwAH ABEACAAEAAUABgEBCYABACEAAAAzNEIyRjZFQkY3M0YwNDQ2ODBENDUwMzlDN0Q1RTAxOQAlBwEE gAEANwAAAFJFOiBbUG9saWN5XSBkcmFmdC1yZXllcy1wb2xpY3ktY29yZS1leHQtc2NoZW1hLTAx LnR4dABqEwENgAQAAgAAAAIAAgABA5AGAEQJAAAwAAAAAwDeP59OAAADAACACCAGAAAAAADAAAAA AAAARgAAAABShQAAfW4BAB4AAYAIIAYAAAAAAMAAAAAAAABGAAAAAFSFAAABAAAABAAAADkuMAAL ACiACCAGAAAAAADAAAAAAAAARgAAAAAGhQAAAAAAAAMABoAIIAYAAAAAAMAAAAAAAABGAAAAAAGF AAAAAAAACwAHgAggBgAAAAAAwAAAAAAAAEYAAAAAA4UAAAAAAAALAAiACCAGAAAAAADAAAAAAAAA RgAAAAAOhQAAAAAAAAMACYAIIAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwAKgAggBgAAAAAA wAAAAAAAAEYAAAAAEYUAAAAAAAADAAuACCAGAAAAAADAAAAAAAAARgAAAAAYhQAAAAAAAAIBCRAB AAAAwwMAAL8DAAA+BgAATFpGdS7Q3owDAAoAcmNwZzEyNeIyA0N0ZXgFQQEDAff/CoACpAPkBxMC gA/zAFAEVj8IVQeyESUOUQMBAgBjaOEKwHNldDIGAAbDESX2MwRGE7cwEiwRMwjvCfe2OxgfDjA1 ESIMYGMAUDMLCQFkMzYWUAumID4QIEkgcQpQc3RpcQIgIHdoFCAd0AXAaasFQAQAIAGgcwbwdQ6w sGx5IG4FkAeQcwrAkR8wdG8gAMByax/g9R3QIBQQdgSQB0AKogqAsxzwBaBtcAIgCfB0BCChA1Ig UENMBfBhBCAAIk9CU09MRVQ4RSIuHQEYIAdAaXqbIJAd8GEFQCKgSU0gkPsBAATyYgeQISYd8RQQ IuN1AQBwGCBjJKAJgCOxQo8e8CBjIyglImlnbiSg1x2CHnET4mgjwXQhJgdwDwtQCJAEICSDYSBE ae8nER/wH8Eq4mUHgAIwKUQbAMAfMW8FQACQbXVsNwGQH1AIYHMfICEmc3V2cCHQACAgBuAd8CKV blpkIpFFIsAjwmQCICdPLcEJ4DBRHzFhbQuAZ58hkAtgKgAHkSWQdHcJ4fshJjAcLCCgIAAdwB8w ICdvIqMhqSLxIzY/ISQhJFmfCGAekBggI/ApEGh0NNDrHkQtoioeqCofTyBUJuj/IKAT0CywK7Ae QCywNtMjKt5UKAwHgBPRAwBzIoAT4Ocy4gnwIZBobxQQA6Ai8d0rsHctcR/xAhByAMAkNf840R1R BRAsEB2CQfEwlB4wfm5B8x1zQwAJ4DmkH/EoQFNIT1VMRAewTzxUKSGRLOELgDHDb2Z/O+4ioz1T I8EDoC/REoF3+QWwZHM00EPUMGRED0USj0XVJZAlIAQAanVuQzH/INA+gh5xQtoFsCkQC4AnQR8i NTv0AJA4wR/xYXZv6mkwgGIA0GtBgAsgIZP9KUFiAxAeQCxRBBAdQUOI/i0CIB8hIaIkMABwK5Ev YI8kMCcxHYEEIDstKTe6/yKjPOsgIjyxIvtLES8xHrCfPPRY0SIBCIEEIGdvINHzAwAyUXNwBZAG kA3gSib+ZDIxBABDAClBINA4oiLx/wuATOAnMiR0C4AdYABwOvH/R0IvQBPQPN1QREyxKREFsP8J gCPBLIsrRTEwLZQvVVjf/ysiMGJax1u/XMItYmB0J+7/XgE9YSIDRuEgczz0AQFlkd1U5GInwSoA CGBsMIAT4P9ccSZEQtkEIAnwQfE68FDhL0cxHfMHgABxLje6UmVuZwsRSgAhJE0r4DrwYQVuRX1w 0AAeAHAAAQAAADMAAABbUG9saWN5XSBkcmFmdC1yZXllcy1wb2xpY3ktY29yZS1leHQtc2NoZW1h LTAxLnR4dAAAAgFxAAEAAAAbAAAAAcLkHWyhInNDobDSRr+2HeaQrHs9QwAy4rhAAAMALgAAAAAA CwACAAEAAAAeAEIQAQAAACwAAAA8M0U2N0FDMTguMzA1MDQwNkBwYXJuZWxsaS5pbmR5LmNyLmly cy5nb3Y+AAMA/T/kBAAAAwAJWQEAAABAADkAMJ7JEP7kwgEDAPE/CQQAAB4AMUABAAAABgAAAE1Q QU5BAAAAAwAaQAAAAAAeADBAAQAAAAYAAABNUEFOQQAAAAMAGUAAAAAAAwAmAAAAAAADADYAAAAA AAsA8hABAAAAAwCAEP////8CAUcAAQAAAD4AAABjPVVTO2E9IDtwPU1ldGFTb2x2IFNvZnR3YXI7 bD1TUlZPVEVNQUlMLTAzMDMwNzIzMDUzN1otMTI0ODk0AAAAAgH5PwEAAABdAAAAAAAAANynQMjA QhAatLkIACsv4YIBAAAAAAAAAC9PPU1FVEFTT0xWIFNPRlRXQVJFLCBJTkMuL09VPU5UX01FVEFT T0xWL0NOPVJFQ0lQSUVOVFMvQ049TVBBTkEAAAAAHgD4PwEAAAANAAAAUGFuYSwgTWlyY2VhAAAA AB4AOEABAAAABgAAAE1QQU5BAAAAAgH7PwEAAABdAAAAAAAAANynQMjAQhAatLkIACsv4YIBAAAA AAAAAC9PPU1FVEFTT0xWIFNPRlRXQVJFLCBJTkMuL09VPU5UX01FVEFTT0xWL0NOPVJFQ0lQSUVO VFMvQ049TVBBTkEAAAAAHgD6PwEAAAANAAAAUGFuYSwgTWlyY2VhAAAAAB4AOUABAAAABgAAAE1Q QU5BAAAAQAAHMF5PxxD+5MIBQAAIMJqPdWj+5MIBHgA9AAEAAAAFAAAAUkU6IAAAAAAeAB0OAQAA ADMAAABbUG9saWN5XSBkcmFmdC1yZXllcy1wb2xpY3ktY29yZS1leHQtc2NoZW1hLTAxLnR4dAAA HgA1EAEAAAA0AAAAPEEzM0VFNUE4MUU2MzRCNDg4QjA5OUZEMzFGNjUxOTYxNTNDQkQ3QFNSVk9U RU1BSUw+AAsAKQAAAAAACwAjAAAAAAADAAYQQddDlAMABxAlBAAAAwAQEAEAAAADABEQAQAAAB4A CBABAAAAZQAAAElRVUVTVElPTldIRVRIRVJJVElTQUJTT0xVVEVMWU5FQ0VTU0FSWVRPTUFSS1RI RVNFVkVSQUxDT01QT05FTlRTRlJPTVBDTFNBUyJPQlNPTEVURSJJUkVBTElaRVRIQVRQQ0kAAAAA AgF/AAEAAAA0AAAAPEEzM0VFNUE4MUU2MzRCNDg4QjA5OUZEMzFGNjUxOTYxNTNDQkQ3QFNSVk9U RU1BSUw+AG5K ------_=_NextPart_000_01C2E4FE.10C99E30-- _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy