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

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

Internet Draft                                          David Zelig
Expires: December 2004                           Corrigent Systems

                                                   Thomas D. Nadeau
                                                Cisco Systems, Inc.

                                                         June 2004


      Ethernet Pseudo Wire (PW) Management Information Base

                 draft-ietf-pwe3-enet-mib-05.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 managed objects
  for modeling of Ethernet Pseudo Wire (PW) services.












   Zelig et al.         Expires August 2004                 [page 1]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


Table of Contents

 1  Abstract.......................................................1
 2  Introduction...................................................2
 3  Terminology....................................................3
 4  The Internet-Standard Management Framework.....................3
 5  Feature Checklist..............................................3
 6  PW-MIB usage...................................................3
 6.1  PW-ENET-MIB usage............................................4
 6.2  PW-ENET management model.....................................5
 6.3  Example of MIB usage.........................................6
 6.4  Service delimiting modes.....................................6
 7  Object definitions.............................................9
 8  Security Considerations.......................................23
 9  IANA considerations...........................................24
 10   References..................................................24
 10.1 Normative references........................................24
 10.2 Informative references......................................25
 11   Author's Addresses..........................................25
 12   Full Copyright Statement....................................26
 13   Intellectual Property Notice................................26

2 Introduction

  This document describes a model for managing Ethernet pseudo wire
  services for transmission over a packet Switched Network (PSN). This
  MIB module is generic and common to all types of PSNs supported in
  the PWE3 architecture [FRARCH], which describes the transport and
  encapsulation of L1 and L2 services over supported PSN types.

  In particular, the MIB module associates a port or specific VLANs on
  top of a physical Ethernet port or a virtual Ethernet interface (for
  VPLS service) to a point-to-point PW. It is complementary to the
  [PWMIB], which is used to manage the generic PW parameters common to
  all service, including all supported PSN types.


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







  Zelig et al            Expires June 2003                  [page 2]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


3 Terminology

  This document uses terminology from the document describing the PW
  architecture [FRARCH] and from [PW-ENET].


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


5 Feature Checklist

  The PW Ethernet MIB module (PW-ENET-MIB) is designed to satisfy the
  following requirements and constraints:

   - The MIB module is designed to be work with the PW-MIB [PW-MIB].

   - The MIB module is independent of the PSN type.

   - The MIB module supports various options for selecting Ethernet
      packets into the PW. These include port-based PW, VLAN-based PW,
     VLAN-change and adding or removing VLAN fields between the port
      to be emulated and the PW.

   - In the case of an MPLS PSN, the MIB module supports the use of
      multiple PWs to carry the same Ethernet service. These PWs can be
      used to support L-LSPs or single COS E-LSPs capable PSN, when
      mapping of the Ethernet PRI bits to the PSN COS is required.

   - The MIB module enables both point-to-point Ethernet services and
      VPLS services as discussed in the L2VPN working group [VPLS].

   - The MIB module allows modeling of the PW as an Ethernet virtual
      port to be managed via existing Ethernet MIBs like Etherlike-MIB
      [RFC3635].



6  PW-MIB usage


  Zelig et al            Expires June 2003                  [page 3]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base



  The MIB module structure for defining a PW service is composed of
  three layers of MIB modules functioning together. This general model
  is defined in the PWE3 architecture [FRARCH].  The layering model is
  intended to sufficiently isolate PW services from the underlying PSN
  layer that carries the emulated service. This is done at the same
  time as providing a standard means for connecting any supported
  services to any supported PSNs.

  The first layer known as the service layer contains service-specific
  modules such as the one defined in this document. These modules
  define service-specific management objects that interface or
  collaborate with existing MIB modules for the native version of the
  service. The service-specific module ôgluesö the standard modules to
  the PWE3 MIB modules.

  The next layer of the PWE3 MIB framework is the PW MIB module
  [PWMIB]. This module is used to configure general parameters of PWs
  that are common to all types of emulated services and PSNs. This
  layer is connected to the service-specific layer above, and the PSN
  layer below.

  The PSN layer provides PSN-specific modules for each type of PSN.
  These modules associate the PW with one or more "tunnels" that carry
  the service over the PSN. These modules are defined in other
  documents. This module is used to ôglueö the PW service to the
  underlying PSN-specific MIB modules. In the case of MPLS, for
  example, the PW MPLS MIB [PWMPLSMIB] is used to connect the PW
  service to either the MPLS-LDP [LDPMIB] or MPLS-TE [TEMIB] MIBs.

  [PWTC] defines some of the object types used in these modules.

  The Etherlike-MIB [RFC3635] does not support virtual Ethernet port,
  however it is sometimes desired to manage the PW as an Ethernet port
  via the Etherlike-MIB. This MIB module supports an option to
  recognize the PW as an ifIndex, enabling standard use of the
  Etherlike-MIB to manage the PW.


