Internet DRAFT - draft-ietf-cdi-model
draft-ietf-cdi-model
A new Request for Comments is now available in online RFC libraries.
RFC 3466
Title: A Model for Content Internetworking (CDI)
Author(s): M. Day, B. Cain, G. Tomlinson, P. Rzewski
Status: Informational
Date: February 2003
Mailbox: mday@alum.mit.edu, bcain@storigen.com,
gary@tomlinsongroup.net, philrz@yahoo.com
Pages: 17
Characters: 37684
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-cdi-model-02.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3466.txt
Content (distribution) internetworking (CDI) is the technology for
interconnecting content networks, sometimes previously called
"content peering" or "CDN peering". A common vocabulary helps the
process of discussing such interconnection and interoperation. This
document introduces content networks and content internetworking, and
defines elements for such a common vocabulary.
This document is a product of the Content Distribution Internetworking
(cdi) Working Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.