INTERNET-DRAFT                                         Benson Schliesser
     draft-bensons-ppvpn-tc-mib-00.txt                  SAVVIS Communications
     Expires: March 2002
                                                             Thomas D. Nadeau
                                                          Cisco Systems, Inc.


                                                                December 2001


           Definition of Textual Conventions for Provider Provisioned
                   Virtual Private Network (PPVPN) 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.














T. Nadeau & B. Schliesser                                         Page 1
PPVPN-TC-MIB                                              December, 2001


     Abstract

         This document defines Textual Conventions used as part of the
         Management Information Base (MIB) for use with network management
         protocols in the Internet Community. In particular, it describes
         Textual Conventions for managing Provider Provisioned Virtual
         Private Networks (PPVPNs).


     Table of Contents

         1  Introduction ............................................ 3
           1.1  Conventions Used in This Document ................... 3
         2  The SNMP Management Framework ........................... 3
         3  PPVPN TC MIB Definitions ................................ 5
         4  Security Considerations ................................. 6
         5  References .............................................. 6
         6  Authors Addresses ....................................... 7
         7  Full Copyright Statement ................................ 7


































T. Nadeau & B. Schliesser                                         Page 2
PPVPN-TC-MIB                                              December, 2001

     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 and OBJECT-IDENTITIES
         used in IETF PPVPN and PPVPN-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 SNMP Management Framework

         The SNMP Management Framework presently consists of five
         major components:

         -  An overall architecture, described in RFC 2571
            [RFC2571].

         -  Mechanisms for describing and naming objects and
            events for the purpose of management.  The first
            version of this Structure of Management Information
            (SMI) is called SMIv1 and described in STD 16, RFC
            1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16,
            RFC 1215 [RFC1215].  The second version, called SMIv2,
            is described in STD 58, RFC 2578 [RFC2578], STD 58,
            RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].

         -  Message protocols for transferring management
            information.  The first version of the SNMP message
            protocol is called SNMPv1 and described in STD 15, RFC
            1157 [RFC1157].  A second version of the SNMP message
            protocol, which is not an Internet standards track
            protocol, is called SNMPv2c and described in RFC 1901
            [RFC1901] and RFC 1906 [RFC1906].  The third version
            of the message protocol is called SNMPv3 and described
            in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574
            [RFC2574].

         -  Protocol operations for accessing management
            information.  The first set of protocol operations and
            associated PDU formats is described in STD 15, RFC
            1157 [RFC1157].  A second set of protocol operations
            and associated PDU formats is described in RFC 1905
            [RFC1905].

         -  A set of fundamental applications described in RFC
            2573 [RFC2573] and the view-based access control
            mechanism described in RFC 2575 [RFC2575].

T. Nadeau & B. Schliesser                                         Page 3
PPVPN-TC-MIB                                              December, 2001

         A more detailed introduction to the current SNMP
         Management Framework can be found in RFC 2570 [RFC2570].
         Managed objects are accessed via a virtual information
         store, termed the Management Information Base or MIB.
         Objects in the MIB are defined using the mechanisms
         defined in the SMI.

         This memo specifies a MIB module that is compliant to the
         SMIv2.  A MIB conforming to the SMIv1 can be produced
         through the appropriate translations.  The resulting
         translated MIB must be semantically equivalent, except
         where objects or events are omitted because no
         translation is possible (use of Counter64).  Some machine
         readable information in SMIv2 will be converted into
         textual descriptions in SMIv1 during the translation
         process.  However, this loss of machine readable
         information is not considered to change the semantics of
         the MIB.




































T. Nadeau & B. Schliesser                                         Page 4
PPVPN-TC-MIB                                              December, 2001

     3. PPVPN TC MIB Definitions

     PPVPN-TC DEFINITIONS ::= BEGIN

     IMPORTS
         TEXTUAL-CONVENTION       FROM SNMPv2-TC;

     -- definition of textual conventions

     VPNId ::= TEXTUAL-CONVENTION
         STATUS current
         DESCRIPTION
             "The purpose of a VPN-ID is to 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 the OUI."
         REFERENCE
             "RFC 2685, Fox & Gleeson, 'Virtual Private Networks
              Identifier', September 1999."
         SYNTAX    OCTET STRING (SIZE (7))

     END































T. Nadeau & B. Schliesser                                         Page 5
PPVPN-TC-MIB                                              December, 2001

     4. Security Considerations

         This memo defines textual conventions and object
         identities for use in PPVPN MIB modules.  Security issues
         for these MIB modules are addressed in the memos defining
         those modules.


     5. References

     [RFC2685]   Fox, B., and B. Gleeson, "Virtual Private Network Identifier",
                 RFC 2685, September 1999.

     [RFC2119]   Bradner, S., "Key words for use in RFCs to Indicate
                 Requirement Levels", BCP 14, RFC 2119, March 1997.

     [RFC2571]   Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
                 for Describing SNMP Management Frameworks", RFC 2571, April
                 1999.

     [RFC1155]   Rose, M., and K. McCloghrie, "Structure and Identification
                 of Management Information for TCP/IP-based Internets", STD
                 16, RFC 1155, May 1990.

     [RFC1212]   Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
                 16, RFC 1212, March 1991.

     [RFC1215]   M. Rose, "A Convention for Defining Traps for use with the
                 SNMP", RFC 1215, March 1991.

     [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.

     [RFC1157]   Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
                 Network Management Protocol", STD 15, RFC 1157, May 1990.

     [RFC1901]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
                 "Introduction to Community-based SNMPv2", RFC 1901, January
                 1996.

     [RFC1906]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
                 "Transport Mappings for Version 2 of the Simple Network
                 Management Protocol (SNMPv2)", RFC 1906, January 1996.

T. Nadeau & B. Schliesser                                         Page 6
PPVPN-TC-MIB                                              December, 2001

     [RFC2572]   Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
                 Processing and Dispatching for the Simple Network Management
                 Protocol (SNMP)", RFC 2572, April 1999.

     [RFC2574]   Blumenthal, U., and B. Wijnen, "User-based Security Model
                 (USM) for version 3 of the Simple Network Management
                 Protocol (SNMPv3)", RFC 2574, April 1999.

     [RFC1905]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
                 "Protocol Operations for Version 2 of the Simple Network
                 Management Protocol (SNMPv2)", RFC 1905, January 1996.

     [RFC2573]   Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
                 RFC 2573, April 1999.

     [RFC2575]   Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
                 Access Control Model (VACM) for the Simple Network
                 Management Protocol (SNMP)", RFC 2575, April 1999.

     [RFC2570]   Case, J., Mundy, R., Partain, D., and B. Stewart,
                 "Introduction to Version 3 of the Internet-standard Network
                 Management Framework", RFC 2570, April 1999.


     6. Authors Addresses

         Benson Schliesser
         SAVVIS Communications
         717 Office Parkway
         Saint Louis, MO 63141
         Phone: +1-314-468-7036
         Email: bensons@savvis.net

         Thomas D. Nadeau
         Cisco Systems, Inc.
         300 Apollo Drive
         Chelmsford, MA 01824
         Phone: +1-978-497-3051
         Email: tnadeau@cisco.com


     7. Full Copyright Statement

        Copyright (C) The Internet Society (2001). 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

T. Nadeau & B. Schliesser                                         Page 7
PPVPN-TC-MIB                                              December, 2001

        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.



































T. Nadeau & B. Schliesser                                          Page 8