idnits 2.17.1 draft-ietf-ldup-replica-req-12.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3384 5 Title: Lightweight Directory Access Protocol (version 3) 6 Replication Requirements 7 Author(s): E. Stokes, R. Weiser, R. Moats, R. Huber 8 Status: Informational 9 Date: October 2002 10 Mailbox: rweiser@trustdst.com, stokese@us.ibm.com, 11 rmoats@lemurnetworks.net, rvh@att.com 12 Pages: 31 13 Characters: 66871 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-ldup-replica-req-12.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3384.txt 20 This document discusses the fundamental requirements for replication 21 of data accessible via the Lightweight Directory Access Protocol 22 (version 3) (LDAPv3). It is intended to be a gathering place for 23 general replication requirements needed to provide interoperability 24 between informational directories. 26 This document is a product of the LDAP Duplication/Replication/Update 27 Protocols Working Group of the IETF. 29 This memo provides information for the Internet community. It does 30 not specify an Internet standard of any kind. Distribution of this 31 memo is unlimited. 33 This announcement is sent to the IETF list and the RFC-DIST list. 34 Requests to be added to or deleted from the IETF distribution list 35 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 36 added to or deleted from the RFC-DIST distribution list should 37 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 39 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 40 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 41 help: ways_to_get_rfcs. For example: 43 To: rfc-info@RFC-EDITOR.ORG 44 Subject: getting rfcs 46 help: ways_to_get_rfcs 48 Requests for special distribution should be addressed to either the 49 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 50 specifically noted otherwise on the RFC itself, all RFCs are for 51 unlimited distribution.echo 52 Submissions for Requests for Comments should be sent to 53 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 54 Authors, for further information.