INTERNET-DRAFT Benson Schliesser draft-ietf-l3vpn-tc-mib-02.txt SAVVIS Communications Expires: November 2004 Thomas D. Nadeau Cisco Systems, Inc. May 2004 Definition of Textual Conventions for Virtual Private Network (VPN) Management Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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/ietf/1id-abstracts.txt 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-MIB ................................................ 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 .................................. 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-MIB 3.1 Description The VPN-TC-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 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-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC; vpnTcMIB MODULE-IDENTITY LAST-UPDATED "200405261200Z" -- 26 May 2004 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 "200405261200Z" -- 26 May 2004 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 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)) 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 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 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 8. Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.
Datatracker
Report a datatracker bug
draft-ietf-l3vpn-tc-mib-02
Internet-Draft
| Document | Document type |
This is an older version of an Internet-Draft that was ultimately published as RFC 4265.
Expired & archived
|
|
|---|---|---|---|
| Select version | |||
| Compare versions | |||
| Author | |||
| Replaces | draft-ietf-ppvpn-tc-mib | ||
| RFC stream |
|
||
| Other formats | |||
| Additional resources | Mailing list discussion |