FW: RFC 4104 on Policy Core Extension Lightweight Directory AccessProtocol Schema (PCELS)

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: [email protected]=20
> [mailto:[email protected]] On Behalf Of=20
> [email protected]
> Sent: Wednesday, June 08, 2005 7:34 PM
> To: [email protected]
> Cc: [email protected]
> 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:    [email protected], [email protected],
>                     [email protected], [email protected],
>                     [email protected]
>         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 [email protected]. =20
> Requests to be added to or deleted from the RFC-DIST=20
> distribution list should be sent to [email protected].
>=20
> Details on obtaining RFCs via FTP or EMAIL may be obtained by=20
> sending an EMAIL message to [email protected] with the=20
> message body=20
> help: ways_to_get_rfcs.  For example:
>=20
>         To: [email protected]
>         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
> [email protected].  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
> [email protected].  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
[email protected]
https://www1.ietf.org/mailman/listinfo/policy

------_=_NextPart_001_01C56DDF.C923201B--