RFC 2926 on Conversion of LDAP Schemas
RFC Editor <rfc-ed@ISI.EDU> Wed, 04 October 2000 23:29 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04078; Wed, 4 Oct 2000 19:29:53 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA17860 for ietf-123-outbound.10@ietf.org; Wed, 4 Oct 2000 19:25:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA17706 for <all-ietf@loki.ietf.org>; Wed, 4 Oct 2000 19:00:42 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA03608 for <all-ietf@ietf.org>; Wed, 4 Oct 2000 19:00:41 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA13231; Wed, 4 Oct 2000 15:27:43 -0700 (PDT)
Message-Id: <200010042227.PAA13231@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2926 on Conversion of LDAP Schemas
Cc: rfc-ed@ISI.EDU, srvloc@srvloc.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 04 Oct 2000 15:27:43 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2926 Title: Conversion of LDAP Schemas to and from SLP Templates Author(s): J. Kempf, R. Moats, P. St. Pierre Status: Informational Date: September 2000 Mailbox: james.kempf@sun.com, rmoats@coreon.net, Pete.StPierre@Eng.Sun.COM Pages: 27 Characters: 55365 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-svrloc-template-conversion-08.txt URL: ftp://ftp.isi.edu/in-notes/rfc2926.txt This document describes a procedure for mapping between Service Location Protocol (SLP) service advertisements and lightweight directory access protocol (LDAP) descriptions of services. The document covers two aspects of the mapping. One aspect is mapping between SLP service type templates and LDAP directory schema. Because the SLP service type template grammar is relatively simple, mapping from service type templates to LDAP types is straightforward. Mapping in the other direction is straightforward if the attributes are restricted to use just a few of the syntaxes defined in RFC 2252. If arbitrary ASN.1 types occur in the schema, then the mapping is more complex and may even be impossible. The second aspect is representation of service information in an LDAP directory. The recommended representation simplifies interoperability with SLP by allowing SLP directory agents to backend into LDAP directory servers. The resulting system allows service advertisements to propagate easily between SLP and LDAP. This document is a product of the Service Location Protocol Working Group of the IETF. 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.
- RFC 2926 on Conversion of LDAP Schemas RFC Editor