RFC 3570: Content Internetworking (CDI) Scenarios
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6770.
Current version: RFC 6770 — Use Cases for Content Delivery Network Interconnection
In plain English — editorial summary, not part of the RFC
In describing content internetworking as a technology targeted for use in production networks, it is useful to provide examples of the sequence of events that may occur when two content networks decide to interconnect. The scenarios presented here seek to provide some concrete examples of what content internetworking is, and also to provide a basis for evaluating content internetworking proposals. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3570
- Published
- July 2003
- Authors
- P. Rzewski; M. Day; D. Gilletti
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 20
- Also known as
- —
- Obsoleted by:
- RFC 6770
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3568Known Content Network (CN) Request-Routing MechanismsUpdated
July 2003
- RFC 3538Secure Electronic Transaction (SET) Supplement for the v1.0 Internet Open Trading Protocol (IOTP)Current
June 2003
- RFC 3510Internet Printing Protocol/1.1: IPP URL SchemeCurrent
April 2003
- RFC 3506Requirements and Design for Voucher Trading System (VTS)Current
March 2003
- RFC 3505Electronic Commerce Modeling Language (ECML): Version 2 RequirementsCurrent
March 2003
- RFC 3504Internet Open Trading Protocol (IOTP) Version 1, ErrataCurrent
March 2003
- RFC 3492Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)Updated
March 2003
- RFC 3648Web Distributed Authoring and Versioning (WebDAV) Ordered Collections ProtocolCurrent
December 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?