6.1  PW-ENET-MIB usage

    - The PW table (pwVcTable) is used for all PW types (ATM, FR,
      Ethernet, SONET, etc.). This table contains high level generic
      parameters related to the PW creation. A row is typically created
      by the operator (see [PWMIB] for other options) for each PW
      service.

    - Based on the PSN type defined for the PW, rows are created in PSN
      specific module (for example [PWMPLSMIB]) and associated to the
      pwVcTable by the common pwVcIndex.



  Zelig et al            Expires June 2003                  [page 4]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


    - If the PW type is Ethernet or EthernetTagged a row is created by
      the agent in pwVcEnetTable.

    - When using a MPLS PSN, it may be required to separate the same
      Ethernet services to multiple PW in order to support multiple COS
      on the same service. In this case, multiple PWs, each with the
      appropriate COS will be created to the same destination, and
      classification will be based also on the Ethernet PRI bits
      marking. The MIB allow any combinations of multiple PRI setting
      to PSN COS mapping (The exact PSN marking (EXP bits, DSCP etc.)
      is out of scope of this MIB). In these cases, pwVcEnetTable will
      hold multiple rows with the same Ethernet port and VLAN mapping,
      each PW will need to be created separately by the signaling
      process.


6.2  PW-ENET management model

  The management model for the Ethernet PW is shown in figure 1, and
  is based on the PW proposed layering [PWARCH].


                  +--------------------------------------+
                  |                PE Device             |
                  +--------------------------------------+
           Single |                 |                    |
           AC     |                 |      Single        | PW Instance
          <------>o   Forwarder     +      PW Instance   X<=========>
                  |                 |                    |
                  +--------------------------------------+
                                    ^
                                    |
                             May be modeled as
                                 ifIndex

     Notation:
     o       A physical CE-bound PE port
     +       A PW IWF instance interface to the forwarder.
     X       A PE PSN-bound port.

               Figure 1: A simple point-to-point service


  In the typical point-to-point service, the object
  pwVcEnetPortIfIndex associates the physical CE-bound PE port ('o')
  to the PW (it is allowed to have multiple PWs associated to the same
  physical port). This MIB module also manages some of the possible
  operations of the forwarder.

  In some models it is convenient to model the forwarder virtual
  interface to a PW IWF instance ('+') as an ifIndex. As discussed in


  Zelig et al            Expires June 2003                  [page 5]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


  the [PWMIB], this is possible by using the PW ifType in the ifTable
  and indicating the ifIndex in the main pwVcTable. In case of
  Ethernet PW a virtual interface of ifType = etherLike will be
  assigned on top of the PW interface to enable statistics gathering
  and statuses and other management configuration tasks via existing
  tools. This way, the PW instance is managed as virtual Ethernet
  interface in the PE.

  The model for using the PW in non-point to point applications, such
  as VPLS are done with the same principle in mind, except that the
  creation of the tables is related typically to an auto-discovery
  process.

6.3  Example of MIB usage

  Assume we would like to create a PW of type VLAN between two PEs,
  for VLAN value 5.

  - Follows the example in [PWMIB], except that the pwVcType is equal
  æethernetTaggedÆ.

  - The agent creates a row in pwVcEnetTable and pwVcEnetStatsTable
  for the specified pwVcindex. The pwVcEnetPwInstance is automatically
  selected by the agent to the value of æ1Æ.

  - The operator fills the following entries in the pwVcEnetTable:

         pwVcEnetPwVlan        5,
         pwVcEnetVlanMode      noChange,
         pwVcEnetPortVlan      5,

         pwVcEnetPortIfIndex   1001,
         pwVcEnetVcIfIndex     0, -- Not managed in the
                                  -- Etherlike MIB module
         .. .

  - The PW is ready for forwarding when signaling has been accomplished
  successfully between the two peers.


6.4  Service delimiting modes

  In this section we will describe how the MIB module supports point-
  to-point applications with various VLAN service delimiting options
  on the physical port and the PW modes and VLAN values. In the VPLS
  case the PW is attached to a virtual interface that is attached to a
  bridge or VPLS forwarder, and it is assumed that this bridge
  function would be responsible for the packet modifications between
  the physical port or other virtual port and the virtual port the PW
  is attached to.



  Zelig et al            Expires June 2003                  [page 6]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base



  There are 3 main services that are supported by this MIB module.

  1) Port mode: In this mode, the whole traffic from the port is
  mapped to the PW.

  1a) In the typical application, the packet is sent to the PW as is:

         pwVcEnetPwVlan        4097,
         pwVcEnetVlanMode      portMode,
         pwVcEnetPortVlan      4097,

         pwVcType              Ethernet

  1a) It is possible to add a provider tag (value 10 for example) to
  the packet when it is sent over the PW:

         pwVcEnetPwVlan        10,
         pwVcEnetVlanMode      addVlan,
         pwVcEnetPortVlan      4097,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  2) Single VLAN: In this mode, only the first VLAN field on the
  packet from the physical port is the service delimiting tag, as an
  example VLAN=5. The following options of processing are possible:

  2a) One to one mapping: the service delimiting tag is kept as is on
  the PW.

         pwVcEnetPwVlan        5,
         pwVcEnetVlanMode      noChange,
         pwVcEnetPortVlan      5,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  2b) One to one mapping: the service delimiting tag change itÆs value
  (to value of 6) on the PW.

         pwVcEnetPwVlan        6,
         pwVcEnetVlanMode      changeVlan,
         pwVcEnetPortVlan      5,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  2c) The service delimiting tag is removed when the packet is sent to
  the PW.



  Zelig et al            Expires June 2003                  [page 7]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


         pwVcEnetPwVlan        5,
         pwVcEnetVlanMode      removeVlan,
         pwVcEnetPortVlan      4097,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  One should note that this mode is also applicable when the service
  delimiting tag is a service provider tag (VLAN=5 in this case), and
  the service provider actually replace the map the traffic to a
  single PW independent of the packet format on top of this VLAN.


  2d) Untagged packets mapped to a PW as is (packets with a VLAN field
  from tha same port MAY be mapped to other PWs).

         pwVcEnetPwVlan        4096,
         pwVcEnetVlanMode      noChange,
         pwVcEnetPortVlan      4096,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  2e) Untagged packets mapped to a PW, and a VLAN field is added to
  the packet.

         pwVcEnetPwVlan        6,
         pwVcEnetVlanMode      addVlan,
         pwVcEnetPortVlan      4096,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  2f) A provider VLAN (value 10) is added to the packet coming with
  VLAN value 5 before it is sent to the PW.

         pwVcEnetPwVlan        10,
         pwVcEnetVlanMode      addVlan,
         pwVcEnetPortVlan      5,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  3) Nested VLAN (QinQ): When only the first VLAN is the service
  delimiting tag, the modes as described in 2) SHOULD be used. In
  other cases, i.e. the service delimiting tag is both the first VLAN
  and the second VLAN, the following option is supported by this MIB
  module. Other scenarios are considered out of the scope and should
  be handled by other MIB modules that manage the forwarder.




  Zelig et al            Expires June 2003                  [page 8]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


  Assuming the provider tag equals 5 and the (inner) VLAN equal 100,
  this traffic can be mapped to the PW without the provider tag by
  using the following configuration:

         pwVcEnetPwVlan        100,
         pwVcEnetVlanMode      removeVLAN,
         pwVcEnetPortVlan      5,

  pwVcType MAY equal æEthernetÆ or æEthernetTaggedÆ, æEthernetTaggedÆ
  is RECOMMENDED.

  Packets of the same provider tag MAY be mapped to other PWs.


