{"meta": {"limit": 20, "next": "/api/v1/doc/document/?limit=20&offset=20", "offset": 0, "previous": null, "total_count": 160845}, "objects": [{"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/1474/", "id": 2087, "intended_std_level": null, "keywords": "[]", "name": "minutes-66-rohc", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/minutes-66-rohc/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/79/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2006-08-11T21:18:22Z", "title": "Minutes for ROHC at IETF-66", "type": "/api/v1/name/doctypename/minutes/", "uploaded_filename": "rohc.txt", "words": null}, {"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/2393/", "id": 120015, "intended_std_level": null, "keywords": "[]", "name": "minutes-117-mlcodec-202307260000", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/minutes-117-mlcodec-202307260000/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/79/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2023-08-05T17:39:58Z", "title": "Minutes IETF117: mlcodec: Tue 17:00", "type": "/api/v1/name/doctypename/minutes/", "uploaded_filename": "minutes-117-mlcodec-202307260000-00.md", "words": null}, {"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/1678/", "id": 4022, "intended_std_level": null, "keywords": "[]", "name": "slides-68-softwire-0", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/slides-68-softwire-0/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/141/", "/api/v1/doc/state/138/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2007-03-19T16:34:29Z", "title": "Intro", "type": "/api/v1/name/doctypename/slides/", "uploaded_filename": "softwire-0/softwire-0.htm", "words": null}, {"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/1678/", "id": 4023, "intended_std_level": null, "keywords": "[]", "name": "slides-68-softwire-1", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/slides-68-softwire-1/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/141/", "/api/v1/doc/state/138/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2007-03-18T07:00:00Z", "title": "Hub & Spoke framework", "type": "/api/v1/name/doctypename/slides/", "uploaded_filename": "softwire-1.pdf", "words": null}, {"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/1678/", "id": 4024, "intended_std_level": null, "keywords": "[]", "name": "slides-68-softwire-2", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/slides-68-softwire-2/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/141/", "/api/v1/doc/state/138/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2007-03-19T16:35:15Z", "title": "Mesh framework", "type": "/api/v1/name/doctypename/slides/", "uploaded_filename": "softwire-2/softwire-2.htm", "words": null}, {"abstract": "This specification defines the \"IPv6 over the TSCH mode of IEEE 802.15.4\" (6TiSCH) Minimal Scheduling Function (MSF).  This Scheduling Function describes both the behavior of a node when joining the network and how the communication schedule is managed in a distributed fashion.  MSF is built upon the 6TiSCH Operation Sublayer Protocol (6P) and the minimal security framework for 6TiSCH.", "ad": "/api/v1/person/person/108992/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1903/", "id": 130835, "intended_std_level": null, "keywords": "['TSCH', 'communication schedule', '6P']", "name": "rfc9033", "note": "", "notify": "", "pages": 20, "resource_uri": "/api/v1/doc/document/rfc9033/", "rev": "", "rfc": "9033", "rfc_number": 9033, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/ps/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:42:50Z", "title": "6TiSCH Minimal Scheduling Function (MSF)", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "This document specifies the Deterministic Networking (DetNet) MPLS data plane when operating over an IEEE 802.1 Time-Sensitive Networking (TSN) sub-network.  This document does not define new procedures or processes.  Whenever this document makes statements or recommendations, they are taken from normative text in the referenced RFCs.", "ad": "/api/v1/person/person/106471/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1962/", "id": 130839, "intended_std_level": null, "keywords": "['sub-network', 'flow mapping']", "name": "rfc9037", "note": "", "notify": "", "pages": 11, "resource_uri": "/api/v1/doc/document/rfc9037/", "rev": "", "rfc": "9037", "rfc_number": 9037, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/inf/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:43:19Z", "title": "Deterministic Networking (DetNet) Data Plane: MPLS over IEEE 802.1 Time-Sensitive Networking (TSN)", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "The Extensible Provisioning Protocol (EPP), as defined in RFC 5730, includes a method for the client and server to determine the objects to be managed during a session and the object extensions to be used during a session.  The services are identified using namespace URIs, and an \"unhandled namespace\" is one that is associated with a service not supported by the client.  This document defines an operational practice that enables the server to return information associated with unhandled namespace URIs and that maintains compliance with the negotiated services defined in RFC 5730.", "ad": "/api/v1/person/person/21684/", "expires": null, "external_url": "", "group": "/api/v1/group/group/2146/", "id": 130840, "intended_std_level": null, "keywords": "['login', 'greeting', 'URI', 'namespace', 'response', 'general', 'poll', 'object-level', 'command-response', 'signal', 'signaling']", "name": "rfc9038", "note": "", "notify": "", "pages": 21, "resource_uri": "/api/v1/doc/document/rfc9038/", "rev": "", "rfc": "9038", "rfc_number": 9038, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/ps/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:43:19Z", "title": "Extensible Provisioning Protocol (EPP) Unhandled Namespaces", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "This document describes a new Uniform Resource Name (URN) namespace for hardware device identifiers.  A general representation of device identity can be useful in many applications, such as in sensor data streams and storage or in equipment inventories.  A URN-based representation can be passed along in applications that need the information.", "ad": "/api/v1/person/person/21684/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1789/", "id": 130841, "intended_std_level": null, "keywords": "['URN', 'device identifier', 'IMEI', '1-Wire', 'MAC address', 'EUI-48', 'EUI-64']", "name": "rfc9039", "note": "", "notify": "", "pages": 15, "resource_uri": "/api/v1/doc/document/rfc9039/", "rev": "", "rfc": "9039", "rfc_number": 9039, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/ps/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:43:20Z", "title": "Uniform Resource Names for Device Identifiers", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "   This document defines RFC-OOP-C, a standard for object-oriented\n   programming in pure C.  It specifies naming conventions, class\n   structure macros, method macros, validation macros, memory allocation\n   patterns, lifecycle management, build-level configuration, struct\n   versioning, Doxygen documentation requirements, and a conformance\n   checker interface (the RFC-OOP-C Conformance Checker, RFC_Checker).\n\n   The standard targets C11 (ISO/IEC 9899:2011) and is applicable to any\n   C project on any microcontroller or platform whose toolchain supports\n   C11.  Supplementary guidance is provided for embedded systems\n   including thread-safety and memory allocation strategies compatible\n   with bare-metal, FreeRTOS and embOS.\n", "ad": null, "expires": "2026-12-25T22:10:00Z", "external_url": "", "group": "/api/v1/group/group/1027/", "id": 157450, "intended_std_level": null, "keywords": "[]", "name": "draft-imcode-rfc-oop-c", "note": "", "notify": "", "pages": 26, "resource_uri": "/api/v1/doc/document/draft-imcode-rfc-oop-c/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/1/", "/api/v1/doc/state/150/"], "std_level": null, "stream": null, "submissions": ["/api/v1/submit/submission/164835/"], "tags": [], "time": "2026-06-23T22:10:00Z", "title": "Object-Oriented Programming Standard for Pure C", "type": "/api/v1/name/doctypename/draft/", "uploaded_filename": "", "words": null}, {"abstract": "This document changes the policy of the \"Location-to-Service Translation (LoST) Location Profiles\" IANA registry established by RFC 5222 from Standards Action to Specification Required.  This allows standards development organizations (SDOs) other than the IETF to add new values.", "ad": "/api/v1/person/person/106842/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1643/", "id": 130838, "intended_std_level": null, "keywords": "[]", "name": "rfc9036", "note": "", "notify": "", "pages": 4, "resource_uri": "/api/v1/doc/document/rfc9036/", "rev": "", "rfc": "9036", "rfc_number": 9036, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/ps/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:16:36Z", "title": "Changing the Location-to-Service Translation (LoST) Location Profiles Registry Policy", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "This memo provides guidance to TCP implementers that is intended to help improve connection convergence to steady-state operation without affecting interoperability.  It updates and replaces RFC 2140's description of sharing TCP state, as typically represented in TCP Control Blocks, among similar concurrent or consecutive connections.", "ad": "/api/v1/person/person/106541/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1620/", "id": 130842, "intended_std_level": null, "keywords": "[]", "name": "rfc9040", "note": "", "notify": "", "pages": 29, "resource_uri": "/api/v1/doc/document/rfc9040/", "rev": "", "rfc": "9040", "rfc_number": 9040, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/inf/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:16:40Z", "title": "TCP Control Block Interdependence", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "This document describes a network architecture that provides low-latency, low-jitter, and high-reliability packet delivery.  It combines a high-speed powered backbone and subnetworks using IEEE 802.15.4 time-slotted channel hopping (TSCH) to meet the requirements of low-power wireless deterministic applications.", "ad": "/api/v1/person/person/106412/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1903/", "id": 130832, "intended_std_level": null, "keywords": "['deterministic wireless', 'radio', 'mesh']", "name": "rfc9030", "note": "", "notify": "", "pages": 57, "resource_uri": "/api/v1/doc/document/rfc9030/", "rev": "", "rfc": "9030", "rfc_number": 9030, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/inf/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:42:26Z", "title": "An Architecture for IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4 (6TiSCH)", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": 17202}, {"abstract": "In the Time-Slotted Channel Hopping (TSCH) mode of IEEE Std 802.15.4, opportunities for broadcasts are limited to specific times and specific channels.  Routers in a TSCH network transmit Enhanced Beacon (EB) frames to announce the presence of the network.  This document provides a mechanism by which additional information critical for new nodes (pledges) and long-sleeping nodes may be carried within the EB in order to conserve use of broadcast opportunities.", "ad": "/api/v1/person/person/106412/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1903/", "id": 130834, "intended_std_level": null, "keywords": "['BRSKI', 'enroll', 'zero-touch', 'DODAG balancing', 'LLN balancing']", "name": "rfc9032", "note": "", "notify": "", "pages": 10, "resource_uri": "/api/v1/doc/document/rfc9032/", "rev": "", "rfc": "9032", "rfc_number": 9032, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/ps/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:42:40Z", "title": "Encapsulation of 6TiSCH Join and Enrollment Information Elements", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "This document updates RFC 8138 by defining a bit in the Routing Protocol for Low-Power and Lossy Networks (RPL) Destination-Oriented Directed Acyclic Graph (DODAG) Configuration option to indicate whether compression is used within the RPL Instance and to specify the behavior of nodes compliant with RFC 8138 when the bit is set and unset.", "ad": "/api/v1/person/person/109802/", "expires": null, "external_url": "", "group": "/api/v1/group/group/1730/", "id": 130837, "intended_std_level": null, "keywords": "['IoT', 'Header Compression', 'Source Routing Header', 'Hop-by-Hop Header', 'RPL artifacts']", "name": "rfc9035", "note": "", "notify": "", "pages": 9, "resource_uri": "/api/v1/doc/document/rfc9035/", "rev": "", "rfc": "9035", "rfc_number": 9035, "shepherd": null, "states": ["/api/v1/doc/state/177/"], "std_level": "/api/v1/name/stdlevelname/ps/", "stream": "/api/v1/name/streamname/ietf/", "submissions": [], "tags": [], "time": "2026-05-20T15:43:14Z", "title": "A Routing Protocol for Low-Power and Lossy Networks (RPL) Destination-Oriented Directed Acyclic Graph (DODAG) Configuration Option for the 6LoWPAN Routing Header", "type": "/api/v1/name/doctypename/rfc/", "uploaded_filename": "", "words": null}, {"abstract": "   Network operators frequently run both Bidirectional Forwarding\n   Detection (BFD) for rapid fault detection and an active measurement\n   protocol such as STAMP for delay and loss measurement between the\n   same pair of nodes, resulting in two parallel packet streams with\n   overlapping timing requirements.\n\n   This document defines an optional STAMP TLV that carries a BFD\n   Control message within STAMP test packets, using the extension format\n   of RFC 8972.  A single test packet stream can then drive both the BFD\n   state machine and STAMP performance measurement.  The BFD protocol\n   itself is unchanged.\n", "ad": null, "expires": "2027-01-06T01:56:54Z", "external_url": "", "group": "/api/v1/group/group/1027/", "id": 157742, "intended_std_level": null, "keywords": "[]", "name": "draft-li-ippm-stamp-bfd-tlv", "note": "", "notify": "", "pages": 6, "resource_uri": "/api/v1/doc/document/draft-li-ippm-stamp-bfd-tlv/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/1/", "/api/v1/doc/state/150/"], "std_level": null, "stream": null, "submissions": ["/api/v1/submit/submission/165628/"], "tags": [], "time": "2026-07-05T01:56:54Z", "title": "A STAMP Extension for Carrying Bidirectional Forwarding Detection Control Messages", "type": "/api/v1/name/doctypename/draft/", "uploaded_filename": "", "words": null}, {"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/1474/", "id": 2088, "intended_std_level": null, "keywords": "[]", "name": "slides-66-rohc-0", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/slides-66-rohc-0/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/141/", "/api/v1/doc/state/138/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2006-07-11T21:21:41Z", "title": "HCoIPsec slides", "type": "/api/v1/name/doctypename/slides/", "uploaded_filename": "rohc-0/rohc-0.htm", "words": null}, {"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/1474/", "id": 2089, "intended_std_level": null, "keywords": "[]", "name": "slides-66-rohc-1", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/slides-66-rohc-1/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/141/", "/api/v1/doc/state/138/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2006-07-09T07:00:00Z", "title": "Chair's slides", "type": "/api/v1/name/doctypename/slides/", "uploaded_filename": "rohc-1/rohc-1.htm", "words": null}, {"abstract": "   Path Segment is a type of Segment Routing (SR) segment, which is used\n   to identify an SR path.  This document provides Target Forwarding\n   Equivalence Class (FEC) Stack TLV definitions for Path Segment\n   Identifiers.\n", "ad": null, "expires": "2024-07-29T08:29:55Z", "external_url": "", "group": "/api/v1/group/group/1140/", "id": 98769, "intended_std_level": null, "keywords": "[]", "name": "draft-xp-mpls-spring-lsp-ping-path-sid", "note": "", "notify": "tsaad.net@gmail.com", "pages": 17, "resource_uri": "/api/v1/doc/document/draft-xp-mpls-spring-lsp-ping-path-sid/", "rev": "09", "rfc": null, "rfc_number": null, "shepherd": "/api/v1/person/email/tsaad.net@gmail.com/", "states": ["/api/v1/doc/state/4/", "/api/v1/doc/state/150/", "/api/v1/doc/state/35/"], "std_level": null, "stream": "/api/v1/name/streamname/ietf/", "submissions": ["/api/v1/submit/submission/115263/", "/api/v1/submit/submission/119147/", "/api/v1/submit/submission/122805/", "/api/v1/submit/submission/124555/", "/api/v1/submit/submission/126770/", "/api/v1/submit/submission/130646/", "/api/v1/submit/submission/131341/", "/api/v1/submit/submission/135957/", "/api/v1/submit/submission/138166/", "/api/v1/submit/submission/139635/"], "tags": [], "time": "2024-06-04T02:35:23Z", "title": "Label Switched Path (LSP) Ping for Segment Routing (SR) Path Segment Identifiers (SIDs) with MPLS Data Planes", "type": "/api/v1/name/doctypename/draft/", "uploaded_filename": "", "words": null}, {"abstract": "", "ad": null, "expires": null, "external_url": "", "group": "/api/v1/group/group/1678/", "id": 4025, "intended_std_level": null, "keywords": "[]", "name": "slides-68-softwire-3", "note": "", "notify": "", "pages": null, "resource_uri": "/api/v1/doc/document/slides-68-softwire-3/", "rev": "00", "rfc": null, "rfc_number": null, "shepherd": null, "states": ["/api/v1/doc/state/141/", "/api/v1/doc/state/138/"], "std_level": null, "stream": null, "submissions": [], "tags": [], "time": "2007-03-19T16:36:16Z", "title": "Tunnel SAFI", "type": "/api/v1/name/doctypename/slides/", "uploaded_filename": "softwire-3/softwire-3.htm", "words": null}]}