From exim@www1.ietf.org Wed Jan 7 21:01:39 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18422 for ; Wed, 7 Jan 2004 21:01:38 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AePTy-0007wF-6L for policy-archive@odin.ietf.org; Wed, 07 Jan 2004 21:01:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0821A16030514 for policy-archive@odin.ietf.org; Wed, 7 Jan 2004 21:01:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AePTq-0007v7-GP; Wed, 07 Jan 2004 21:01:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeJqi-0006Nn-5t for policy@optimus.ietf.org; Wed, 07 Jan 2004 15:00:16 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27045 for ; Wed, 7 Jan 2004 15:00:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeJqf-0000Jb-00 for policy@ietf.org; Wed, 07 Jan 2004 15:00:13 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeJoi-0000FE-00 for policy@ietf.org; Wed, 07 Jan 2004 14:58:12 -0500 Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AeJnF-0000C6-00; Wed, 07 Jan 2004 14:56:41 -0500 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i07JueN14628; Wed, 7 Jan 2004 11:56:40 -0800 (PST) Message-Id: <200401071956.i07JueN14628@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-editor@rfc-editor.org, policy@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 07 Jan 2004 11:56:40 -0800 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.0 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Subject: [Policy] RFC 3670 on Information Model for Describing Network Device QoS Datapath Mechanisms 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: , --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3670 Title: Information Model for Describing Network Device QoS Datapath Mechanisms Author(s): B. Moore, D. Durham, J. Strassner, A. Westerinen, W. Weiss Status: Standards Track Date: January 2004 Mailbox: remoore@us.ibm.com, david.durham@intel.com, john.strassner@intelliden.com, andreaw@cisco.com, walterweiss@attbi.com Pages: 97 Characters: 221687 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-policy-qos-device-info-model-10.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3670.txt The purpose of this document is to define an information model to describe the quality of service (QoS) mechanisms inherent in different network devices, including hosts. Broadly speaking, these mechanisms describe the properties common to selecting and conditioning traffic through the forwarding path (datapath) of a network device. This selection and conditioning of traffic in the datapath spans both major QoS architectures: Differentiated Services and Integrated Services. This document should be used with the QoS Policy Information Model (QPIM) to model how policies can be defined to manage and configure the QoS mechanisms (i.e., the classification, marking, metering, dropping, queuing, and scheduling functionality) of devices. Together, these two documents describe how to write QoS policy rules to configure and manage the QoS mechanisms present in the datapaths of devices. This document, as well as QPIM, are information models. That is, they represent information independent of a binding to a specific type of repository. This document is a product of the Policy Framework Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040107115414.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3670 --OtherAccess Content-Type: Message/External-body; name="rfc3670.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040107115414.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Tue Jan 20 13:00:43 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14469 for ; Tue, 20 Jan 2004 13:00:43 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj0Ai-0004jF-17 for policy-archive@odin.ietf.org; Tue, 20 Jan 2004 13:00:16 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KI0GFx018177 for policy-archive@odin.ietf.org; Tue, 20 Jan 2004 13:00:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj0AW-0004hv-Eh; Tue, 20 Jan 2004 13:00:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj0A9-0004g6-G7 for policy@optimus.ietf.org; Tue, 20 Jan 2004 12:59:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14393 for ; Tue, 20 Jan 2004 12:59:37 -0500 (EST) From: mpana@metasolv.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj0A7-00014f-00 for policy@ietf.org; Tue, 20 Jan 2004 12:59:39 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj098-000111-00 for policy@ietf.org; Tue, 20 Jan 2004 12:58:40 -0500 Received: from mail.metasolv.com ([216.30.145.7] helo=srvplemail1.metasolv.com) by ietf-mx with esmtp (Exim 4.12) id 1Aj08j-0000xR-00 for policy@ietf.org; Tue, 20 Jan 2004 12:58:13 -0500 Received: by srvplemail1.metasolv.com with Internet Mail Service (5.5.2653.19) id ; Tue, 20 Jan 2004 11:57:33 -0600 Message-ID: To: policy@ietf.org Date: Tue, 20 Jan 2004 11:53:10 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C3DF7E.44C631BE" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE, HTML_TITLE_EMPTY,NO_REAL_NAME autolearn=no version=2.60 Subject: [Policy] FW: I-D ACTION:draft-reyes-policy-core-ext-schema-04.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_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: owner-ietf-announce@ietf.org > [mailto:owner-ietf-announce@ietf.org]On Behalf Of > Internet-Drafts@ietf.org > 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: mailserv@ietf.org. 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 FW: I-D ACTION:draft-reyes-policy-core-ext-schema-04.txt

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: owner-ietf-announce@ietf.org
> [mailto:owner-ietf-announce@= ietf.org]On Behalf Of
> Internet-Drafts@ietf.org
> 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:
        mailserv@ietf.org.
