[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00 01 03 04 05 06 07 08 09 10 11 12 13 14 15 RFC 5542

Internet Draft                                          Thomas D. Nadeau
Expires: December 2002                               Cisco Systems, Inc.

                                                          Dave Danenberg
                                         Litchfield Communications, Inc.

                                                             David Zelig
                                                       Corrigent Systems

                                                         Andrew G. Malis
                                                   Vivace Networks, Inc.
                                                               June 2002


        Definitions for Textual Conventions and OBJECT-IDENTITIES
                       for Pseudo-Wires Management

                    draft-ietf-pwe3-pw-tc-mib-00.txt

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

1  Abstract

  This memo defines an experimental portion of the Management
  Information Base (MIB) for use with network management protocols in
  the Internet community.  In particular, it describes the textual
  conventions to be used in the various Pseudo Wire (PW) MIB modules.







   Nadeau et al.       Expires December 2002                [page 1]


                             PWE3 TC MIB                    June 2002



Table of Contents


   1  Abstract.......................................................1
   2  Introduction...................................................2
   3  Terminology....................................................2
   4  The SNMP Management Framework..................................3
   4.1  Object Definitions...........................................4
   5  Object definitions.............................................4
   6  Security Considerations........................................7
   7  References.....................................................7
   8  Author's Addresses.............................................9
   9  Full Copyright Statement.......................................9


2  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
  IETF PW and PW-related MIBs.

  Comments should be made directly to the MPLS mailing list at
  pwe3@ietf.org.

  For an introduction to the concepts of Pseudo-Wires, see [PWREQ]
  and [FRMWK].

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


3  Terminology

  This document uses terminology from the document describing the PW
  framework [FRMWK].











  Nadeau et al         Expires December 2002                [page 2]


                             PWE3 TC MIB                    June 2002




4  The SNMP Management Framework

  The SNMP Management Framework presently consists of five major
  components:

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

  o 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 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].

  o 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].

  o 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].
  o A set of fundamental applications described in RFC 2573 [RFC2573]
  and the view-based access control mechanism described in RFC 2575
  [RFC2575].

  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.




  Nadeau et al         Expires December 2002                [page 3]


                             PWE3 TC MIB                    June 2002




4.1  Object Definitions

  Managed objects are accessed via a virtual information store,
  termed the Management Information Base or MIB.  Objects in the MIB
  are defined using the subset of Abstract Syntax Notation One
  (ASN.1) defined in the SMI. In particular, an OBJECT IDENTIFIER, an
  administratively assigned name, names each object type. The object
  type together with an object instance serves to uniquely identify a
  specific instantiation of the object.  For human convenience, we
  often use a textual string, termed the descriptor, to also refer to
  the object type.