7 Object definitions

  --
  -- Ethernet PW MIB
  --

  PW-ENET-DRAFT05-MIB DEFINITIONS ::= BEGIN

  IMPORTS
      OBJECT-TYPE, MODULE-IDENTITY
          FROM SNMPv2-SMI

      MODULE-COMPLIANCE, OBJECT-GROUP
          FROM SNMPv2-CONF

      StorageType, RowStatus
          FROM SNMPv2-TC

      InterfaceIndexOrZero
          FROM IF-MIB

      ZeroBasedCounter32
          FROM RMON2-MIB

      pwVcIndex
          FROM PW-DRAFT05-MIB

      pwStdMIB, PwVcVlanCfg, PwVcIndexType
          FROM PW-TC-DRAFT05-MIB;

  pwVcEnetMIB MODULE-IDENTITY
      LAST-UPDATED "200406101200Z"  -- 10 June 2004 12:00:00 GMT
      ORGANIZATION "IETF PWE3 Working group"
      CONTACT-INFO
           "David Zelig
            Postal: Corrigent Systems
            126, Yigal Alon St.


  Zelig et al            Expires June 2003                  [page 9]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


            Tel-Aviv, ISRAEL
            Tel: +972-3-6945273
            E-mail: davidz@corrigent.com

            Thomas D. Nadeau
            Postal: Cisco Systems, Inc.
            250 Apollo Drive
            Chelmsford, MA 01824
            Tel:    +1-978-497-3051
            Email:  tnadeau@cisco.com
          "
      DESCRIPTION
          "This MIB module describes a model for managing Ethernet
          point-to-point pseudo wire services over a Packet
          Switched Network (PSN).

          Copyright (C) The Internet Society (date).  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
        "200406101200Z"  -- 10 June 2004 12:00:00 GMT
     DESCRIPTION
        " Changes from as draft-pwe3-enet-mib-04:
         - Move the VLAN field from an index to an object, and add
           an arbitrary index instead.
         - Typo Fixes.
         - Adapt modes to draft-ietf-pwe3-ethernet-encap-06.txt
         - Adding detailed compliance requirements.
        "

     REVISION
        "200402041200Z" -- 4 February 2004 12:00:00 GMT
     DESCRIPTION
        " Changes from as draft-pwe3-enet-mib-03:
          1) Remove pwVcEnetFragSize and pwVcEnetCwStatus since they
          are controlled by the PW MIB module and they are duplicated
          here.
          2) Change counter64 to ZeroBasedCounter32 in error
          statistics, and fix them to be read-only.
        "

     REVISION
        "200312161200Z" -- 16 December 2003 12:00:00 GMT
     DESCRIPTION
        " Changes from as draft-pwe3-enet-mib-02.
          1) Module identity under the PW MIB tree.


  Zelig et al            Expires June 2003                 [page 10]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


        "

     REVISION
         "200307291200Z" -- 29 July 2003 12:00:00 GMT
     DESCRIPTION
        " Changes from as draft-pwe3-enet-mib-01.
          1) Added Control Word status and fragmentation status.
          2) Aligning description of objects and rules based on
             draft-ietf-pwe3-ethernet-encap-06.txt.
        "

     REVISION
        "200209221200Z" -- 22 September 2002 12:00:00 GMT
     DESCRIPTION
        " Submitted as draft-pwe3-enet-mib-00.
          Changes from previous version:
          1) Alignment with draft-pwe3-ethernet-encap-00.txt:
             removing 'rangeVLAN' mode and the associated objects.
          2) Relaxing requirement on value of pwVcEnetPortVlan in
             port mode.
        "

     REVISION
         "200208201200Z" -- 20 August 2002 12:00:00 GMT
     DESCRIPTION
         "Changes from previous version:
          1) Add pwVcEnetVcIfIndex - Option for VC as ifIndex.
          2) Change counters to 64 bits.
          3) Add mode for adding/removing VLAN fields between PW and
             CE bound interface.
          4) Referencing draft-martini instead of draft-so.
          5) Editorial changes for some description clauses.
          6) MPLS PRI mapping table to be independent (not augmented).
          7) Adapt descriptions and rules of use to
             dratf-ietf-pwe3-Ethernet-encap-00.
          "
     REVISION
         "200202031200Z"  -- 03 February 2002 12:00:00 GMT
     DESCRIPTION
         "initial revision as -00 draft"

      ::= { pwStdMIB x } -- To be assigned by IANA
                         -- The value of 5 is requested.


  pwVcEnetObjects        OBJECT IDENTIFIER ::= { pwVcEnetMIB 1 }
  pwVcEnetConformance    OBJECT IDENTIFIER ::= { pwVcEnetMIB 2 }

  --
  -- Ethernet PW table
  --


  Zelig et al            Expires June 2003                 [page 11]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base



  pwVcEnetTable  OBJECT-TYPE
      SYNTAX SEQUENCE OF PwVcEnetEntry
      MAX-ACCESS  not-accessible
      STATUS     current
      DESCRIPTION
          "This table contains the index to the Ethernet tables
          associated with this ETH PW, the VLAN configuration and
          VLAN mode."
      ::= { pwVcEnetObjects 1 }

  pwVcEnetEntry  OBJECT-TYPE
      SYNTAX     PwVcEnetEntry
      MAX-ACCESS  not-accessible
      STATUS     current
      DESCRIPTION
          "This table is indexed by the same index that was created
          for the associated entry in the PW generic table in the PW
          MIB module.
          The PwVcIndex and the pwVcEnetPwInstance are used as indexes
          to allow multiple VLANs to exist on the same PW.

          An entry is created in this table by the agent for every
          entry in the pwVcTable with a pwVcType of 'ethernetTagged'
          or 'ethernet'. Additional rows may be created by the
          operator or the agent if multiple entries are required for
          the same PW.

          The value of pwVcEnetPwInstance can be arbitrary selected
          to make the row unique, however implementations that know
          the VLAN field value when the row is created MAY use the
          value of the VLAN itself for better readability and
          backward compatibility with older versions of this MIB
          module.

          This table provides Ethernet port mapping and VLAN
          configuration for each Ethernet PW."

      INDEX { pwVcIndex, pwVcEnetPwInstance }
      ::= { pwVcEnetTable 1 }

  PwVcEnetEntry ::= SEQUENCE {
         pwVcEnetPwInstance    PwVcIndexType,
         pwVcEnetPwVlan        PwVcVlanCfg,
         pwVcEnetVlanMode      INTEGER,
         pwVcEnetPortVlan      PwVcVlanCfg,

         pwVcEnetPortIfIndex   InterfaceIndexOrZero,
         pwVcEnetVcIfIndex     InterfaceIndexOrZero,

         pwVcEnetRowStatus     RowStatus,


  Zelig et al            Expires June 2003                 [page 12]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


         pwVcEnetStorageType   StorageType
                    }

  pwVcEnetPwInstance  OBJECT-TYPE
      SYNTAX      PwVcIndexType
      MAX-ACCESS  not-accessible
      STATUS      current
      DESCRIPTION
          "If multiple rows are mapped to the same PW, this index is
           used to uniquely identify the individual row.
           If the value of the VLAN field is known at the time of
           of row creation, the value of pwVcEnetPwVlan MAY be used
           for better readability and backward compatibility with
           older versions of this MIB module. Otherwise the value
           of '1' SHOULD be set to the first row for each pwVcIndex
           for better readability and in order that the management
           application would know in advance how to access the
           first row when it was created by the agent.
          "

      ::= { pwVcEnetEntry 1 }

  pwVcEnetPwVlan  OBJECT-TYPE
      SYNTAX      PwVcVlanCfg
      MAX-ACCESS  read-create
      STATUS      current
      DESCRIPTION
          "This Object defines the (service delimiting) VLAN field
          value on the PW. The value of 4097 MUST be used if the
          object is not applicable, for example when mapping all
          packets from an Ethernet port to this PW (raw mode).
          The value of 4096 MUST be set to indicate untagged frames
          (from the PW point of view), i.e. when pwVcEnetVlanMode
          equals 'noChange' and pwVcEnetPortVlan equals 4096."
      ::= { pwVcEnetEntry 2 }

  pwVcEnetVlanMode  OBJECT-TYPE
      SYNTAX     INTEGER {
              other(0),
              portBased(1),
              noChange(2),
              changeVlan(3),
              addVlan(4),
              removeVlan(5)
      }
      MAX-ACCESS  read-create
      STATUS     current
      DESCRIPTION
          "Indicates the mode of VLAN handling between the port
           associated to the PW and the PW encapsulation.



  Zelig et al            Expires June 2003                 [page 13]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


          - 'other' indicate operation that is not defined by
            this MIB module.

          - 'portBased' indicates that the forwarder will forward
            packets between the port and the PW independent of their
            structure (i.e. there is no service delimiting VLAN tags
            from the PE standpoint).

          - 'noChange' indicates that the PW contains the original
             user VLAN, as specified in pwVcEnetPortVlan, i.e. the
             VLAN on the PE-CE link is the service delimiting tag
             and is kept as is on the PW. This is allowed only for
             pwVcType equal 'ethernetTagged'.

          - 'changeVlan' indicates that the VLAN field on the PW
            may be different than the VLAN field on the user's
            port. the VLAN on the PE-CE link is the service delimiting
            tag but has a different value on the PW.

          - 'removeVlan' indicates that the encapsulation on the
            PW does not include the service delimiting VLAN field.
            Note that PRI bits transparency is lost in this case.

          - 'addVlan' indicate that a VLAN field will be added
            on the PSN bound direction. pwVcEnetPwVlan indicates
            the value that will be added.

          - Implementation of 'portsbased', 'removeVlan', 'addVlan'
            'other' and 'changeVlan' is OPTIONAL.
          "

      DEFVAL { noChange }
      ::= { pwVcEnetEntry 3 }

  pwVcEnetPortVlan  OBJECT-TYPE
      SYNTAX     PwVcVlanCfg
      MAX-ACCESS read-create
      STATUS     current
      DESCRIPTION
          "This object defines the VLAN value on the physical port (or
          VPLS virtual port) or a mapping of the whole port traffic
          to the same PW.

          The value of '4097' NUST be used if the whole port traffic
          is mapped to the same PW. Note that a pwVcType of
          'ethernetTagged' can still be used if service delimiting tag
          is added on the PW (pwVcEnetVlanMode equals 'addVlan').

          It MUST be equal to pwVcEnetPwVlan if pwVcEnetVlanMode
          equals'noChange'.



  Zelig et al            Expires June 2003                 [page 14]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


          The value 4096 indicates that packet without a VLAN field
          (i.e. untagged frames) on the port are associated to this
          PW. This allows the same behaviors as assigning 'Default
          VLAN' to un-tagged frames.
          "

      DEFVAL  { 4097 }
      ::= { pwVcEnetEntry 4 }

  pwVcEnetPortIfIndex  OBJECT-TYPE
      SYNTAX     InterfaceIndexOrZero
      MAX-ACCESS  read-create
      STATUS     current
      DESCRIPTION
          "This object is used to specify the ifIndex of the Ethernet
           port associated with this PW for point-to-point Ethernet
           service, or the ifIndex of the virtual interface of the
           VPLS instance associated with the PW if the service is
           VPLS. Two rows in this table can point to the same ifIndex
           only if:

           1) It is required to support multiple COS on a MPLS PSN
              for the same service (i.e.: a combination of ports and
              VLANs) by the use of multiple PW, each with a different
              COS.

           2) There is no overlap of VLAN values specified in
              pwVcEnetPortVlan that are associated with this port.

           A value of zero indicates that association to an ifIndex is
           not yet known."

      ::= { pwVcEnetEntry 5 }

  pwVcEnetVcIfIndex  OBJECT-TYPE
      SYNTAX     InterfaceIndexOrZero
      MAX-ACCESS read-create
      STATUS     current
      DESCRIPTION
          "If the PW is modeled as an ifIndex in the ifTable, this
           object indicates the value of the ifIndex representing the
           Ethernet PW on the PSN side in the Etherlike-MIB. Note that
           this value may be different from the value of pwVcIfIndex
           that represent the ifIndex of the PW for ifType 'pw'."

       DEFVAL { 0 }
      ::= { pwVcEnetEntry 6 }

  pwVcEnetRowStatus  OBJECT-TYPE
      SYNTAX     RowStatus
      MAX-ACCESS  read-create


  Zelig et al            Expires June 2003                 [page 15]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


      STATUS     current
      DESCRIPTION
          "Enable creating, deleting and modifying this row."
      ::= { pwVcEnetEntry 7 }

  pwVcEnetStorageType  OBJECT-TYPE
      SYNTAX     StorageType
      MAX-ACCESS  read-create
      STATUS     current
      DESCRIPTION
          "Indicates the storage type of this row."
      ::= { pwVcEnetEntry 8 }

  --
  -- Ethernet Priority Mapping Table
  --

  pwVcEnetMplsPriMappingTable  OBJECT-TYPE
      SYNTAX SEQUENCE OF PwVcEnetMplsPriMappingTableEntry
      MAX-ACCESS  not-accessible
      STATUS     current
      DESCRIPTION
          "This table may be used for MPLS PSNs if there is a need
          to hold multiple PW, each with different COS, for the same
          user service (port + PW VLAN). Such a need may arise if the
          MPLS network is capable of L-LSP or E-LSP without multiple
          COS capabilities.  Each row is indexed by the pwVcIndex
          and indicate the PRI bits on the packet received from the
          user port (or VPLS virtual port) that are
          classified to this PW. Note that the EXP bit value of the
          PW is configured in the PW MPLS MIB module."

      ::= { pwVcEnetObjects 2 }

  pwVcEnetMplsPriMappingTableEntry  OBJECT-TYPE
      SYNTAX     PwVcEnetMplsPriMappingTableEntry
      MAX-ACCESS  not-accessible
      STATUS     current
      DESCRIPTION
          "Each entry is created by the operator or by the agent
           based on local policy if special classification based on
           the PRI bits is required for this PW."

      INDEX { pwVcIndex }

      ::= { pwVcEnetMplsPriMappingTable 1 }

  PwVcEnetMplsPriMappingTableEntry ::= SEQUENCE {
      pwVcEnetMplsPriMapping             BITS,
      pwVcEnetMplsPriMappingRowStatus    RowStatus,
      pwVcEnetMplsPriMappingStorageType  StorageType


  Zelig et al            Expires June 2003                 [page 16]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


  }

  pwVcEnetMplsPriMapping  OBJECT-TYPE
      SYNTAX     BITS {
          pri000 (0),
          pri001 (1),
          pri010 (2),
          pri011 (3),
          pri100 (4),
          pri101 (5),
          pri110 (6),
          pri111 (7),
          untagged (8)
      }
      MAX-ACCESS  read-create
      STATUS     current
      DESCRIPTION
          "This object defines the groups of user PRI mapped into
          this PW. Each bit set indicates that this user priority
          is assigned to this PW.

          The value 'untagged' is used to indicate that untagged
          frames are also associated to this PW.

          This object allows the use of different PSN COS based on
          user marking of PRI bits in MPLS PSN with L-LSP or
          E-LSP without multiple COS support. In all other cases,
          the default value MUST be used.

          It is REQUIRED that there is no overlap on this object
          between rows serving the same service (port+ PW VLAN).

          In case of missing BIT configuration between rows to
          the same service, incoming packets with PRI marking not
          configured should be handled by the PW with the lowest
          COS.
          "
      REFERENCE
          "See appendix A of 'Encapsulation Methods for Transport of
           Ethernet Frames Over IP/MPLS Networks' (work-in-progress)
           for mapping rules of the PRI bits to PSN COS."

      ::= { pwVcEnetMplsPriMappingTableEntry 1 }

  pwVcEnetMplsPriMappingRowStatus  OBJECT-TYPE
      SYNTAX     RowStatus
      MAX-ACCESS  read-create
      STATUS     current
      DESCRIPTION
          "Enable creating, deleting and modifying this row.
           pwVcEnetMplsPriMapping may be changed when this object is


  Zelig et al            Expires June 2003                 [page 17]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


           in the active(1) state, assuming the new value honors the
           rules as described in the description clause of
           pwVcEnetMplsPriMapping. Otherwise, the row status MUST be
           set to notActive(3) before a change can be made to
           pwVcEnetMplsPriMappingRowStatus."
      ::= { pwVcEnetMplsPriMappingTableEntry 2 }

  pwVcEnetMplsPriMappingStorageType  OBJECT-TYPE
      SYNTAX     StorageType
      MAX-ACCESS  read-create
      STATUS     current
      DESCRIPTION
          "Indicates the storage type of this row."
      ::= { pwVcEnetMplsPriMappingTableEntry 3 }


  --
  -- Ethernet PW Statistics Table
  --

  pwVcEnetStatsTable  OBJECT-TYPE
      SYNTAX SEQUENCE OF PwVcEnetStatsEntry
      MAX-ACCESS  not-accessible
      STATUS     current
      DESCRIPTION
          "This table contains statistical counters specific for
           Ethernet PW."
      ::= { pwVcEnetObjects 3 }

  pwVcEnetStatsEntry  OBJECT-TYPE
      SYNTAX     PwVcEnetStatsEntry
      MAX-ACCESS  not-accessible
      STATUS     current
      DESCRIPTION
          "Each entry represents the statistics gathered for the
           PW carrying the Ethernet packets since this PW was
           first created in the pwVcEnetTable."
      INDEX { pwVcIndex }
      ::= { pwVcEnetStatsTable 1 }

  PwVcEnetStatsEntry ::= SEQUENCE {
      pwVcEnetStatsIllegalVlan        ZeroBasedCounter32,
      pwVcEnetStatsIllegalLength      ZeroBasedCounter32
  }

  pwVcEnetStatsIllegalVlan  OBJECT-TYPE
      SYNTAX     ZeroBasedCounter32
      MAX-ACCESS  read-only
      STATUS     current
      DESCRIPTION
          "The number of packets received (from the PSN) on this PW


  Zelig et al            Expires June 2003                 [page 18]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


           with an illegal VLAN field, missing VLAN field that was
           expected, or A VLAN field when it was not expected. This
           counter is not applicable if the PW type is 'ethernet'
           (i.e. raw mode), and MUST return the value of zero in
           this case."
      ::= { pwVcEnetStatsEntry 1 }

  pwVcEnetStatsIllegalLength  OBJECT-TYPE
      SYNTAX     ZeroBasedCounter32
      MAX-ACCESS  read-only
      STATUS     current
      DESCRIPTION
          "The number of packets that were received with an illegal
           Ethernet packet length on this PW. An illegal length is
           defined as being greater than the value in the advertised
           MTU supported, or shorter than the allowed Ethernet packet
           size. The agent should start the value of this counter at
           the value of zero."
      ::= { pwVcEnetStatsEntry 2 }

  ---
  --- Conformance description
  ---

  pwVcEnetGroups      OBJECT IDENTIFIER ::= { pwVcEnetConformance 1 }
  pwVcEnetCompliances OBJECT IDENTIFIER ::= { pwVcEnetConformance 2 }


  -- Compliance requirement for fully compliant implementations.

  pwVcEnetModuleFullCompliance MODULE-COMPLIANCE
      STATUS  current
      DESCRIPTION
              "The compliance statement for agents that provide full
               support for PW-ENET MIB Module. Such devices can
               then be monitored and also be configured using
               this MIB module."

      MODULE  -- this module
        MANDATORY-GROUPS { pwVcEnetGroup,
                           pwVcStatsGroup
                           }

     GROUP pwVcEnetMplsPriGroup
     DESCRIPTION
         "Collection of objects defining classification to
          different PW based on the user's PRI bits mapping.
          This group is optional, and should be implemented
          only for MPLS PSN where only L-LSP or single OA
          E-LSP, exists, and different PSN COS is required
          based on the PRI mapping."


  Zelig et al            Expires June 2003                 [page 19]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base



     OBJECT       pwVcEnetVlanMode
     DESCRIPTION "An implementation MUST support at least the value
                  noChange(2)."

     OBJECT       pwVcEnetVcIfIndex
     MIN-ACCESS   read-only
     DESCRIPTION "Write access and values other than zero are
                  required only for implementations that support the
                  modeling the Ethernet PW in the Etherlike-MIB."

     OBJECT       pwVcEnetRowStatus
     SYNTAX       RowStatus { active(1), notInService(2),
                              notReady(3) }
     WRITE-SYNTAX RowStatus { active(1), notInService(2),
                              createAndGo(4), destroy(6)
                            }
     MIN-ACCESS   read-only
     DESCRIPTION "Support for createAndWait is not required. Support
                  of notReady is not required for implementations that
                  do not support signaling.
                  Support of read-write is not required for
                  implementations that do not support more than one
                  VLAN mapping to the same PW."

     OBJECT       pwVcEnetMplsPriMappingRowStatus
     SYNTAX       RowStatus { active(1), notInService(2),
                              notReady(3) }
     WRITE-SYNTAX RowStatus { active(1), notInService(2),
                              createAndGo(4), destroy(6)
                            }
     DESCRIPTION "Support for createAndWait is not required."

      ::= { pwVcEnetCompliances 1 }

  -- Compliance requirement for read-only compliant implementations.

  pwVcEnetModuleReadOnlyCompliance MODULE-COMPLIANCE
      STATUS  current
      DESCRIPTION
              "The compliance statement for agents that provide read
               only support for PW-ENET MIB Module. Such devices can
               then be monitored but cannot be configured using this
               MIB module."

      MODULE  -- this module
        MANDATORY-GROUPS { pwVcEnetGroup,
                           pwVcStatsGroup
                           }

        GROUP pwVcEnetMplsPriGroup


  Zelig et al            Expires June 2003                 [page 20]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


        DESCRIPTION
            "Collection of objects defining classification to
             different PW based on the user's PRI bits mapping.
             This group is optional, and should be implemented
             only for MPLS PSN where only L-LSP or single OA
             E-LSP, exists, and different PSN COS is required
             based on the PRI mapping."

     OBJECT       pwVcEnetPwVlan
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required."

     OBJECT       pwVcEnetVlanMode
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required. An implementation
                  MUST support at least the value noChange(2)."

     OBJECT       pwVcEnetPortVlan
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required."

     OBJECT       pwVcEnetPortIfIndex
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required."

     OBJECT       pwVcEnetVcIfIndex
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required. Values other than
                  zero are required only for implementations that
                  support the modeling the Ethernet PW in the
                  Etherlike-MIB."

     OBJECT       pwVcEnetRowStatus
     SYNTAX       RowStatus { active(1), notInService(2),
                              notReady(3) }
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required. Support
                  of notReady is not required for implementations that
                  do not support signaling."

     OBJECT       pwVcEnetStorageType
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required."

     OBJECT       pwVcEnetMplsPriMapping
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required."

     OBJECT       pwVcEnetMplsPriMappingRowStatus
     SYNTAX       RowStatus { active(1), notInService(2),
                              notReady(3) }


  Zelig et al            Expires June 2003                 [page 21]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required."

     OBJECT       pwVcEnetMplsPriMappingStorageType
     MIN-ACCESS   read-only
     DESCRIPTION "Write access is not required."

      ::= { pwVcEnetCompliances 2 }

  -- Units of conformance.

  pwVcEnetGroup OBJECT-GROUP
     OBJECTS {
              pwVcEnetPwVlan,
              pwVcEnetVlanMode,
              pwVcEnetPortVlan,
              pwVcEnetPortIfIndex,
              pwVcEnetVcIfIndex,
              pwVcEnetRowStatus,
              pwVcEnetStorageType
     }
     STATUS  current
     DESCRIPTION
         "Collection of objects for basic Ethernet PW config."
     ::= { pwVcEnetGroups 1 }

  pwVcStatsGroup OBJECT-GROUP
     OBJECTS {
              pwVcEnetStatsIllegalVlan,
              pwVcEnetStatsIllegalLength
     }
     STATUS  current
     DESCRIPTION
         "Collection of objects counting various PW level errors."
     ::= { pwVcEnetGroups 2 }

  pwVcEnetMplsPriGroup OBJECT-GROUP
     OBJECTS {
              pwVcEnetMplsPriMapping,
              pwVcEnetMplsPriMappingRowStatus,
              pwVcEnetMplsPriMappingStorageType
     }
     STATUS  current
     DESCRIPTION
         "Collection of objects defining classification to
          different PW based on the user's PRI bits mapping.
          This group is optional, and should be implemented
          only for MPLS PSN where only L-LSP or single OA
          E-LSP exists, and different PSN COS is required
          based on the PRI mapping."
     ::= { pwVcEnetGroups 3 }


  Zelig et al            Expires June 2003                 [page 22]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base



  END


