RFC 8763: Deployment Considerations for Information-Centric Networking (ICN)
In plain English — editorial summary, not part of the RFC
Information-Centric Networking (ICN) is now reaching technological maturity after many years of fundamental research and experimentation. This document provides a number of deployment considerations in the interest of helping the ICN community move forward to the next step of live deployments. First, the major deployment configurations for ICN are described, including the key overlay and underlay approaches. Then, proposed deployment migration paths are outlined to address major practical issues, such as network and application migration. Next, selected ICN trial experiences are summarized. Finally, protocol areas that require further standardization are identified to facilitate future interoperable ICN deployments. This document is a product of the Information-Centric Networking Research Group (ICNRG).
Document record
- Document ID
- RFC8763
- Published
- April 2020
- Authors
- A. Rahman; D. Trossen; D. Kutscher; R. Ravindran
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9386IPv6 Deployment StatusCurrent
April 2023
- RFC 9437Publish/Subscribe Functionality for the Locator/ID Separation Protocol (LISP)Current
August 2023
- RFC 7047The Open vSwitch Database Management ProtocolCurrent
December 2013
- RFC 7018Auto-Discovery VPN Problem Statement and RequirementsCurrent
September 2013
- RFC 2642Cabletron's VLS Protocol SpecificationCurrent
August 1999
- RFC 7426Software-Defined Networking (SDN): Layers and Architecture TerminologyCurrent
January 2015
- RFC 6693Probabilistic Routing Protocol for Intermittently Connected NetworksCurrent
August 2012
- RFC 6179The Internet Routing Overlay Network (IRON)Current
March 2011
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?