FW: I-D ACTION:draft-reyes-policy-core-ext-schema-04.txt
[email protected] Tue, 20 Jan 2004 11:53:10 -0600
| Newsgroups | gmane.ietf.policy |
|---|---|
| Message-ID | <[email protected]> |
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_01C3DF7E.44C631BE Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3DF7E.44C631BE" ------_=_NextPart_001_01C3DF7E.44C631BE Content-Type: text/plain; charset="iso-8859-1" A long due revision on PCELS is now available on-line. It includes changes that address: - the issues raised by Bert in his AD Review - the issues and suggestions expressed on this mailing list. In particular none of the PCLS classes is deprecated and the impact on PCLS implementations is now explicitly assessed. A brief list of the changes follows: 1. This revision does not deprecate schema items defined in PCLS. The "Abstract" of this document has been modified accordingly. 2. To make them easily distinguishable from the object classes and attributes defined in PCLS, the schema items defined in this document are now prefixed "pcels" instead of "pcim". 3. In previous versions of this document the pcimPolicyGroup object class (initially defined by PCLS) was redefined as a subclass of pcimPolicySet (now pcelsPolicySet). This modification has been abandoned. 4. Added note on PolicyGroup representation as pcelsRule or pcelsPolicySet. 5. Abandoned deprecation of pcimRepository and modified pcelsReusableContainer to subclass pcimRepository. 6. Added general considerations in the opening of the schema definitions (section 5). 7. Added text to clarify which attributes defined in PCLS are also used in object classes defined here. 8. Instead of deprecating pcimRuleConditionAssociation and replacing it with pcelsConditionAssociation, the latter object class has been modified, so that is now a subclass of pcimRuleConditionAssociation which is no longer deprecated. 9. Instead of deprecating pcimRuleActionAssociation and replacing it with pcelsActionAssociation, the latter object class has been modified, so that is now a subclass of pcimRuleActionAssociation which is no longer deprecated. 10. The class pcimRule and its subclasses defined by PCLS are no longer deprecated. A note has been added to clarify the issue regarding the functionality replacement for compatibility with PCIM_EXT. 11. The pcimGroupContainmentAuxClass and pcimRuleContainmentAuxClass object classes defined by PCLS are no longer deprecated. A note has been added to clarify the issue regarding the functionality replacement for compatibility with PCIM_EXT. 12. Added text to explicitly describe the use of pcelsPolicySetAssociation for the realization of the PolicySetInSystem association. This was unclear in previous revisions. 13. Revised "Summary of changes since PCLS" in accordance with the changes listed above. 14. Revised security considerations. 15. Updated normative and informative references. 16. Added section to explain impact on PCLS implementations. 17. Added note on OID assignment status. (before section 1). 18. For compliance with NITS, the abstract does not use citations. 19. Added text to indicate valid and default attribute values where applicable. Note that a few (new) open issues are listed at the end of the document. Comments from the group are *very* welcome. Thank You, Mircea. > -----Original Message----- > From: [email protected] > [mailto:[email protected]]On Behalf Of > [email protected] > Sent: Tuesday, January 20, 2004 10:05 AM > Subject: I-D ACTION:draft-reyes-policy-core-ext-schema-04.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > > > Title : Policy Core Extension LDAP Schema (PCELS) > Author(s) : A. Reyes > Filename : draft-reyes-policy-core-ext-schema-04.txt > Pages : 63 > Date : 2004-1-19 > > This document defines a number of changes and extensions to the > Policy Core LDAP Schema (RFC zzzz) based on the model extensions > defined by RFC 3640. These changes and extensions consist of > new LDAP object classes and attribute types. Some of the > schema items defined > in this document re-implement existing concepts in accordance with > their new semantics modified by RFC 3640. The other schema items > implement new concepts, not covered by RFC zzzz. > This document updates RFC zzzz. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-reyes-policy-core-ex t-schema-04.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-reyes-policy-core-ext-schema-04.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: [email protected]. In the body type: "FILE /internet-drafts/draft-reyes-policy-core-ext-schema-04.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_01C3DF7E.44C631BE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2657.73"> <TITLE>FW: I-D ACTION:draft-reyes-policy-core-ext-schema-04.txt</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>A long due revision on PCELS is now available = on-line. It includes changes that address:</FONT> <BR><FONT SIZE=3D2>- the issues raised by Bert in his AD Review</FONT> <BR><FONT SIZE=3D2>- the issues and suggestions expressed on this = mailing list.</FONT> </P> <P><FONT SIZE=3D2>In particular none of the PCLS classes is deprecated = and the impact on PCLS implementations is now explicitly assessed. = </FONT></P> <P><FONT SIZE=3D2>A brief list of the changes follows:</FONT> <BR><FONT SIZE=3D2> 1. This revision does not deprecate = schema items defined in PCLS.</FONT> <BR><FONT SIZE=3D2> The "Abstract" of this = document has been modified accordingly.</FONT> </P> <P><FONT SIZE=3D2> 2. To make them easily distinguishable = from the object classes and</FONT> <BR><FONT SIZE=3D2> attributes defined in PCLS, the schema = items defined in this document</FONT> <BR><FONT SIZE=3D2> are now prefixed "pcels" = instead of "pcim".</FONT> </P> <P><FONT SIZE=3D2> 3. In previous versions of this document = the pcimPolicyGroup object</FONT> <BR><FONT SIZE=3D2> class (initially defined by PCLS) was = redefined as a subclass of</FONT> <BR><FONT SIZE=3D2> pcimPolicySet (now pcelsPolicySet). = This modification has been</FONT> <BR><FONT SIZE=3D2> abandoned.</FONT> </P> <P><FONT SIZE=3D2> 4. Added note on PolicyGroup = representation as pcelsRule or</FONT> <BR><FONT SIZE=3D2> pcelsPolicySet.</FONT> </P> <P><FONT SIZE=3D2> 5. Abandoned deprecation of = pcimRepository and modified</FONT> <BR><FONT SIZE=3D2> pcelsReusableContainer to subclass = pcimRepository.</FONT> </P> <P><FONT SIZE=3D2> 6. Added general considerations in the = opening of the schema</FONT> <BR><FONT SIZE=3D2> definitions (section 5).</FONT> </P> <P><FONT SIZE=3D2> 7. Added text to clarify which = attributes defined in PCLS are also</FONT> <BR><FONT SIZE=3D2> used in object classes defined = here.</FONT> </P> <P><FONT SIZE=3D2> 8. Instead of deprecating = pcimRuleConditionAssociation and replacing</FONT> <BR><FONT SIZE=3D2> it with pcelsConditionAssociation, the = latter object class has been</FONT> <BR><FONT SIZE=3D2> modified, so that is now a subclass of = pcimRuleConditionAssociation</FONT> <BR><FONT SIZE=3D2> which is no longer deprecated.</FONT> </P> <P><FONT SIZE=3D2> 9. Instead of deprecating = pcimRuleActionAssociation and replacing it</FONT> <BR><FONT SIZE=3D2> with pcelsActionAssociation, the latter = object class has been</FONT> <BR><FONT SIZE=3D2> modified, so that is now a subclass of = pcimRuleActionAssociation</FONT> <BR><FONT SIZE=3D2> which is no longer deprecated.</FONT> </P> <P><FONT SIZE=3D2> 10. The class pcimRule and its = subclasses defined by PCLS are no</FONT> <BR><FONT SIZE=3D2> longer deprecated. A note has been = added to clarify the issue</FONT> <BR><FONT SIZE=3D2> regarding the functionality replacement = for compatibility with</FONT> <BR><FONT SIZE=3D2> PCIM_EXT.</FONT> </P> <P><FONT SIZE=3D2> 11. The pcimGroupContainmentAuxClass and = pcimRuleContainmentAuxClass</FONT> <BR><FONT SIZE=3D2> object classes defined by PCLS are no = longer deprecated. A note has</FONT> <BR><FONT SIZE=3D2> been added to clarify the issue = regarding the functionality</FONT> <BR><FONT SIZE=3D2> replacement for compatibility with = PCIM_EXT.</FONT> </P> <P><FONT SIZE=3D2> 12. Added text to explicitly describe = the use of</FONT> <BR><FONT SIZE=3D2> pcelsPolicySetAssociation for the = realization of the</FONT> <BR><FONT SIZE=3D2> PolicySetInSystem association. This was = unclear in previous</FONT> <BR><FONT SIZE=3D2> revisions.</FONT> </P> <P><FONT SIZE=3D2> 13. Revised "Summary of changes = since PCLS" in accordance with the</FONT> <BR><FONT SIZE=3D2> changes listed above.</FONT> </P> <P><FONT SIZE=3D2> 14. Revised security = considerations.</FONT> </P> <P><FONT SIZE=3D2> 15. Updated normative and informative = references.</FONT> </P> <P><FONT SIZE=3D2> 16. Added section to explain impact on = PCLS implementations.</FONT> </P> <P><FONT SIZE=3D2> 17. Added note on OID assignment status. = (before section 1).</FONT> </P> <P><FONT SIZE=3D2> 18. For compliance with NITS, the = abstract does not use citations.</FONT> </P> <P><FONT SIZE=3D2> 19. Added text to indicate valid and = default attribute values where</FONT> <BR><FONT SIZE=3D2> applicable.</FONT> </P> <BR> <P><FONT SIZE=3D2>Note that a few (new) open issues are listed at the = end of the document. Comments from the group are *very* welcome.</FONT> </P> <P><FONT SIZE=3D2>Thank You,</FONT> <BR><FONT SIZE=3D2>Mircea.</FONT> </P> <P><FONT SIZE=3D2> </FONT> </P> <P><FONT SIZE=3D2>> -----Original Message-----</FONT> <BR><FONT SIZE=3D2>> From: [email protected]</FONT> <BR><FONT SIZE=3D2>> [<A = HREF=3D"mailto:[email protected]">mailto:owner-ietf-announce@= ietf.org</A>]On Behalf Of</FONT> <BR><FONT SIZE=3D2>> [email protected]</FONT> <BR><FONT SIZE=3D2>> Sent: Tuesday, January 20, 2004 10:05 AM</FONT> <BR><FONT SIZE=3D2>> Subject: I-D = ACTION:draft-reyes-policy-core-ext-schema-04.txt</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> A New Internet-Draft is available from the = on-line </FONT> <BR><FONT SIZE=3D2>> Internet-Drafts directories.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> = Title : Policy = Core Extension LDAP Schema (PCELS)</FONT> <BR><FONT SIZE=3D2>> = Author(s) : A. Reyes</FONT> <BR><FONT SIZE=3D2>> = Filename : = draft-reyes-policy-core-ext-schema-04.txt</FONT> <BR><FONT SIZE=3D2>> = Pages : = 63</FONT> <BR><FONT SIZE=3D2>> = Date : = 2004-1-19</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> This document defines a number of changes and = extensions to the</FONT> <BR><FONT SIZE=3D2>> Policy Core LDAP Schema (RFC zzzz) based on the = model extensions</FONT> <BR><FONT SIZE=3D2>> defined by RFC 3640. These changes and = extensions consist of </FONT> <BR><FONT SIZE=3D2>> new LDAP object classes and attribute types. = Some of the </FONT> <BR><FONT SIZE=3D2>> schema items defined</FONT> <BR><FONT SIZE=3D2>> in this document re-implement existing concepts = in accordance with</FONT> <BR><FONT SIZE=3D2>> their new semantics modified by RFC 3640. The = other schema items</FONT> <BR><FONT SIZE=3D2>> implement new concepts, not covered by RFC = zzzz.</FONT> <BR><FONT SIZE=3D2>> This document updates RFC zzzz.</FONT> <BR><FONT SIZE=3D2>> </FONT> <BR><FONT SIZE=3D2>> A URL for this Internet-Draft is:</FONT> <BR><FONT SIZE=3D2>> <A = HREF=3D"http://www.ietf.org/internet-drafts/draft-reyes-policy-core-ex" = TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-reyes-policy= -core-ex</A></FONT> <BR><FONT SIZE=3D2>t-schema-04.txt</FONT> </P> <P><FONT SIZE=3D2>To remove yourself from the IETF Announcement list, = send a message to </FONT> <BR><FONT SIZE=3D2>ietf-announce-request with the word unsubscribe in = the body of the message.</FONT> </P> <P><FONT SIZE=3D2>Internet-Drafts are also available by anonymous FTP. = Login with the username</FONT> <BR><FONT SIZE=3D2>"anonymous" and a password of your e-mail = address. After logging in,</FONT> <BR><FONT SIZE=3D2>type "cd internet-drafts" and then</FONT> <BR> <FONT SIZE=3D2>"get = draft-reyes-policy-core-ext-schema-04.txt".</FONT> </P> <P><FONT SIZE=3D2>A list of Internet-Drafts directories can be found = in</FONT> <BR><FONT SIZE=3D2><A HREF=3D"http://www.ietf.org/shadow.html" = TARGET=3D"_blank">http://www.ietf.org/shadow.html</A> </FONT> <BR><FONT SIZE=3D2>or <A = HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" = TARGET=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A></FONT> </P> <BR> <P><FONT SIZE=3D2>Internet-Drafts can also be obtained by = e-mail.</FONT> </P> <P><FONT SIZE=3D2>Send a message to:</FONT> <BR> <FONT = SIZE=3D2>[email protected].</FONT> <BR><FONT SIZE=3D2>In the body type:</FONT> <BR> <FONT = SIZE=3D2>"FILE = /internet-drafts/draft-reyes-policy-core-ext-schema-04.txt".</FONT>= <BR> =20 <BR><FONT SIZE=3D2>NOTE: The mail server at ietf.org can = return the document in</FONT> <BR> <FONT = SIZE=3D2>MIME-encoded form by using the "mpack" = utility. To use this</FONT> <BR> <FONT SIZE=3D2>feature, = insert the command "ENCODING mime" before the = "FILE"</FONT> <BR> <FONT = SIZE=3D2>command. To decode the response(s), you will need = "munpack" or</FONT> <BR> <FONT SIZE=3D2>a = MIME-compliant mail reader. Different MIME-compliant mail = readers</FONT> <BR> <FONT SIZE=3D2>exhibit = different behavior, especially when dealing with</FONT> <BR> <FONT = SIZE=3D2>"multipart" MIME messages (i.e. documents which have = been split</FONT> <BR> <FONT SIZE=3D2>up into = multiple messages), so check your local documentation on</FONT> <BR> <FONT SIZE=3D2>how to = manipulate these messages.</FONT> <BR> = =20 <BR> = =20 <BR><FONT SIZE=3D2>Below is the data which will enable a MIME compliant = mail reader</FONT> <BR><FONT SIZE=3D2>implementation to automatically retrieve the ASCII = version of the</FONT> <BR><FONT SIZE=3D2>Internet-Draft.</FONT> </P> <P><FONT FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"></FONT> </BODY> </HTML> ------_=_NextPart_001_01C3DF7E.44C631BE-- ------_=_NextPart_000_01C3DF7E.44C631BE Content-Type: message/rfc822 To: Subject: Date: Tue, 20 Jan 2004 09:28:06 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C3DF7E.44C631BE" ------_=_NextPart_002_01C3DF7E.44C631BE Content-Type: multipart/alternative; boundary="----_=_NextPart_003_01C3DF7E.44C631BE" ------_=_NextPart_003_01C3DF7E.44C631BE Content-Type: text/plain ------_=_NextPart_003_01C3DF7E.44C631BE Content-Type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.73"> <TITLE></TITLE> </HEAD> <BODY> <P><FONT FACE="Arial" SIZE=2 COLOR="#000000"></FONT><FONT FACE="Arial" SIZE=2 COLOR="#000000"></FONT> </BODY> </HTML> ------_=_NextPart_003_01C3DF7E.44C631BE-- ------_=_NextPart_002_01C3DF7E.44C631BE Content-Type: application/octet-stream; name="ATT32575" Content-Disposition: attachment; filename="ATT32575" Content-type: message/external-body; access-type="mail-server"; server="[email protected]" Content-Type: text/plain Content-ID: <[email protected]> ENCODING mime FILE /internet-drafts/draft-reyes-policy-core-ext-schema-04.txt ------_=_NextPart_002_01C3DF7E.44C631BE Content-Type: message/external-body; site="internet-drafts"; dir="draft-reyes-policy-core-ext-schema-04.txt"; mode="ftp.ietf.org"; access-type="anon-ftp" ------_=_NextPart_002_01C3DF7E.44C631BE-- ------_=_NextPart_000_01C3DF7E.44C631BE--