[rfc-dist] RFC 3712 on Lightweight Directory Access Protocol (LDAP): Schema for Printer Services
rfc-editor@rfc-editor.org (rfc-editor@rfc-editor.org) Thu, 26 February 2004 20:00 UTC
From: rfc-editor@rfc-editor.org
Date: Thu, 26 Feb 2004 12:00:01 -0800
Subject: [rfc-dist] RFC 3712 on Lightweight Directory Access Protocol (LDAP): Schema for Printer Services
Message-ID: <200402262000.i1QK01k20468@gamma.isi.edu>
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 3712 Title: Lightweight Directory Access Protocol (LDAP): Schema for Printer Services Author(s): P. Fleming, I. McDonald Status: Informational Date: February 2004 Mailbox: flemingp@us.ibm.com, imcdonald@sharplabs.com Pages: 33 Characters: 62301 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-fleming-ldap-printer-schema-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3712.txt This document defines a schema, object classes and attributes, for printers and printer services, for use with directories that support Lightweight Directory Access Protocol v3 (LDAP-TS). This document is based on the printer attributes listed in Appendix E of Internet Printing Protocol/1.1 (IPP) (RFC 2911). A few additional printer attributes are based on definitions in the Printer MIB (RFC 1759). This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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: <040226115200.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3712 --OtherAccess Content-Type: Message/External-body; name="rfc3712.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040226115200.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--
- [rfc-dist] RFC 3712 on Lightweight Directory Acce… rfc-editor@rfc-editor.org