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)
The RFC (Request for Comments) model originated in 1969 during the ARPANET era and later became the core process by which the IETF develops Internet standards.
RFC 9309 was published by the IETF in 2022 and is the first formal standard for the robots.txt protocol.
SCIM is an open standard published by the IETF, initially jointly promoted by vendors such as Salesforce, Google and Microsoft; it is REST-style, uses JSON as its data format, and defines core resource models such as User, Group and EnterpriseUser.
SIP (Session Initiation Protocol) is the most widely used signaling standard in internet telephony, responsible for establishing, modifying, and terminating voice and video calls.
SCIM 2.0 is an open standard protocol for cross-domain identity management published by the IETF as RFC 7642/7643/7644, defining standard REST endpoints and JSON Schema so that identity providers can automatically push user and group creation, update and deactivation events to application systems.
RFC 8785 (JCS) was published by the IETF in 2020 and defines rules for converting any JSON object into a unique byte sequence, including sorting keys by Unicode code point, normalizing number formats, removing extra whitespace, and fixing string escaping.
AER-1 is currently at the Internet-Draft stage and has not yet gone through the full IETF review and consensus process; the specification content may still change.
An IETF Internet-Draft is a precursor draft to an RFC; anyone can obtain it for free and comment publicly, with each round of revisions and review comments publicly archived.
Each receipt follows the AER-1 open standard, an Internet-Draft the author submitted to the IETF that defines a portable AI execution receipt format.
AER-1 (AI Execution Receipt) is currently still in draft stage and has not yet become a formal RFC standard.
38 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 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%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%UnverifiedSCIM (System for Cross-domain Identity Management) is currently at version 2.0 and is an IETF-standardized user directory synchronization protocol
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%UnverifiedThe RFC (Request for Comments) model originated in 1969 during the ARPANET era and later became the core process by which the IETF develops Internet standards.
50%UnverifiedRFC 9309 was published by the IETF in 2022 and is the first formal standard for the robots.txt protocol.
50%UnverifiedSCIM is an open standard published by the IETF, initially jointly promoted by vendors such as Salesforce, Google and Microsoft; it is REST-style, uses JSON as its data format, and defines core resource models such as User, Group and EnterpriseUser.
50%UnverifiedSCIM 2.0 is an open standard protocol for cross-domain identity management published by the IETF as RFC 7642/7643/7644, defining standard REST endpoints and JSON Schema so that identity providers can automatically push user and group creation, update and deactivation events to application systems.
50%UnverifiedRFC 8785 (JCS) was published by the IETF in 2020 and defines rules for converting any JSON object into a unique byte sequence, including sorting keys by Unicode code point, normalizing number formats, removing extra whitespace, and fixing string escaping.
50%UnverifiedAER-1 is currently at the Internet-Draft stage and has not yet gone through the full IETF review and consensus process; the specification content may still change.
50%UnverifiedAn IETF Internet-Draft is a precursor draft to an RFC; anyone can obtain it for free and comment publicly, with each round of revisions and review comments publicly archived.
50%