As per Relevance of the word provider, we have this rfc below:
Network Working Group B.
Request for Comments: 2685 Lucent
Category: Standards Track B.
Nortel
September 1999
Virtual Private Networks
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
Virtual Private IP networks may span multiple Autonomous Systems
Service Providers. There is a requirement for the use of a
unique VPN identifier in order to be able to refer to a
VPN (see section 6.1.1 of [1]). This document proposes a format
a globally unique VPN identifier
1.
As the Public Internet expands and extends its
globally, the determination to exploit this infrastructure has led
widespread interest in IP based Virtual Private Networks. A
emulates a private IP network over public or shared infrastructures
Virtual Private Networks provide advantages to both the
Provider and its customers. For its customers, a VPN can extend
IP capabilities of a corporate site to remote offices and/or
with intranet, extranet, and dialup services. This
should be achieved at a lower cost to the customer with savings
capital equipment, operations, and services. The Service
is able to make better use of its infrastructure and
administration expertise offering IP VPN connectivity and/or
to its customers
There are many ways in which IP VPN services may be implemented.
IP based VPN framework document [1] identifies four types of VPN
be supported: Virtual Leased Lines, Virtual Private Routed Networks
Fox & Gleeson Standards Track [Page 1]
RFC 2685 Virtual Private Networks Identifier September 1999
Virtual Private Dial Networks, and Virtual Private LAN Segments.
addition, numerous drafts and white papers outline methods to be
by Service Providers and/or Service Provider customers to enable
service. Solutions may be customer based or network based.
based solutions may provide connectivity and services at layer 2
and/or layer 3. The devices involved in enabling the solution may
Customer Premises Equipment (CPE), Service Provider Edge equipment
Service Provider Core equipment, or some combination of these
While the various methods of VPN service implementation are
discussed and debated, there are two points on which there
agreement
Because a VPN is private, it may use a private address space
may overlap with the address space of another VPN or the
Internet
A VPN may span multiple IP Autonomous Systems (AS) or
Providers
The first point indicates that an IP address only has meaning
the VPN in which it exists. For this reason, it is necessary
identify the VPN in which a particular IP address has meaning,
"scope" of the IP address
The second point indicates that several methods of VPN
implementation may be used to provide connectivity and services to
single VPN. Different service providers may employ
strategies based on their infrastructure and expertise. It
desirable to be able to identify any particular VPN at any layer
at any location in which it exists using the same VPN identifier
2. Global VPN
The purpose of a VPN-ID is to identify a VPN. This identifier may
used in various ways depending on the method of VPN
implementation. For example, the VPN-ID may be included
- In a MIB to configure attributes to a VPN, or to assign a
or logical access interface to a particular VPN
- In a control or data packet, to identify the "scope" of a
IP address and the VPN to which the data belongs
It is necessary to be able to identify the VPN with which a
packet is associated. The VPN-ID may be used to make
association, either explicitly (e.g. through inclusion of the VPN-
in an encapsulation header [2]) or implicitly (e.g. through
Fox & Gleeson Standards Track [Page 2]
RFC 2685 Virtual Private Networks Identifier September 1999
of the VPN-ID in a ATM signalling exchange [3]). The
of using the VPN-ID in other contexts needs to be
evaluated
There is another very important function that may be served by
VPN identifier. The VPN identifier may be used to define the "
authority" who is responsible for coordinating the connectivity
services employed by that VPN. The VPN authority may be the
Network administrator or the primary Service Provider. The
authority will administer and serve as the main point of contact
the VPN. The authority may outsource some functions
connectivity, set up contractual agreements with the
Service Providers involved, and coordinate configuration
performance, and fault management
These functions require a VPN that is global in scope and usable
various solutions. To be a truly global VPN identifier, the
cannot force assumptions about the shared network(s). Conversely,
format should not be defined in such a way as to prohibit use
features of the shared network. It is necessary to note that
same VPN may be identified at different layers of the same
network, e.g. ATM and IP layers. The same VPN-ID format and
should apply at both layers
The methods of VPN-ID usage are beyond the scope of this memo
3. Global VPN Identifier Format
The VPN Identifier format should meet the following requirements
- Provide a globally unique VPN Identifier usable
multiple Service Providers
- Enable support of a non-IP dependent VPN-ID for use
layer 2 VPNs
- Identify the VPN Authority within the VPN Identifier
4. Global VPN Identifier
The global VPN Identifier format is
3 octet VPN authority Organizationally Unique Identifier [4]
followed
4 octet VPN index identifying VPN according to
Fox & Gleeson Standards Track [Page 3]
RFC 2685 Virtual Private Networks Identifier September 1999
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
| VPN OUI (MSB) |
+-+-+-+-+-+-+-+-+
| VPN OUI |
+-+-+-+-+-+-+-+-+
| VPN OUI (LSB) |
+-+-+-+-+-+-+-+-+
|VPN Index (MSB)|
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
|VPN Index (LSB)|
+-+-+-+-+-+-+-+-+
The VPN OUI (IEEE 802-1990 Organizationally Unique Identifier) [4]
identifies the VPN authority. The VPN authority will serve as
primary VPN administrator. The VPN authority may be
company/organization to which the VPN belongs or a Service
that provides the underlying infrastructure using its own and/
other providers' shared networks. The 4 octet VPN Index identifies
particular VPN serviced by the VPN authority
5. Security
This document defines the format of the global VPN identifier
specifying usage. However, the association of
characteristics and capabilities with a VPN identifier
use of standard security procedures with any specified usage
Misconfiguration or deliberate forging of VPN identifier may
different breaches in security including the interconnection
different VPNs
6.
[1] Gleeson, Heinanen, Lin, Armitage, Malis, "A Framework for
Based Virtual Private Networks", Work in Progress
[2] Grossman, D. and J. Heinanen, "Multiprotocol Encapsulation
ATM Adaptation Layer 5", RFC 2684, September 1999.
[3] "MPOA v1.1 Addendum on VPN Support", ATM Forum, af-mpoa-0129.000,
August, 1999, Bernhard Petri, editor, final ballot document
[4] http://standards.ieee.org/regauth/oui/index.
Fox & Gleeson Standards Track [Page 4]
RFC 2685 Virtual Private Networks Identifier September 1999
7. Authors'
Barbara A.
Lucent
300 Baker Ave, Suite 100
Concord, MA 01742-2168
Phone: +1-978-287-2843
EMail: barbarafox@lucent.
Bryan
Nortel
4500 Great America Parkway
Santa Clara, CA 95054
Phone: +1-408-855-3711
EMail: bgleeson@shastanets.
Fox & Gleeson Standards Track [Page 5]
RFC 2685 Virtual Private Networks Identifier September 1999
8. Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Fox & Gleeson Standards Track [Page 6]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
