Using DNS for VPN Discovery
draft-luciani-ppvpn-vpn-discovery-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. James V. Luciani | ||
| Last updated | 2002-11-04 | ||
| 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
Virtual private networks are becoming a common offering of many service providers. There are many technologies with which to implement a VPN service, ranging from MPLS to GRE to IPSEC. A common requirement of all VPN technologies is the need to discover all of the sites, or at least all the provider equipment associated with the sites, that are in a particular VPN. DNS provides a simple and commonly available mechanism for site discovery that is independent of any signaling or tunneling protocol. This draft proposes the use of DNS as a discovery mechanism for VPN maintenance and control.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)