idnits 2.17.1 draft-ietf-cdi-model-02.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3466 5 Title: A Model for Content Internetworking (CDI) 6 Author(s): M. Day, B. Cain, G. Tomlinson, P. Rzewski 7 Status: Informational 8 Date: February 2003 9 Mailbox: mday@alum.mit.edu, bcain@storigen.com, 10 gary@tomlinsongroup.net, philrz@yahoo.com 11 Pages: 17 12 Characters: 37684 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-cdi-model-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3466.txt 19 Content (distribution) internetworking (CDI) is the technology for 20 interconnecting content networks, sometimes previously called 21 "content peering" or "CDN peering". A common vocabulary helps the 22 process of discussing such interconnection and interoperation. This 23 document introduces content networks and content internetworking, and 24 defines elements for such a common vocabulary. 26 This document is a product of the Content Distribution Internetworking 27 (cdi) Working Group of the IETF. 29 This memo provides information for the Internet community. It does 30 not specify an Internet standard of any kind. Distribution of this 31 memo is unlimited. 33 This announcement is sent to the IETF list and the RFC-DIST list. 34 Requests to be added to or deleted from the IETF distribution list 35 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 36 added to or deleted from the RFC-DIST distribution list should 37 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 39 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 40 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 41 help: ways_to_get_rfcs. For example: 43 To: rfc-info@RFC-EDITOR.ORG 44 Subject: getting rfcs 46 help: ways_to_get_rfcs 48 Requests for special distribution should be addressed to either the 49 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 50 specifically noted otherwise on the RFC itself, all RFCs are for 51 unlimited distribution.echo 52 Submissions for Requests for Comments should be sent to 53 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 54 Authors, for further information.