The Virtual Private Network (VPN) Service in ALTO: Use Cases, Requirements and Extensions
draft-scharf-alto-vpn-service-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Michael Scharf , Vijay K. Gurbani , Greg Soprovich, Volker Hilt | ||
Last updated | 2014-08-17 (Latest revision 2014-02-13) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Application-Layer Traffic Optimization (ALTO) protocol is designed to allow entities with knowledge about the network infrastructure to export such information to applications that need to choose one or more resources from a candidate set. This document provides motivation for using ALTO in a Virtual Private Network (VPN) environment. We discuss use cases, requirements, and possible extensions to the base ALTO protocol that will be needed to support VPN services.
Authors
Michael Scharf
Vijay K. Gurbani
Greg Soprovich
Volker Hilt
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)