ISO/IEC 9594-8:2005/Cor 4:2012
(Corrigendum)Information technology — Open Systems Interconnection — The Directory: Public-key and attribute certificate frameworks — Part 8: — Technical Corrigendum 4
Information technology — Open Systems Interconnection — The Directory: Public-key and attribute certificate frameworks — Part 8: — Technical Corrigendum 4
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — L'annuaire: Cadre général des certificats de clé publique et d'attribut — Partie 8: — Rectificatif technique 4
General Information
Relations
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9594-8:2005
TECHNICAL CORRIGENDUM 4
Published 2012-09-15
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Open Systems Interconnection —
The Directory: Public-key and attribute certificate frameworks
TECHNICAL CORRIGENDUM 4
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — L'annuaire: Cadre général des
certificats de clé publique et d'attribut
RECTIFICATIF TECHNIQUE 4
Technical Corrigendum 4 to ISO/IEC 9594-8:2005 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 6, Telecommunications and information
exchange between systems, in collaboration with ITU-T. The identical text is published as
Rec. ITU-T X.509 (2005)/Cor.4 (04/2012).
ICS 35.100.70 Ref. No. ISO/IEC 9594-8:2005/Cor.4:2012(E)
© ISO/IEC 2012 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 9594-8:2005/Cor.4:2012 (E)
INTERNATIONAL STANDARD
RECOMMENDATION ITU-T
Information technology – Open Systems Interconnection –
The Directory: Public-key and attribute certificate frameworks
Technical Corrigendum 4
(covering resolution to defect reports 353, 362, 365, 366, 368, 369, 372 and 373)
1) Correction of the defects reported in defect report 353
In Annex A, replace the definition for CertificatePair data type with:
CertificatePair ::= SEQUENCE {
issuedToThisCA [0] Certificate OPTIONAL,
issuedByThisCA [1] Certificate OPTIONAL }
(WITH COMPONENTS { ., issuedToThisCA PRESENT} |
WITH COMPONENTS { ., issuedByThisCA PRESENT})
2) Correction of the defects reported in defect report 362
Add clause 2.3 as follows:
2.3 Recommendations
– ITU-T Recommendation X.1252 (2010), Baseline identity management terms and definitions.
Insert the following new clause 3.2 after clause 3.1 and renumber subsequent clauses accordingly:
3.2 Baseline identity management terms and definitions
The following term is defined in Rec. ITU-T X.1252:
a) trust: The firm belief in the reliability and truth of information or in the ability and disposition of an
entity to act appropriately, within a specified context.
Delete the 'trust' definition from clause 3.3 (now clause 3.4) and renumber subsequent clauses accordingly.
For consistency purposes, modify the first paragraph of clause 18.2.1, Obtaining public-key certificates from the
directory, as shown:
Certificates are held within directory entries as attributes of type UserCertificate, CACertificate and
CrossCertificatePair. These attribute types are known to the Directory. These attributes can be operated on using the
same protocol operations as other attributes. The definition of these types can be found in clause 33.3; the specification
of these attribute types is defined in clause 11.2.
3) Correction of the defects reported in defect report 365
Update the definition for end-entity as shown:
3.34.27 end-entity: Either a public-key certificate subject that uses its private key for purposes other than signing
certificates, or an attribute certificate holder that uses its attributes to gain access to a resource, or an entity that is a
relying party.
Rec. ITU-T X.509 (2005)/Cor.4 (04/2012) 1
---------------------- Page: 2 ----------------------
ISO/
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.