# protocol Published articles for protocol. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## \[Podcast\] 'Just say no' isn't as simple as you think DevFeed: [\[Podcast\] 'Just say no' isn't as simple as you think]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-09-16T23:23:11Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [APNIC Labs](), [Protocol (disambiguation)](), [Server]() Tags: [apnic-labs](), [dns](), [measurement](), [podcast](), [protocol](), [tech-matters]() ### AI overview A PING podcast episode continues a discussion of surplus DNS queries observed in an APNIC Labs experiment. It examines how different ways of answering negatively affect query volume and the work required by servers, resolvers, and clients, and considers whether maintaining transport protocol state could reduce repeated-query work. ### Source excerpt A continuation of the discussion on surplus DNS queries seen at APNIC Labs, the implications of how you say 'no', and the transport used for the DNS ## How Neon made Postgres claimable for agents with auth.md DevFeed: [How Neon made Postgres claimable for agents with auth.md]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-10T14:21:50Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Database](), [Protocol (disambiguation)](), [API](), [OAuth]() Tags: [agents](), [api](), [auth](), [database](), [protocol]() ### AI overview Neon used auth.md to let agents provision bounded temporary Postgres projects before a human creates an account. People can later claim the projects into a Neon organization, while unclaimed projects expire. ### Source excerpt How Neon used auth.md to let agents provision bounded database projects before a human signs up, then later transfer them to people who want to keep them. ## Can you design a chip? Announcing the protocol emulator ASIC competition DevFeed: [Can you design a chip? Announcing the protocol emulator ASIC competition]() Original publisher: [Read original article]() Author: Benjamin Devlin Published: 2026-09-10T00:00:00Z Content type: release Language: en Sources: [Jane Street]() Topics: [Chip design](), [Protocol (disambiguation)](), [Hardware](), [Open Source](), [Emulator](), [cpu](), [Reverse Engineering](), [fpga](), [Formal methods](), [Verilog]() Tags: [chip-design](), [cpu](), [emulator](), [ethernet](), [firmware](), [formal-methods](), [fpga](), [hardware](), [i2c](), [jtag](), [open-source](), [peripheral](), [protocol](), [reverse-engineering]() ### AI overview Jane Street announces a competition to design an open-source, general-purpose protocol emulator ASIC. The proposed chip would use a small programmable CPU to read and write pins, count cycles, and implement protocols in firmware, with fabrication planned through IHP and Tiny Tapeout. ### Source excerpt Last month, we asked you to reverse engineer a chip from nothing but its layout and teased a bigger challenge. Results and our favorite writeups are coming soon. In the meantime, here's our next challenge! This time, you're designing the chip, and we'll pay to fabricate our favorite designs! We're particularly interested in projects with unique functionality, as well as those that demonstrate novel approaches to design and verification methodologies! ## SCIM directory sync: A deep dive into deprovisioning DevFeed: [SCIM directory sync: A deep dive into deprovisioning]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-08T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Protocol (disambiguation)](), [Security](), [Parser](), [Entra ID]() Tags: [audit](), [deep-dive](), [filter](), [protocol](), [provisioning](), [reconciliation](), [security]() ### AI overview This deep dive explains how SCIM directory deprovisioning reaches applications, why identity providers commonly deactivate users instead of deleting them, and how provider-specific payloads and missed events can create security risks. It covers normalization, reconciliation, session termination, and inspecting provider requests. ### Source excerpt What actually happens when a user is removed: the event your app receives, the directories that never send one, and how to catch what gets dropped. ## Patching This Site's MCP Endpoint and Limiting What It Can Do DevFeed: [Patching This Site's MCP Endpoint and Limiting What It Can Do]() Original publisher: [Read original article]() Author: Brent Leekley Published: 2026-09-08T00:00:00Z Content type: tutorial Language: en Sources: [brent.leekley.me blog]() Topics: [Model Context Protocol](), [MCP Server](), [API](), [HTTP](), [JSON]() Tags: [aeo](), [agent-ready-website](), [agentic-ai](), [agents](), [api](), [api-security](), [clients](), [json-rpc](), [logs](), [mcp](), [mcp-server](), [model-context-protocol](), [prompt-injection](), [protocol](), [rate-limiting](), [retry](), [server](), [streamable-http](), [webmcp]() ### AI overview This article explains how to patch a website's public, unauthenticated MCP endpoint. It covers updating to the current protocol revision while retaining compatibility with older clients, and applying limits including read-only tools, per-IP rate limiting, request-size caps, Origin checks, POST-only access, non-reflected strings, and privacy-preserving logs. ### Source excerpt An MCP server on your website is a public, unauthenticated API. Bringing one to the current protocol revision while keeping older clients working, and the seven limits that bound it: read-only tools, a per-IP rate limit that always sends Retry-After, hard caps on body and argument size, an https-only Origin check, POST only, no reflected strings, and logs that store a salted hash instead of an address. ## EF Protocol: The Hegotá EIP Opinion Post and Tier List DevFeed: [EF Protocol: The Hegotá EIP Opinion Post and Tier List]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Cluster Published: 2026-09-07T00:00:00Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Protocol (disambiguation)](), [Testing](), [client]() Tags: [opinion](), [process](), [protocol](), [research-development](), [testing]() ### AI overview The EF Protocol cluster presents a unified tier list for 62 EIPs proposed for Hegotá. The assessment combines 397 tier grades from nine teams and individual contributors, with tiers defining delivery expectations and conditions for considering lower-tier proposals. ### Source excerpt This is the EF Protocol cluster's tier list for Hegotá. We evaluated the 62 EIPs proposed for inclusion, each with a tier and a short note on the grade. It is the first time the cluster has published one unified view rather than per-team opinions. Geth, of course, being... ## EF Protocol: Current and Emerging Priorities DevFeed: [EF Protocol: Current and Emerging Priorities]() Original publisher: [Read original article]() Author: Ethereum Foundation Protocol Cluster Published: 2026-09-07T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Post-Quantum](), [Protocol (disambiguation)](), [migration](), [data](), [Cloudflare](), [Google](), [Microsoft]() Tags: [data](), [ethereum](), [migration](), [post-quantum](), [protocol](), [research-development]() ### AI overview The EF Protocol cluster outlines Ethereum Protocol priorities through 2029, including scoping the Hegotá upgrade and preparing Ethereum L1 to become quantum-resistant across the execution, consensus, and data layers by December 2029. The plan uses an intentionally aggressive assumption that Q-day could occur as early as 2030, with the deadline to be reassessed in January 2027. ### Source excerpt In May, the Protocol cluster welcomed a trio of new cluster coordinators and promised updates to follow. After months of settling in and aligning with contributors cluster-wide, across the EF and across the Ethereum ecosystem, we are now happy to share Protocol's priorities: what Protocol is for, the commitments... ## Latent Powers DevFeed: [Latent Powers]() Original publisher: [Read original article]() Author: Armin Ronacher Published: 2026-09-05T00:00:00Z Content type: opinion Language: en Sources: [Armin Ronacher]() Topics: [Dongle](), [Hacking](), [Rust](), [Embedded Software Dev](), [Protocol (disambiguation)](), [Raspberry Pi]() Tags: [ai](), [dongle](), [firmware](), [hacking](), [protocol](), [raspberry-pi](), [rust](), [soc](), [thoughts](), [usb]() ### AI overview A developer experiments with modifying a cheap CarPlay dongle to run custom code while preserving regular CarPlay functionality. After receiving a different SoC than expected, they use LLM-assisted discussions to flash the device and compile CatPlay, a Rust reimplementation of the CarPlay protocol, for the hardware. ### Source excerpt A few weeks ago I felt like it would be fun to see if I can make one of those cheap Chinese CarPlay dongles run something other than the stock firmware. The idea was that rather than just forwarding CarPlay, why not do something more interesting with them? They all work quite similarly: they act as bridges between your car and the phone. From there they deal with video and audio streams and pass some other data through. Most of them also bring up a custom UI for pairing and have a web interface that your phone can reach for updates. Long story short: I had a conversation with Fable and Sol via Pi about what could be done with such a dongle or whether I should use a Raspberry Pi instead if I wanted to do my own thing there. I figured it might be quite fun to run my own code while still allowing regular CarPlay to pass through. Through working with the LLM I learned about CatPlay, which is a Rust reimplementation of the CarPlay protocol that can run on Carlinkit devices. In particular, it can run on the Carlinkit Mini Ultra, which I figured would be easy enough to buy. I do have a few CarPlay adapters around, but I did not have that particular model, so I bought one on Amazon. Twenty-four hours later, I had a device in my hand that was branded as a Carlinkit Mini Ultra, but instead of being the Ingenic device that the original author used, it turned out to be something else. This is normally where the story would stop. However, it's 2026. Armed with a bit of knowledge about how these systems work, I managed to have some fruitful discussions with Kimi K3 and Sol and figure out how flash the device and in turn, how to make CatPlay compile for that SoC. I guess that hacking these USB devices is not necessarily hard, but it's laborious and you can easily end up bricking your devices. It also just sucks because sometimes you need to work with someone else's code that does not itself run on your machine. In the past, I would abandon many such projects for lack of tenacity. ## The Evolution of HTTP, Clearly Explained DevFeed: [The Evolution of HTTP, Clearly Explained]() Original publisher: [Read original article]() Author: Nikki Siapno Published: 2026-09-04T16:39:02Z Content type: article Language: en Sources: [Level Up Coding System Design Newsletter]() Topics: [HTTP](), [client](), [servers](), [Caching](), [Web]() Tags: [browser](), [caching](), [encoding](), [evolution](), [http](), [http-3](), [protocol](), [request](), [responses](), [server](), [tcp]() ### AI overview An explanatory article traces HTTP from versions 0.9 through 1.1, describing how headers, status codes, persistent connections, caching, and chunked transfer encoding addressed the web's growing scale and performance needs. It introduces HTTP/3 as part of that broader evolution. ### Source excerpt From 0.9 to 3.0: What changed and why? ## MCP: Scope step-up is not authentication step-up DevFeed: [MCP: Scope step-up is not authentication step-up]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-01T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Model Context Protocol](), [Authentication](), [Authorization](), [MCP Server]() Tags: [authentication](), [authorization](), [browser](), [compliance](), [delivery](), [mcp](), [mcp-server](), [model-context-protocol](), [permission](), [protocol](), [scope](), [token]() ### AI overview The article distinguishes MCP scope step-up from authentication step-up. MCP's current authorization flow addresses insufficient permission by obtaining broader scopes, but it does not standardize verifying whether a human recently authenticated or is still present. It recommends binding out-of-band approval to the user and exact operation until this changes. ### Source excerpt MCP standardized how an agent asks for more permission. It has no vocabulary yet for asking whether the human behind the token is still there. ## Propagating User Identity Chains Across JVM Service Calls DevFeed: [Propagating User Identity Chains Across JVM Service Calls]() Original publisher: [Read original article]() Author: Peter Firmstone Published: 2026-08-23T00:00:00Z Content type: article Language: en Sources: [Nicolas Fränkel]() Topics: [Security](), [Java](), [Authorization](), [Protocol (disambiguation)]() Tags: [authorization](), [dirtychai](), [java](), [jgdms](), [jini](), [jvm](), [microservices](), [protocol](), [security](), [technical](), [tls](), [tokens]() ### AI overview This article explains how a chain of user identities crosses service calls on the wire. It distinguishes TLS machine authentication from in-band user claims, describes receiver-side limits and principal handling, and notes that standard Java 24 lacks the required authorization support without DirtyChai on both ends. ### Source excerpt Alice calls the order service. The order service calls the ledger on her behalf. At the second hop, the ledger has to decide whose authority the debit is being made under. Most stacks answer badly. Forward Alice's bearer token verbatim, and the ledger cannot tell her from the service that relayed it. Drop the token and the ledger sees a machine, with no record that a human started the chain. Neither option lets the ledger authorize the combination. ## Lowering Slot Time and Validator Economics DevFeed: [Lowering Slot Time and Validator Economics]() Original publisher: [Read original article]() Author: Umberto Natale Published: 2026-08-19T10:00:00Z Content type: article Language: en Sources: [Solana News Feed]() Topics: [Solana](), [Latency](), [Protocol (disambiguation)]() Tags: [blockchain](), [blockchain-technology](), [consensus](), [crypto-news](), [cryptocurrency](), [defi](), [infrastructure](), [latency](), [nfts](), [performance](), [podcasts](), [protocol](), [reports](), [solana](), [solana-ecosystem](), [upgrades](), [web3]() ### AI overview Solana plans to reduce slot times from 400 ms to 200 ms. The article examines possible effects on latency, arbitrage, sandwich MEV, validator rewards and costs, voting frequency, and consensus performance, while noting that some impacts require empirical mainnet monitoring. ### Source excerpt Solana will reduce its slot times from 400ms to 200ms. This change will make the protocol more competitive in terms of latency. Here we explore some possible implication on validators economic. ## A2A Is Now an Open Standard. The Data Layer Underneath It Isn't. DevFeed: [A2A Is Now an Open Standard. The Data Layer Underneath It Isn't.]() Original publisher: [Read original article]() Author: Quentin Packard Published: 2026-08-19T00:00:00Z Content type: opinion Language: en Sources: [Cockroach Labs]() Topics: [agent to agent communication](), [Multi Agent Systems](), [Model Context Protocol](), [Database](), [Artificial Intelligence]() Tags: [a2a](), [agent-to-agent-communication](), [agentic](), [agents](), [ai](), [architecture](), [database](), [mcp](), [model-context-protocol](), [multi-agent-systems](), [protocol](), [standards]() ### AI overview The article argues that A2A standardizes communication between agents but leaves the underlying data and state layer undefined. It contrasts A2A's horizontal agent-to-agent communication with MCP's vertical connection between an agent and external tools or data, and argues that production systems need both alongside a database-centered state architecture. AGENTS.md is presented as another interface standard that leaves durable state outside its scope. ### Source excerpt In April 2025, Google released a protocol for agent-to-agent communication. Within three months, Google had donated it to the Linux Foundation... ## RFC 9470 explained: The OAuth step-up authentication challenge protocol DevFeed: [RFC 9470 explained: The OAuth step-up authentication challenge protocol]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [OAuth 2.0](), [Protocol (disambiguation)](), [API](), [Authentication](), [Authorization](), [OpenID connect (OIDC)](), [client]() Tags: [api](), [authentication](), [authorization](), [oauth](), [oauth-2-0](), [oidc](), [openid-connect](), [protocol]() ### AI overview This article explains RFC 9470, the OAuth 2.0 Step-Up Authentication Challenge Protocol. It describes how a resource server can tell a client that the current access token does not meet the required authentication level and how the client can obtain stronger authentication, including the roles of acr_values, max_age, and auth_time. ### Source excerpt How an API tells a client that the user needs to authenticate again, why acr_values is only a request while max_age is a requirement, and what the auth_time claim actually proves. ## Is MCP Stateless or Stateful? DevFeed: [Is MCP Stateless or Stateful?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-08-14T06:51:31Z Content type: article Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Model Context Protocol (MCP)](), [Load Balancing]() Tags: [2026](), [architecture](), [faq](), [load-balancing](), [mcp](), [protocol](), [stateful](), [stateless]() ### AI overview The article states that MCP became stateless in version 2026-07-28, whereas the original release was stateful. It says requests are self-describing and independent, eliminating the need for connection handshakes, session IDs, and sticky load balancing. ### Source excerpt As of version 2026-07-28 the MCP protocol is now stateless. The original release was stateful. Every request is self-describing and independent, removing the need for connection handshakes, session IDs, or sticky load balancing. You can read all the important updates here: https://modelcontextprotocol.io/docs/2026-07-28/learn/architecture ## How an MCP client should tell your OAuth server who it is DevFeed: [How an MCP client should tell your OAuth server who it is]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-12T00:00:00Z Content type: comparison Language: en Sources: [WorkOS Blog]() Topics: [Model Context Protocol](), [OAuth](), [Authorization](), [API](), [client](), [audit trail](), [Deployment]() Tags: [api](), [audit-trail](), [authorization](), [mcp](), [oauth](), [open](), [protocol](), [server]() ### AI overview This article compares three ways an MCP client can identify itself to an OAuth authorization server: Dynamic Client Registration, Client ID Metadata Documents, and auth.md. It explains that DCR and CIMD establish software identity, while auth.md also addresses user delegation, and describes the MCP registration priority order and relevant deployment tradeoffs. ### Source excerpt Dynamic Client Registration is deprecated, and Client ID Metadata Documents answer only half the question. Here is what each pattern actually proves, and how auth.md adds the user delegation they leave out. ## IP Addressing, Part III: Inside the IP Packet DevFeed: [IP Addressing, Part III: Inside the IP Packet]() Original publisher: [Read original article]() Author: Franco Fernando Published: 2026-08-07T09:49:52Z Content type: tutorial Language: en Sources: [The Polymathic Engineer]() Topics: [Network](), [Protocol (disambiguation)]() Tags: [fragmentation](), [internet](), [ipv4](), [ipv6](), [network](), [payload](), [protocol]() ### AI overview This tutorial examines the IPv4 datagram and header fields, explains fragmentation and MTU constraints, discusses why TCP and IP use checksums, and describes changes introduced by IPv6. ### Source excerpt What actually travels on the wire: the IPv4 header, fragmentation, and what IPv6 changed. ## SCIM Deprovisioning Is a Promise Your App Probably Breaks DevFeed: [SCIM Deprovisioning Is a Promise Your App Probably Breaks]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T01:29:36Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Security](), [API](), [HTTP](), [JSON](), [Internet Engineering Task Force (IETF)](), [Protocol (disambiguation)]() Tags: [api](), [http](), [identity](), [idp](), [ietf](), [json](), [net-conf](), [protocol](), [schema](), [security](), [standards](), [state](), [token]() ### AI overview This article explains that SCIM deprovisioning updates identity state but does not automatically invalidate an application's sessions, refresh tokens, or API keys. It describes how identity providers commonly use soft deactivation and why applications must explicitly handle the resulting offboarding state. ### Source excerpt SCIM tells you a user is gone, but sessions, refresh tokens, and API keys often outlive deprovisioning. Here's why offboarding needs more than a user row. ## Emulating Terraform on Pulumi's Engine DevFeed: [Emulating Terraform on Pulumi's Engine]() Original publisher: [Read original article]() Author: Ian Wahbe Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Pulumi]() Topics: [Terraform](), [opentofu](), [terraform provider](), [configuration]() Tags: [engineering](), [hcl](), [modules](), [opentofu](), [protocol](), [providers](), [pulumi](), [terraform](), [terraform-provider](), [translation]() ### AI overview This article explains how Pulumi's HCL interpreter maps Terraform configuration, resources, providers, and modules onto the Pulumi engine. It reports that the implementation works with 96% of Pulumi's top Terraform modules and describes how Pulumi's terraform-provider relays between Pulumi and Terraform provider protocols. ### Source excerpt The core promise of Pulumi's HCL support is that you can bring your existing Terraform configuration and modules, and pulumi will run them. If it works in OpenTofu and doesn't work in Pulumi, we would like to fix that. Given that goal, our HCL interpreter needs to take HCL as input and emit instructions to the Pulumi engine that semantically match how tofu would interpret the same input. This is made harder by the fact that Pulumi and OpenTofu have fundamentally different engine semantics and provider ecosystems. This blog post will explore how we have implemented that mapping well enough to get 96%1 of our top Terraform modules working on Pulumi. We'll briefly walk through how Pulumi's HCL interpreter handles Terraform's resource semantics, providers, and modules. It will also call out where Pulumi's HCL support lets you do things that Terraform and OpenTofu will not allow. Providers Both Pulumi and Terraform have providers, but they don't have the same providers. While there are providers that Terraform does not have, Pulumi can always resolve a Terraform provider using Pulumi's confusingly named terraform-provider provider.2 This is the same provider that lets you consume Any Terraform Provider in another Pulumi program with pulumi package add terraform-provider .... The terraform-provider provider acts as a relay: it speaks Pulumi's protocol to the Pulumi engine, and speaks Terraform's provider protocol to the Terraform provider it stands up. Because Pulumi HCL needs to work with all Pulumi providers and because terraform-provider lets Pulumi HCL speak to Terraform providers via the Pulumi protocol, Pulumi HCL actually only speaks Pulumi protocols directly: flowchart LR subgraph n2Entry[" "] n2["terraform-provider"] end subgraph providerBox["Pulumi Provider"] direction TD n2Entry n3["Terraform Provider"] end n0["Pulumi HCL"] <--> n1["Pulumi Engine"] n1 <--> n2Entry n2 <--> n3 n2@{ shape: rect} n3@{ shape: rect} n0@{ shape: rect} n1@{ shape: rect} style n2Entry f ## I Rebuilt a Minimal BitTorrent Client in Go to Understand Peer-to-Peer Choking Algorithms DevFeed: [I Rebuilt a Minimal BitTorrent Client in Go to Understand Peer-to-Peer Choking Algorithms]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Algorithms](), [P2P](), [Go Language](), [Programming](), [Network]() Tags: [algorithms](), [bittorrent](), [distributed-systems](), [go](), [golang](), [network](), [networking](), [p2p](), [peer-to-peer](), [protocol](), [system-design]() ### AI overview A hands-on explanation of BitTorrent choking algorithms through rebuilding a minimal client in Go. The article describes choking as a decentralized bandwidth-allocation mechanism, explains the choked and interested states, and shows how upload capacity affects peer prioritization. ### Source excerpt The BitTorrent spec explains choking in two paragraphs; implementing it in Go and watching every peer choke you within 60 seconds is what makes it stick. Choking is a bandwidth allocator running independently on every node, not a courtesy flag. Upload is the scarce resource on an asymmetric link, and each connection carries just two booleans, choked and interested, whose four combinations drive the entire fairness policy of the swarm. ## Bluetooth Support Across Every Codename One Target DevFeed: [Bluetooth Support Across Every Codename One Target]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-26T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Bluetooth](), [API](), [simulator](), [Web](), [JavaScript]() Tags: [api](), [ble](), [bluetooth](), [browser](), [chrome](), [core](), [desktop](), [hardware](), [javascript](), [permission](), [platform](), [protocol](), [simulator](), [tests](), [web]() ### AI overview Codename One's core Bluetooth API adds cross-target support for BLE, GATT, L2CAP, classic RFCOMM, Web Bluetooth, and a scriptable simulator. The API exposes platform capabilities and limits, while the implementation handles queued GATT operations and callback timeouts. ### Source excerpt The core Bluetooth API covers BLE, GATT, L2CAP, classic RFCOMM, Web Bluetooth, and a scriptable simulator while exposing each platform's limits. ## RFC 9880 and the IoT Validation Problem DevFeed: [RFC 9880 and the IoT Validation Problem]() Original publisher: [Read original article]() Author: Stefano Fago Published: 2026-07-26T00:00:00Z Content type: article Language: en Sources: [Nicolas Fränkel]() Topics: [Internet of things](), [SDF](), [data](), [JSON](), [Code](), [CoAP](), [MQTT](), [HTTP](), [TLS (Transport Layer Security)]() Tags: [architecture](), [code](), [data](), [development](), [iot](), [json](), [protocol](), [sdf](), [standards](), [validation]() ### AI overview This article examines RFC 9880 and its Semantic Definition Format (SDF) as an ecosystem-neutral, JSON-based way to describe IoT devices. It argues that SDF validation is best understood as a compilation problem and discusses how different IoT ecosystems represent the same physical concepts incompatibly. ### Source excerpt The IoT/IIoT world has a data model problem and the concept of Digital Twin has made this issue more important. Plenty of people have tried to fix it. RFC 9880 and its Semantic Definition Format (SDF) are a serious attempt: a JSON-based, ecosystem-neutral way to describe what a device is and what it does. I have had some experiences with this specification, and I've understood that the format shows its full value once you treat it as source code, something you compile. ## Announcing Espressif's Aliro SDK DevFeed: [Announcing Espressif's Aliro SDK]() Original publisher: [Read original article]() Author: John Lee Published: 2026-07-16T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [SDKs](), [Matter]() Tags: [aliro](), [blog](), [bluetooth-le](), [espressif](), [matter](), [mobile](), [nfc](), [protocol](), [sdk]() ### AI overview Espressif announces esp-aliro, an SDK for supporting the Aliro standardized mobile access-credentials protocol on Espressif SoCs. Initial support covers Aliro over NFC, while Bluetooth LE and UWB support are planned. ### Source excerpt Aliro brings mobile access credentials to Espressif devices and is compatible with Matter. We are excited to announce esp-aliro, an SDK that enables support for the Aliro standardized protocol on Espressif SoCs. ## \[GSoC 2026\] Modernizing Haiku's Bluetooth stack: Implementing support for HFP profile - Mid-Term Progress Report DevFeed: [\[GSoC 2026\] Modernizing Haiku's Bluetooth stack: Implementing support for HFP profile - Mid-Term Progress Report]() Original publisher: [Read original article]() Author: vighnesh-sawant Published: 2026-07-15T14:32:12Z Content type: article Language: en Sources: [Haiku Project]() Topics: [Bluetooth](), [Protocol (disambiguation)](), [systems](), [real-time](), [Streaming](), [USB](), [Kernel](), [interface]() Tags: [api](), [bluetooth](), [driver](), [gsoc](), [haiku](), [implementing](), [kernel](), [modernizing](), [progress-report](), [protocol](), [real-time](), [report](), [software](), [streaming](), [usb]() ### AI overview A GSoC 2026 progress report on modernizing Haiku's Bluetooth stack by adding groundwork for the Hands-Free Profile. Completed work includes isochronous USB endpoint support, SCO handling, kernel hooks, and SCO and RFCOMM protocol implementations. Planned work covers SPP, SDP, and the remaining HFP functionality. ### Source excerpt Introduction Hello again! It has been a fun journey since the beginning of GSoC. My project focuses on modernizing Haiku's Bluetooth stack, specifically adding support for the Hands-Free Profile (HFP). HFP is a profile that allows operating systems to interact with Bluetooth audio devices, such as headsets, for two-way voice calls and audio streaming. Today, I'll be sharing a progress report on the work I have completed till now, and will outline my plans for the remainder of the project. Progress So Far A significant portion of my work has been dedicated to laying the groundwork for the HFP profile. Because Haiku's Bluetooth stack previously lacked the necessary transport layers for real-time audio, I had to implement several underlying protocols. Here is a breakdown of the changes I've made: USB and Driver Support (Isochronous Endpoints): I started off by adding support for isochronous USB endpoints to the h2generic Bluetooth driver. Isochronous transfers are critical because they guarantee bandwidth and timely delivery of data, which is a requirement for streaming real-time audio. Following this, I implemented SCO (Synchronous Connection-Oriented) handling within h2transactions, along with the proper scheduling mechanism.. Kernel Hooks: I added the necessary hooks for SCO and HCI (Host Controller Interface) commands. Protocol Implementations (SCO and RFCOMM): I successfully added the core implementations for both the SCO and RFCOMM protocols. RFCOMM provides an emulated serial interface over L2CAP. It serves as the control channel for many higher-level profiles, including HFP. SCO handles the actual low-latency audio transmission needed for voice calls. What's Next? Short-term Goals: Serial Port Profile (SPP) The Serial Port Profile sits on top of RFCOMM and provides a standard way to send and receive data. Implement SPP API: I will be implementing the JSR82 API methods for SPP in the Bluetooth kit. Implementing the Hands-Free Profile (HFP) The remaining time wil [Next page]()