| | MEC(19)000119 | Minutes of the ETSI MEC17 meeting | Accepted | Secretary | Report |
| | MEC(19)000118 | Chairman's Opening Report | Noted | Chairman | Other |
| | MEC(19)000117 | Response to LS Information by European Commission related to EC Expert Group on RRS | Accepted | Chairman | LSout |
| | MEC(19)000116 | RGS/MEC-003 Framework and Reference Architecture | Accepted | Huawei Technologies France | NWI |
| | MEC(19)000115 | Chairman's WG DECODE#001 report | Noted | ViaviSolutions Deutsch. GmbH | Report |
| | MEC(19)000114 | Response to TC INT WG AFI | Accepted | Chairman | Other |
| | MEC(19)000113r1 | MEC027 – Impact of AVT on Management API Specification | Accepted | Hewlett-Packard Enterprise | Other |
| | MEC(19)000113 | MEC027 – Impact of AVT on Management API Specification | Revised | Hewlett-Packard Enterprise | Other |
| | MEC(19)000112 | MEC Hackathon in China 2019 | Noted | Huawei Technologies France | Other |
| | MEC(19)000111 | LS reply from 3GPP WG SA on Information on MEC work on 5G | Noted | ETSI Secretariat | LSin |
| | MEC(19)000110 | LS from TC RRS on Information by EC related to EC Expert Group on RRS | Noted | ETSI Secretariat | LSin |
| | MEC(19)000109 | MEC related work in 3GPP SA2 | Noted | Huawei Technologies France | Other |
| | MEC(19)000108r2 | NWI Proposal MEC 003 Term 3 | Accepted | Huawei Technologies France | Other |
| | MEC(19)000108r1 | Draft NWI Proposal MEC 003 Phase 3 | Revised | Huawei Technologies France | Other |
| | MEC(19)000108 | Draft NWI Proposal MEC 003 Phase 3 | Revised | Huawei Technologies France | Other |
| | MEC(19)000107 | MEC031 - Clarification on traffic rules control | Accepted | Huawei Technologies France,ViaviSolutions Deutsch. GmbH | Other |
| | MEC(19)000106r3 | MEC031 - MEC as Application Function(s) of 5G system | Accepted | Huawei Technologies France,China Telecommunications,InterDigital, Inc. | Other |
| | MEC(19)000106r2 | MEC031 - MEC as Application Function(s) of 5G system | Revised | China Telecommunications,Huawei Technologies France | Other |
| | MEC(19)000106r1 | MEC031 - MEC as Application Function(s) of 5G system | Revised | China Telecommunications,Huawei Technologies France | Other |
| | MEC(19)000106 | MEC031 - MEC as Application Function(s) of 5G system | Revised | China Telecommunications,Huawei Technologies France | Other |
| | MEC(19)000105r1 | MEC011-MEC010-2 discussion on ME App Termination procedures | Accepted | VODAFONE Group Plc | Other |
| | MEC(19)000105 | MEC011-MEC010-2 discussion on ME App Termination procedures | Revised | VODAFONE Group Plc | Other |
| | MEC(19)000104 | MEC010-2 Update MEC service | Noted | Sony Europe Limited | Other |
| | MEC(19)000103r1 | MEC010-2 Scope | Accepted | Sony Europe Limited | Other |
| | MEC(19)000103 | MEC010-2 Scope | Revised | Sony Europe Limited | Other |
| | MEC(19)000102 | Discussion_on_how_to_reconstruct_edge_data_center | Noted | China Unicom | Other |
| | MEC(19)000101 | Demonstration of security monitoring scheme based on MEC system facing to PoC12 | Noted | China Unicom | Other |
| | MEC(19)000100 | MEC0010-2 Analysis for Support MEC in NFV | Noted | ZTE Corporation | Other |
| | MEC(19)000099r1 | MEC0031 Key Issue MEC System Level Interacts with NEF | Noted | ZTE Corporation | Other |
| | MEC(19)000099 | MEC0031 Key Issue MEC System Level Interacts with NEF | Revised | ZTE Corporation | Other |
| | MEC(19)000098 | MEC027 – Impact of AVT on Management API Specification | Noted (Rev. Requested) | Hewlett-Packard Enterprise | Other |
| | MEC(19)000097r1 | MEC027 – Impact of AVT on Service Exposure API Specification | Accepted | Hewlett-Packard Enterprise | Other |
| | MEC(19)000097 | MEC027 – Impact of AVT on Service Exposure API Specification | Revised | Hewlett-Packard Enterprise | Other |
| | MEC(19)000096 | MEC discussion on possible IOT API | Noted | Intel Corporation (UK) Ltd | Other |
| | MEC(19)000095r2 | MEC0031_Input_to_Overview_Section | Accepted | InterDigital, Inc. | Other |
| | MEC(19)000095r1 | MEC0031_Input_to_Overview_Section | Revised | InterDigital, Inc. | Other |
| | MEC(19)000095 | MEC0031_Input_to_Overview_Section | Revised | InterDigital, Inc. | Other |
| | MEC(19)000094r1 | MEC Hackathon 2019 proposal | Noted | Intel Corporation (UK) Ltd,Huawei Technologies France,ViaviSolutions Deutsch. GmbH,Saguna Networks Ltd,TELEFONICA S.A. | Other |
| | MEC(19)000094 | MEC Hackathon 2019 proposal | Revised | Huawei Technologies France,Intel Corporation (UK) Ltd,Saguna Networks Ltd,ViaviSolutions Deutsch. GmbH | Other |
| | MEC(19)000093 | MEC011 Providing a Service Description | Noted | ViaviSolutions Deutsch. GmbH | Other |
| | MEC(19)000092 | MEC011-Update to subscriptions | Accepted | VODAFONE Group Plc | Other |
| | MEC(19)000091 | MEC029-update to A.3 | Accepted | VODAFONE Group Plc | Other |
| | MEC(19)000090r1 | MEC029-update to A.2 | Accepted | VODAFONE Group Plc | Other |
| | MEC(19)000090 | MEC029-update to A.2 | Revised | VODAFONE Group Plc | Other |
| | MEC(19)000089r1 | MEC031 – Key issue on traffic routing | Accepted | Intel Corporation (UK) Ltd | Other |
| | MEC(19)000089 | MEC031 – Key issue on traffic routing | Revised | Intel Corporation (UK) Ltd | Other |
| | MEC(19)000088 | MEC024 – Discussion on the need for slice-aware support for MEC-enabled 5G deployments | Noted | Intel Corporation (UK) Ltd,University Carlos IIIde Madrid | Other |
| | MEC(19)000087 | MEC030 – Possible topics for the V2X API | Noted | Intel Corporation (UK) Ltd | Other |
| | MEC(19)000086r1 | MEC030 WI status update | Noted | Intel Corporation (UK) Ltd | Other |
| | MEC(19)000086 | MEC030 WI status update | Revised | Intel Corporation (UK) Ltd | Other |
| | MEC(19)000085r2 | MEC027 -MEC deployment considerations based on container | Accepted | China Mobile Research Inst. | Other |
| | MEC(19)000085r1 | MEC027 -MEC deployment considerations based on container | Revised | China Mobile Research Inst. | Other |
| | MEC(19)000085 | MEC027 -MEC deployment considerations based on container | Revised | China Mobile Research Inst. | Other |
| | MEC(19)000084 | MEC027 –Management API specifications impact | Noted (Rev. Requested) | China Mobile Research Inst. | Other |
| | MEC(19)000083r1 | MEC027 –Application to MEC: Mixing of virtualization technologies | Accepted | China Mobile Research Inst. | Other |
| | MEC(19)000083 | MEC027 –Application to MEC: Mixing of virtualization technologies | Revised | China Mobile Research Inst. | Other |
| | MEC(19)000082 | MEC0021_AMS_API_Individual_Subscription | Accepted | ZTE Corporation | Other |
| | MEC(19)000081 | MEC0021_AMS_API_Subscriptions | Accepted | ZTE Corporation | Other |
| | MEC(19)000080r1 | MEC0021_AMS_Data_Models_Subscription | Noted (Rev. Pre-Approved) | ZTE Corporation | Other |
| | MEC(19)000080 | MEC0021_AMS_Data_Models_Subscription | Revised | ZTE Corporation | Other |
| | MEC(19)000079r1 | MEC0021_AMS_Data_Models_Referenced_structured_data_types | Accepted | ZTE Corporation | Other |
| | MEC(19)000079 | MEC0021_AMS_Data_Models_Referenced_structured_data_types | Revised | ZTE Corporation | Other |
| | MEC(19)000078r2 | MEC0021_AMS_Data_Models_Notification | Accepted | ZTE Corporation | Other |
| | MEC(19)000078r1 | MEC0021_AMS_Data_Models_Notification | Revised | ZTE Corporation | Other |
| | MEC(19)000078 | MEC0021_AMS_Data_Models_Notification | Revised | ZTE Corporation | Other |
| | MEC(19)000077r1 | MEC0021_AMS_Sequence_diagram_intro | Accepted | ZTE Corporation | Other |
| | MEC(19)000077 | MEC0021_AMS_Sequence_diagram_intro | Revised | ZTE Corporation | Other |
| | MEC(19)000076 | MEC0021_AMS_API_Registration | Accepted | ZTE Corporation | Other |
| | MEC(19)000075r1 | MEC027_Virtualization_Technology_Descriptions_Text | Accepted | China Mobile Research Inst. | Other |
| | MEC(19)000075 | MEC027_Virtualization_Technology_Descriptions_Text | Revised | China Mobile Research Inst. | Other |
| | MEC(19)000074r1 | MEC0031 Key issue #X: Ping-pong handover mitigation | Accepted | KDDI Corporation | Other |
| | MEC(19)000074 | MEC0031 Key issue #X: Ping-pong handover mitigation | Revised | KDDI Corporation | Other |
| | MEC(19)000073r3 | MEC0031 Key issue #X: Traffic path update in the case where T-MEC HOST is not available | Accepted | KDDI Corporation | Other |
| | MEC(19)000073r2 | MEC0031 Key issue #X: Traffic path update in the case where T-MEC HOST is not available | Revised | KDDI Corporation | Other |
| | MEC(19)000073r1 | MEC0031 Key issue #X: Traffic path update in the case where T-MEC HOST is not available | Revised | KDDI Corporation | Other |
| | MEC(19)000073 | MEC0031 Key issue #X: Traffic path update in the case where T-MEC HOST is not available | Revised | KDDI Corporation | Other |
| | MEC(19)000072 | MEC0010-2 Status Update and Plan | Noted | ZTE Corporation | Other |
| | MEC(19)000071 | MEC0010-2_Editors_Notes_part-4 | Accepted | ZTE Corporation | Other |
| | MEC(19)000070r1 | MEC0010-2_Editors_Notes_part-3 | Accepted | ZTE Corporation | Other |
| | MEC(19)000070 | MEC0010-2_Editors_Notes_part-3 | Revised | ZTE Corporation | Other |
| | MEC(19)000069 | Draft - DGR/MEC-0027ContainerStudy v2.0.6 (GR MEC 027 ) | Noted | China Mobile Research Inst. | Draft |
| | MEC(19)000068 | MEC024 - Scope text proposal (section 1) | Accepted | University Carlos IIIde Madrid | Other |
| | MEC(19)000067r1 | MEC024 - Editorial changes and references formatting | Accepted | University Carlos IIIde Madrid | Other |
| | MEC(19)000067 | MEC024 - Editorial changes and references formatting | Revised | University Carlos IIIde Madrid | Other |
| | MEC(19)000066 | New draft of ETSI GR MEC 024 v2.0.8 | Noted | University Carlos IIIde Madrid | Draft |
| | MEC(19)000065 | ETSI MEC#128-Tech Call Minutes | Accepted | University Carlos IIIde Madrid | Report |
| | MEC(19)000064 | MEC0010-2AppLcRRMv207draft | Noted | ZTE Corporation | Other |
| | MEC(19)000058 | LS from ISG NFV on Status of FEAT12 (MECinNFV) | Noted | ETSI Secretariat | LSin |
| | MEC(19)000056r3 | Agenda for ETSI MEC Meeting#17 | Accepted | Chairman | Agenda |
| | MEC(19)000056r2 | Agenda for ETSI MEC Meeting#17 | Revised | Chairman | Agenda |
| | MEC(19)000056r1 | Agenda for ETSI MEC Meeting#17 | Revised | Chairman | Agenda |
| | MEC(19)000056 | Agenda for ETSI MEC Meeting#17 | Revised | Chairman | Agenda |
| | MEC(18)000510r4 | MEC IoT API | Accepted | Athonet S.r.l. | NWI |
| | MEC(18)000510r3 | MEC IoT API | Revised | Athonet S.r.l. | NWI |
| | MEC(18)000510r2 | MEC IoT API | Revised | Athonet S.r.l. | NWI |
| | MEC(18)000510r1 | MEC IoT API | Revised | Athonet S.r.l. | NWI |