hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.18 Q | QAM Quadrature Amplitude Modulation QM Quality Management QoS Quality of Service QPSK Quadrature Phase Shift Keying ETSI ETSI TR 103 902 V2.1.1 (2026-01) 19 |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.19 R | R Release R-ITS-S Roadside ITS Station RLT Road and Lane Topology RM Resource Management RRM Radio Resource Management RSE Road Side Equipment RSSI Received Signal-Strength Indicator RSU Roadside Unit RTCM Radio Technical Commission for Maritime services RTCMEM RTCM Extended Message RTK Real Time Kinematic RWW Roads Wo... |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.20 S | SA Service Announcement SAM Service Announcement Message SAS Service Announcement Service SCH Service CHannel SCI Security Control Information SCO Single Channel Operations SDO Standards Development Organisation SDU Service Data Unit SDV Slow Driving Vehicle SHA Secure Hash Algorithm SHB Single Hop Broadcast SIB Securi... |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.21 T | TB Technical Body TC ID Traffic Class IDentity TC Technical Committee TCC Traffic Control Centre TLC Traffic Light Control TLM Traffic Light Manoeuver TMC Traffic Management Centre TOGAF The Open Group Architecture Framework TPEG Transport Protocol Experts Group TR Technical Report TS Technical Specification TVRA Threa... |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.22 U | UC Use Case UML Unified Modelling Language UMTS Universal Mobile Telecommunications System UPER Unaligned Packed Encoding Rule USB Universal Serial Bus |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.23 V | V2I Vehicle to Infrastructure V2N Vehicle to Network V2N2X Vehicle to Network to Everything V2V Vehicle to Vehicle V2X Vehicle to Everything VAM VRU Awareness Message VBS VRU Basic Service V-ITS-S Vehicular and personal ITS Station VoI Value of Information VRU Vulnerable Road User |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.24 W | WGX Working Group X (where X is a number) |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.25 X | X2X Everything to Everything X2N2X Anything to Network to Anything |
3be34f7b3db0557b264c09436216ee4a | 103 902 | 3.3.26 Y - Z | Void. ETSI ETSI TR 103 902 V2.1.1 (2026-01) 21 History Version Date Status V2.1.1 January 2026 Publication |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 1 Scope | The present document is a Framework (Guide) to Implementing Autonomic/Autonomous IPv6 based 5G Networks, by leveraging the ETSI GANA Multi-Layer AI / Multi-Layer Autonomic Management and Control Model and IPv6 Capabilities & Extensions that enable to Build Autonomic Networks. The Framework prescribes how to introduce s... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 2 References | |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 2.1 Normative references | Normative references are not applicable in the present document. |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 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... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 3 Definition of terms, symbols and abbreviations | |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 3.1 Terms | Void. |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 3.2 Symbols | Void. |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project 5G SA 5G StandAlone AcN Autonomic Network AFI Autonomic Future Internet AFTR Address Family Transition Router AGG AGgregation Gateway AI Artificial Intelligence AMC Autonomic Management & Control AMF Acc... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 5.3 Autonomic Mobility Management and Control Use Case | This is an Autonomics Use Case by which GANA FUNC_LEVEL_MOM_DE provides logic, algorithm(s) to manage mobility related MEs hosted by NE, for example, MEs that help drive handover or handoff of devices/nodes between different networks and technologies and also ensure service continuity of applications flows. The Use Cas... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 5.4 Autonomic Routing Management and Control Use Case | This is an Autonomics Use Case by which the GANA FUNC_LEVEL_RM_DE provides logic, algorithms to ensure the optimal and resilient routing of packets in the network in order to optimize the network utilization. The Use Case also includes the aspect by which the GANA NET_LEVEL_RM_DE provides logic, algorithms to ensure op... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 5.5 Autonomic Forwarding Management Use Case | This is an Autonomics Use Case by which GANA FUNC_LEVEL_FWD_DE provides logic, algorithm that autonomically manages the forwarding protocols and mechanisms of the node in order to optimize the forwarding behaviour of the node so as to meet certain objectives. The Use Case also includes the aspect by which GANA NET_LEVE... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 5.7 Autonomic Monitoring Management and Control Use Case | This is an Autonomics Use Case by which GANA FUNC_LEVEL_MON_DE provides logic and algorithms to orchestrate monitoring MEs or to (re)-configure them, and to retrieve information from various potential sources of monitoring data and information in order to intelligently cause dissemination of monitoring data needed by D... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 5.8 Autonomic Security Management and Control Use Case | This is an Autonomics Use Case by which GANA NODE_LEVEL_SEC_M_DE is used to manage any security issues in the Node. NODE_LEVEL_SEC_M_DE may also be used to secure and authenticate interactions between DEs and MEs within the same domain or to secure interaction with other MEs and DEs within different domain. The Use Cas... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 5.9 Autonomic Fault Management Use Case | This is an Autonomics Use Case by which GANA NODE_LEVEL_FM_DE is for autonomic fault management within the GANA Node by employing appropriate Fault Detection Mechanisms, Fault Isolation/Localization/Diagnosis Mechanisms, and Fault Removal Mechanisms that enable to repair the node's components and the node as a whole. N... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 5.11 Autonomic Performance Management Use Case | This is an Autonomics Use Case by which Autonomic Management Software (GANA Autonomic Performance-Management DE) monitors and measures network and service performance Key Performance Indicators (KPIs), i.e. any performance degradations, and dynamically allocate resources in the network that help to achieve certain KPI ... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 6.3 Slicing in packet networks | |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 6.3.1 Network Slicing high level architecture | Network slicing is one of the biggest differentiators of 5G compared to previous generations of mobile services. Network slicing brings increased network resource utilization efficiency and deployment flexibility. It also provides a higher quality of experience in servicing the differentiated requirements of customers ... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 6.3.2 SRv6 based network slicing | SRv6 is the more suitable protocol to underpin Network Slicing in 5G network. Possibility to define connection flow spanning the whole network provide benefits in service creation and monitoring. Traffic Engineering policies can be prescribed to network slice instances and implemented in different sections of the netwo... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 6.3.3 SR-based network programming | Network programming combines Segment Routing functions, both topological and service, to achieve a networking objective that goes beyond mere packet routing. The concept of network programming comes from computer programming. In computer programming, human beings can translate their intentions into a series of instruct... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 6.3.4 Application-aware Networking | There are proposals in the IETF for APplication-Aware Networking (APN), for which a working group is being considered. One of the key objectives of APN is for the network to provide fine-grain SLA guarantees instead of coarse-grain traffic operations. Among various applications being carried and running in the network,... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 6.3.5 SRv6 and SDWAN | With the adoption of the public cloud reliable and efficient data interconnection is critical. The solution to build a high performance Wide Area network (WAN) is given by Segment Routing over IPv6 (SRv6 and SDWAN technologies SRv6 brings several key benefits. First, it connects enterprise sites and clouds by programmi... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 6.5 Network Automation and SDN | In the new world of networking, Network Functions Virtualisation (NFV) and Software-Defined Networking (SDN) are new paradigms in the move towards open software and network hardware. While NFV aims to virtualize network functions and deploy them into general-purpose hardware, SDN makes networks programmable by separati... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 8.2.3 GANA Autonomics for Multi Layer Transport SDN Architecture | Figure 24: Integration of the GANA Knowledge Plane (KP) Platform with SDN Controllers for Multi-Layer Transport SDN Network Figure 25 presents Integration of the GANA Knowledge Plane (KP) Platform with OSS/BSS, E2E Service Orchestrator, Domain Orchestrators, SDN Controllers for Multi-Layer Transport SDN Network, and Te... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 8.2.4 GANA for 5G Service Based Architecture (SBA) | Regarding GANA for 5G SBA Architecture, the three levels of GANA DEs hierarchy apply, namely GANA levels 2&3 that can be introduced into Network Functions (or Services in the case of the SBA) and GANA level (network level). However, GANA Levels 2 and 3 DEs should be implemented as micro services in SBA. The GANA Knowle... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 8.2.5 GANA Autonomics for MEC Architecture | Figure 27 presents GANA Autonomics for MEC Architecture. It shows the GANA Levels where DEs can be introduced into the architecture. NOTE: The lower level GANA DEs introduced in some components of the architecture may be limited to GANA Node-level DEs (GANA Level 3 DEs such as Auto-Configuration DE, Fault- Management D... |
7470f1226238696862acc2f2b74c08a3 | 103 858 | 11 Conclusion and Further Work | DE algorithms are not subject to standardization as they provide for the space for innovation and DE and Algorithm supplier differentiations. Examples of Autonomic Functions (i.e. GANA DEs) are: QoS-management-DE, Security-management-DE, Mobility-management-DE, Fault-management-DE, Resilience & Survivability-DE, Servic... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 1 Scope | The present document provides requirements that are specific enough to define the desired security outcomes, but flexible enough that there can be innovation and different ways for how they can be achieved. Whilst it is initially targeted towards the Telecoms Sector, the principles are designed to be industry agnostic.... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 2 References | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-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... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-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... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 3 Definition of terms, symbols and abbreviations | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 3.1 Terms | For the purposes of the present document, the following terms apply: Privileged Access Workstation (PAW): appropriately secured device that enables an admin user to access data and/or make changes to security critical functions via a management plane NOTE: This is defined in [i.1]. |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 3.2 Symbols | Void. |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: IAM Identity and Access Management OS Operating System OT Operational Technology PAM Privileged Access Management PAW Privileged Access Workstation PDF Portable Document Format SOC Security Operations Centre VPN Virtual Private Network |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4 PAW design considerations and integration | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.1 PAW design considerations | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.1.1 Introduction | The deployment of a Privileged Access Workstation (PAW) solution shall account for the impact on user workflows. The design process shall incorporate input from end users as well as risk owners, ensuring that operational realities are reflected in the solution. Assumptions regarding role execution shall not replace dir... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.1.2 Factors to consider during Commissioning and Procurement | Failure to define accurate requirements at this stage may result in procuring or developing an unsuitable solution. The organization should consider: • current processes: what functions effectively and what does not; • role-specific tasks and operational conditions; • actual work practices versus prescribed processes; ... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.2 Identify high-risk accesses | PAWs may be deployed for all privileged access scenarios; however, their use is most critical for high-risk accesses. An access shall be considered high risk if: • the potential impact of compromise is severe; or • the systems protected by such access are likely to be targeted by a capable threat actor. High-risk acces... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.3 PAM Integration | Prior to the deployment of a PAW, the organization shall establish a clear understanding of the operational need and associated risk scenarios. The implementation of a PAW shall form part of a risk-based approach that identifies potential threats and defines the required defensive measures. ETSI ETSI TS 103 994-3 V1.1.... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.4 Cross Domain Dataflow | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.4.1 Introduction | When implementing an import/export mechanism for a PAW environment, the organization shall begin by identifying the types of data that require transfer between enterprise and PAW environments. Complex data formats (e.g. Microsoft Word, PDF) present higher security risks and are more difficult to sanitise than structure... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.4.2 Data Transfer Solution Requirements | The data transfer solution shall: • generate a complete audit trail for all data entering or leaving the PAW environment; • require user authentication prior to any transfer; • ensure that only approved and authorized content is exported; • automate transfers to predefined, pre-configured endpoints, prohibiting export ... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.4.3 Threat Context Considerations | For high-threat environments, data control solutions should, where feasible, be implemented in hardware. For lower-threat contexts, software-based controls combined with network boundary restrictions may be acceptable. The organization should refer to their National Technical Authority on secure data import/export patt... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.5 Legacy Technology | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.5.1 Introduction | The organization shall avoid running obsolete software or Operating Systems (OS) on PAWs. Where this is not feasible for operational continuity - primarily in Operational Technology (OT) environments - obsolete applications shall be isolated and segregated from the PAW environment. |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.5.2 Preferred Approach | The organization shall engage with the vendor of the obsolete application or OS to identify alternative solutions, such as: • upgrading to a supported version; • porting the application to a modern OS; • implementing containerization or virtualization strategies. |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.5.3 Virtualization and Isolation Controls | If obsolete products remain necessary and no viable alternatives exist, the organization shall: • use virtualization to segregate obsolete software from the PAW; • restrict access to obsolete applications to only those users who require it; • document obsolete products and associated users as technical debt, and mainta... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.5.4 Virtualization Security Requirements | Each obsolete OS instance shall have: • no direct network connectivity to the host machine; • no connectivity to other virtualized hosts (each instance shall operate on an isolated virtual network). A virtualized managed firewall appliance shall be pre-configured centrally: • PAW users shall not have the ability to mod... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 4.5.5 Security Tooling Considerations | The organization shall assess the risk of deploying security tools (e.g. antivirus) on obsolete virtual machines, as these tools operate on vulnerable OS platforms and their results cannot be fully trusted. Additional external monitoring should be implemented to compensate for the limited effectiveness of on-host secur... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 5 Initial Device | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 5.1 Build in isolation | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 5.1.1 Introduction | The initial configuration of a Privileged Access Workstation (PAW) solution shall prioritize security to prevent cross-contamination and maintain system integrity. The organization shall not build PAW systems from existing devices. Instead, PAWs shall be provisioned using new, clean devices sourced through a trusted an... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 5.1.2 Single-Device and Initial Deployment Scenarios | In small-scale or single-device deployments, the initial device may serve as the sole PAW. To ensure compliance, this device shall adhere to all applicable lockdown policies. Typically, this device is used to provision the PAW management environment, establishing a clean and physically segregated network segment. This ... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 5.1.3 Multi-Device Deployments | Where multiple PAW devices are required, the initial device shall be integrated into the PAW Mobile Device Management (MDM) solution and enrolled as a PAW device once the MDM is operational. The initial device shall not be used for administrative tasks until all technical controls and lockdown policies are fully implem... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 5.2 Secure your PAW Infrastructure | Once the Privileged Access Workstation (PAW) infrastructure has been deployed within an isolated environment, it shall be subject to a series of security and operational controls to ensure its integrity and compliance with organizational requirements. All systems shall be kept up to date through the application of rele... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 5.3 Scale with MDM / Zero touch deployments | Where a PAW solution comprises multiple devices, the organization shall ensure that security controls can be scaled effectively. This requires the use of a well-secured management platform, which shall be administered from a trusted system. The organization should ensure that all modifications and configuration changes... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 6 PAW backup plan | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 6.1 PAW Resilience | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 6.1.1 Introduction | Once implemented, a PAW solution shall be the exclusive method for performing high-risk privileged access within the organization. The PAW solution shall be designed with sufficient resilience to support both normal operations and failure scenarios. During the design phase, the organization shall assess: • the required... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 6.1.2 Break-Glass Access Requirements | Break-glass accounts shall be exempt from technical enforcement controls to ensure availability during emergencies. Break-glass accounts shall, where possible, be accessed from a trusted PAW device due to the high-risk nature of these credentials. In exceptional circumstances where PAWs are unavailable and business-cri... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 6.1.3 Security and Operational Controls | Activation of a break-glass account shall automatically trigger an alert for immediate investigation and be treated as a maximum criticality incident. Break-glass access shall only be used as a last resort and never for routine operations or remote access by third parties. Post-incident, the organization shall conduct ... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 6.1.4 Credential Management and Testing | Break-glass credentials shall be stored securely, including maintaining a physical copy where appropriate. Access to credentials shall be restricted to authorized personnel and subject to monitoring and auditing. ETSI ETSI TS 103 994-3 V1.1.1 (2026-01) 13 Break-glass access shall be routinely tested to confirm function... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 7 Protective Monitoring | |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 7.1 Monitoring Requirements | The monitoring solution shall provide visibility over: • the PAW device itself; • supporting systems, including configuration and change management platforms. Logging events shall be streamed to a secure log-processing system in near real-time. Protections shall be implemented to prevent tampering with logs on the devi... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 7.3 Anomaly Detection | The organization shall implement anomaly detection for all uses of privileged identities. Additional logging should be enabled to capture actions performed on PAW devices, enhancing accountability and mitigating insider threats. Given the constrained nature of PAWs, anomaly detection shall identify any activity outside... |
8c07a0652e2fc39ac1f6114bccf9b279 | 103 994-3 | 8 Threats and Mitigations | The present document addresses four primary threat vectors; however, these are not exhaustive, and additional risks may be covered within the points outlined here. It also considers the risk of lock-out and its mitigation through a Break- Glass procedure. While lock-out may not be a direct threat vector, being unable t... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 1 Scope | The present document contains the following material relating to takedown requests: • A statement of benefits for using standardized interfaces for takedown requests. • Suggestions around potential requirements (though the present document does not formally define requirements). • Use cases, examples and scenarios whic... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 2 References | |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 2.1 Normative references | Normative references are not applicable in the present document. |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 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... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 3 Definition of terms, symbols and abbreviations | |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 3.1 Terms | Void. |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 3.2 Symbols | Void. |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: DNS Domain Name System IP Internet Protocol ETSI ETSI TR 104 126 V1.1.1 (2026-02) 6 |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 4 Core concepts | |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 4.1 Foundations | A takedown request is a technical request to take down an account, content or service. The present document does not make any statement about legislation. The request should contain supporting information which will allow the recipient to fully understand what is being asked for and why (e.g. can cite relevant legislat... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 4.2 Benefits | The goal is to create a way of submitting requests that is clear, consistent, secure and efficient. This goal helps deliver the following benefits: • All parties can quickly have a common understanding of the action that is being requested and the justification for it. • Parties can have confidence that material is not... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 4.3 Scenarios | The following scenarios are relevant: • Takedown of user-generated content. • Blocking of a service based on phone number, email address or (potentially) IP address (care needed about ephemeral identifiers). • Blocking material by a hosting organization or blocking a domain at a registrar level (for DNS Abuse, Fraud, h... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 5 Approaches | |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 5.1 Two principles | The following two principles are recommended: 1) It is recommended to re-use existing TC LI standards where they are suitable i.e. re-use protocols and structures from existing TC LI specifications. Care has been taken to avoid confusion between takedowns and lawful disclosure requests: there are distinct standards and... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 5.2 Outline of the candidate solution | The recommended solution involves following these steps: • Establishing a secure link between the people making the request and the people receiving it. The goal is to use standard internet-based secure protocols which are easy to code. • Follow a certain message flow, which defines who starts the conversation and how ... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 5.3 Implementing this approach | The above approach is implemented by using the structure for takedown tasks (Called TDTask) as defined in ETSI TS 103 120 [i.1]. The TDTask is distinct from the existing tasks at a high level in the stack, so that software will be able to immediately see whether a request is a disclosure or takedown request. The TDTask... |
dba25161077ab25d04f1eb028c9d59ca | 104 126 | 5.4 Comparing TDTask to other request types | Clause 5.4 examines differences and similarities between the Takedown Task (TDTask) compared to the other types of tasks in ETSI TS 103 120 [i.1], such as the Lawful Disclosure Task LDTask. The purpose of clause 5.4 is to demonstrate that a balance has been struck: • Relevant material from other task types has been re-... |
c162d88c5a832e40110a86ba070ce0ef | 104 147-2 | 1 Scope | The present document provides the Implementation Conformance Statement (ICS) pro forma for testing Server implementations for compliance to the Mission Critical Services over LTE protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [i.6] and ISO/IEC 9646-7 [2]. The... |
c162d88c5a832e40110a86ba070ce0ef | 104 147-2 | 2 References | |
c162d88c5a832e40110a86ba070ce0ef | 104 147-2 | 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... |
c162d88c5a832e40110a86ba070ce0ef | 104 147-2 | 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... |
c162d88c5a832e40110a86ba070ce0ef | 104 147-2 | 3 Definitions of terms, symbols and abbreviations | |
c162d88c5a832e40110a86ba070ce0ef | 104 147-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 121 905 [i.1] (3GPP TR 21.905), ISO/IEC 9646-1 [i.6], ISO/IEC 9646-7 [2] and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905), IS... |
c162d88c5a832e40110a86ba070ce0ef | 104 147-2 | 3.2 Symbols | Void. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.