IETF
The Internet Engineering Task Force is the primary international body responsible for developing internet technical standards. It publishes RFC (Request for Comments) documents through an open working group process, covering core internet infrastructure standards including network protocols, security, and identity management.
Core Facts
OAuth 2.0 is defined by the IETF in RFC 6749.
The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011.
WebRTC was open-sourced by Google in 2011 and was subsequently standardized by W3C and IETF.
Timeline (last 90 days)
SCIM is an open identity management standard developed by the IETF and defined by RFC 7642/7643/7644.
SCIM is a RESTful protocol standardized by the IETF, and the current mainstream version is SCIM 2.0 (RFC 7642/7643/7644).
RFC 9449 (OAuth 2.0 Demonstrating Proof of Possession) is a standards specification published by the IETF that defines the complete DPoP framework, including binding for access tokens and refresh tokens, the nonce mechanism, error responses, and more.
The team is working on a post-quantum version, exploring two directions in parallel: replacing it with a post-quantum commitment scheme, and supporting identifier reuse (introducing a recycling mechanism and formalizing the "lifetime" concept proposed by Optics, using "certification age" to let users judge how new or old a label is); and they are submitting related standardization discussions to the IETF.
For an IETF draft to become a formal standard (RFC), it must go through multiple stages such as individual draft, working group draft and IESG review, and the cycle may last several years.
Web Bot Auth is an IETF draft that is still being developed.
In March 2018, someone on the IETF TLS mailing list discussed Section 4.2.1 of draft-ietf-tls-tls13-24: five people, six emails, and after three days the discussion fell silent.
RDAP is the standardized successor to WHOIS, defined by the IETF, used to query registration information for domain names and IP addresses, and returns structured JSON.
QUIC is a UDP-based transport-layer protocol designed by Google and standardized by the IETF as RFC 9000, aimed at reducing connection establishment latency and improving multiplexing efficiency.
The industry is discussing extending robots.txt semantics, for example clearly distinguishing different purposes such as "search crawling", "training data crawling" and "agent acting on behalf of a user", along with the IETF AIPREF working group and others developing machine-readable preference expressions.
40 more timeline events
All Facts (20)
OAuth 2.0 is defined by the IETF in RFC 6749.
90%VerifiedThe WebSocket protocol was standardized by the IETF as RFC 6455 in 2011.
80%VerifiedWebRTC was open-sourced by Google in 2011 and was subsequently standardized by W3C and IETF.
80%VerifiedJSON Schema is a specification for describing and validating JSON data structures, capable of defining field requirements, data types, and value ranges.
80%VerifiedJSON Schema is a declarative specification based on JSON format, originating from a community draft in 2009, with standardization work advanced by the IETF in RFC 8927 and subsequent drafts.
75%VerifiedAtom is an improved version of RSS, standardized by the IETF (RFC 4287), and is superior to RSS 2.0 in terms of format specification and internationalization support.
75%VerifiedJSON Schema is maintained by the IETF, and the current version is Draft 2020-12.
70%VerifiedThe IETF is the primary international body responsible for developing Internet technical standards, and the documents it publishes are called RFCs.
65%VerifiedSCIM 2.0 is a user directory synchronization protocol standardized by the IETF that defines a RESTful API specification for automating user lifecycle management between IdPs and applications.
65%VerifiedSCIM (System for Cross-domain Identity Management) is currently at version 2.0 and is an IETF-standardized user directory synchronization protocol
65%VerifiedGeoJSON is an open standard geospatial data format based on JSON, formally specified by the IETF in RFC 7946.
65%VerifiedThe /.well-known/ path is a standard convention defined by the IETF in RFC 5785.
65%UnverifiedGSMA在2024年底发布了RCS Universal Profile的加密扩展规范，基于MLS（Messaging Layer Security）协议
85%Partially VerifiedEach receipt follows the AER-1 open standard, an Internet-Draft the author submitted to the IETF that defines a portable AI execution receipt format.
65%Partially VerifiedAtom是2003年由IETF标准化的替代协议（RFC 4287）
65%UnverifiedSIP (Session Initiation Protocol) is the most widely used signaling standard in internet telephony, responsible for establishing, modifying, and terminating voice and video calls.
60%UnverifiedJMAP is a modern mail access protocol standardized by the IETF (RFC 8620/8621), based on HTTP and JSON, designed to replace the IMAP protocol that has existed for over 30 years, and natively supports push notifications, batch operations, and incremental synchronization.
60%UnverifiedSCIM is an open identity management standard developed by the IETF and defined by RFC 7642/7643/7644.
50%UnverifiedSCIM is a RESTful protocol standardized by the IETF, and the current mainstream version is SCIM 2.0 (RFC 7642/7643/7644).
50%UnverifiedRFC 9449 (OAuth 2.0 Demonstrating Proof of Possession) is a standards specification published by the IETF that defines the complete DPoP framework, including binding for access tokens and refresh tokens, the nonce mechanism, error responses, and more.
50%