Protocol Action: 'LDAP Cancel Operation' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 19 April 2004 22:47 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18132 for <ietf-announce-archive@ietf.org>; Mon, 19 Apr 2004 18:47:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFhY9-000327-Mb for ietf-announce-archive@ietf.org; Mon, 19 Apr 2004 18:47:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFhX9-0002iN-00 for ietf-announce-archive@ietf.org; Mon, 19 Apr 2004 18:46:36 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFhWC-0002Ok-00 for ietf-announce-archive@ietf.org; Mon, 19 Apr 2004 18:45:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFhCO-0005Ww-GI; Mon, 19 Apr 2004 18:25:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BFgJP-00050N-Dh for ietf-announce@optimus.ietf.org; Mon, 19 Apr 2004 17:28:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11751 for <ietf-announce@ietf.org>; Mon, 19 Apr 2004 17:28:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BFgJM-0005er-VJ for ietf-announce@ietf.org; Mon, 19 Apr 2004 17:28:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BFgIU-0005Q1-00 for ietf-announce@ietf.org; Mon, 19 Apr 2004 17:27:23 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BFgHf-0005BV-00; Mon, 19 Apr 2004 17:26:31 -0400
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BFgCQ-0003Ls-J0; Mon, 19 Apr 2004 17:21:06 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'LDAP Cancel Operation' to Proposed Standard
Message-Id: <E1BFgCQ-0003Ls-J0@optimus.ietf.org>
Date: Mon, 19 Apr 2004 17:21:06 -0400
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'LDAP Cancel Operation '
   <draft-zeilenga-ldap-cancel-11.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Ted Hardie.

Technical Summary
 
The Lightweight Directory Access Protocol (LDAP) [RFC3377] provides an
  Abandon operation [RFC2251] which clients may use to cancel other
  operations.  The Abandon operation does not have a response and calls
  for there to be no response of the abandoned operation.  These
  semantics provide the client with no clear indication of the outcome
  of the Abandon operation.   The LDAP Cancel operation should be used 
   instead of the LDAP Abandon operation when the client needs an indication
  of the outcome.  This operation may be used to cancel both interrogation 
  and update operations.
 
Working Group Summary

This is an individual submission, but there are working group documents
 (e.g. the LDUP working group's LCUP specification) which depend on it.
 There were no issues raised during Last Call, and the IETF LDAP community
 seems to be in favor adopting this mechanism as a parallel mechanism
 to the DAP abandon operation.
  
Protocol Quality
 
This document was reviewed for the IESG by Ted Hardie.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce