RFC 3570 (rfc3570) - Page 2 of 20
Content Internetworking (CDI) Scenarios
Alternative Format: Original Text Document
RFC 3570 CDI Scenarios July 2003
5.1.2. Threats to the PUBLISHER..........................17
5.1.3. Threats to a CN...................................17
6. Acknowledgements..............................................18
7. References....................................................18
8. Authors' Addresses............................................19
9. Full Copyright Statement......................................20
1. Introduction
In [1], the concept of a "content network" is introduced and
described. In addition to describing some general types of content
networks, it also describes motivations for allowing content networks
to interconnect (defined as "content internetworking").
In describing content internetworking as a technology targeted for
use in production networks, it's useful to provide examples of the
sequence of events that may occur when two content networks decide to
interconnect. Naturally, different types of content networks may be
created due to different business motivations, and so many
combinations are likely.
This document first provides detailed examples of special cases of
content networks that are specifically designed to participate in
content internetworking (Section 2). We then discuss the steps that
would be taken in order to "bring up" or "tear down" a content
internetworking arrangement (Section 3). Next we provide some
detailed examples of how content networks (such as those from Section
2) could interconnect (Section 4). Finally, we describe any security
considerations that arise specifically from the examples presented
here (Section 5).
The scenarios presented here answer two distinct needs:
1. To provide some concrete examples of what content internetworking
is, and
2. To provide a basis for evaluating content internetworking
proposals.
A number of content internetworking systems have been implemented,
but there are few published descriptions. One such description is
[2].
1.1. Terminology
Terms in ALL CAPS are defined in [1] except for the following terms
defined below in this document: PCN, BCN, and LCN. Additionally, the
term SLA is used as an abbreviation for Service Level Agreement.
Rzewski, et al. Informational