In the body type:
        "FILE = /internet-drafts/draft-reyes-policy-core-ext-schema-04.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_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

  ------_=_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="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-1-20102603.I-D@ietf.org> 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-- _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy From exim@www1.ietf.org Wed Jan 28 12:35:39 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15974 for ; Wed, 28 Jan 2004 12:35:39 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Altaq-0007iR-J5 for policy-archive@odin.ietf.org; Wed, 28 Jan 2004 12:35:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SHZCBW029653 for policy-archive@odin.ietf.org; Wed, 28 Jan 2004 12:35:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Altah-0007hn-RH; Wed, 28 Jan 2004 12:35:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AltaW-0007ei-HJ for policy@optimus.ietf.org; Wed, 28 Jan 2004 12:34:52 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15937 for ; Wed, 28 Jan 2004 12:34:48 -0500 (EST) From: mpana@metasolv.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AltaU-00042k-00 for policy@ietf.org; Wed, 28 Jan 2004 12:34:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AltZY-0003wx-00 for policy@ietf.org; Wed, 28 Jan 2004 12:33:53 -0500 Received: from passwd.metasolv.com ([216.30.145.17] helo=srvplemail2.metasolv.com) by ietf-mx with esmtp (Exim 4.12) id 1AltYk-0003kY-00 for policy@ietf.org; Wed, 28 Jan 2004 12:33:02 -0500 Received: by passwd.metasolv.com with Internet Mail Service (5.5.2653.19) id ; Wed, 28 Jan 2004 11:32:40 -0600 Message-ID: To: policy@ietf.org Date: Wed, 28 Jan 2004 11:27:40 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3E5C4.07D44B50" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE, NO_REAL_NAME autolearn=no version=2.60 Subject: [Policy] PCELS and PCLS 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_01C3E5C4.07D44B50 Content-Type: text/plain; charset="ISO-8859-1" PCLS implementers, The main issue that was expressed relative to the previous revision (-03) of PCELS was its "unfriendly" position relative to PCLS. PCELS has been changed (-04) to address this issue and a new section was specifically added to the document for discussing the [non]impact of PCELS on PCLS implementations. Has anybody had the chance to read the -04 revision? Do you find the new approach acceptable? In particular, are there any comments regarding the provisions of section "4.3 Impact on existing implementations of the Policy Core LDAP Schema"? Thank You, Mircea Pana. ------_=_NextPart_001_01C3E5C4.07D44B50 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable PCELS and PCLS

PCLS implementers, The main issue that was expressed = relative to the previous revision (-03) of PCELS was its = "unfriendly" position relative to PCLS. PCELS has been = changed (-04) to address this issue and a new section was specifically = added to the document for discussing the [non]impact of PCELS on PCLS = implementations.

Has anybody had the chance to read the -04 revision? = Do you find the new approach acceptable? In particular, are there any = comments regarding the provisions of section "4.3 Impact on = existing implementations of the Policy Core LDAP = Schema"?

Thank You,
Mircea Pana.

------_=_NextPart_001_01C3E5C4.07D44B50-- _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy