| |    | MEC(23)000128r1 | GUTMA - Opportunities with MEC | Noted | Nokia Germany | Other |
| | | MEC(23)000128 | GUTMA - Opportunities with MEC | Revised | Nokia Germany | Other |
| | | MEC(23)000127 | pres from Optare Solutions - MEC hackathon 2022 special 5GAA prize winner | Noted | Chair | Other |
| | | MEC(23)000124 | ISG answers to ETSI survey on inclusiveness | Noted | Chair | Other |
| | | MEC(23)000123r1 | Work Items State of play at MEC33 closing plenary | Accepted | Chair | Other |
| | | MEC(23)000123 | Work Items State of play at MEC33 closing plenary | Revised | Chair | Other |
| | | MEC(23)000122 | Joint TFS - MEC contribution | Noted | CTTC | Other |
| | | MEC(23)000121 | A demonstration of embedding distributed MonB5G intelligence for 6G networks | Noted | CTTC | Other |
| | | MEC(23)000120r1 | MEC040 Reverting Editor’s notes and reflecting editorial corrections from v311 | Accepted | KDDI Corporation | Other |
| | | MEC(23)000120 | MEC040 Reverting Editor’s notes and reflecting editorial corrections from v311 | Revised | KDDI Corporation | Other |
| | | MEC(23)000119 | Hackathon Discussion MEC#33 | Noted | InterDigital, Inc. | Other |
| | | MEC(23)000118 | CTTC Overview - Welcome Slot | Noted | CTTC | Other |
| | | MEC(23)000117 | WG Chair’s DECODE Report to ETSI ISG MEC Meeting#33 | Noted | WG/TG Chair | Other |
| | | MEC(23)000116r1 | ETSI_MEC#33 meeting minutes | Accepted | Chair | Report |
| | | MEC(23)000116 | ETSI_MEC#33 meeting minutes | Revised | Chair | Report |
| | | MEC(23)000115 | MEC discussion slot on 6G | Noted | Chair | Other |
| | | MEC(23)000114r2 | LS on publication of ETSI MEC specifications | Accepted | Chair | LSout |
| | | MEC(23)000114r1 | LS on publication of ETSI MEC specifications | Revised | Chair | LSout |
| | | MEC(23)000114 | LS on publication of ETSI MEC specifications | Revised | Chair | LSout |
| | | MEC(23)000113 | MEC044 remove the Editor’s Note in clause 6.3.2 | Available | China Telecommunications | Other |
| | | MEC(23)000112 | MEC044 remove the Editor’s Note in clause 6.2.2 | Accepted | China Telecommunications | Other |
| | | MEC(23)000111 | MEC044 Structuring the needed signalling for two recommended architectures for MEC App Slice | Noted | China Telecommunications | Other |
| | | MEC(23)000110 | STF644 Progress Report Milestone A | Withdrawn | xFlow Research Inc. | Other |
| | | MEC(23)000109 | Discussion on Possible ETSI MEC Enhancements | Noted | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000108r1 | MEC043 Thoughts on way forward | Noted | Nokia Germany | Other |
| | | MEC(23)000108 | MEC043 Thoughts on way forward | Revised | Nokia Germany | Other |
| | | MEC(23)000107r3 | MEC010-2 – create app instance info over Mm3, part 1 | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000107r2 | MEC010-2 – create app instance info over Mm3, part 1 | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000107r1 | MEC010-2 – create app instance info over Mm3, part 1 | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000107 | MEC010-2 – create app instance info over Mm3, part 1 | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000106r1 | MEC045 Synchronisation threshold | Accepted | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000106 | MEC045 Synchronisation threshold | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000105r1 | MEC045 throughput | Accepted | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000105 | MEC045 throughput | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000104r1 | MEC036 – Open Discussion @ MEC#33 | Noted | InterDigital, Inc. | Other |
| |  | MEC(23)000104 | MEC036 – Open Discussion @ MEC#33 | Revised | InterDigital, Inc. | Other |
| | | MEC(23)000103r2 | MEC 036 Input to Solution section - Telco Edge and Far Edge Interaction – Relay Function | Accepted | InterDigital, Inc. | Other |
| | | MEC(23)000103r1 | MEC 036 Input to Solution section - Telco Edge and Far Edge Interaction – Relay Function | Revised | InterDigital, Inc. | Other |
| | | MEC(23)000103 | MEC 036 Input to Solution section - Telco Edge and Far Edge Interaction – Mediator Function | Revised | InterDigital, Inc. | Other |
| | | MEC(23)000102r1 | MEC011 – adding runtime attributes to AppInfo | Accepted | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000102 | MEC011 – adding runtime attributes to AppInfo | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000101r1 | MEC046 – Status of the WI activity and next steps | Noted | FONDAZIONE LINKS | Other |
| | | MEC(23)000101 | MEC046 – Status of the WI activity and next steps | Revised | FONDAZIONE LINKS | Other |
| | | MEC(23)000100r1 | Work Items State of play at MEC33 opening plenary | Noted | Chair | Other |
| | | MEC(23)000100 | Work Items State of play at MEC33 opening plenary | Revised | Chair | Other |
| | | MEC(23)000099 | MEC33 opening plenary - report from the chair perspective | Noted | Chair | Other |
| | | MEC(23)000098r7 | MEC040 data model of FedServiceInfo | Accepted | KDDI Corporation | Other |
| | | MEC(23)000098r6 | MEC040 data model of FedServiceInfo | Revised | KDDI Corporation | Other |
| | | MEC(23)000098r5 | MEC040 data model of FedServiceInfo | Revised | KDDI Corporation | Other |
| | | MEC(23)000098r4 | MEC040 data model and URI Resource of FedServiceInfo | Revised | KDDI Corporation | Other |
| | | MEC(23)000098r3 | MEC040 data model and URI Resource of FedServiceInfo | Revised | KDDI Corporation | Other |
| | | MEC(23)000098r2 | MEC040 data model and URI Resource of FedServiceInfo | Revised | KDDI Corporation | Other |
| | | MEC(23)000098r1 | MEC040 data model and URI Resource of FedServiceInfo | Revised | KDDI Corporation | Other |
| | | MEC(23)000098 | MEC040 data model and URI Resource of FedServiceInfo | Revised | KDDI Corporation | Other |
| | | MEC(23)000097r2 | MEC040_discussion on service discovery | Noted | KDDI Corporation | Other |
| | | MEC(23)000097r1 | MEC040_discussion on service discovery | Revised | KDDI Corporation | Other |
| | | MEC(23)000097 | MEC040_discussion on service discovery | Revised | KDDI Corporation | Other |
| | | MEC(23)000096r1 | MEC011-MEC010-2-MEC040 – discussion on app registration and discovery | Noted | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000096 | MEC011-MEC010-2-MEC040 – discussion on app registration and discovery | Revised | Huawei Tech.(UK) Co.. Ltd | Other |
| | | MEC(23)000095 | Discussion on Edge Native White Paper | Noted | CNIT | Other |
| | | MEC(23)000094 | LS from ETSI Board INCLU on inclusiveness in ETSI | Noted | ETSI Secretariat | LSin |
| | | MEC(23)000093 | Considerations on V2X messages interoperability and QoS predictions for abstracted RNIS | Noted | Mitsubishi Electric RCE | Other |
| | | MEC(23)000092r1 | MEC010-2 APIs resource URI structure variant for supporting forward request to MEF | Revised | ZTE Corporation | Other |
| | | MEC(23)000092 | MEC010-2 APIs resource URI structure variant for supporting forward request to MEF | Revised | ZTE Corporation | Other |
| | | MEC(23)000091r1 | MEC010-2 Updating message flows description for supporting forward request to MEF | Accepted | ZTE Corporation | Other |
| | | MEC(23)000091 | MEC010-2 Updating message flows description for supporting forward request to MEF | Revised | ZTE Corporation | Other |
| | | MEC(23)000090r2 | MEC010-2 Adding new requirement on Mm1 for supporting MEC federation | Accepted | ZTE Corporation | Other |
| | | MEC(23)000090r1 | MEC010-2 Adding new requirement on Mm1 for supporting MEC federation | Revised | ZTE Corporation | Other |
| | | MEC(23)000090 | MEC010-2 Adding new requirement on Mm1 for supporting MEC federation | Revised | ZTE Corporation | Other |
| | | MEC(23)000089 | Discussion about MEC010-2 change proposal on supporting APP package management and LCM in Federation scenario | Noted | ZTE Corporation | Other |
| | | MEC(23)000088r3 | MEC 010-2 Add annex on application updates best practices | Revised | MITRE Corporation | CR |
| | | MEC(23)000088r2 | MEC 010-2 Add annex on application updates best practices | Revised | MITRE Corporation | CR |
| | | MEC(23)000088r1 | MEC 010-2 Add annex on application updates best practices | Revised | MITRE Corporation | CR |
| | | MEC(23)000088 | MEC 010-2 Add annex on application updates best practices | Revised | MITRE Corporation | CR |
| | | MEC(23)000087r2 | MEC041 Add key issue on security for application decommissioning | Accepted | MITRE Corporation | Other |
| | | MEC(23)000087r1 | MEC041 Add key issue on security for application decommissioning | Revised | MITRE Corporation | Other |
| | | MEC(23)000087 | MEC041 Add key issue on security for application decommissioning | Revised | MITRE Corporation | Other |
| | | MEC(23)000086r1 | MEC041 - Add solution on example attestation | Revised | MITRE Corporation | Other |
| | | MEC(23)000086 | MEC041 - Add solution on example attestation | Revised | MITRE Corporation | Other |
| | | MEC(23)000085r2 | MEC041 - Add solution on security for application decommissioning | Accepted | MITRE Corporation | Other |
| | | MEC(23)000085r1 | MEC041 - Add solution on security for application decommissioning | Revised | MITRE Corporation | Other |
| | | MEC(23)000085 | MEC041 - Add solution on security for application decommissioning | Revised | MITRE Corporation | Other |
| | | MEC(23)000084r2 | MEC041 - Add solution on security for application updates | Accepted | MITRE Corporation | Other |
| | | MEC(23)000084r1 | MEC041 - Add solution on security for application updates | Revised | MITRE Corporation | Other |
| | | MEC(23)000084 | MEC041 - Add solution on security for application updates | Revised | MITRE Corporation | Other |
| | | MEC(23)000083 | Virtualized mobile and edge infrastructures with OpenAPI integrations | Noted | CTTC | Other |
| | | MEC(23)000082r1 | VERGE project outline | Noted | CTTC | Other |
| | | MEC(23)000082 | VERGE project outline | Revised | CTTC | Other |
| | | MEC(23)000081 | MEC for AR in a law enforcement ecosystem | Noted | CTTC | Other |
| | | MEC(23)000080 | MEC011 draft revision v3.1.5 | Noted | Huawei Tech.(UK) Co.. Ltd | Draft |
| | | MEC(23)000079r1 | MEC040 moving a note to proper place | Accepted | ZTE Corporation | Other |
| | | MEC(23)000079 | MEC040 moving a note to proper place | Revised | ZTE Corporation | Other |
| | | MEC(23)000078 | MEC011 little bug fix in clause 7.1.2.2 | Accepted | ZTE Corporation | Other |
| | | MEC(23)000077r1 | MEC010-2 Improvement to 6.2.1.9 based on RC comment | Accepted | ZTE Corporation | Other |
| | | MEC(23)000077 | MEC010-2 Improvement to 6.2.1.9 based on RC comment | Revised | ZTE Corporation | Other |
| | | MEC(23)000076 | ETSI_MEC TECH call 276 minutes | Accepted | Chair | Report |
| | | MEC(23)000075r1 | ISG MEC rules and process for next appointment of MEC WG DECODE Vice Chair | Noted | ETSI Secretariat | Other |
| | | MEC(23)000075 | ISG MEC rules and process for next appointment of MEC WG DECODE Vice Chair | Revised | ETSI Secretariat | Other |
| | | MEC(23)000071r2 | ISG MEC related 2023 events | Noted | ETSI Secretariat | Other |
| | | MEC(23)000071r1 | ISG MEC related 2023 events | Revised | ETSI Secretariat | Other |