Skip to main content
  • Working on Post-Quantum Cryptography for Open Source Software from Africa

    During the IETF 122 Hackathon in Bangkok and online last month, the cyberstorm.mu team from Mauritius, the United States, and Kenya participated remotely to implement post-quantum cryptography components currently missing from widely-used open source software such as nmap, zmap, wireshark, and GnuTLS.

    30 Apr 2025
  • IETF 122 post-meeting survey

    IETF 122 Bangkok was held 15-21 March 2025 and the results of the post-meeting survey are now available on a web-based interactive dashboard.

    17 Apr 2025
  • IETF Snapshot 2024

    Want to catch up on IETF activity in 2024? How many RFCs were published? How many Internet-Drafts were submitted? How many Working Groups were chartered or concluded? The IETF Snapshot provides a short summary of IETF activity for the previous year.

    17 Apr 2025
  • Report from RPC Retreat 2025

    In early April 2025, the RFC Production Center (RPC) and IETF LLC senior staff met for the first RPC retreat following the contract change that now has the RPC reporting directly to the IETF Executive Director. This was a high-level retreat, the first of its kind for the RPC, looking at community requirements and the RPC internal processes that deliver those.

    16 Apr 2025
  • New IRTF Chair Dirk Kutscher: Advancing Global Collaboration and Innovation in Internet Research

    The IETF Blog recently chatted with new Internet Research Task Force chair Dirk Kutscher about his views of where the IRTF is now and what the path ahead looks like.

    10 Apr 2025

Filter by topic and date

Filter by topic and date

WIMSE Working Group: Serious business for cloud computing

15 Oct 2024

Chartered in March 2024, the IETF Workload Identity in Multi System Environments (WIMSE) working group aims to address challenges of implementing fine-grained access control across platforms in the public and private clouds, which is increasingly important to how complex software functions are built and deployed.

The increasing prevalence of cloud computing and micro service architectures has led to the rise of complex software functions being built and deployed as workloads—instances of software executing for a specific purpose, across multiple service platforms. 

pexels-brett-sayles-buildingblock-wimse

WIMSE focuses on the unique identity and access management aspects of workloads at runtime and their execution context, particularly focusing on the propagation, representation, and processing of workload identity. While several standards and open-source projects—such as OAuth, JWT, and SPIFFE—offer foundational elements for this work, there are no established standards on how to combine these standards, or any guidance on how to bridge the gaps between them. . This can lead to inconsistencies, interoperability issues, and potential security vulnerabilities.

WIMSE formed from a Birds of a Feather session held during the IETF 118 meeting in Prague and first met as a working group during IETF 119 in Brisbane. Work has progressed rapidly since then and the group has already adopted three documents that identify, articulate, and bridge the gaps and ambiguities in multi-cloud workload identity deployments and define solutions that can be adopted across a diverse set of platforms and deployments. WIMSE is scheduled to meet during IETF 121 Dublin in November 2024.

WIMSE Service to Service Authentication“ defines authentication and authorization for software workloads in a variety of runtime environments, from the most basic ones up to complex multi-service, multi-cloud, multi-tenant deployments. This document defines the simplest, atomic unit of this architecture: the protocol between two workloads that need to verify each other's identity in order to communicate securely.

Workload Identity in a Multi System Environment (WIMSE) Architecture“ discusses an architecture for designing and standardizing protocols and payloads for conveying workload identity and security context information. 

Best Current Practice for OAuth 2.0 Client Authentication in Workload Environments” describes the current best practices to avoid client_secret provisioning and leverage platform attestation to receive access tokens from an OAuth 2.0 authorization server via RFC 7523. 

Work is ongoing…. If you are interested in working on these issues and contributing ideas and solutions, please sign up for the mailing list and plan to attend the session during IETF 121


Share this page