hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.7 Ensure software integrity | Provision SVD 7.7-1 (added): If the SVD uses a root key to protect the integrity of code running on the device, the root key should not be shared between different models. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.8 Ensure that personal data is secure | No additions to the provisions from ETSI TS 103 645 [1], clause 5.8 are defined in the present document. ETSI ETSI TS 103 927 V1.1.1 (2024-01) 13 |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.9 Make systems resilient to outages | Provision SVD 7.9-1 (added): If the SVD cannot execute the user's voice command due to a network connection failure within a brief period it shall inform the user in an explicit manner. Provision SVD 7.9-2 (added): After a user-perceivable network failure, when the network connection is restored, the SVD shall not sile... |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.10 Collecting log data | No additions to the provisions from ETSI TS 103 645 [1], clause 5.10 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.11 Make it easy for users to delete user data | No additions to the provisions from ETSI TS 103 645 [1], clause 5.11 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.12 Make installation and maintenance of devices easy | No additions to the provisions from ETSI TS 103 645 [1], clause 5.12 are defined in the present document. |
dbafb4ec8d074ab7b270f83c9f497dd0 | 103 927 | 7.13 Validate input data | Provision SVD 7.13-1 (added): The SVD shall validate the voice input to filter out hidden voice commands and only respond to the human voice input. NOTE: Hidden voice commands are voice commands that are unintelligible to human users but are interpreted as commands by the device. Such voice commands may be either outsi... |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) for the IPv6-only services over 5G in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.1]. The test notation used in the ATS is TTCN-3 (see ETSI ES 201 873-1 [i.2]). The following test specifica... |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 2 References | |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 2.1 Normative 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... |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 2.2 Informative 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. NOTE: While any hyperlinks i... |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 3 Definition of terms, symbols and abbreviations | |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 3.1 Terms | Void. |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 3.2 Symbols | Void. |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 3.3 Abbreviations | Void. |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 4 Abstract Test Method (ATM) | |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 4.1 Introduction | The following clauses describes the ATM used to test the interoperability IPv6-only services over 5G. |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 4.2 Test architecture | The test architecture foreseen is a complex system of all involved components. The following figures give an overview. Figure 1 shows the network entities involved in the interoperability testing and the mapping to test components. Figure 2 adds a more technical view of the implementation plans for the test system comp... |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 4.3 Interconnection of TS and SUT | The interconnection of the Test System (TS) and the System Under Test (SUT) is depicted in figure 2. The IPv6only5GCCoordinator controls the overall test execution by coordinating theIPv6only5GCInterfaceMonitor components on the IPv6 and DNS interfaces under observation. It synchronizes those test components and receiv... |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 4.4 Implementation of TS | The implementation of the TS in TTCN-3 is depicted in figure 3 which gives the names of all test components and the related TTCN-3 ports, variables and timers. It also shows the connections between the test components via CoordinationPort, VerdictPort and SyncPort and the connections to the IotSystemInterface via NasPo... |
7a2d0e855dbd24752e02e6b626775337 | 103 878-3 | 4.5 Test Adapter | For execution of the tests the Test Adapter (TA) will be developed. ETSI ETSI TS 103 878-3 V1.1.1 (2025-05) 9 History Document history V1.1.1 May 2025 Publication |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 1 Scope | The present document contains specifications of interoperability test descriptions to validate implementations of ETSI TS 103 300-3 [1]. |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 2 References | |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 2.1 Normative 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... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 2.2 Informative 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. NOTE: While any hyperlinks i... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 3 Definition of terms, symbols and abbreviations | |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 300-3 [1] apply. |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 300-3 [1] apply. ETSI ETSI TS 103 925 V2.1.1 (2024-11) 6 |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 300-3 [1] and the following apply: CL Cluster Leader EUT Equipment Under Test QE Qualified Equipment |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4 Requirements and configuration | |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.1 Requirements | |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.1.1 Overview | The clauses 4.1.2, 4.1.3 and 4.1.4 define mandatory and optional requirements for the implementation of the ITS-S in the role of the Equipment Under Test (EUT) and in the role of the Qualified Equipment (QE) and the network sniffer. |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.1.2 Equipment under test | The EUT in the VAM interoperability tests is an ITS-S with the following mandatory requirements: • The EUT shall be able to send and receive VAMs [1]). • The EUT's parameters as defined in ETSI TS 103 300-3 [1] shall be configurable by the test operator. The EUT shall be checked if it behaves accordingly to the VRU sta... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.1.3 Qualified equipment | The QE in the VAM interoperability tests is an ITS-S with the following mandatory requirements: • The QE shall be able to send and receive VAMs [1]. • The QE is verified to fulfil the interoperability test specification. • The QE's parameters as defined in ETSI TS 103 300-3 [1] shall be configurable by the test operato... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.1.4 Network sniffer | To validate the behaviour of the EUT in certain test cases it is necessary to observe the send and received VAMs. To enable this observation a network sniffer is required. The network sniffer does not participate actively in the communication. Mandatory requirements: • The Network sniffer shall be able to receive and d... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.2 Configurations | |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.2.1 VRU basic configuration | The parameters used in the following tests are the default parameters as described in ETSI TS 103 300-3 [1], clause 8 unless stated otherwise. For compatibility, these shall be synchronized between the ITS-S. To participate in the test with the present configuration, ITS-S shall be configured as following if it is not ... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.2.2 Stations operate under cluster join conditions | Some use cases test the ability to create or join a VRU cluster or avoiding doing so. In these use cases, at least two stations shall interact in a way that the (configurable) "clustering conditions" are met during the test. The clustering conditions that shall be fulfilled include that an ITS-S A: • is in within the b... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 4.2.3 Station operate under cluster leave conditions | Some use cases test the ability to leave or disband a VRU cluster or refrain from doing so. Analogous to clause 4.2.2, at least two stations shall interact in a way that the previously defined clustering conditions are not met anymore. At least one of the clustering conditions stated in clause 4.2.2 shall be violated w... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 5 Requirements to be tested | |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 5.1 Overview | The clauses below collect and enumerate the requirements that can be tested with the present document. |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 5.2 VAM interoperability requirements | NN Requirement Reference UCs 1.1 ITS-S may be configurable to activate and deactivate clustering ETSI TS 103 300-3 [1], clause 5.4.1 UC1-1 UC1-2 UC1-4 1.2 ITS-S shall be part of maximum one cluster ETSI TS 103 300-3 [1], clauses 5.4.1 and 5.4.2.2 UC1-3 UC1-4 UC1-10 UC1-11 1.3 ITS-S shall be only part of a cluster when ... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6 Interoperability test descriptions | |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.1 Use-case 1-1 Cluster deactivation | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-1 Objective: Check that EUT can deactivate the clustering Configuration: Participants: QE 1, QE 2, EUT QE 1 and QE 2 (can be emulated) already fulfil cluster join conditions (see clause 4.2.2). QE 1 is configured with numCreateCluster = 2, QE 2 is configured ... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.2 Use-case 1-2 Cluster activation | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-2 Objective: Check that EUT can activate the clustering Configuration: Participants: QE 1, QE 2, EUT QE 1 and QE 2 (can be emulated) already fulfil cluster join conditions (see clause 4.2.2). QE 1 is configured with numCreateCluster = 2, QE 2 is configured wi... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.3 Use-case 1-3 Cluster leader break cluster up | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-3 Objective: Check that EUT disbands a cluster if a larger, compatible cluster is available Configuration: Participants: QE 1, QE 2, QE 3 & QE 4, EUT QE 1 is fulfilling cluster join conditions (see clause 4.2.2) of EUT. QE 1 is configured with numCreateCluste... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.4 Use-Case 1-4 Creating a cluster | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-4 Objective: Check that EUT successfully creates a cluster when compatible stations are close Configuration: Participants: QE 1, EUT QE 1 is configured with numCreateCluster >= 3, EUT is configured with numCreateCluster = 2 QE 1 fulfils cluster join condition... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.5 Use-Case 1-5 Stop sending VAMs after cluster joining | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-5 Objective: Check that EUT stops sending individual VAMs after joining a cluster Configuration: Participants: QE 1, QE 2 EUT QE 1 is configured with numCreateCluster = 2, QE 2 with numCreateCluster >= 4. EUT's timeClusterJoinNotification is set to 3 s. QE 2 ... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.6 Use-Case 1-6 Cluster Breakup triggered by leader | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-6 Objective: Check that EUT sends individual VAMs after a cluster breakup is triggered by the cluster leader. Configuration: Participants: QE 1, EUT QE 1 is configured with numCreateCluster = 1, EUT is configured with numCreateCluster >= 2 EUT fulfils cluster... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.7 Use-Case 1-7 Failed joining a cluster | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-7 Objective: Check that EUT sends cluster leave notifications when it fails to join a cluster. Configuration: Participants: QE 1, QE 2, EUT. EUT's timeClusterJoinNotification is set to 10 s. EUT's timeClusterLeaveNotification is set to 1 s. QE 2 fulfils clust... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.10 Use-Case 1-10 Leave VAM cluster | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-10 Objective: Check that EUT leaves the cluster if the cluster conditions are not fulfilled anymore. Configuration: Participants: QE 1, EUT. EUT's timeClusterLeaveNotification is set to 1 s. At the beginning of the test, EUT fulfils cluster join conditions (s... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.11 Use-Case 1-11 Leave cluster in case of connection loss | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-11 Objective: Check that EUT is leaving the cluster if the connection with the cluster leader is lost Configuration: Participants: QE 1, EUT. EUT fulfils cluster join conditions (see clause 4.2.2) of QE 1. EUT's timeClusterContinuity is set to 2 s. EUT's time... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.12 Use-Case 1-12 Leave cluster on Safe Distance Violation | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-12 Objective: Check that EUT leaves the cluster indicating "SafetyCondition" when its minimumSafeLateralDistance,, minimumSafeLongitudinalDistance and minimumSafeVerticalDistance are violated Configuration: Participants: QE 1, QE 2, EUT EUT's timeClusterLeave... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.13 Use-Case 1-13 Leave cluster after cluster ID change | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-13 Objective: Check that EUT leaves the cluster if the cluster leader has changed the cluster ID Configuration: Participants: QE 1, EUT. EUT fulfils cluster join conditions (see clause 4.2.2) of QE 1. EUT's timeClusterIdPersist is set to 3 s. Pre-test conditi... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.15 Use-Case 1-15 Stop sending VAM if ITS-S is part of CPM | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-15 Objective: Check that EUT stops sending individual VAMs if it detects that it is already part of a CPM [2] Configuration: Participants: QE 1, EUT. EUT's timeClusterJoinNotification is set to 3 s. QE 1 sends CPMs [2] with detected objects. EUT starts outsid... |
a9e81b60fb60fde5a903c4dbdf3f3590 | 103 925 | 6.18 Use-Case 1-18 Trajectory interception probability | Interoperability Test Description Identifier: TC_ITS_VRU_UC1-18 Objective: Check that EUT sends VAMs with an increasing trajectory interception probability Configuration: Participants: QE 1, EUT QE 1 stands perpendicular to EUT with 25 m of longitudinal and lateral offset. QE 1 and EUT start moving towards a common int... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 1 Scope | The present document provides a catalogue of baseline requirements specific to optical network and devices covering access network, transport network and network management system. The present document presents the functional requirements using the stage 2 model approach outlined in Recommendation ITU-T Q.65 [i.1] and ... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 2 References | |
2796895e601da73b48ab7b5231086b1f | 103 924 | 2.1 Normative 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... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 2.2 Informative 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. NOTE: While any hyperlinks i... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 3 Definition of terms, symbols and abbreviations | |
2796895e601da73b48ab7b5231086b1f | 103 924 | 3.1 Terms | For the purposes of the present document, the following terms apply: adaptation source: transport processing function which adapts the client layer network characteristic information into a form suitable for transport over a trail in the server layer network Control Plane Security Function (CPSF): set of security funct... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 3.2 Symbols | Void. |
2796895e601da73b48ab7b5231086b1f | 103 924 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABAC Attribute Based Access Control AEAD Authenticated Encryption with Associated Data AES Advanced Encryption Standard AON Active Optical Network CBA Cost Benefit Analysis CIA Confidentiality Integrity Availability C-MAC Cipher-based Message ... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 4.2 Definition of optical network | An optical network is distinguished from a non-optical network by the physical means of transferring data, which is achieved using fibre optic links, data encoded using photons, and by the use of optical switching. The core definition of the structure of Optical Networking interfaces is found in Recommendation ITU-T G.... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 4.3 Optical network functionality (user and control) | NOTE 1: The text in this clause summarizes functions in optical networks that is derived from G.709, SDH and SONET. The optical network in the scope of the present document describes a transmission system that is used to carry client data, where client data can be presented in a number of formats, including Ethernet fr... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 4.4 Optical network functionality (management) | The provisions for securing the management of the optical network should follow existing best practice for securing management data and protocols. In particular it is recognized that the NMS manages and controls devices on optical networks, supports unified management, and offers control of networks. Thus the NMS integ... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 4.5 Optical network security objectives | It is noted in [i.5] that optical networks are susceptible to eavesdropping attacks by interception of the signals on the fibre, and have associated vulnerabilities of availability from conventional physical attack. It is also noted that as the data load carried by optical networks is substantial, and that a single fib... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 5 Identification and authentication framework | |
2796895e601da73b48ab7b5231086b1f | 103 924 | 5.1 Introduction | In simple terms identity, semantic or canonical, in context, is the anchor for most security functions if a key or credential is bound to an identified entity and purpose. NOTE: A semantic identity is one that informs of its purpose, so an email address is a semantic identifier as it informs that the content is for use... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 5.2 Functional identification and authentication | An entity is functionally defined by semantics and context. A device has function, e.g. a demultiplexer functions by dividing the WDM path into its non-multiplexed elements, and it has context including its physical location. The combination of sematic identity, contextual identity and canonical identity uniquely ident... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 6 Confidentiality protection | |
2796895e601da73b48ab7b5231086b1f | 103 924 | 6.1 Protection of data in transit (access and core) | Confidentiality protection shall be applied, in the OTN, to the OPU prior to its encapsulation in an ODU (the header elements of the ODU are required for system control). In the OAN the protection shall be applied to the GPON Encapsulation Method (GEM) Frame using an identical mechanism (i.e. the base confidentiality p... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 6.2 Protection of data at rest | |
2796895e601da73b48ab7b5231086b1f | 103 924 | 6.2.1 Cryptographic key management (symmetric keying) | The keys shall be stored in a hardware based secure element acting as a Root of Trust (RoT). A key manager shall be instigated at the network core and shall distribute keys. 6.2.2 Certificate management (asymmetric keying) Each element shall be able to create an asymmetric key pair and have it certified within a design... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 7 Integrity protection | |
2796895e601da73b48ab7b5231086b1f | 103 924 | 7.1 Core capabilities of OTH | In order to give higher assurance of system reliability OTH defines the use of Forward Error Correcting (FEC) codes in Recommendation ITU-T G.975 [4] calculated using a Reed-Solomon coding scheme across the payload columns. The FEC codes are not mandatory to implement in G.709 but shall be implemented for the purposes ... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 7.2 Network and Data integrity protection in transit | The risk analysis in Annex A suggests that malicious modification of data in transit is unlikely without significantly increasing either jitter or latency in the connection (see also Recommendation ITU-T X.800 [i.14] where data integrity services are only considered as applicable at layer 3 and above). However manageme... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 7.3 Integrity protection of data at rest | ONs should apply best practice. In particular any security data, e.g. keys, certificates, should be maintained in a hardware root of trust for storage. NOTE: The ON is intended to transfer data and is not expected to store any user level data. The configuration and management data of any ON device is not addressed in t... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 8 Availability protection | |
2796895e601da73b48ab7b5231086b1f | 103 924 | 8.1 Redundancy protection | The capabilities defined in Recommendation ITU-T G.987 [i.37] series, Recommendation ITU-T G.989 series [i.38], and Recommendation ITU-T G.9807.1 [i.32] as applied to each of XG-PON, NG‑PON2, and XGS-PON systems apply and should be implemented as appropriate to the specific technology. An extension defined in Supplemen... |
2796895e601da73b48ab7b5231086b1f | 103 924 | 8.3 Network security awareness | The general principles outlined in the Security Controls defined in ETSI TR 103 305-1 [i.20] apply and are detailed in clause A.4. As indicated in clause A.4 many security processes, functions and actions should be implemented to benefit from the security provisions of the ON/OTN described in the present document. |
2796895e601da73b48ab7b5231086b1f | 103 924 | 8.4 Passive versus Active Optical Networks | In a passive network optical couplers/splitters can be used to differentiate/route user traffic. As there is no active amplification of the signal on any PON there is a limit to the number of connections possible before the impact of noise makes communication impossible. In contrast an Active Optical Network making use... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 1 Scope | The present document provides the baseline requirements specific to Optical Access Network (OAN) and devices which provides network access service to network service subscribers. The present document extends the provisions identified in the Catalogue of Requirements for Optical Network (ON) and Device Security from ETS... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 2 References | |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 2.1 Normative 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... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 2.2 Informative 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. NOTE: While any hyperlinks i... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 3 Definition of terms, symbols and abbreviations | |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 3.1 Terms | For the purposes of the present document, the following terms apply: canonical identifier: structured identifier that is globally unique EXAMPLE: An IMSI is an example of a canonical identifier. crypto-agile: able to utilize crypto-agility crypto-agility: property that permits changing or upgrading cryptographic algori... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 3.2 Symbols | Void. |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAT Attribute Authority Tree AEAD Authenticated Encryption with Associated Data AES-GCM Advanced Encryption Scheme - Galois Counter Mode CIA Confidentiality Integrity Availability C-MAC Cipher based Message Authentication Code ECDSA Elliptical... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 4.1 Optical access network device functional model | The general provisions stated in ETSI TS 103 924 [1] apply to Optical Network (ON) devices operating in the access network with the additional specializations given in the present document. The access network is defined as the set of access links sharing the same network-side interfaces and supported by an optical acce... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 4.2 Trust architecture in Optical access network devices | As outlined in ETSI TS 103 924 [1] ON systems shall be designed to be secure by default and to support the functionality required by the CIA paradigm (Confidentiality, Integrity, Availability). At initialization and at runtime all links shall be established and security associations created within the trust and securit... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 4.4 Guidance on cryptographic processes | All cryptographic modules shall be designed to be crypto-agile. The specific cryptographic algorithms for each security association shall be defined by the security policy. Cryptographic algorithms should be sufficient to inhibit known cryptanalysis attacks and mechanisms (see also the impact of Quantum Computing on cr... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 4.5 Security error and misuse reporting | The security processes shall be self-monitoring and report detected errors to the local security authority which may in turn report errors to a remote, central, security authority. EXAMPLE 1: Self-monitoring may use an Intrusion Detection System (IDS) to detect malicious activity. EXAMPLE 2: If a device identifies a po... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.1 Common provisions | The general provisions of the ON management standard (ETSI TS 103 961 [3]) apply wherein all devices shall be identified with a canonical/root identity and, optionally, additional semantic identifiers identifying their functional nature. The management entity, for the purposes of the present document, is referred to as... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2 Identification and authentication | |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.1 Symmetric keyed systems | |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.1.1 Symmetric key distribution | The ONDS-M, defined in ETSI TS 103 961 [3], is responsible for ensuring that symmetric keys for each specific security association are made available at the device. A key shall be associated to an attribute or identifier of the OAN Device. The binding of key to the attribute or identifier shall be maintained for each s... |
ea8f3a93c6753efab0f52fb8a38247ec | 103 962 | 5.2.1.2 MAC based systems | A Message Authentication Code (MAC) method should be used in established security associations as an alternative to simple integrity check functions where the integrity, MAC, key is pre-defined or established as a session specific key (based on the mechanisms used in clause 6.2 of ETSI TS 133 501 [i.11]). If used the p... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.