X.500 Standard status
(Implementors' Guide)
How to be involved
More Information
Tutorial section 1
X.500 General
Tutorial section 2
X.509 specific
X.509 at work
This defect register contains a list of Defect Reports (DRs).
To submit a new Defect Report please click here.
Defects Reports are in theory handled by a Defect Report editing group with country representation. However, resolution of Defect Reports is mainly done on our mailing list and/or at meetings. When there appears to be some agreement on the resolution, the result may either be:
A DTC is related to a particular edition and part of the X.500 standards. As a DR may affect up to two editions and several parts, the same DR may be reflected in several DTCs.
A DTC may include the result from several DRs.
When a DTC has been completed, it sent to the ISO/IEC JTC1/SC6 for a 3 month ballot among members (National Bodies). If the text is approved, the Draft Technical Corrigenda is turned into a final (Technical) Corrigendum (abbreviated to f). Several DTCs may be included in a single Cor.
The table below gives a list of DRs. If a DR has been resolved and a suggested text has been created, links are given to the resulting DTCs or Cors. When the DTC has successfully passed the ballot, these links are changed to the resulting Cors.
The notation for a link consists of three fields separated by hyphens. The first field indicates the part of the standard affected by the DTC or Cor. The second field indicates the edition of that part and the third field indicates whether it is DTC or Cor and its number.
|
DR |
Description of Defect |
Source |
Cor(s)/DTC(s) |
Status |
|
Handling of unknown operation code |
Erik |
- |
Discussion | |
|
Recursive structure rules |
Jean-Paul |
- |
Discussion | |
|
Inconsistency in IdmResult |
Jean-Paul |
- |
Discussion | |
|
ASN.1 errors in Association-informationBind related data types |
Jean-Paul |
- |
Discussion | |
|
ASN.1 error in ABRT-apdu |
Jean-Paul |
- |
Discussion | |
|
Error in the X.509 crossCertificatePair attribute type |
Erik |
- |
Discussion | |
|
Misleading text in X.509 |
Jean-Paul |
Discussion | ||
|
ASN.1 errors in temporal examples |
Erik |
Discussion | ||
|
IDM version negotiation |
Erik |
Discussion | ||
|
Clarification of UII Format attribute type and tag-bases object classes |
Erik |
- |
Discussion | |
|
Trust anchor vs. trust anchor information |
Erik | |||
|
Compatibility problem between X.519 and ROSE for reject |
Jean-Paul |
Discussion | ||
|
Backward compatibility problem in DOP |
Jean-Paul |
Discussion | ||
|
Bad references to Unbind specifications |
Erik |
Is fixed for 6th ed. | ||
|
Certificate terminology |
Erik |
Is fixed for 6th ed. | ||
|
Definition of Root Naming Context |
Erik |
Is fixed for 6th ed. | ||
|
Wrong reference to ISO 3166 |
Erik |
Is fixed for 6th ed. | ||
|
Missing bit in ServiceControlOptions |
Erik |
Is fixed for 6th ed. | ||
|
Critical extension specified for SPKM in Bind |
Erik |
Is fixed for 6th ed. | ||
|
Separation of DSA-DSA Binds from Directory (DAP) Bind |
Erik |
X.501-Ed5-DTC3 |
Discussion | |
|
Error in transport of LDAP messages |
Erik |
- | ||
|
Error code for IDM directoryBindError |
Erik |
Is fixed for 6th ed. | ||
|
Basic Access Control decision point for replaceValues |
Erik |
Discussion | ||
|
Transcoding TeletexString to Unicode |
Erik |
- |
Discussion | |
|
OID clash for attribute types extensions |
Erik |
Is fixed for 6th edition | ||
|
Presence matching rules for certificate extensions |
Erik |
Is fixed for 6th edition | ||
|
Value reference for OID in X.509 |
Erik |
Is fixed for 6th edition | ||
|
Editorial in Scope clause of X.509 |
Hoyt |
Resolved | ||
|
Partially known critical extensions |
D. Chadwick |
Resolved | ||
|
Redundant information in Bind |
Erik |
Resolved | ||
|
Data integrity in storage |
Erik |
Resolved | ||
|
String matching rule |
Erik |
Resolved | ||
|
Error in protected password definition |
AFNOR |
Resolved | ||
|
Telephone number syntax and matching |
Erik |
Resolved | ||
|
The exclusions component of CommonArguments |
Erik |
Resolved | ||
|
Remove dangling references to end-to-end |
Erik |
Resolved | ||
|
Attribute subtype problem |
Erik |
Resolved | ||
|
Signing of Bind Errors |
Erik |
Resolved | ||
|
serialNumber in certficates as specified in |
AFNOR |
Liaison to PKIX |
Rejected | |
|
Remove dangling references to end-to-end encryption |
Erik email |
Resolved | ||
|
Handling of unknown NSAP address structures |
Erik email |
X.501-Ed5-Cor1 |
Resolved | |
|
Embedded PDV; Support PER |
AFNOR |
Resolved | ||
|
Wrong reference and missing text |
Erik email |
Resolved | ||
|
Errors in Managed object Definitions |
Erik email |
Resolved | ||
|
Name constraints extension alignment with RFC 3280 |
Stefan email |
Resolved | ||
|
ServiceProblem error in ITU-T Rec. X.511 - ISO/IEC |
Erik email |
Resolved | ||
|
ASN.1 errors in ITU-T Rec. X.501 |
Erik email |
Resolved | ||
|
Differences between crl and crl entry extensions |
Sharon email |
Resolved | ||
|
Unrecognised crl and crl entry extensions |
Sharon email |
Resolved | ||
|
Mandadting that unavailableCriticalExtension be returned if extension not supported |
UK ballot #5 |
Resolved | ||
|
validity in SimpleCredentials missing OPTIONAL |
Erik email |
Resolved | ||
|
Incorrect clause cross reference |
Erik email |
Resolved | ||
|
ASN.1 Error introduced by DR225 |
Erik email |
Resolved | ||
|
IDP Extension |
Sharon email |
Resolved | ||
|
old RSA encryption algorithm OID |
Sharon email |
Resolved | ||
|
303 |
Attribute value preserved as supplied |
Sharon email |
- |
?? |
|
Skip Certs in policy constraints |
Sharon email |
- |
?? | |
|
Base CRL window |
Sharon /NIST2 |
Resolved | ||
|
Basic constraints requirement for path |
Sharon /NIST2 |
Resolved |
For previous defect reports, please click here.