{"author":{"id":0,"name":"","url":"https://llmpages.org/author/"},"canonical_url":"https://llmpages.org/drafts/","categories":null,"content":"Drafts\n\nThe current published Internet-Drafts, with stable links to the exact Datatracker revisions used by this site.\n\nAll four are individual submissions. Publication as an Internet-Draft does not imply IETF adoption, consensus, endorsement, or standards status.\n\n\nProtocol drafts\n\nThe Collaboration Content Transfer (TCT) Protocol\nRevision: -03 · Status: published Internet-Draft\nPublisher-selected machine-facing representations, bidirectional discovery, deterministic JSON catalogs, and strong HTTP validators.\nTCT overview · Datatracker -03\n\nHTTP Profile for Conditional Updates to Shared Resource State\nRevision: -02 · Status: published Internet-Draft\nAST Core uses strong ETags and If-Match; the optional AST Semantic profile adds concurrency domains.\nAST overview · Datatracker -02\n\n\n\nSemantic Validators for HTTP\nRevision: -01 · Status: published Internet-Draft\nSemantic-ETag and If-Semantic-Match for representation-independent optimistic concurrency.\nSemantic Validators overview · Datatracker -01\n\nDeterministic Three-Way Merge for JSON Values\nRevision: -00 · Status: published Internet-Draft\nDeterministic merge, ordered conflicts, typed failures, and bounded processing for a restricted JSON domain.\nJSON Merge overview · Datatracker -00\n\n\n\nReading guidance\nUse the exact revision links above; later local candidates are not presented here as published revisions.\nRead AST Core independently before the optional Semantic profile.\nTreat JSON merge as an application-independent reconciliation primitive, not an HTTP protocol.\nImplementation results are bounded engineering evidence, not proof of IETF status or general deployment suitability.","content_media_type":"text/plain; charset=utf-8","excerpt":"The current published Internet-Drafts, with stable links to the exact Datatracker revisions used by this site. All four are individual submissions. Publication as an Internet-Draft does not imply IETF adoption, consensus, endorsement, or standards status. Protocol drafts The Collaboration Content Transfer (TCT) Protocol Revision: -03 · Status: published Internet-Draft Publisher-selected machine-facing representations, bidirectional discovery, deterministic","headings":[{"anchor":null,"level":2,"text":"Protocol drafts"},{"anchor":null,"level":3,"text":"The Collaboration Content Transfer (TCT) Protocol"},{"anchor":null,"level":3,"text":"HTTP Profile for Conditional Updates to Shared Resource State"},{"anchor":null,"level":3,"text":"Semantic Validators for HTTP"},{"anchor":null,"level":3,"text":"Deterministic Three-Way Merge for JSON Values"},{"anchor":null,"level":2,"text":"Reading guidance"}],"image":null,"images":null,"lastModified":"2026-08-15T16:46:40+00:00","llm_url":"https://llmpages.org/drafts/llm/","post_id":920,"post_type":"page","profile":"https://www.ietf.org/archive/id/draft-jurkovikj-collab-tunnel-03.html#tct-m-url-profile","published":"2026-08-15T14:42:32+00:00","slug":"drafts","tags":null,"title":"Drafts","word_count":203}