From policy-bounces@ietf.org Fri Jun 10 13:14:17 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgn5F-00072e-86; Fri, 10 Jun 2005 13:14:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgn5E-00072P-KZ for policy@megatron.ietf.org; Fri, 10 Jun 2005 13:14:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11135 for ; Fri, 10 Jun 2005 13:14:13 -0400 (EDT) Received: from webmail.metasolv.com ([216.30.145.19] helo=srvplmailfe.metasolv.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DgnQv-0001zJ-PF for policy@ietf.org; Fri, 10 Jun 2005 13:36:42 -0400 Received: from srvotmail1.metasolv.com ([10.13.1.34]) by srvplmailfe.metasolv.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 10 Jun 2005 12:13:58 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6524.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C56DDF.C923201B" Date: Fri, 10 Jun 2005 13:13:56 -0400 Message-ID: X-MS-Has-Attach: yes Thread-Topic: RFC 4104 on Policy Core Extension Lightweight Directory AccessProtocol Schema (PCELS) Thread-Index: AcVshub/h5qxIRn3SAqBubuQTZIB5wBWMBiw From: "Pana, Mircea" To: X-OriginalArrivalTime: 10 Jun 2005 17:13:58.0318 (UTC) FILETIME=[C9F294E0:01C56DDF] X-Spam-Score: 1.1 (+) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Subject: [Policy] FW: RFC 4104 on Policy Core Extension Lightweight Directory AccessProtocol Schema (PCELS) X-BeenThere: policy@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Policy Framework List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: policy-bounces@ietf.org Errors-To: policy-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C56DDF.C923201B Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable fyi > -----Original Message----- > From: ietf-announce-bounces@ietf.org=20 > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of=20 > rfc-editor@rfc-editor.org > Sent: Wednesday, June 08, 2005 7:34 PM > To: ietf-announce@ietf.org > Cc: rfc-editor@rfc-editor.org > Subject: RFC 4104 on Policy Core Extension Lightweight=20 > Directory AccessProtocol Schema (PCELS) >=20 >=20 >=20 > A new Request for Comments is now available in online RFC libraries. >=20 >=20 > RFC 4104 >=20 > Title: Policy Core Extension Lightweight > Directory Access Protocol Schema (PCELS) > Author(s): M. Pana, Ed., A. Reyes, A. Barba, D. Moron, > M. Brunner > Status: Standards Track > Date: June 2005 > Mailbox: mpana@metasolv.com, mreyes@ac.upc.edu, > telabm@mat.upc.es, dmor4477@hotmail.com, > brunner@netlab.nec.de > Pages: 88 > Characters: 190951 > Updates: 3703 >=20 > I-D Tag: draft-reyes-policy-core-ext-schema-07.txt >=20 > URL: ftp://ftp.rfc-editor.org/in-notes/rfc4104.txt >=20 >=20 > This document defines a number of changes and extensions to=20 > the Policy Core Lightweight Directory Access Protocol (LDAP)=20 > Schema (RFC 3703) based on the model extensions defined by=20 > the Policy Core Information Model (PCIM) Extensions (RFC=20 > 3460). These changes and extensions consist of new LDAP=20 > object classes and attribute types. Some of the schema items=20 > defined in this document re-implement existing concepts in=20 > accordance with their new semantics introduced by RFC 3460. =20 > The other schema items implement new concepts, not covered by=20 > RFC 3703. This document updates RFC 3703. >=20 > This is now a Proposed Standard Protocol. >=20 > This document specifies an Internet standards track protocol=20 > for the Internet community, and requests discussion and=20 > suggestions for improvements. Please refer to the current=20 > edition of the "Internet Official Protocol Standards" (STD 1)=20 > for the standardization state and status of this protocol. =20 > Distribution of this memo is unlimited. >=20 > This announcement is sent to the IETF list and the RFC-DIST=20 > list. Requests to be added to or deleted from the IETF=20 > distribution list should be sent to IETF-REQUEST@IETF.ORG. =20 > Requests to be added to or deleted from the RFC-DIST=20 > distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. >=20 > Details on obtaining RFCs via FTP or EMAIL may be obtained by=20 > sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the=20 > message body=20 > help: ways_to_get_rfcs. For example: >=20 > To: rfc-info@RFC-EDITOR.ORG > Subject: getting rfcs >=20 > help: ways_to_get_rfcs >=20 > Requests for special distribution should be addressed to=20 > either the author of the RFC in question, or to=20 > RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted=20 > otherwise on the RFC itself, all RFCs are for unlimited distribution. >=20 > Submissions for Requests for Comments should be sent to=20 > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223,=20 > Instructions to RFC Authors, for further information. >=20 >=20 > Joyce K. Reynolds and Sandy Ginoza > USC/Information Sciences Institute >=20 > ... >=20 > Below is the data which will enable a MIME compliant Mail Reader=20 > implementation to automatically retrieve the ASCII version > of the RFCs. >=20 ------_=_NextPart_001_01C56DDF.C923201B Content-Type: application/octet-stream; name="rfc4104.URL" Content-Description: rfc4104.URL Content-Disposition: attachment; filename="rfc4104.URL" Content-Transfer-Encoding: base64 W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlzaS5lZHUvaW4tbm90ZXMvcmZjNDEw NC50eHQNCg== ------_=_NextPart_001_01C56DDF.C923201B Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy ------_=_NextPart_001_01C56DDF.C923201B-- From policy-bounces@ietf.org Fri Jun 10 17:06:15 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgqhi-0007dQ-WA; Fri, 10 Jun 2005 17:06:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgqhg-0007dD-NC for policy@megatron.ietf.org; Fri, 10 Jun 2005 17:06:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13354 for ; Fri, 10 Jun 2005 17:06:10 -0400 (EDT) Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dgr3Q-0005j5-JX for policy@ietf.org; Fri, 10 Jun 2005 17:28:41 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j5AL61bc019895; Fri, 10 Jun 2005 16:06:01 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Fri, 10 Jun 2005 23:06:00 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550751F14F@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Pana, Mircea" , policy@ietf.org Subject: RE: [Policy] FW: RFC 4104 on Policy Core Extension Lightweight Di rectory AccessProtocol Schema (PCELS) Date: Fri, 10 Jun 2005 23:06:00 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 1.1 (+) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Cc: X-BeenThere: policy@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Policy Framework List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: policy-bounces@ietf.org Errors-To: policy-bounces@ietf.org And thanks for the good work! Bert > -----Original Message----- > From: policy-bounces@ietf.org > [mailto:policy-bounces@ietf.org]On Behalf > Of Pana, Mircea > Sent: Friday, June 10, 2005 19:14 > To: policy@ietf.org > Subject: [Policy] FW: RFC 4104 on Policy Core Extension Lightweight > Directory AccessProtocol Schema (PCELS) > > > fyi > > > -----Original Message----- > > From: ietf-announce-bounces@ietf.org > > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of > > rfc-editor@rfc-editor.org > > Sent: Wednesday, June 08, 2005 7:34 PM > > To: ietf-announce@ietf.org > > Cc: rfc-editor@rfc-editor.org > > Subject: RFC 4104 on Policy Core Extension Lightweight > > Directory AccessProtocol Schema (PCELS) > > > > > > > > A new Request for Comments is now available in online RFC libraries. > > > > > > RFC 4104 > > > > Title: Policy Core Extension Lightweight > > Directory Access Protocol Schema (PCELS) > > Author(s): M. Pana, Ed., A. Reyes, A. Barba, D. Moron, > > M. Brunner > > Status: Standards Track > > Date: June 2005 > > Mailbox: mpana@metasolv.com, mreyes@ac.upc.edu, > > telabm@mat.upc.es, dmor4477@hotmail.com, > > brunner@netlab.nec.de > > Pages: 88 > > Characters: 190951 > > Updates: 3703 > > > > I-D Tag: draft-reyes-policy-core-ext-schema-07.txt > > > > URL: ftp://ftp.rfc-editor.org/in-notes/rfc4104.txt > > > > > > This document defines a number of changes and extensions to > > the Policy Core Lightweight Directory Access Protocol (LDAP) > > Schema (RFC 3703) based on the model extensions defined by > > the Policy Core Information Model (PCIM) Extensions (RFC > > 3460). 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 introduced by RFC 3460. > > The other schema items implement new concepts, not covered by > > RFC 3703. This document updates RFC 3703. > > > > 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. > > > > 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. > > > _______________________________________________ Policy mailing list Policy@ietf.org https://www1.ietf.org/mailman/listinfo/policy