You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/05/29 04:40:01 UTC

[jira] Updated: (DIRSNICKERS-41) Write DelRequest rules

The following issue has been updated:

    Updater: Alex Karasulu (mailto:aok123@bellsouth.net)
       Date: Fri, 28 May 2004 7:39 PM
    Changes:
             description changed from Write the delete request rules for the BERDigester.  

Here's the ASN.1 for both the request and the response:

        DelRequest ::= [APPLICATION 10] LDAPDN

        DelResponse ::= [APPLICATION 11] LDAPResult

Here's the raw tag nesting patterns for both the request and the response in that order where all the tag's have the constructed bit turned off:

Request Nesting
===============

-|---16 [0x10000000][38]--------SEQUENCE
-|-------2 [0x02000000][1]------------messageId
-|-------10 [0x4a000000][31]----------[APPLICATION 10] LDAPDN OCTET STRING
-|-------0 [0x80000000][0]------------controls
 v time

Response Nesting
================

-|---16 [0x10000000][71] ------------------- SEQUENCE
-|------- 2 [0x02000000][1] -------------------- messageId
-|-------11 [0x4b000000][64] ------------------- [APPLICATION 11] deleteResponse
-|-----------10 [0x0a000000][1] --------------------- ENUMERATED resultCode
-|----------- 4 [0x04000000][31] -------------------- matchedDN OCTET STRING
-|----------- 4 [0x04000000][10] -------------------- errorMessage OCTET STRING
-|----------- 3 [0x83000000][14] -------------------- referral
-|---------------4 [0x04000000][5] --------------------- LDAPURL   
-|---------------4 [0x04000000][5] --------------------- LDAPURL   
-|-------0 [0x80000000][0] --------------------- controls
 to Write the delete request rules for the BERDigester.  

Here's the ASN.1 for both the request and the response:

        DelRequest ::= [APPLICATION 10] LDAPDN

        DelResponse ::= [APPLICATION 11] LDAPResult

Here's the raw tag nesting patterns for both the request and the response in that order where all the tag's have the constructed bit turned off:

Request Nesting
===============

-|---16 [0x10000000][38]--------SEQUENCE
-|-------2 [0x02000000][1]------------messageId
-|-------10 [0x4a000000][31]----------[APPLICATION 10] LDAPDN OCTET STRING
-|-------0 [0x80000000][0]------------controls
 v time

Response Nesting
================

-|---16 [0x10000000][71] ------------------- SEQUENCE
-|------- 2  [0x02000000][1] ------------------- messageId
-|-------11 [0x4b000000][64] ------------------- [APPLICATION 11] deleteResponse
-|-----------10 [0x0a000000][1] ---------------------- ENUMERATED resultCode
-|----------- 4  [0x04000000][31] -------------------- matchedDN OCTET STRING
-|----------- 4  [0x04000000][10] -------------------- errorMessage OCTET STRING
-|----------- 3  [0x83000000][14] -------------------- referral
-|---------------4 [0x04000000][5] --------------------- LDAPURL   
-|---------------4 [0x04000000][5] --------------------- LDAPURL   
-|-------0 [0x80000000][0] --------------------- controls

    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/DIRSNICKERS-41?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSNICKERS-41

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSNICKERS-41
    Summary: Write DelRequest rules
       Type: Task

     Status: In Progress
   Priority: Major

    Project: Directory Snickers
 Components: 
             LDAP Provider

   Assignee: Alex Karasulu
   Reporter: Alex Karasulu

    Created: Sun, 18 Apr 2004 1:19 PM
    Updated: Fri, 28 May 2004 7:39 PM

Description:
Write the delete request rules for the BERDigester.  

Here's the ASN.1 for both the request and the response:

        DelRequest ::= [APPLICATION 10] LDAPDN

        DelResponse ::= [APPLICATION 11] LDAPResult

Here's the raw tag nesting patterns for both the request and the response in that order where all the tag's have the constructed bit turned off:

Request Nesting
===============

-|---16 [0x10000000][38]--------SEQUENCE
-|-------2 [0x02000000][1]------------messageId
-|-------10 [0x4a000000][31]----------[APPLICATION 10] LDAPDN OCTET STRING
-|-------0 [0x80000000][0]------------controls
 v time

Response Nesting
================

-|---16 [0x10000000][71] ------------------- SEQUENCE
-|------- 2  [0x02000000][1] ------------------- messageId
-|-------11 [0x4b000000][64] ------------------- [APPLICATION 11] deleteResponse
-|-----------10 [0x0a000000][1] ---------------------- ENUMERATED resultCode
-|----------- 4  [0x04000000][31] -------------------- matchedDN OCTET STRING
-|----------- 4  [0x04000000][10] -------------------- errorMessage OCTET STRING
-|----------- 3  [0x83000000][14] -------------------- referral
-|---------------4 [0x04000000][5] --------------------- LDAPURL   
-|---------------4 [0x04000000][5] --------------------- LDAPURL   
-|-------0 [0x80000000][0] --------------------- controls



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira