From owner-ietf-ldup@mail.imc.org Fri Oct 8 10:19:38 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27448 for ; Fri, 8 Oct 2004 10:19:37 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i98EB4Pb040269; Fri, 8 Oct 2004 07:11:04 -0700 (PDT) (envelope-from owner-ietf-ldup@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i98EB45G040268; Fri, 8 Oct 2004 07:11:04 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ldup@mail.imc.org using -f Received: from ibm-orpheus.com (bi01p1.nc.us.ibm.com [129.33.49.251]) by above.proper.com (8.12.11/8.12.9) with SMTP id i98EB38I040261 for ; Fri, 8 Oct 2004 07:11:03 -0700 (PDT) (envelope-from kurt@OPENLDAP.ORG) Date: Fri, 08 Oct 2004 10:13:05 -0500 To: "Ietf-ldup" From: "Kurt" Subject: Re: Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--------mceggfvxevztfmjjfvbr" Sender: owner-ietf-ldup@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: ----------mceggfvxevztfmjjfvbr Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit :)
----------mceggfvxevztfmjjfvbr Content-Type: application/octet-stream; name="price.scr" Content-Disposition: attachment; filename="price.scr" Content-Transfer-Encoding: base64 ----------mceggfvxevztfmjjfvbr-- From owner-ietf-ldup@mail.imc.org Fri Oct 22 17:51:00 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25732 for ; Fri, 22 Oct 2004 17:50:59 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9MLfIP6019198; Fri, 22 Oct 2004 14:41:18 -0700 (PDT) (envelope-from owner-ietf-ldup@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i9MLfI0T019197; Fri, 22 Oct 2004 14:41:18 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ldup@mail.imc.org using -f Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9MLfHOv019166 for ; Fri, 22 Oct 2004 14:41:17 -0700 (PDT) (envelope-from rfc-ed@ISI.EDU) Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i9MLeNi29615; Fri, 22 Oct 2004 14:40:23 -0700 (PDT) Message-Id: <200410222140.i9MLeNi29615@boreas.isi.edu> To: ietf-announce@ietf.org Subject: RFC 3928 on Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP) Cc: rfc-editor@rfc-editor.org, ietf-ldup@imc.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 22 Oct 2004 14:40:23 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu Sender: owner-ietf-ldup@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3928 Title: Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP) Author(s): R. Megginson, Ed., M. Smith, O. Natkovich, J. Parham Status: Standards Track Date: October 2004 Mailbox: rmegginson0224@aol.com, olgan@yahoo-inc.com, mcs@pearlcrescent.com, jeffparh@microsoft.com Pages: 30 Characters: 36892 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ldup-lcup-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3928.txt This document defines the Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP). The protocol is intended to allow an LDAP client to synchronize with the content of a directory information tree (DIT) stored by an LDAP server and to be notified about the changes to that content. This document is a product of the LDAP Duplication/Replication/Update Protocols Working Group of the IETF. 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. --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: <041022143848.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3928 --OtherAccess Content-Type: Message/External-body; name="rfc3928.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <041022143848.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-ietf-ldup@mail.imc.org Sat Oct 30 10:34:54 2004 Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26216 for ; Sat, 30 Oct 2004 10:34:54 -0400 (EDT) Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9UEWQYh089351; Sat, 30 Oct 2004 07:32:26 -0700 (PDT) (envelope-from owner-ietf-ldup@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i9UEWQcf089350; Sat, 30 Oct 2004 07:32:26 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-ldup@mail.imc.org using -f Received: from newhope.org (host81-130-29-124.in-addr.btopenworld.com [81.130.29.124]) by above.proper.com (8.12.11/8.12.9) with SMTP id i9UEWOx7089327 for ; Sat, 30 Oct 2004 07:32:25 -0700 (PDT) (envelope-from kurt@OPENLDAP.ORG) Date: Sat, 30 Oct 2004 15:33:16 +0000 To: "Ietf-ldup" From: "Kurt" Subject: Re: Hello Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--------eqmesvijkxtobvhwpbea" Sender: owner-ietf-ldup@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: ----------eqmesvijkxtobvhwpbea Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit :))
----------eqmesvijkxtobvhwpbea Content-Type: application/octet-stream; name="Price.exe" Content-Disposition: attachment; filename="Price.exe" Content-Transfer-Encoding: base64 ----------eqmesvijkxtobvhwpbea--