5   Object definitions

  PW-TC-MIB DEFINITIONS ::= BEGIN

  IMPORTS
     MODULE-IDENTITY, Unsigned32, Integer32, experimental
        FROM SNMPv2-SMI

     TEXTUAL-CONVENTION
        FROM SNMPv2-TC;

  pwTCMIB MODULE-IDENTITY
     LAST-UPDATED "200205281200Z"  -- 28 May 2002 12:00:00 GMT
     ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
                   Group"
     CONTACT-INFO
     " Thomas D. Nadeau
       Postal: Cisco Systems, Inc.
               250 Apollo Drive
               Chelmsford, MA 01824
       Tel:    +1-978-497-3051
       Email:  tnadeau@cisco.com

       Dave Danenberg
       Postal: Litchfield Communications, Inc.
               76 Westbury Park Rd
               Princeton Building East
               Watertown, CT 06795
       Tel:    +1-860-945-1573 x3180
       Email:  dave_danenberg@litchfieldcomm.com

               David Zelig
       Postal: Corrigent Systems.
               126, Yigal Alon St.
               Tel Aviv, ISRAEL
               Phone: +972-3-6945273
       E-mail: davidz@corrigent.com

  Nadeau et al         Expires December 2002                [page 4]


                             PWE3 TC MIB                    June 2002




               Andrew G. Malis
       Postal: Vivace Networks, Inc.
               2730 Orchard Parkway
               San Jose, CA 95134
       Email:  Andy.Malis@vivacenetworks.com

       PWE3 Working Group Mailing List: pwe3@ietf.org"

     DESCRIPTION
         "This MIB Module provides Textual Conventions
          and OBJECT-IDENTITY Objects to be used PW services."

     -- Revision history.

     REVISION "200205281200Z"  -- 28 May 2002 12:00:00 GMT
     DESCRIPTION "Adding PwVcType, and enhance some descriptions."

     REVISION "200201301200Z"  -- 30 January 2002 12:00:00 GMT
     DESCRIPTION "Adding PwVcVlanCfg, PwAddressType and
                  PwOperStatus."

     REVISION "200112201200Z"  -- 20 Dec 2001 12:00:00 GMT
     DESCRIPTION "Remove PwVcInstance"

     REVISION "200107121200Z"  -- 12 July 2001 12:00:00 GMT
     DESCRIPTION "Initial version."

     ::= { pwMIB 1 } -- pwMIB To Be Assigned by IANA

  pwMIB OBJECT IDENTIFIER
         ::= { experimental xxx } -- To be assigned by IANA

  -- Textual Conventions defined below are organized alphabetically

  PwGroupID ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
          "An administrative identification mechanism for grouping a
           set of service-specific pseudo-wire services. May only
           have local significance."
     SYNTAX  Unsigned32

  PwVcIDType ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
          "Virtual Circuit Identifier. Used to identify the VC
           (together with some other fields) in the signaling
           session. Zero if the VC is set-up manually."
     SYNTAX  Unsigned32


  Nadeau et al         Expires December 2002                [page 5]


                             PWE3 TC MIB                    June 2002



  PwVcIndexType ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
          "Virtual Circuit Index. Locally unique index for indexing
           several MIB tables associated with a particular VC."
     SYNTAX  Unsigned32

  PwVcVlanCfg ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
          "VLAN configuration for Ethernet PW.
           Values between 0 to 4095 indicate the actual VLAN field
           value.
           A value of 4096 indicates that the object refer to
           untagged frames, i.e. frames without 802.1Q field.
           A value of 4097 indicates that the object is not
           relevant."
     SYNTAX  Integer32 (0..4097)

   PwOperStatus ::= TEXTUAL-CONVENTION
     STATUS      current
     DESCRIPTION
        "Indicate the operational status of the PW VC.

        - up:             Ready to pass packets.
        - down:           If PW signaling has not yet finished, or
                          indications available at the service
                          level indicate that the VC is not
                          passing packets.
        - testing:        If AdminStatus at the VC level is set to
                          test.
        - dormant:        The VC is not available because of the
                          required resources are occupied VC with
                          higher priority VCs .
        - notPresent:     Some component is missing to accomplish
                          the set up of the VC.
        - lowerLayerDown: The underlying PSN or outer tunnel is not
                          in OperStatus 'up'.
        "
   SYNTAX   INTEGER {
       up(1),
       down(2),
       testing(3),
       unknown(4),
       dormant(5),
       notPresent(6),
       lowerLayerDown(7)
       }

   PwVcType ::= TEXTUAL-CONVENTION
     STATUS      current

  Nadeau et al         Expires December 2002                [page 6]


                             PWE3 TC MIB                    June 2002



     DESCRIPTION
        "Indicate the VC type (i.e. the carried service).
         Note: the exact set of VC types is yet to be worked
         out by the WG.
        "
   SYNTAX   INTEGER {
      other(0),
      frameRelay(1),
      atmAal5Vcc(2),
      atmTransparent(3),
      ethernetVLAN(4),
      ethernet(5),
      hdlc(6),
      ppp(7),
      cep(8),
      atmVccCell(9),
      atmVpcCell(10),
      ethernetVPLS (11)
       }

  END

6  Security Considerations

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

7  References

  [FRMWK]     Pate et al, "Framework for Pseudo Wire Emulation Edge-
               to-Edge (PWE3)", <draft-ietf-pwe3-framework-00.txt>,
               February 2002.

  [PWREQ]     Xiao et al, "Requirements for Pseudo Wire Emulation
               Edge-to-Edge (PWE3)", <draft-ietf-pwe3-requirements-
               02.txt>, November 2001.

  [Assigned]  Reynolds, J., and J. Postel, "Assigned Numbers", RFC
               1700, October 1994. See also: http://www.isi.edu/in-
               notes/iana/assignments/smi-numbers

  [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
               FAMILY NUMBERS,(http://www.isi.edu/in-
               notes/iana/assignements/address-family-numbers), for
               MIB see:
               ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib

  [IFMIB]     McCloghrie, K., and F. Kastenholtz, "The Interfaces
               Group MIB using SMIv2", RFC 2863, June 2000.


  Nadeau et al         Expires December 2002                [page 7]


                             PWE3 TC MIB                    June 2002



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

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


  Nadeau et al         Expires December 2002                [page 8]


                             PWE3 TC MIB                    June 2002



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

8  Author's Addresses

  Thomas D. Nadeau
  Cisco Systems, Inc.
  250 Apollo Drive
  Chelmsford, MA 01824
  Email: tnadeau@cisco.com

  Dave Danenberg
  Litchfield Communications, Inc.
  76 Westbury Park Rd
  Princeton Building East
  Watertown, CT 06795
  Email: dave_danenberg@litchfieldcomm.com

  David Zelig
  Corrigent Systems
  126, Yigal Alon st.
  Tel Aviv, ISRAEL
  Phone:  +972-3-6945273
  Email:  davidz@corrigent.com

  Andrew G. Malis
  Vivace Networks, Inc.
  2730 Orchard Parkway
  San Jose, CA 95134
  Email:  Andy.Malis@vivacenetworks.com

9  Full Copyright Statement

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

  Nadeau et al         Expires December 2002                [page 9]


                             PWE3 TC MIB                    June 2002



  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.


































  Nadeau et al         Expires December 2002               [page 10]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/