draft-ietf-cdi-scenarios-00.txt   draft-ietf-cdi-scenarios-01.txt 
Network Working Group M. Day Network Working Group P. Rzewski
Internet-Draft Cisco Internet-Draft Inktomi
Expires: August 22, 2002 D. Gilletti Expires: October 24, 2002 M. Day
Cisco
D. Gilletti
CacheFlow CacheFlow
P. Rzewski April 24, 2002
Inktomi
February 22, 2002
Content Internetworking (CDI) Scenarios Content Internetworking (CDI) Scenarios
draft-ietf-cdi-scenarios-00.txt draft-ietf-cdi-scenarios-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 22, 2002. This Internet-Draft will expire on October 24, 2002.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
In describing content internetworking as a technology targeted for In describing content internetworking as a technology targeted for
use in the "real world", it's useful to provide examples of the use in production networks, it's useful to provide examples of the
possible sequence of events that may occur when two content networks sequence of events that may occur when two content networks decide
decide to interconnect. The scenarios presented here seek to provide to interconnect. The scenarios presented here seek to provide some
some concrete examples of what content internetworking is, and also concrete examples of what content internetworking is, and also to
to provide a basis for evaluating content internetworking proposals. provide a basis for evaluating content internetworking proposals.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1 Terminology....................................................3 1.1 Terminology....................................................3
2. Special Cases of Content Networks..............................3 2. Special Cases of Content Networks..............................3
2.1 Publishing Content Network.....................................4 2.1 Publishing Content Network.....................................4
2.2 Brokering Content Network......................................4 2.2 Brokering Content Network......................................4
2.3 Local Request-Routing Content Network..........................4 2.3 Local Request-Routing Content Network..........................4
3. Content Internetworking Arrangements...........................5 3. Content Internetworking Arrangements...........................5
skipping to change at page 2, line 25 skipping to change at page 2, line 25
4.1 General Content Internetworking................................6 4.1 General Content Internetworking................................6
4.2 BCN providing ACCOUNTING INTERNETWORKING and REQUEST-ROUTING 4.2 BCN providing ACCOUNTING INTERNETWORKING and REQUEST-ROUTING
INTERNETWORKING................................................9 INTERNETWORKING................................................9
4.3 BCN providing ACCOUNTING INTERNETWORKING......................11 4.3 BCN providing ACCOUNTING INTERNETWORKING......................11
4.4 PCN ENLISTS multiple CNs......................................12 4.4 PCN ENLISTS multiple CNs......................................12
4.5 Multiple CNs ENLIST LCN.......................................13 4.5 Multiple CNs ENLIST LCN.......................................13
5. Security Considerations.......................................15 5. Security Considerations.......................................15
6. Acknowledgements..............................................15 6. Acknowledgements..............................................15
References....................................................15 References....................................................15
Authors' Addresses............................................16 Authors' Addresses............................................16
Full Copyright Statement..........................................16 Full Copyright Statement......................................16
1. Introduction 1. Introduction
In [1], the concept of a "content network" is introduced and In [1], the concept of a "content network" is introduced and
described. In addition to describing some general types of content described. In addition to describing some general types of content
networks, it also describes motivations for allowing content networks, it also describes motivations for allowing content
networks to interconnect (defined as ˘content internetworking÷). networks to interconnect (defined as "content internetworking").
In describing content internetworking as a technology targeted for In describing content internetworking as a technology targeted for
use in the "real world", it's useful to provide examples of the use in production networks, it's useful to provide examples of the
possible sequence of events that may occur when two content networks sequence of events that may occur when two content networks decide
decide to interconnect. Naturally, different types of content to interconnect. Naturally, different types of content networks may
networks may be created due to different business motivations, and be created due to different business motivations, and so many
so many combinations are likely. combinations are likely.
This document first provides detailed examples of special cases of This document first provides detailed examples of special cases of
content networks that are specifically designed to participate in content networks that are specifically designed to participate in
content internetworking (Section 2). We then discuss the steps that content internetworking (Section 2). We then discuss the steps that
would be taken in order to "bring up" or "tear down" a content would be taken in order to "bring up" or "tear down" a content
internetworking arrangement (Section 3). Next we provide some internetworking arrangement (Section 3). Next we provide some
detailed examples of how content networks (such as those from detailed examples of how content networks (such as those from
Section 2) could interconnect (Section 4). Finally, we describe any Section 2) could interconnect (Section 4). Finally, we describe any
security considerations that arise specifically from the examples security considerations that arise specifically from the examples
presented here (Section 5). presented here (Section 5).
skipping to change at page 4, line 49 skipping to change at page 4, line 49
example, a BCN could aggregate CONTENT SIGNALS from CNs that example, a BCN could aggregate CONTENT SIGNALS from CNs that
represent PUBLISHERS into a single update stream for the benefit of represent PUBLISHERS into a single update stream for the benefit of
CNs that contain SURROGATES. A BCN may also choose to participate in CNs that contain SURROGATES. A BCN may also choose to participate in
ACCOUNTING INTERNETWORKING in order to aggregate utilization data ACCOUNTING INTERNETWORKING in order to aggregate utilization data
from several CNs into combined reports for CNs that represent from several CNs into combined reports for CNs that represent
PUBLISHERS. PUBLISHERS.
This definition of a BCN implies that a BCN's CIGs would implement This definition of a BCN implies that a BCN's CIGs would implement
the sending and/or receiving of any combination of ADVERTISEMENTS the sending and/or receiving of any combination of ADVERTISEMENTS
and ACCOUNTING data as is necessary to provide desired services to and ACCOUNTING data as is necessary to provide desired services to
other CONTENT NETWORKS. For example, a BCN only interested in other CONTENT NETWORKS. For example, if a BCN is only interested in
aggregating ACCOUNTING data on behalf of other CNs would only need aggregating ACCOUNTING data on behalf of other CNs, it would only
to have an ACCOUNTING INTERNETWORKING interface on its CIGs. need to have an ACCOUNTING INTERNETWORKING interface on its CIGs.
2.3 Local Request-Routing Content Network 2.3 Local Request-Routing Content Network
Another type of CN is the Local Request-Routing CONTENT NETWORK Another type of CN is the Local Request-Routing CONTENT NETWORK
(LCN). An LCN is defined as a type of network where CLIENTS' CONTENT (LCN). An LCN is defined as a type of network where CLIENTS' CONTENT
REQUESTS are always handled by some local SERVER (such as a caching REQUESTS are always handled by some local SERVER (such as a caching
proxy [1]). In this context, "local" is taken to mean that both the proxy [1]). In this context, "local" is taken to mean that both the
CLIENT and SERVER are within the same administrative domain, and CLIENT and SERVER are within the same administrative domain, and
there is an administrative motivation for forcing the local mapping. there is an administrative motivation for forcing the local mapping.
This type of arrangement is common in enterprises where all CONTENT This type of arrangement is common in enterprises where all CONTENT
REQUESTS must be directed through a local SERVER for access control REQUESTS must be directed through a local SERVER for access control
purposes. purposes.
As implied by the name, the LCN creates an exception to the rule As implied by the name, the LCN creates an exception to the rule
that there is a single AUTHORITATIVE REQUEST-ROUTING SYSTEM for a that there is a single AUTHORITATIVE REQUEST-ROUTING SYSTEM for a
particular item of CONTENT. By directing CONTENT REQUESTS through particular item of CONTENT. By directing CONTENT REQUESTS through
the local SERVER, CONTENT RESPONSES may be given to CLIENTS without the local SERVER, CONTENT RESPONSES may be given to CLIENTS without
first referring to the AUTHORITATIVE REQUEST-ROUTING SYSTEM. Knowing first referring to the AUTHORITATIVE REQUEST-ROUTING SYSTEM. Knowing
this to be true, other CNs may seek a NEGOTIATED RELATIONSHIP with this to be true, other CNs may seek a NEGOTIATED RELATIONSHIP with
an LCN in order to perform DISTRIBUTION into the LCN and receive an LCN in order to perform DISTRIBUTION into the LCN and receive
ACCOUNTING data from it. Note that once it's participating in ACCOUNTING data from it. Note that once SERVERS participate in
DISTRIBUTION INTERNETWORKING and ACCOUNTING INTERNETWORKING, the DISTRIBUTION INTERNETWORKING and ACCOUNTING INTERNETWORKING, they
SERVERS within the LCN effectively take on the role of SURROGATES. effectively take on the role of SURROGATES. However, an LCN would
However, an LCN would not intend to allow its SURROGATES to be not intend to allow its SURROGATES to be accessed by non-local
accessed by non-local CLIENTS. CLIENTS.
This set of assumptions implies multiple things about the LCN's This set of assumptions implies multiple things about the LCN's
CONTENT INTERNETWORKING relationships. First, it is implied that the CONTENT INTERNETWORKING relationships. First, it is implied that the
LCN's DISTRIBUTION INTERNETWORKING SYSTEM need only be able to send LCN's DISTRIBUTION INTERNETWORKING SYSTEM need only be able to send
DISTRIBUTION ADVERTISEMENTS, it need not receive them. Second, it is DISTRIBUTION ADVERTISEMENTS, it need not receive them. Second, it is
implied that an LCN's ACCOUNTING INTERNETWORKING SYSTEM need only be implied that an LCN's ACCOUNTING INTERNETWORKING SYSTEM need only be
able to send ACCOUNTING data, it need not receive it. Finally, due able to send ACCOUNTING data, it need not receive it. Finally, due
to the locally defined REQUEST-ROUTING, the LCN would not to the locally defined REQUEST-ROUTING, the LCN would not
participate in REQUEST-ROUTING INTERNETWORKING. participate in REQUEST-ROUTING INTERNETWORKING.
skipping to change at page 6, line 8 skipping to change at page 6, line 8
The next step would be to configure CONTENT INTERNETWORKING The next step would be to configure CONTENT INTERNETWORKING
protocols on the CIGs of the respective CNs in order to technically protocols on the CIGs of the respective CNs in order to technically
support the terms of the NEGOTIATED RELATIONSHIP. To follow our support the terms of the NEGOTIATED RELATIONSHIP. To follow our
previous example, this could include the configuration of the previous example, this could include the configuration of the
ENLISTED CN's CIGs in a particular country to send DISTRIBUTION ENLISTED CN's CIGs in a particular country to send DISTRIBUTION
ADVERTISEMENTS to the CIGs of the ORIGINATING CN. In order to ADVERTISEMENTS to the CIGs of the ORIGINATING CN. In order to
configure these protocols, technical details (such as CIG configure these protocols, technical details (such as CIG
addresses/hostnames and authentication information) would be addresses/hostnames and authentication information) would be
exchanged by administrators of the respective CNs. exchanged by administrators of the respective CNs.
Note also that some terms of the NEGOTIATED RELATIONSHIP would be
upheld through means outside the scope of CDI protocols. These could
include non-technical terms (such as financial settlement) or other
technical terms (such as SLAs).
In the event that the controlling interests of two CNs no longer In the event that the controlling interests of two CNs no longer
wish to have their networks interconnected, it is expected that wish to have their networks interconnected, it is expected that
these tasks would be undone in reverse order. That is, first the these tasks would be undone. That is, the protocol configurations
protocol configurations would be changed to cease the movement of would be changed to cease the movement of ADVERTISEMENTS and/or
ADVERTISEMENTS and/or ACCOUNTING data between the networks. After ACCOUNTING data between the networks, and the NEGOTIATED
this, the NEGOTIATED RELATIONSHIP would be legally terminated. RELATIONSHIP would be legally terminated.
4. Content Internetworking Scenarios 4. Content Internetworking Scenarios
This section provides several scenarios that may arise in CONTENT This section provides several scenarios that may arise in CONTENT
INTERNETWORKING implementations. INTERNETWORKING implementations.
Note that we obviously cannot examine every single permutation. Note that we obviously cannot examine every single permutation.
Specifically, it should be noted that: Specifically, it should be noted that:
o Any one of the interconnected CNs may have other CONTENT o Any one of the interconnected CNs may have other CONTENT
skipping to change at page 6, line 50 skipping to change at page 6, line 55
This scenario considers the general case where two or more existing This scenario considers the general case where two or more existing
CNs wish to establish a CONTENT INTERNETWORKING relationship in CNs wish to establish a CONTENT INTERNETWORKING relationship in
order to provide increased scale and reach for their existing order to provide increased scale and reach for their existing
customers. It assumes that all of these CNs already provide REQUEST- customers. It assumes that all of these CNs already provide REQUEST-
ROUTING, DISTRIBUTION, and ACCOUNTING services and that they will ROUTING, DISTRIBUTION, and ACCOUNTING services and that they will
continue to provide these services to existing customers as well as continue to provide these services to existing customers as well as
offering them to other CNs. offering them to other CNs.
In this scenario, these CIs would interconnect with others via a CIG In this scenario, these CIs would interconnect with others via a CIG
which provides a REQUEST-ROUTING INTERNETWORKING SYSTEM, a that provides a REQUEST-ROUTING INTERNETWORKING SYSTEM, a
DISTRIBUTION INTERNETWORKING SYSTEM, and an ACCOUNTING DISTRIBUTION INTERNETWORKING SYSTEM, and an ACCOUNTING
INTERNETWORKING SYSTEM. The net result of this interconnection would INTERNETWORKING SYSTEM. The net result of this interconnection would
be that a larger set of SURROGATES will now be available to the be that a larger set of SURROGATES will now be available to the
CLIENTS. CLIENTS.
FIGURE 1 shows three CNs which have interconnected to provide FIGURE 1 shows three CNs which have interconnected to provide
greater scale and reach to their existing customers. They are all greater scale and reach to their existing customers. They are all
participating in DISTRIBUTION INTERNETWORKING, REQUEST-ROUTING participating in DISTRIBUTION INTERNETWORKING, REQUEST-ROUTING
INTERNETWORKING, and ACCOUNTING INTERNETWORKING. INTERNETWORKING, and ACCOUNTING INTERNETWORKING.
As a result of the NEGOTIATED RELATIONSHIPS it is assumed that: As a result of the NEGOTIATED RELATIONSHIPS it is assumed that:
1. CONTENT that has been INJECTED into any one of these ORIGINATING 1. CONTENT that has been INJECTED into any one of these ORIGINATING
CNs may be distributed into any other ENLISTED CN. CNs may be distributed into any other ENLISTED CN.
2. Commands affecting the DISTRIBUTION of CONTENT may be issued 2. Commands affecting the DISTRIBUTION of CONTENT may be issued
within the ORIGINATING CN, or may also be issued within the within the ORIGINATING CN, or may also be issued within the
ENLISTED CN. ENLISTED CN. The latter case allows local decisions to be made
about DISTRIBUTION within the ENLISTED CN, but such commands
would not control DISTRIBUTION within the ORIGINATING CN.
3. ACCOUNTING information regarding CLIENT access and/or 3. ACCOUNTING information regarding CLIENT access and/or
DISTRIBUTION actions will be made available to the ORIGINATING DISTRIBUTION actions will be made available to the ORIGINATING
CN by the ENLISTED CN. CN by the ENLISTED CN.
4. The ORIGINATING CN would provide this ACCOUNTING information to 4. The ORIGINATING CN would provide this ACCOUNTING information to
the PUBLISHER based on existing Service Level Agreements (SLAs). the PUBLISHER based on existing Service Level Agreements (SLAs).
5. CONTENT REQUESTS by CLIENTS may be directed to SURROGATES within 5. CONTENT REQUESTS by CLIENTS may be directed to SURROGATES within
any of the ENLISTED CNs. any of the ENLISTED CNs.
skipping to change at page 8, line 15 skipping to change at page 8, line 15
FIGURE 1 - General CONTENT INTERNETWORKING FIGURE 1 - General CONTENT INTERNETWORKING
+--------------+ +--------------+ +--------------+ +--------------+
| CN A | | CN B | | CN A | | CN B |
|..............| +---------+ +---------+ |..............+ |..............| +---------+ +---------+ |..............+
| REQ-ROUTING |<=>| |<=>| |<=>| REQ-ROUTING | | REQ-ROUTING |<=>| |<=>| |<=>| REQ-ROUTING |
|..............| | CONTENT | | CONTENT | |..............| |..............| | CONTENT | | CONTENT | |..............|
| DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION | | DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION |
|..............| | GATEWAY | | GATEWAY | |..............| |..............| | GATEWAY | | GATEWAY | |..............|
| ACCOUNTING |<=>| |<=>| |<=>| ACCOUNTING | | ACCOUNTING |<=>| |<=>| |<=>| ACCOUNTING |
|--------------| +---------+ +---------+ +--------------+ +--------------+ +---------+ +---------+ +--------------+
| ^ \^ \^ \^ ^/ ^/ ^/ | ^ | ^ \^ \^ \^ ^/ ^/ ^/ | ^
v | \\ \\ \\ // // // v | v | \\ \\ \\ // // // v |
+--------------+ \\ \\ \\ // // // +--------------+ +--------------+ \\ \\ \\ // // // +--------------+
| SURROGATES | \\ v\ v\ /v /v // | SURROGATES | | SURROGATES | \\ v\ v\ /v /v // | SURROGATES |
+--------------+ \\+---------+// +--------------+ +--------------+ \\+---------+// +--------------+
^ | v| |v ^ | ^ | v| |v ^ |
| | | CONTENT | | | | | | CONTENT | | |
| | |INTWRKING| | | | | |INTWRKING| | |
| | | GATEWAY | | | | | | GATEWAY | | |
| | | | | | | | | | | |
skipping to change at page 10, line 26 skipping to change at page 10, line 26
+-----------+ +-----------+
^| ^| ^| ^| ^| ^| ^| ^|
+--------------+ // // \\ \\ +--------------+ +--------------+ // // \\ \\ +--------------+
| CN A | |v |v |v |v | CN B | | CN A | |v |v |v |v | CN B |
|..............| +---------+ +---------+ |..............| |..............| +---------+ +---------+ |..............|
| REQ-ROUTING |<=>| | | |<=>| REQ-ROUTING | | REQ-ROUTING |<=>| | | |<=>| REQ-ROUTING |
|..............| | CONTENT | | CONTENT | |..............| |..............| | CONTENT | | CONTENT | |..............|
| DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION | | DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION |
|..............| | GATEWAY | | GATEWAY | |..............| |..............| | GATEWAY | | GATEWAY | |..............|
| ACCOUNTING |<=>| | | |<=>| ACCOUNTING | | ACCOUNTING |<=>| | | |<=>| ACCOUNTING |
|--------------| +---------+ +---------+ +--------------+ +--------------+ +---------+ +---------+ +--------------+
| ^ | ^ | ^ | ^
v | v | v | v |
+--------------+ +--------------+ +--------------+ +--------------+
| SURROGATES | | SURROGATES | | SURROGATES | | SURROGATES |
+--------------+ +--------------+ +--------------+ +--------------+
^ \ ^ / ^ \ ^ /
\ \ / / \ \ / /
\ \ / / \ \ / /
\ \ / / \ \ / /
\ \ +---------+ / / \ \ +---------+ / /
skipping to change at page 11, line 34 skipping to change at page 11, line 34
+-----------+ +-----------+
^| ^| ^| ^|
+--------------+ // \\ +--------------+ +--------------+ // \\ +--------------+
| CN A | |v |v | CN B | | CN A | |v |v | CN B |
|..............| +---------+ +---------+ |..............| |..............| +---------+ +---------+ |..............|
| REQ-ROUTING |<=>| |<=>| |<=>| REQ-ROUTING | | REQ-ROUTING |<=>| |<=>| |<=>| REQ-ROUTING |
|..............| | CONTENT | | CONTENT | |..............| |..............| | CONTENT | | CONTENT | |..............|
| DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION | | DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION |
|..............| | GATEWAY | | GATEWAY | |..............| |..............| | GATEWAY | | GATEWAY | |..............|
| ACCOUNTING |<=>| | | |<=>| ACCOUNTING | | ACCOUNTING |<=>| | | |<=>| ACCOUNTING |
|--------------| +---------+ +---------+ +--------------+ +--------------+ +---------+ +---------+ +--------------+
| ^ | ^ | ^ | ^
v | v | v | v |
+--------------+ +--------------+ +--------------+ +--------------+
| SURROGATES | | SURROGATES | | SURROGATES | | SURROGATES |
+--------------+ +--------------+ +--------------+ +--------------+
^ \ ^ / ^ \ ^ /
\ \ / / \ \ / /
\ \ / / \ \ / /
\ \ / / \ \ / /
\ \ +---------+ / / \ \ +---------+ / /
skipping to change at page 13, line 25 skipping to change at page 13, line 25
+--------------+ +-----------+ \\ \\ +--------------+ +-----------+ \\ \\
^| ^| ^| ^| \\ || ^| ^| ^| ^| \\ ||
+--------------+ || || || \\ || || +--------------+ +--------------+ || || || \\ || || +--------------+
| CN A | |v |v |v \v |v |v | CN B | | CN A | |v |v |v \v |v |v | CN B |
|..............| +---------+ +---------+ |..............| |..............| +---------+ +---------+ |..............|
| REQ-ROUTING |<=>| | | |<=>| REQ-ROUTING | | REQ-ROUTING |<=>| | | |<=>| REQ-ROUTING |
|..............| | CONTENT | | CONTENT | |..............| |..............| | CONTENT | | CONTENT | |..............|
| DISTRIBUTION |<=>|INTWRKING| |INTWRKING|<=>| DISTRIBUTION | | DISTRIBUTION |<=>|INTWRKING| |INTWRKING|<=>| DISTRIBUTION |
|..............| | GATEWAY | | GATEWAY | |..............| |..............| | GATEWAY | | GATEWAY | |..............|
| ACCOUNTING |<=>| | | |<=>| ACCOUNTING | | ACCOUNTING |<=>| | | |<=>| ACCOUNTING |
|--------------| +---------+ +---------+ +--------------+ +--------------+ +---------+ +---------+ +--------------+
| ^ | ^ | ^ | ^
v | v | v | v |
+--------------+ +--------------+ +--------------+ +--------------+
| SURROGATES | | SURROGATES | | SURROGATES | | SURROGATES |
+--------------+ +--------------+ +--------------+ +--------------+
^ \ ^ / ^ \ ^ /
\ \ / / \ \ / /
\ \ / / \ \ / /
\ \ / / \ \ / /
\ \ +---------+ / / \ \ +---------+ / /
skipping to change at page 14, line 15 skipping to change at page 14, line 15
FIGURE 5 - Multiple CNs ENLIST LCN FIGURE 5 - Multiple CNs ENLIST LCN
+--------------+ +--------------+ +--------------+ +--------------+
| CN A | | CN B | | CN A | | CN B |
|..............| +---------+ +---------+ |..............+ |..............| +---------+ +---------+ |..............+
| REQ-ROUTING |<=>| |<=>| |<=>| REQ-ROUTING | | REQ-ROUTING |<=>| |<=>| |<=>| REQ-ROUTING |
|..............| | CONTENT | | CONTENT | |..............| |..............| | CONTENT | | CONTENT | |..............|
| DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION | | DISTRIBUTION |<=>|INTWRKING|<=>|INTWRKING|<=>| DISTRIBUTION |
|..............| | GATEWAY | | GATEWAY | |..............| |..............| | GATEWAY | | GATEWAY | |..............|
| ACCOUNTING |<=>| |<=>| |<=>| ACCOUNTING | | ACCOUNTING |<=>| |<=>| |<=>| ACCOUNTING |
|--------------| +---------+ +---------+ +--------------+ +--------------+ +---------+ +---------+ +--------------+
| ^ \^ \^ ^/ ^/ | ^ | ^ \^ \^ ^/ ^/ | ^
v | \\ \\ // // v | v | \\ \\ // // v |
+--------------+ \\ \\ // // +--------------+ +--------------+ \\ \\ // // +--------------+
| SURROGATES | v\ v\ /v /v | SURROGATES | | SURROGATES | v\ v\ /v /v | SURROGATES |
+--------------+ +---------+ +--------------+ +--------------+ +---------+ +--------------+
| | | |
| CONTENT | | CONTENT |
|INTWRKING| |INTWRKING|
| GATEWAY | | GATEWAY |
| | | |
skipping to change at page 15, line 35 skipping to change at page 15, line 35
The authors acknowledge the contributions and comments of Fred The authors acknowledge the contributions and comments of Fred
Douglis (AT&T), Raj Nair (Cisco), Gary Tomlinson (CacheFlow), John Douglis (AT&T), Raj Nair (Cisco), Gary Tomlinson (CacheFlow), John
Scharber (CacheFlow), Nalin Mistry (Nortel), Steve Rudkin (BT), Scharber (CacheFlow), Nalin Mistry (Nortel), Steve Rudkin (BT),
Christian Hoertnagl (IBM), Christian Langkamp (Oxford University), Christian Hoertnagl (IBM), Christian Langkamp (Oxford University),
and Don Estberg (Activate). and Don Estberg (Activate).
References References
[1] Day, M., Cain, B., Tomlinson, G., and P. Rzewski, "A Model for [1] Day, M., Cain, B., Tomlinson, G., and P. Rzewski, "A Model for
Content Internetworking (CDI)", draft-ietf-cdi-model-00.txt Content Internetworking (CDI)", draft-ietf-cdi-model-01.txt
(work in progress), February 2002, (work in progress), February 2002,
<URL:http://www.ietf.org/internet-drafts/draft-ietf-cdi-model- <URL:http://www.ietf.org/internet-drafts/draft-ietf-cdi-model-
00.txt>. 01.txt>.
[2] Green, M., Cain, B., Tomlinson, G., Thomas, S., and P. Rzewski, [2] Green, M., Cain, B., Tomlinson, G., Thomas, S., and P. Rzewski,
"Content Internetworking Architectural Overview", draft-ietf- "Content Internetworking Architectural Overview", draft-ietf-
cdi-architecture-00.txt (work in progress), February 2002, cdi-architecture-00.txt (work in progress), February 2002,
<URL:http://www.ietf.org/internet-drafts/draft-ietf-cdi- <URL:http://www.ietf.org/internet-drafts/draft-ietf-cdi-
architecture-00.txt>. architecture-00.txt>.
[3] Gilletti, D., Nair, R., Scharber, J., and J. Guha, "CDN-I [3] Gilletti, D., Nair, R., Scharber, J., and J. Guha, "CDN-I
Internetworking Authentication, Authorization, and Accounting Internetworking Authentication, Authorization, and Accounting
Requirements", draft-ietf-cdi-aaa-reqs-00.txt (work in Requirements", draft-ietf-cdi-aaa-reqs-00.txt (work in
skipping to change at page 16, line 44 skipping to change at page 16, line 44
4100 East Third Avenue 4100 East Third Avenue
MS FC2-4 MS FC2-4
Foster City, CA 94404 Foster City, CA 94404
US US
Phone +1 650 653 2487 Phone +1 650 653 2487
Email: philr@inktomi.com Email: philr@inktomi.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 23 change blocks. 
43 lines changed or deleted 50 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/