One document matched: draft-ietf-l3vpn-tc-mib-06.txt
Differences from draft-ietf-l3vpn-tc-mib-05.txt
INTERNET-DRAFT Benson Schliesser
draft-ietf-l3vpn-tc-mib-06.txt SAVVIS Communications
Expires: October 2005
Thomas D. Nadeau
Cisco Systems, Inc.
April 2005
Definition of Textual Conventions for
Virtual Private Network (VPN) Management
Status of this Memo
By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of
BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This document describes Textual Conventions used for managing
Virtual Private Networks (VPNs).
Table of Contents
1. Introduction ..............................................
1.1 Conventions Used in This Document .........................
2. The Internet-Standard Management Framework ................
3. VPN-TC-STD-MIB ............................................
Layer-3 VPN Group Expires October 31, 2005 [Page 1]
Internet Draft VPN-TC-STD-MIB April 1, 2005
3.1 Description ...............................................
3.2 Definitions ...............................................
4. Security Considerations ...................................
5. References ................................................
5.1 Normative References ......................................
5.2 Informative References ....................................
6. Authors Addresses .........................................
7. Intellectual Property Considerations ......................
8. Full Copyright Statement ..................................
9. IANA Considerations for VPN-TC-STD-MIB.....................
1. Introduction
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 VPNs and IETF
VPN-related MIBs.
1.1 Conventions Used in This Document
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 RFC-2119
[RFC2119].
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
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, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58,
RFC 2580 [RFC2580].
3. VPN-TC-STD-MIB
3.1 Description
The VPN-TC-STD-MIB defines a Textual Convention for the Global VPN
Identifier, or VPN-ID, as specified in [RFC2685]. 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
Layer-3 VPN Group Expires October 31, 2005 [Page 2]
Internet Draft VPN-TC-STD-MIB April 1, 2005
Identifier (OUI) which 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.
3.2 Definitions
VPN-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
vpnTcMIB MODULE-IDENTITY
LAST-UPDATED "200504011200Z" -- 01 April 2005 12:00:00 GMT
ORGANIZATION
"Layer 3 Virtual Private Networks (L3VPN) Working Group."
CONTACT-INFO
"Benson Schliesser
bensons@savvis.net
Thomas D. Nadeau
tnadeau@cisco.com
This TC MIB is a product of the PPVPN
http://www.ietf.org/html.charters/ppvpn-charter.html
and subsequently the L3VPN
http://www.ietf.org/html.charters/l3vpn-charter.html
working groups.
Comments and discussion should be directed to l3vpn@ietf.org"
DESCRIPTION
"This MIB contains TCs for VPNs.
Copyright (C) The Internet Society (2004). This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
-- Revision history.
REVISION "200504011200Z" -- 01 April 2005 12:00:00 GMT
DESCRIPTION "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note
-- definition of textual conventions
Layer-3 VPN Group Expires October 31, 2005 [Page 3]
Internet Draft VPN-TC-STD-MIB April 1, 2005
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', RFC 2685, September 1999."
SYNTAX OCTET STRING (SIZE (7))
VPNIdOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension of the
VPNId textual convention which defines non-zero-length
OCTET STRING to identify a physical entity. This extension
permits the additional value of a zero-length OCTET STRING.
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 which uses this
syntax. Examples of the usage of this extension are
situations where none or all VPN IDs need to be
referenced."
SYNTAX OCTET STRING (SIZE (0 | 7))
END
4. Security Considerations
This memo defines textual conventions and object identities
for use in VPN MIB modules. Security issues for these MIB
modules are addressed in the memos defining those modules.
5. References
5.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Layer-3 VPN Group Expires October 31, 2005 [Page 4]
Internet Draft VPN-TC-STD-MIB April 1, 2005
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
5.2 Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC2685] Fox, B. and Gleeson, B., "Virtual Private Networks
Identifier", RFC 2685, September 1999.
6. Authors' Addresses
Benson Schliesser
SAVVIS Communications
1 Savvis Parkway
Saint Louis, MO 63017
USA
Phone: +1-314-628-7036
Email: bensons@savvis.net
Thomas D. Nadeau
Cisco Systems, Inc.
300 Beaverbrook Drive
Boxborough, MA
USA
Phone: +1-978-936-1470
Email: tnadeau@cisco.com
7. Intellectual Property Considerations
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
Layer-3 VPN Group Expires October 31, 2005 [Page 5]
Internet Draft VPN-TC-STD-MIB April 1, 2005
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
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
http://www.ietf.org/ipr.
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-
ipr@ietf.org.
8. Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is
subject to the rights, licenses and restrictions contained in BCP
78, 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.
9. IANA Considerations for VPN-TC-STD-MIB
The IANA is requested to assign { mib-2 XXX } to the
VPN-TC-STD-MIB module specified in this document.
Layer-3 VPN Group Expires October 31, 2005 [Page 6]
| PAFTECH AB 2003-2026 | 2026-04-21 13:04:31 |