4265
PROPOSED STANDARD
Definition of Textual Conventions for Virtual Private Network (VPN) Management
Authors: B. Schliesser, T. Nadeau
Date: November 2005
Area: int
Working Group: l3vpn
Stream: IETF
Abstract
This document describes Textual Conventions used for managing Virtual Private Networks (VPNs). [STANDARDS-TRACK]
RFC 4265
PROPOSED STANDARD
Network Working Group B. Schliesser
Request for Comments: 4265 SAVVIS Communications
Category: Standards Track T. Nadeau
Cisco Systems, Inc.
November 2005
<span class="h1">Definition of Textual Conventions for</span>
<span class="h1">Virtual Private Network (VPN) Management</span>
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 (2005).
Abstract
This document describes Textual Conventions used for managing Virtual
Private Networks (VPNs).
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-1">1</a>
<a href="#section-1.1">1.1</a>. Conventions Used in This Document ..........................<a href="#page-2">2</a>
<a href="#section-2">2</a>. The Internet-Standard Management Framework ......................<a href="#page-2">2</a>
<a href="#section-3">3</a>. VPN-TC-STD-MIB ..................................................<a href="#page-2">2</a>
<a href="#section-3.1">3.1</a>. Description ................................................<a href="#page-2">2</a>
<a href="#section-3.2">3.2</a>. Definitions ................................................<a href="#page-2">2</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-4">4</a>
<a href="#section-5">5</a>. IANA Considerations for VPN-TC-STD-MIB ..........................<a href="#page-4">4</a>
<a href="#section-6">6</a>. References ......................................................<a href="#page-4">4</a>
<a href="#section-6.1">6.1</a>. Normative References .......................................<a href="#page-4">4</a>
<a href="#section-6.2">6.2</a>. Informative References .....................................<a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines Textual Conventions used in Virtual Private
Networks (VPNs) and IETF VPN-related MIBs.
<span class="grey">Schliesser & Nadeau Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc4265">RFC 4265</a> VPN-TC-STD-MIB November 2005</span>
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC-2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Internet-Standard Management Framework</span>
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section 7 of
RFC 3410</a> [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
<a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC 2580</a>
[<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. VPN-TC-STD-MIB</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Description</span>
The VPN-TC-STD-MIB defines a Textual Convention for the Global VPN
Identifier, or VPN-ID, as specified in [<a href="./rfc2685" title=""Virtual Private Networks Identifier"">RFC2685</a>]. The purpose of a
VPN-ID is to uniquely identify a VPN. It MUST be 7 octets in length,
and SHOULD be comprised of a 3 octet Organizationally Unique
Identifier (OUI) that uniquely identifies the VPN Authority, followed
by a 4 octet value assigned by the VPN Authority that uniquely
identifies the VPN within the context of the OUI.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Definitions</span>
VPN-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
vpnTcMIB MODULE-IDENTITY
LAST-UPDATED "200511150000Z" -- 15 November 2005
ORGANIZATION
"Layer 3 Virtual Private Networks (L3VPN) Working Group."
<span class="grey">Schliesser & Nadeau Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc4265">RFC 4265</a> VPN-TC-STD-MIB November 2005</span>
CONTACT-INFO
"Benson Schliesser
[email protected]
Thomas D. Nadeau
[email protected]
This TC MIB is a product of the PPVPN
<a href="http://www.ietf.org/html.charters/ppvpn-charter.html">http://www.ietf.org/html.charters/ppvpn-charter.html</a>
and subsequently the L3VPN
<a href="http://www.ietf.org/html.charters/l3vpn-charter.html">http://www.ietf.org/html.charters/l3vpn-charter.html</a>
working groups.
Comments and discussion should be directed to
[email protected]"
DESCRIPTION
"This MIB contains TCs for VPNs.
Copyright (C) The Internet Society (2005). This version
of this MIB module is part of <a href="./rfc4265">RFC 4265</a>; see the RFC
itself for full legal notices."
-- Revision history.
REVISION "200511150000Z" -- 15 November 2005
DESCRIPTION "Initial version, published as <a href="./rfc4265">RFC 4265</a>."
::= { mib-2 129 }
-- definition of textual conventions
VPNId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The purpose of a VPN-ID is to uniquely identify a VPN.
The Global VPN Identifier format is:
3 octet VPN Authority, Organizationally Unique Identifier
followed by 4 octet VPN index identifying VPN according
to OUI"
REFERENCE
"Fox, B. and Gleeson, B., 'Virtual Private Networks
Identifier', <a href="./rfc2685">RFC 2685</a>, September 1999."
SYNTAX OCTET STRING (SIZE (7))
VPNIdOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension of the
VPNId textual convention that defines a non-zero-length
OCTET STRING to identify a physical entity. This extension
permits the additional value of a zero-length OCTET STRING.
<span class="grey">Schliesser & Nadeau Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc4265">RFC 4265</a> VPN-TC-STD-MIB November 2005</span>
The semantics of the value zero-length OCTET STRING are
object-specific and must therefore be defined
as part of the description of any object that uses this
syntax. Examples of usage of this extension are
situations where none or all VPN IDs need to be
referenced."
SYNTAX OCTET STRING (SIZE (0 | 7))
END
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This module does not define any management objects. Instead, it
defines a set of textual conventions that may be used by other MIB
modules to define management objects.
Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document has
no impact on the security of the Internet.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations for VPN-TC-STD-MIB</span>
The IANA has assigned { mib-2 129 } to the VPN-TC-STD-MIB module
specified in this document.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)",
STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999.
[<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
Conventions for SMIv2", STD 58, <a href="./rfc2579">RFC 2579</a>, April 1999.
[<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>, April
1999.
[<a id="ref-RFC2685">RFC2685</a>] Fox, B. and B. Gleeson, "Virtual Private Networks
Identifier", <a href="./rfc2685">RFC 2685</a>, September 1999.
<span class="grey">Schliesser & Nadeau Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc4265">RFC 4265</a> VPN-TC-STD-MIB November 2005</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002.
Authors' Addresses
Benson Schliesser
SAVVIS Communications
1 Savvis Parkway
Saint Louis, MO 63017
USA
Phone: +1-314-628-7036
EMail: [email protected]
Thomas D. Nadeau
Cisco Systems
1414 Massachusetts Ave.
Boxborough, MA 01719
Phone: +1-978-244-3051
EMail: [email protected]
<span class="grey">Schliesser & Nadeau Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc4265">RFC 4265</a> VPN-TC-STD-MIB November 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
[email protected].
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Schliesser & Nadeau Standards Track [Page 6]
Annotations
Select text to annotate