Browse Prior Art Database

Virtual Private Networks Identifier (RFC2685)

IP.com Disclosure Number: IPCOM000003277D
Original Publication Date: 1999-Sep-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 5 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Fox: AUTHOR [+2]

Abstract

Virtual Private IP networks may span multiple Autonomous Systems or Service Providers. There is a requirement for the use of a globally unique VPN identifier in order to be able to refer to a particular VPN (see section 6.1.1 of [1]). This document proposes a format for a globally unique VPN identifier.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 26% of the total text.

Network Working Group B. Fox

Request for Comments: 2685 Lucent Technologies

Category: Standards Track B. Gleeson

Nortel Networks

September 1999

Virtual Private Networks Identifier

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

Virtual Private IP networks may span multiple Autonomous Systems or

Service Providers. There is a requirement for the use of a globally

unique VPN identifier in order to be able to refer to a particular

VPN (see section 6.1.1 of [1]). This document proposes a format for

a globally unique VPN identifier.

1. Introduction

As the Public Internet expands and extends its infrastructure

globally, the determination to exploit this infrastructure has led to

widespread interest in IP based Virtual Private Networks. A VPN

emulates a private IP network over public or shared infrastructures.

Virtual Private Networks provide advantages to both the Service

Provider and its customers. For its customers, a VPN can extend the

IP capabilities of a corporate site to remote offices and/or users

with intranet, extranet, and dialup services. This connectivity

should be achieved at a lower cost to the customer with savings in

capital equipment, operations, and services. The Service Provider

is able to make better use of its infrastructure and network

administration expertise offering IP VPN connectivity and/or services

to its customers.

There are many ways in which IP VPN services may be implemented. The

IP based VPN framework document [1] identifies four types of VPN to

be supported: Virtual Leased Lines, Virtual Private Routed Networks,

Virtual Private Dial Networks, and Virtual Private LAN Segments. In

addition, numerous drafts and white papers outline methods to be used

by Service Providers and/or Service Provider customers to enable this

service. Solutions may be customer based or network based. Network

based solutions may provide connectivity and services at layer 2

and/or layer 3. The devices involved in enabling th...