8 Security Considerations

  It is clear that this MIB module is potentially useful for
  Monitoring of Ethernet PW capable PEs.  This MIB module can also be
  used for configuration of certain objects, and anything that can be
  configured can be incorrectly configured, with potentially
  disastrous results.

  There are a number of management objects defined in this MIB module
  with a MAX-ACCESS clause of read-write and/or read-create.  Such
  objects may be considered sensitive or vulnerable in some network
  environments.  The support for SET operations in a non-secure
  environment without proper protection can have a negative effect on
  network operations.  These are the tables and objects and their
  sensitivity/vulnerability:

     o    the pwVcEnetTable and the pwVcEnetMplsPriMappingTable
          collectively contain objects to provision Ethernet PWs.
          Unauthorized access to objects in these tables, could result
          in disruption of traffic on the network.  The use of
          stronger mechanisms such as SNMPv3 security should be
          considered where possible.  Specifically, SNMPv3 VACM and
          USM MUST be used with any v3 agent which implements this MIB
          module.
          Administrators should consider whether read access to these
          objects should be allowed, since read access may be
          undesirable under certain circumstances.

  Some of the readable objects in this MIB module "i.e., objects with
  a MAX-ACCESS other than not-accessible" may be considered sensitive
  or vulnerable in some network environments.  It is thus important to
  control even GET and/or NOTIFY access to these objects and possibly
  to even encrypt the values of these objects when sending them over
  the network via SNMP.  These are the tables and objects and their
  sensitivity/vulnerability:

     o    the pwVcEnetTable and the pwVcEnetMplsPriMappingTable
          collectively show the Ethernet PW service configuration.
          If an Administrator does not want to reveal this
          information, then these tables should be
          considered sensitive/vulnerable.

  SNMP versions prior to SNMPv3 did not include adequate security.
  Even if the network itself is secure "for example by using IPSec",
  even then, there is no control as to who on the secure network is
  allowed to access and GET/SET "read/change/create/delete" the
  objects in this MIB module.


  Zelig et al            Expires June 2003                 [page 23]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base



  It is RECOMMENDED that implementers consider the security features
  as provided by the SNMPv3 framework "see [RFC3410], section 8",
  including full support for the SNMPv3 cryptographic mechanisms "for
  authentication and privacy".

  Further, deployment of SNMP versions prior to SNMPv3 is NOT
  RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
  enable cryptographic security.  It is then a customer/operator
  responsibility to ensure that the SNMP entity giving access to an
  instance of this MIB module, is properly configured to give access
  to the objects only to those principals "users" that have legitimate
  rights to indeed GET or SET "change/create/delete" them.

