Status: Individual Draft (Submitted to IETF) Version: draft-jurkovikj-collab-tunnel-01 Date: November 14, 2025 Author: Antun Jurkovikj IETF Datatracker: https://datatracker.ietf.org/doc/draft-jurkovikj-collab-tunnel/
This document specifies the Collaboration Tunnel Protocol, an HTTP-based method for efficient, verifiable delivery of web content to automated agents. The protocol uses bidirectional URL discovery, template-invariant content fingerprinting with strong ETags, sitemap-first verification, and strict conditional request discipline to reduce bandwidth while preserving canonical URLs.
Current Version (01):
- π Markdown
- π Text (RFC format)
- π XML (IETF submission)
- π HTML
- π PDF
Previous Versions:
- WordPress Plugin - 491 URLs across 4 production sites, 100% RFC compliance
- Cloudflare Worker - Edge-based header normalization
- Python Client Library - Available on PyPI:
pip install collab-tunnel
Test the protocol on these production sites:
- https://bestdemotivationalposters.com/llm-sitemap.json (200 URLs)
- https://wellbeing-support.com/llm-sitemap.json (200 URLs)
- https://omacedonii.com/llm-sitemap.json (65 URLs)
- https://llmpages.org/llm-sitemap.json (26 URLs)
Based on 491 URLs across 4 production sites:
- Bandwidth savings: 83% vs HTML-only crawling (103 KB average HTML β 17.7 KB average JSON)
- Token savings: 86% for AI processing (13,900 tokens β 1,960 tokens)
- Skip rate: 90%+ for unchanged content using sitemap-first verification
- 304 response rate: 100% after initial fetch (ETag validation working)
- RFC compliance: 100% of endpoints (RFC 9110, 9111, 8288)
The Collaboration Tunnel Protocol consists of four coordinated mechanisms:
- C-URL (HTML page) β M-URL (JSON endpoint) via
<link rel="alternate"> - M-URL β C-URL via
Link: <C-URL>; rel="canonical"header - Prevents SEO conflicts
- Content normalized through 6-step pipeline (operates on JSON
contentfield, not HTML):- Decode HTML entities (& β &, β β β)
- Apply Unicode NFKC normalization
- Apply Unicode case folding (locale-independent lowercase)
- Remove control characters (Unicode category Cc), except TAB, LF, CR
- Collapse ASCII whitespace (SPACE, TAB, LF, CR) to single space
- Trim leading/trailing whitespace
- Then compute SHA-256 hash over normalized UTF-8 bytes
- Strong ETag format:
"sha256-..."(computed over canonical JSON bytes) - Method A (recommended): Hash canonical JSON excluding hash field
- Method B (allowed): Hash normalized content text (content-locked)
- Stable across theme/template changes
- Parity verification: Clients MUST verify
contentHash == clean(ETag) == payload.hashvia string equality - Deterministic JSON: Implementations MUST use stable key order, UTF-8, compact serialization per RFC 8785 or equivalent
- If-None-Match takes precedence
- 304 Not Modified for unchanged content
- Strict caching requirements
- JSON sitemap lists (cUrl, mUrl, contentHash)
- Skip fetch if hash unchanged (zero-fetch optimization)
- 90%+ skip rate in production
{
"profile": "tct-1",
"canonical_url": "https://example.com/post/",
"title": "Article Title",
"content": "Core article content...",
"hash": "sha256-2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae",
"modified": "2025-10-15T14:30:00Z"
}HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Link: <https://example.com/post/>; rel="canonical"
ETag: "sha256-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
Cache-Control: max-age=0, must-revalidate, stale-while-revalidate=60, stale-if-error=86400
Vary: Accept-Encoding{
"version": 1,
"profile": "tct-1",
"items": [
{
"cUrl": "https://example.com/post/",
"mUrl": "https://example.com/post/llm/",
"modified": "2025-10-23T18:00:00Z",
"contentHash": "sha256-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
}
]
}Profile Field: The "profile": "tct-1" field enables protocol versioning. Future versions (e.g., tct-2) can introduce new fields while maintaining backward compatibility.
WordPress:
# Install plugin
wp plugin install trusted-collab-tunnel --activate
# Or download from: https://wordpress.org/plugins/trusted-collab-tunnel/Cloudflare Worker:
// Deploy worker from: https://github.com/antunjurkovic-collab/trusted-collab-workerPython:
pip install collab-tunnelfrom collab_tunnel import CollabTunnelCrawler
crawler = CollabTunnelCrawler(user_agent="MyBot/1.0")
sitemap = crawler.fetch_sitemap("https://example.com/llm-sitemap.json")
for item in sitemap.items:
if crawler.should_fetch(item): # Zero-fetch optimization
content = crawler.fetch_content(item['mUrl'])
print(content['title'])
stats = crawler.get_stats()
print(f"Bandwidth saved: {stats['savings_percentage']}%")This is an individual draft submitted to the IETF and seeking community feedback.
- IETF Datatracker: https://datatracker.ietf.org/doc/draft-jurkovikj-collab-tunnel/
- Issues: https://github.com/antunjurkovic-collab/collab-tunnel-spec/issues
- Email: antunjurkovic@gmail.com
- Version 01 (November 14, 2025): Incorporated expert feedback, added Unicode normalization test vectors, enhanced security considerations
- Version 00 (October 2025): Initial submission
This specification may be covered by US Patent Application 63/895,763 (filed October 8, 2025, status: Patent Pending).
An IPR disclosure has been submitted to the IETF declaring that licenses under any patent claims held by the author will be made available on a Royalty-Free basis under reasonable terms and conditions for all implementations of this specification.
For All Implementers:
- β Royalty-Free licensing for all implementations
- β No restrictions on commercial or non-commercial use
- β No restrictions on scale or deployment size
- β Open and interoperable implementations encouraged
For questions about IPR: antunjurkovic@gmail.com
This specification document is provided under the IETF Trust Legal Provisions for IETF Documents (BCP 78, BCP 79).
Implementations of this protocol are licensed on a Royalty-Free basis as described in the IPR disclosure above. The specification is published to encourage widespread adoption and ensure interoperability.
- Website: https://llmpages.org
- Validator: https://llmpages.org/validator/
- Documentation: https://llmpages.org/docs/
- PyPI Package: https://pypi.org/project/collab-tunnel/
- WordPress Plugin: https://wordpress.org/plugins/trusted-collab-tunnel/
Contributions, suggestions, and feedback are welcome!
Please open an issue or submit a pull request for:
- Specification improvements
- Clarifications
- Additional examples
- Error corrections
Thanks to:
- WordPress and Cloudflare communities for implementation platforms
- IETF HTTP Working Group for foundational HTTP standards (RFC 9110, 9111, 8288, 6596)
- Open Archives Initiative for ResourceSync inspiration
- Early adopters testing the protocol on production sites