The Lightweight Directory Access Protocol (LDAP) Content Synchronization Operation
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: RFC Editor <firstname.lastname@example.org> Cc: The IESG <email@example.com>, <firstname.lastname@example.org>, email@example.com Subject: Re: Experimental RFC to be: draft-zeilenga-ldup-sync-07.txt The IESG has no problem with the publication of 'LDAP Content Synchronization Operation' <draft-zeilenga-ldup-sync-07.txt> as an Experimental RFC. The IESG would also like the IRSG or RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9612&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Ted Hardie. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-zeilenga-ldup-sync-07.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
Technical Summary Personal submission competitor to the LDUP-specified mechanism. Working Group Summary The working group knew and agreed to the production of an Experimental RFC along these lines. Protocol Quality The document was reviewed for the IESG by Ted Hardie. IESG Note The IESG notes that this work was originally discussed in the LDUP working group. The group came to consensus on a different approach, documented in RFC 3928; that document is on the standards track and should be reviewed by those considering implementation of this proposal.