9 IANA considerations

  As requested in the PW TC MIB [PWTCMIB], PWE3 related standards
  track MIB modules should be rooted under the pwStdMIB subtree. The
  IANA is requested to assign { pwStdMIB 5 } to the PW ENET MIB module
  specified in this document.


10 References

10.1 Normative references

  [ENETPW]    Martini, L., et al, "Encapsulation Methods for Transport
               of Ethernet Frames Over IP/MPLS Networks", work-in-
               progress.

  [PWARCH]    Bryant, S., et al, ôPWE3 Architectureö, work-in-
               progress.

  [PWREQ]     Xiao, X., et al, "Requirements for Pseudo Wire Emulation
               Edge-to-Edge (PWE3)", work-in-progress.

  [PWTC]      Nadeau, T., et al, "Definitions for Textual Conventions
               and OBJECT-IDENTITIES for Pseudo-Wires Management",
               work-in-progress.

  [PWMIB]     Zelig, D., et al, ôPseudo Wire (PW) Management
               Information Baseö, work-in-progress.

  [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

  [RFC2021]   Waldbusser, S., "Remote Network Monitoring Management
               Information Base Version 2 using SMIv2", RFC 2021,
               January 1997.


  Zelig et al            Expires June 2003                 [page 24]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base



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

  [RFC2434]   Narten, T. and H. Alvestrand, "Guidelines for Writing an
               IANA Considerations Section in RFCs", BCP: 26, RFC 2434,
               October 1998.

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

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

  [RFC3635]   Flick, J., "Definitions of Managed Objects for the
               Ethernet-like Interface Types", RFC 3635, September
               2003.

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

  [PWMPLSMIB] Zelig, D., et al, ôPseudo Wire (PW) Over MPLS PSN
               Management Information Baseö, work-in-progress.

  [VPLS]      Anderson, L., Rosen E.L., et al, "L2VPN Framework",
               work-in-progress.

11 Author's Addresses

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

  Thomas D. Nadeau


  Zelig et al            Expires June 2003                 [page 25]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


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

12 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, 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.

13 Intellectual Property Notice

  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 [RFC2028].
  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 implementors 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 that may cover technology that may be required to practice


  Zelig et al            Expires June 2003                 [page 26]


                     Ethernet Pseudo Wire (PW)         February 2004
                    Management Information Base


  this standard.  Please address the information to the IETF Executive
  Director.



















































  Zelig et al            Expires June 2003                 [page 27]


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