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)
Last updated 2014-08-17 (latest revision 2014-02-13)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-scharf-alto-vpn-service-02.txt

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 (michael.scharf@alcatel-lucent.com)
Vijay Gurbani (vkg@bell-labs.com)
Greg Soprovich (greg.soprovich@alcatel-lucent.com)
Volker Hilt (volker.hilt@bell-labs.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)