RFC 6875: The P2P Network Experiment Council's Activities and Experiments with Application-Layer Traffic Optimization (ALTO) in Japan
In plain English — editorial summary, not part of the RFC
This document describes experiments that clarify how an approach similar to Application-Layer Traffic Optimization (ALTO) was effective in reducing network traffic. These experiments were performed in Japan by the P2P Network Experiment Council in an attempt to harmonize peer-to-peer (P2P) technology with network infrastructure. Based on what was learned from these experiments, this document provides some suggestions that might be useful for the ALTO architecture and especially for application-independent ALTO- like server operation.
Document record
- Document ID
- RFC6875
- Published
- February 2013
- Authors
- S. Kamei; T. Momose; T. Inoue; T. Nishitani
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7904A SIP Usage for REsource LOcation And Discovery (RELOAD)Current
October 2016
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 6029A Survey on Research on the Application-Layer Traffic Optimization (ALTO) ProblemCurrent
October 2010
- RFC 7025Requirements for GMPLS Applications of PCECurrent
September 2013
- RFC 6457PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic EngineeringCurrent
December 2011
- RFC 7336Framework for Content Distribution Network Interconnection (CDNI)Current
August 2014
- RFC 7399Unanswered Questions in the Path Computation Element ArchitectureCurrent
October 2014
- RFC 6028Host Identity Protocol (HIP) Multi-Hop Routing ExtensionCurrent
October 2010
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?