| Recommendation | International Standard | Defect N° | Date | Nature of defect | Solution | Technical Corrigendum |
| Rec. ITU-T X.680 | ISO/IEC 8824-1 | 1 | 2008/07 | Inconsistency between C.3.2.2.h and 29.5c. | Automatic tagging should take place before a CHOICE is sorted in "NamedType" order not afterwards. | Cor.1 (10/2011) |
| | 2 | 2010/04 | The amendments on ISO/IEC 10646 (particularly Amd. 4) should be considered. | A note will be added specifying that ASN.1 is compatible with ISO/IEC 10646:2003. | Cor.1 (10/2011) |
| | 3 | 2010/06 | Typo in 12.27. | "and" was replaced with "an". | Cor.1 (10/2011) |
| | 4 | 2011/09 | Object identifiers in examples do not begin with {joint-iso-itu-t(2) example(999)}. | All object identifiers in examples were reviewed. | Cor.2 (03/2014) |
| | 5 | 2011/11 | Clarification about white-space around "XMLValue" in "XMLTypedValue" for an "XMLRestrictedCharacter StringValue". | Clauses 16.2 and 41.9 were modified. | Cor.2 (03/2014) |
| | 6 | 2012/12 | Non breaking characters (white-space and hyphen) are not mentioned in clause 11. | These characters were added. | Cor.2 (03/2014) |
| | 7 | 2013/06 | Clauses 50.6 and 50.8 are only applicable to extensible types and are not consistent with annex I. | Two new clauses were added to before existing 50.6 and 50.8 respectively. | Cor.2 (03/2014) |
| | 8 | 2013/06 | Typo in 50.1 note 7. | 12.3 was replaced with 12.10 in the note | Cor.2 (03/2014) |
| | 9 | 2013/08 | D.2 does not contain the object identifier related to extended XER. | This object identifier was added. | Cor.2 (03/2014) |
| | | | | | |
| Rec. ITU-T X.681 | ISO/IEC 8824-2 | 1 | 2009/11 | The conditions of error in E.2 are not correct in case of an extensible object set. | In that case, it is not an error if field marked as UNIQUE is not found in the object set. | Cor.1 (10/2011) |
| | | | | | |
| Rec. ITU-T X.682 | ISO/IEC 8824-3 | 1 | 2013/06 | The "UserDefinedCons traintParameter" production in Annex B is not correct | Annex B was changed to use the same production as clause 9.3. | Cor.1 (03/2014) |
| | | | | | |
| Rec. ITU-T X.683 | ISO/IEC 8824-4 | 1 | 2011/09 | Object identifiers in examples do not begin with {joint-iso-itu-t(2) example(999)}. | All object identifiers in examples were reviewed. | Cor.1 (03/2014) |
| | 2 | 2013/06 | Clause 8.4 is not consistent with Rec. ITU-T X.680 | ISO/IEC 8824-1 16.8 | The scope of a "DummyReference" was reviewed | Cor.1 (03/2014) |
| | | | | | |
| Rec. ITU-T X.690 | ISO/IEC 8825-1 | 1 | 2005/04 | UTF8String is missing in 8.23.5 | Clause 8.23.5 was updated | Cor.1 (10/2011) |
| | 2 | 2005/04 | Canonical encoding of GeneralizedTime value when local time is used | A local time value is distinct from UTC value abstract syntax but the encodings are the same. The problem is solved with the TIME type. | No corrigendum needed. |
| | 3 | 2010/06 | The amendments on ISO/IEC 10646 (particularly Amd. 4) should be considered. | A note was added specifying that ASN.1 is compatible with ISO/IEC 10646:2003. | Cor.1 (10/2011) |
| | 4 | 2011/08 | Object identifiers in examples do not begin with {joint-iso-itu-t(2) example(999)}. | All object identifiers in examples were reviewed. | Cor.2 (03/2014) |
| | | | | | |
| Rec. ITU-T X.691 | ISO/IEC 8825-2 | 1 | 2005/04 | Canonical encoding of GeneralizedTime value when local time is used. | A local time value is distinct from UTC value abstract syntax but the encodings are the same. The problem is solved with the TIME type. | No corrigendum needed. |
| | 2 | 2009/07 | Clause 23.7 does not mention the encoding of the chosen alternative. | The encoding of the chosen alternative is present in that case and 23.7 was changed. | Cor.1 (10/2011) |
| | 3 | 2010/06 | Clause 3.7.20 contains "two's complement binary number" instead of "non-negative-binary-integer". | Clause 3.7.20 was changed. | Cor.1 (10/2011) |
| | 4 | 2010/06 | In clause 11.1.3, the number of bits to be appended is "one to seven" instead of "zero to seven". | Clause 11.1.3 was changed. | Cor.1 (10/2011) |
| | 5 | 2010/06 | The amendments on ISO/IEC 10646 (particularly Amd. 4) should be considered. | A note was added specifying that ASN.1 is compatible with ISO/IEC 10646:2003. | Cor.1 (10/2011) |
| | 6 | 2010/07 | The note after 13.2.6 is only for PER Aligned variant. | The note was changed. | Cor.1 (10/2011) |
| | 7 | 2013/03 | Clause 11.1.1 requires that for a the encoding of bit string with a content constraint shall contain a multiple of 8 bits. | Clause 11.1.1 was reviewed to apply only to octet string. | Corr.2 (04/2012) |
| | 8 | 2013/11 | Clauses 10.3.22 and 23.5 are not consistent about usage of extension bit. | Clauses 19.1 and 23.5 was changed. | Cor.3 (under ballot) |
| | | | | | |
| Rec. ITU-T X.692 | ISO/IEC 8825-3 | 1 | 2008/12 | ECN alignment is not fully defined for built-in encoding objects. | The alignment was be specified in clause 18.2.3. | Cor.1 (10/2011) |
| | 2 | 2009/07 | Errors in Annex D (examples) | Annex D was be reviewed and replaced. | Cor.1 (10/2011) |
| | | | | | |
| Rec. ITU-T X.693 | ISO/IEC 8825-4 | 1 | 2005/04 | Canonical encoding of GeneralizedTime value when local time is used. | A local time value is distinct from UTC value abstract syntax but the encodings are the same. The problem is solved with the TIME type. | No corrigendum needed. |
| | 2 | 2010/06 | The amendments on ISO/IEC 10646 (particularly Amd. 4) should be considered. | A note was added specifying that ASN.1 is compatible with ISO/IEC 10646:2003. | Cor.1 (2011/10) |
| | 3 | 2011/09 | Object identifiers in examples do not begin with {joint-iso-itu-t(2) example(999)}. | All object identifiers in examples were reviewed. | Cor.2 (03/2014) |
| | 4 | 2011/01 | Clarification about white-space in XML encodings and XML value notation. | It related to the defect 5 of Rec. ITU-T X.680 | ISO/IEC 8824-1. Clause 31.3.4.1 was changed. | Cor.2 (03/2014) |
| | | | | | |
| Rec. ITU-T X.694 | ISO/IEC 8825-5 | 1 | 2010/06 | The amendments on ISO/IEC 10646 (particularly Amd. 4) should be considered. | A note was added specifying that ASN.1 is compatible with ISO/IEC 10646:2003. | Cor.1 (10/2011) |
| | 2 | 2011/11 | Clarification about white-space in XML encodings and XML value notation. | The clause 12.4.1.4 was be modified. | Cor.2 (03/2014) |
