hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.3.1 Calling line identification presentation | No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.3.2 Calling line identification restriction | No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.4 Completion of calls to busy subscriber | No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.5 Diversion services | |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.5.1 Call forwarding unconditional | The subaddress associated with the original called party number shall not be forwarded if the call is forwarded. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.5.2 Call forwarding busy | The subaddress associated with the original called party number shall not be forwarded if the call is forwarded. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.5.3 Call forwarding no reply | The subaddress associated with the original called party number is delivered to the original called party and shall not be forwarded if the call is forwarded. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.6 Freephone | No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.7 Malicious call identification | No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.8 Multiple Subscriber Number | Not applicable. The two services shall not be provided together. ETSI TR 102 089 V1.1.1 (1998-12) 14 |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.9 Subaddressing | Not applicable. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.10 Connection Type Service | Not applicable. The two services shall not be provided together. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.11 Three party | No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 6.5.12 Message Waiting Indication | No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7 Connection Type Service (CTS) service description | |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.1 Description | The "Connection Type Service" (CTS) supplementary service shall apply to an analogue access. The CTS enables the calling user with the possibility of sending a Connection Type information to the called user. The CTS provides the called user with the possibility of receiving a Connection Type information. The network sh... |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2 Procedures | |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.1 Provision and withdrawal | The CTS shall either be provided after prior arrangement with the service provider or generally available. As a service provider option, the calling user can select a valid CTS as a default permanent value to be applied to the calling user's line or MSN. The CTS shall be withdrawn by the service provider upon the reque... |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.2 Normal procedures | |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.2.1 Registration and erasure | Not applicable |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.2.2 Activation and deactivation | Not applicable ETSI TR 102 089 V1.1.1 (1998-12) 15 |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.2.3 Invocation and operation | |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.2.3.1 Calling user side | During the call set-up the calling user can insert the CTS information which shall then be transported by the network form the calling user to the called user. The invocation procedure for the CTS service on the calling user side shall be "*08* CTS #". The CTS codes are shown in table 7.1. The service code "08" is unde... |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.2.3.2 Called user side | The network shall provide the called user with the Connection Type information. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.2.4 Interrogation | Not applicable. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.3 Exceptional procedures | |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.3.1 Registration and erasure | Not applicable. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.3.2 Activation and deactivation | Not applicable. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.3.3 Invocation and operation | In some interworking situations in which the information is not supported by sufficient signalling capability, the called user may receive no CTS information. If the CTS information cannot be transported to the user, the calling user shall not be given an indication that this has occurred. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.2.3.4 Interrogation | Not applicable. |
172515ee0aa129d07f6479a18965f721 | 102 089 | 7.3 Terminal assignment | Specific TE has to be used. ETSI TR 102 089 V1.1.1 (1998-12) 16 Annex A (informative): Parameter coding This annex describes the enhancements to the subscriber line protocol to support the MSN, SUB and CTS supplementary services over the PSTN. The LE shall use the Selection of Terminal Function parameter, as specified ... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 1 Scope | The present document provides the User Requirement Specifications for Mission Critical Broadband Communications. The present document describes the functionalities which are most needed by users and the requirements they make on the technology The present document is applicable to the specification of Mission Critical ... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 170 001: "Project MESA; Service Specification Group - Services and Applications; Statement of Requirements (SoR)". [i.2] ETSI TR 102 021-2 (V1... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 3 Definitions and abbreviations | |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: mission critical broadband: work programme within ETSI Project TETRA to enhance the services and facilities of TETRA, Tetrapol and P25 in order to meet new user requirements, utilize new technology and meet user needs into the future w... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ANPR Automatic Number Plate Recognition API Application Programming Interface APL Automatic Person Location AVL Automatic Vehicle Location AVLS Automatic Vehicle Location System BB Broad Band solution for PMR CCC Command & Control Centre COM C... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4 Mission Critical Broadband Requirements | |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.1 General | With increasing use of data in PPDR, capacity issues for voice and data on existing TETRA 1,TETRAPOL and P25 networks together with the user experience of 3G terminals and applications there has been an increasing demand for more data throughput on PPDR systems. TEDS goes some way in this direction and requirements for... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.2 Systems Requirements for Professional Users | Analysis Masons concluded in their report for the TETRA Association, now the TETRA and Critical Communications Association [i.3] that the requirements that PPDR and other users have of their systems today to support their way of working will be needed for BB too. These are: • Availability - in time (often) specified as... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.3 Operational Requirements | The services required should be built upon that offered in the TETRA, TETRAPOL and P25 standards. These include for voice:- Group calls, encrypted individual and group calls with authentication, individual calls to command centre PABX and /or public telephone networks, direct mode operation between terminals, emergency... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4 Application requirements of PPDR | In the Analysis Masons study [i.3] they summarised all of the findings of the TETRA Association, now called the TETRA and Critical Communications Association and presented case studies and possible scenarios for the evolution of data that included as an option full multi-media reliance. This is the scenario that is mos... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4.1 Location data | This covers automatic person or vehicle location data being fed back from terminals to the command and control centre as well as positioning information or directions being fed back to terminals. These applications are available today. Whilst the package size for such information is small (SDS) the use of high reportin... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4.2 Multi-media | Included in this is: • video to and from the command and control centre during pursuit so that other units may be informed and intervene; • video for fixed observation of people or other assets (stakeout); • video at the scene of a disaster or event to inform command and control; • video conferencing; • the broadcast o... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4.3 Office applications | The anticipated needs are PDA/PIM synchronisation and mobile workspace including public internet access. These functions are being satisfied currently by devices such as smartphone but there is a desire to have this functionality in the same terminal as other communications and within the same secure system. |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4.4 Download operational information | This envisages: • the supply of text and image data from the command and control centre to terminals in the field and net centric working; • ANPR update hit list; • the downloading of maps with annotations to field units and the downloading of command and control information such as task management and briefings. |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4.5 Upload operational information | This mirrors the category above and includes: • the sending of incident information to the command and control centre; • status information tied with location (currently supported), for ANPR/speed control an automatic upload to the database including picture evidence from temporary fixed cameras and from vehicles; • th... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4.6 Online database enquiry | There is a need to make operational searches of own and external databases. Particular cases are: • remote medical databases; • number plate checking; ETSI ETSI TR 102 022-1 V1.1.1 (2012-08) 12 • biometrics such as fingerprints, cargo data; • crash recovery (enquiry and updates). |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.4.7 Miscellaneous | This set of requirements include: • the ability to update firmware, software and device & application settings over the air; • GIS map updates over the air; automatic telemetry such as remote control and the presentation of information from static sensors; • capacity to be able to manage a large amount of communication... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.5 Ranking of the Criticality of Applications. | In the LEWP/RCEG matrix of 40 applications the urgency of availability was rated as "now", "short" (<2 yr), "medium"(2 yr to 5 yr) and "long"(>5 yr).Not surprisingly of the 12 in the "now" category 11 are reported as partly used already although the one excluded (AVL) is definitely operational. 4.5.1 Highest Priority, ... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.6 Expected Capability of TEDS | The packet data throughput rate (table 1) that is achieved for TEDS is based on the level of QAM modulation and the bandwidth. The initial bandwidth being offered by manufacturers is 50 kHz. The maximum rate therefore is with the highest level of 64QAM (coefficient of 1) i.e. about 150 kbit/s. This is not likely to be ... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.7 Applications identified today that cannot be met by TEDS | Table 2 has been used to look at how data requirements may be met with TETRA. This is very general though and does not consider the use case or the competing requirement for voice. For example if the receiving device for a photograph is a handheld terminal with a small display then high resolution images may not be ver... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 4.8 Ranking of those Applications by Customer Need | Of the three applications identified the priorities for the LEWP group based on their urgency of requirement are: • Video at disasters to inform co-ordinators, managers, etc. • Video back to the command and control centre during chases to allow intervention. • Hotspot mobile communication centres. These examples of urg... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 5 If LTE is chosen | LTE defines a high speed radio access for IP, but 3GPP LTE standardisation scope does not define any PMR specific services (no TETRA like Group or PTT services covered). TETRA voice services may therefore have to be provided outside of the 3GPP LTE standard and LTE radio access network scope. The most obvious solution ... |
a87064b515d19ca6683cf7218bb7eb71 | 102 022-1 | 5.1 Some Blue Sky Applications for the Future. | Some Blue Sky Applications for the Future (source: Analysis Masons Report [i.3]): • 3-D video forensics • Tele -health • High quality, evidential facial recognition applications ETSI ETSI TR 102 022-1 V1.1.1 (2012-08) 18 Annex A: LEWP Matrix of Requirements The following is an extract from the matrix showing all the ap... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 1 Scope | The present document records comments and issues raised with the ETSI TC ESI on Technical Specifications and on Technical Reports published for Electronic Signatures and Infrastructures, and in some cases proposes resolution for these issues. These comments may result in new versions of some or all of these specificati... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI TR 102 317: "Electronic Signatures and Infrastructures (ESI); Process and tool for maintenance of ETSI deliverables". [2] ETSI TS 101 456: "Policy requirements for certification authorities issuing qualified certificates". [3] ETSI ... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 3 Definitions and abbreviations | For the purposes of the present document, the terms, definitions and abbreviations given in TS 101 456 [2], TS 102 042 [3], TS 101 733 [4], TS 101 903 [5], TS 101 861 [6], TS 101 862 [7], TS 102 023 [8], TR 102 038 [9] and TR 102 041 [10] apply. |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 4 Role and structure of the present document | |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 4.1 Role of the present document in the maintenance process | The current document is the resolute of an ongoing maintenance process for ETSI Technical Specifications and Technical Reports in the area of Electronic Signatures and Infrastructures. The document: a) Provides a means of tracking the contributions received. b) Organizes the contributions under the relevant document he... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 4.2 Structure of the present document | |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 4.2.1 Clause 5: fields and structure | Clause 5 constitutes the main part of the present document, it is the outcome of the organizing the contributions under the relevant heading and records the proposed resolution of the comment. The elementary comments and their metadata will be inserted in a database; the tables for each deliverable included in the clau... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 4.2.2 Annex A: Fields and structure | Annex A collects all comments received in their original format grouped by originator, then by deliverable. Annex A is the outcome of the tracking phase and could be intended as a historical section. If the text received as a whole includes comments on more deliverables, the text is splitted into blocks, each related t... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5 Comments | This clause collects all the elementary comments obtained by pre-processing the original contributions in a structured format. |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.1 TS 101 456 - Qualified certificate policy | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TS101456-001 1.2.1 7.4.8 TC-ESI_1-001 14/03/2003 technical not yet processed Comment text In clause 7.4.8 subsection CA General an ad... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.2 TS 101 733 - ES electronic signature formats | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TS101733-001 1.4.0 UNSTT-003 01/09/2002 editorial STF242 02/09/2003 already applied 1.5.1 Comment text References to the various RFCs... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.3 TS 101 861 - Time stamping profile | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TS101861-001 1.2.1 5.1.2 JCPKI-004 17/02/2003 editorial STF242 21/06/2003 in process Comment text Please add "One of" to the beginnin... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.4 TS 101 862 - Qualified certificate profile | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TS101862-001 1.2.1 2 UNSTT-005 editorial STF242 09/01/2004 applied 1.3.1 Comment text Since TS 101 862 has been published, RFC 2459 h... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.5 TS 101 903 - XML advanced electronic signatures (XAdES) | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TS101903-001 1.1.1 JCPKI-003 17/02/2003 Technical STF242 25/01/2004 no change Comment text Rationale: Some comments regarding EESSI S... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.6 TS 102 023 - Time stamping policy | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TS102023-001 1.1.1 Introduction UNSTT-006 editorial not yet processed Comment text Modify the text: "The quality of this evidence is ... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.7 TR 102 038 - XML format for signature policies | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TR102038-001 1.1.1 JCPKI-006 17/02/2003 technical STF242 21/06/2003 no change Comment text To describe about OCSP trust condition, bo... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.8 TR 102 041 - Signature policies report | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TR102041-001 1.2.1 8.3.1 JCPKI-007 17/02/2003 technical STF242 21/06/2003 no change Comment text In this clause, the Reports describe... |
17670891e5db8e58b2d6e51eabf17e85 | 102 046 | 5.9 TS 102 042 - PKC certificate policy | Comment ID Deliverable version Deliverable clause Original contribution reference Comment date Comment type Resolution source Resolution date Resolution status Deliverable target version TS102042-001 1.2.1 2 UNSTT-002 editorial not yet processed Comment text Update the reference "FIPS PUB 140-1 (1994): "Security Requir... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 1 Scope | The present document identifies a set of requirements that will provide a basis for a subsequent standard, which will then build policy requirements for attributes certified by Attribute Authorities or Certification Authorities complying with [4] and related standards. In some electronic signature applications, roles a... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] ETSI TS 101 733: "Electronic Signatures and Infrastructures (ESI); Electronic Signature Formats". [2] ETSI TR 102 041: "Signature Policies Report". [3] Directive 1999/93/EC of the European Parliament and of the Council of 13 December 19... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 3 Definitions and abbreviations | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: attribute: information bounded to an entity that specifies a characteristic of an entity, such as a group membership or a role, or other information associated with that entity Attribute Authority (AA): authority trusted by one or more... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AA Attribute Authority AC Attribute Certificate ACA Attribute Certification Authority ACP Attribute Certificate Policy ACPS Attribute Certification Practice Statement AIA Attribute Issuing Authority ASN.1 Abstract Syntax No. 1 CA Certification... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 4 Implications from the requirements of the Directive | Directive [3] article 2(3) states that: "'signatory' means a person who … acts either on his own behalf or on behalf of the natural or legal person or entity he represents", introduces the need to define under which role do subjects sign. Directive [3], annex I specifies that: "Qualified certificates must contain (…) …... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5 European surveys | A survey has been performed in order to ascertain, at least in Europe: 1) if the current requirements of personnel certification, by accredited certification bodies, matches the forecast usage of attribute certificates; 2) currently implemented attribute certificate usage. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5.1 Personnel certification | In addition to perusing EAC/G4, the following certification organizations accredited by national bodies have been contacted, by phone and by e-mail: France - AFNOR - BRGM (BUREAU RECHERCHE GEOLOGIQUES MINIERES (see note) Germany - TGA-GMBH (see note) - TUV Akademie Rheinland - Koeln Italy - CEPAS (see note) Documentati... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 5.2 Currently implemented attribute certificate usage | A survey within the PERMIS European project has been performed. The following three organizations participating to the PERMIS project have been contacted: 1) Municipality of Bologna. 2) Safelayer Secure Communications S.A. - Camerfirma (Partners in the Municipality of Barcelona implementation). ETSI ETSI TR 102 044 V1.... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6 Various kinds of attributes | An attribute may specify group memberships, roles, or other authorization information. This clause lists examples of attributes and their uses. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.1 Group memberships | Group membership apply to hierarchical groups or functional groups. Hierarchical groups involve several persons belonging to the same organization branch of an enterprise or a company. It specifies the position of the individual within an enterprise or a company. Functional groups involve several persons having the sam... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.2 Roles | A role is a way of expressing an organizational or functional responsibility. The responsibility is often mirroring a user's job title. It may be fulfilled by just one person (e.g. head of department) or by several persons. A role also designates an individual's status in a particular society. It corresponds to a socia... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.3 Other authorization information | In this category, two authorization information are being considered: • proxies; and • capabilities. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.3.1 Proxies | A subject may sign on behalf of another individual, either under the name of that individual or under an attribute from that individual. The person delegating its signature may like to restrict the use of its attributes, so that the signature can only be applied under some signature policies or/and for some commitment ... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 6.3.2 Capabilities | Capabilities are well known when used in an access control context. In a capability-based system, access to protected objects such as files is granted if the would-be accessor possesses a capability for the object. The capability can be implemented by using a token that gives the bearer or holder the right to access a ... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 7 Claimed and certified attributes | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 7.1 Claimed attributes | An attribute may be claimed instead of being certified. When it is claimed, the claimant will be responsible for the assertion and in case the assertion is proven to be false, it will have to support the consequences. When the role is a company role, and if the verifier finds out later on that the signer did not had th... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 7.2 Certified Attributes | When an attribute is certified, it is certified by an ACA based information provided by an AIA. The same organization may be in charge of both the ACA function and the AIA function; in such a case attributes are said to be directly-certified. When different organizations are involved, the ACA takes the information prov... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 7.2.1 The Attribute Issuing Authority | In EN 45013 [9], clause 2.5 mentions: "Document issued under the rules of a certification system, indicating that adequate confidence is provided that the named person is competent in performing specific services." The AIA is an authority that ascertains "that the named person is competent in performing specific servic... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 7.2.2 Directly certified attributes | Attributes are directly certified when the authority issuing the certificate (i.e. the ACA) is also the authoritative source of an attribute (i.e. the AIA). This is the case, for example for judges which are testified by the official bodies (i.e. the Lord Chancelor Department for judges). This may also be the case for ... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 7.2.3 Verified attributes | Attributes are verified when the authority issuing the certificate (i.e. the ACA) is not the authoritative source of an attribute (i.e. the AIA). Before being granted, attributes shall be verified in a way that the ACA has no reasonable doubt on their truth. It shall be verified that, at the time of registration for th... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 8 Attribute meaning and representation | |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 8.1 Attribute meaning | As a basis to decide whether an attribute can be used in an application, a clear description of the meaning of an attribute is needed. That description shall be given in readily-understandable terms, and if appropriate the law that defines the attribute shall be indicated. There must be a way to find the description. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 8.2 Attribute representation | Once an attribute is defined, it is important for a verifier to be able to recognize it. An attribute can be: • either only directly user understandable; or • only machine processable; or • both machine processable and user understandable. An attribute that is only user understandable is not able to be processed and di... |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 8.2.1 Group membership | The group attribute carries information about group memberships. |
01f4af13098f74b559cb63e7f82c38b9 | 102 044 | 8.2.2 Role | The role attribute is the only attribute specified in ISO/IEC 9594-8 [4]; it carries information about roles. It is composed of two components: a role Authority and a role name. The role Authority is optional: when the AIA is not the AA, it allows to identify the AIA for that role. ETSI ETSI TR 102 044 V1.1.1 (2002-12)... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.