Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 2511 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 2511.

Report 2511 Actions

    Problem Report Number 2511
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0678
    Raised 2006-02-17 08:18
    Updated 2006-02-22 19:22
    Published 2006-02-22 19:22
    Product Standard LDAP Certified
    Certification Program The Open Brand certification program
    Test Suite VSLDAP version 2.2 GA
    Test Identification not relevant
    Specification IETF RFC2253
    Location in Spec Par.3
    Problem Summary The Extras.ldif file cannot be imported
    Problem Text The extras.ldif file cannot be imported due to incorrect DN in respect
    with RFC 2849 and RFC 2253 :

    the following entry seems to be incorrect :
    dn: cn=Billy Bakers, OID.2.5.4.11=Corporate Tax, ou=Fin-Accounting,
    ou=Americas, ou=Search, o=IMC, c=US

    with the componentName OID.2.5.4.11=Corporate Tax.

    It should be 2.5.4.11=..., without 'OID.'.

    RFC 2253 #3 reads :

    attributeTypeAndValue = attributeType "=" attributeValue

    attributeType = (ALPHA 1*keychar) / oid
    keychar = ALPHA / DIGIT / "-"

    oid = 1*DIGIT *("." 1*DIGIT)


    DN should be
    dn: cn=Billy Bakers, 2.5.4.11=Corporate Tax, ou=Fin-Accounting,
    ou=Americas, ou=Search, o=IMC, c=US

    instead of
    dn: cn=Billy Bakers, OID.2.5.4.11=Corporate Tax, ou=Fin-Accounting,
    ou=Americas, ou=Search, o=IMC, c=US

    Review Information

    Review Type TSMA Review
    Start Date 2006-02-17 08:18
    Last Updated 2006-02-20 22:33
    Completed 2006-02-20 22:33
    Status Complete
    Review Recommendation Rejected (REJ)
    Review Response As stated in RFC2253, "Implementations MUST allow an oid in the
    attribute type to be prefixed by one of the character strings "oid." or
    "OID.".", so it is agreed that the prefix oid or OID is a valid syntax.
    A REJ is recommeneded.

    Review Type SA Review
    Start Date 2006-02-20 22:33
    Last Updated 2006-02-22 00:52
    Completed 2006-02-22 00:52
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion The specification explicitly states that "Implementations MUST allow
    an oid in the attribute type to be prefixed by one of the character
    strings "oid." or "OID."." thus this PR is rejected as a TSD.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority