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

Versions: 00 01 02 03 04 05 06 07 RFC 6767

Network Working Group                                           E. Beili
Internet-Draft                                          Actelis Networks
Intended status: Standards Track                          M. Morgenstern
Expires: December 7, 2007                                    ECI Telecom
                                                           June 05, 2007


      Ethernet-based xDSL multi-pair bonding (G.Bond/Ethernet) MIB
                draft-ietf-adslmib-gbond-eth-mib-00.txt

Status of This Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on December 7, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This document defines Management Information Base (MIB) module for
   use with network management protocols in TCP/IP based internets.
   This document proposes an extension to the G.Bond MIB module with a
   set of objects for managing Ethernet-based multi-pair bonded xDSL
   interfaces, defined in ITU-T recommendation G.998.2.





Beili & Morgenstern     Expires December 7, 2007                [Page 1]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  The Internet-Standard Management Framework . . . . . . . . . .  3
   3.  The DSL Forum Management Framework for xDSL Bonding  . . . . .  3
   4.  Relation to other MIB modules  . . . . . . . . . . . . . . . .  3
     4.1.  Relationship to Interfaces Group MIB module  . . . . . . .  4
     4.2.  Relationship to G.Bond MIB module  . . . . . . . . . . . .  4
     4.3.  Relationship to EFM Copper MIB module  . . . . . . . . . .  4
   5.  MIB Structure  . . . . . . . . . . . . . . . . . . . . . . . .  4
     5.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . .  4
       5.1.1.  TODO/Open Issues . . . . . . . . . . . . . . . . . . .  4
     5.2.  Mapping of IEEE 802.3 Managed Objects  . . . . . . . . . .  5
     5.3.  Mapping of DSL Forum WT-159 Managed Objects  . . . . . . .  5
   6.  G.Bond/Ethernet MIB Definitions  . . . . . . . . . . . . . . .  6
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 20
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 20
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 20
     10.2. Informative References . . . . . . . . . . . . . . . . . . 21






























Beili & Morgenstern     Expires December 7, 2007                [Page 2]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


1.  Introduction

   The Ethernet-based xDSL Multi-Pair Bonding, a.k.a.  G.Bond/Ethernet,
   is specified in ITU-T G.998.2 recommendation [G.998.2], which defines
   a method for bonding (or aggregating) of multiple xDSL lines into a
   single bi-directional logical link, carrying an Ethernet traffic.

   The MIB module, defined in this document, provides G.Bond/Ethernet
   specific objects for the management of G.998.2 bonded interfaces,
   extending the common bonding objects specified in GBOND-MIB
   [I-D.ietf-adslmib-gbond-mib] module.

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

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

3.  The DSL Forum Management Framework for xDSL Bonding

   This document makes use of the DSL Forum technical report Management
   Framework for xDSL Bonding [WT-159], defining a management model and
   a hierarchy of management objects for the bonded xDSL interfaces.

4.  Relation to other MIB modules

   This section outlines the relationship of the MIB modules defined in
   this document with other MIB modules described in the relevant RFCs.
   Specifically, the following MIB modules are discussed: Interfaces
   Group MIB (IF-MIB), G.Bond MIB (GBOND-MIB), and EFM Copper MIB (EFM-
   CU-MIB).







Beili & Morgenstern     Expires December 7, 2007                [Page 3]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


4.1.  Relationship to Interfaces Group MIB module

   A G.Bond/Ethernet port is a private case of a Bonded multi-pair xDSL
   interface and as such is managed using generic interface management
   objects defined in the IF-MIB [RFC2863].  In particular, an interface
   index (ifIndex) is used to index instances of G.Bond/Ethernet ports
   and channels in a managed system.

4.2.  Relationship to G.Bond MIB module

   GBOND-MIB [I-D.ietf-adslmib-gbond-mib] module defines management
   objects common for all Bonded multi-pair xDSL interfaces.  In
   particular it describes the bonding management, port and channel
   configuration, initialization sequence etc.

   Both GBOND-MIB and GBOND-ETH-MIB modules are REQUIRED to manage a
   G.Bond/Ethernet port.

4.3.  Relationship to EFM Copper MIB module

   EFM-CU-MIB [I-D.ietf-hubmib-efm-cu-mib] module defines objects for
   managing Ethernet in the First Mile Copper (EFMCu) interfaces
   10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3-2005 [802.3].
   These interfaces are based on Single-pair High-speed Digital
   Subscriber Line (SHDSL) [G.991.2] and Very High speed Digital
   Subscriber Line (VDSL) [G.993.1] technology respectively, and can be
   optionally aggregated (bonded).

   ITU-T G.998.2 specification extends the IEEE 802.3 Clause 61 bonding
   to work over any xDSL technology, providing the ability to bond
   individual channels as well as physical lines.

   EFM-CU-MIB can be used to manage all aspects of the EFMCu interfaces,
   including the management of SHDSL/VDSL lines.  GBOND-MIB and GBOND-
   ETH-MIB modules provide management objects only for the bonding part,
   leaving the management of the individual xDSL interfaces (lines/
   channels) to the respective xDSL MIB modules.

5.  MIB Structure

5.1.  Overview

   _EdNote: TBC... _

5.1.1.  TODO/Open Issues






Beili & Morgenstern     Expires December 7, 2007                [Page 4]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


   o  Peformance Monitoring counters

   o  Support for ITU-T draft BACP

5.2.  Mapping of IEEE 802.3 Managed Objects

   This section contains the mapping between relevant managed objects
   (attributes) defined in [802.3] and managed objects defined in this
   document.

           +----------------------+---------------------------+
           | 802.3 Managed Object | Corresponding SNMP Object |
           +----------------------+---------------------------+
           | oGroup               |                           |
           +----------------------+---------------------------+
           +----------------------+---------------------------+
           | TBC...               | TBC...                    |
           +----------------------+---------------------------+

                 Table 1: Mapping of 802.3 Managed Objects

   _EdNote: Finish the table and remove TBC... _

5.3.  Mapping of DSL Forum WT-159 Managed Objects

   This section contains the mapping between relevant managed objects
   (attributes) defined in [WT-159] and managed objects defined in this
   document.























Beili & Morgenstern     Expires December 7, 2007                [Page 5]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


     +---------------------------------+-----------------------------+
     | WT-159 Managed Object           | Corresponding SNMP Object   |
     +---------------------------------+-----------------------------+
     | oBondEth                        |                             |
     +---------------------------------+-----------------------------+
     | aEthTcAdminType                 | gBondEthTcAdminType         |
     +---------------------------------+-----------------------------+
     | aEthTcOperType                  | gBondEthTcOperType          |
     +---------------------------------+-----------------------------+
     | aEthTcTypesSupported            | gBondEthTcTypesSupported    |
     +---------------------------------+-----------------------------+
     | aEthRxErrors                    | gBondEthInErrors            |
     +---------------------------------+-----------------------------+
     | aEthRxSmallFragments            | gBondEthInSmallFragments    |
     +---------------------------------+-----------------------------+
     | aEthRxLargeFragments            | gBondEthInLargeFragments    |
     +---------------------------------+-----------------------------+
     | aEthRxBadFragments              | gBondEthInBadFragments      |
     +---------------------------------+-----------------------------+
     | aEthRxLostFragments             | gBondEthInLostFragments     |
     +---------------------------------+-----------------------------+
     | aEthRxLostStarts                | gBondEthInLostStarts        |
     +---------------------------------+-----------------------------+
     | aEthRxLostEnds                  | gBondEthInLostEnds          |
     +---------------------------------+-----------------------------+
     | aEthRxOverflows                 | gBondEthInOverflows         |
     +---------------------------------+-----------------------------+
     | oChannel                        |                             |
     +---------------------------------+-----------------------------+
     | aChannelPtmTcRxCodingViolations | gBondEthBceTcInCodingErrors |
     +---------------------------------+-----------------------------+
     | aChannelPtmTcRxCrcErrors        | gBondEthBceTcInCrcErrors    |
     +---------------------------------+-----------------------------+

                Table 2: Mapping of WT-159 Managed Objects

6.  G.Bond/Ethernet MIB Definitions

   GBOND-ETH-MIB DEFINITIONS ::= BEGIN

     IMPORTS
       MODULE-IDENTITY, OBJECT-TYPE, Counter32
         FROM SNMPv2-SMI         -- RFC 2578
       TEXTUAL-CONVENTION
         FROM SNMPv2-TC          -- RFC 2579
       MODULE-COMPLIANCE, OBJECT-GROUP
         FROM SNMPv2-CONF        -- RFC 2580
       ifIndex



Beili & Morgenstern     Expires December 7, 2007                [Page 6]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


         FROM IF-MIB             -- RFC 2863
       gBondMIB
         FROM GBOND-MIB          -- RFC YYYY
         -- EdNote: Replace YYYY with the actual RFC number &
         -- remove this note
       ;

     gBondEthMIB MODULE-IDENTITY
       LAST-UPDATED "200706050000Z"  -- June 05, 2007
       ORGANIZATION "IETF ADSL MIB Working Group"
       CONTACT-INFO
         "WG charter:
           http://www.ietf.org/html.charters/adslmib-charter.html

         Mailing Lists:
           General Discussion: adslmib@ietf.org
           To Subscribe: adslmib-request@ietf.org
           In Body: subscribe your_email_address

          Chair: Menachem Dodge
         Postal: ECI Telecom, Ltd.
                 30 Hasivim St.,
                 Petach-Tikva 49517
                 Israel
          Phone: +972-3-926-8421
          EMail: menachem.dodge@ecitele.com

         Editor: Edward Beili
         Postal: Actelis Networks, Inc.
                 25 Bazel St., P.O.B. 10173
                 Petach-Tikva 10173
                 Israel
          Phone: +972-3-924-3491
          EMail: edward.beili@actelis.com

         Editor: Moti Morgenstern
         Postal: ECI Telecom
                 30 Hasivim St.
                 Petach-Tikva 49517
                 Israel
          Phone: +972-3-926-6258
          EMail: moti.morgenstern@ecitele.com"

       DESCRIPTION
         "The objects in this MIB module are used to manage the
         Ethernet-based multi-pair bonded xDSL Interfaces, defined in
         ITU-T recommendation G.998.2 (G.Bond/Ethernet).




Beili & Morgenstern     Expires December 7, 2007                [Page 7]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


         This MIB module MUST be used in conjunction with GBOND-MIB
         module, common to all G.Bond technologies.

         The following references are used throughout this MIB module:

         [G.998.2] refers to:
           ITU-T Recommendation G.998.2: 'Ethernet-based multi-pair
           bonding', January 2005.

         [802.3] refers to:
           IEEE Std 802.3-2005: 'IEEE Standard for Information
           technology - Telecommunications and information exchange
           between systems - Local and metropolitan area networks -
           Specific requirements -
           Part 3: Carrier Sense Multiple Access with Collision
           Detection (CSMA/CD) Access Method and Physical Layer
           Specifications', December 2005.

         [WT-159] refers to:
           DSL Forum Technical Report: 'Management Framework for xDSL
           Bonding', May 2007.

         Naming Conventions:
           BCE    - Bonding Channel Entity
           CO     - Central Office
           CPE    - Customer Premises Equipment
           GBS    - Generic Bonding Sublayer
           HDLC   - High-level Data Link Control
           PTM-TC - Packet Transfer Mode Transmission Convergence
                    (sub-layer)
           SNR    - Signal to Noise Ratio
           TC     - Transmission Convergence (sub-layer)

         Copyright (C) The Internet Society (2007). This version of this
         MIB module is part of RFC XXXX;  see the RFC itself for full
         legal notices."

       REVISION    "200706050000Z"  -- June 05, 2007
       DESCRIPTION "Initial version, published as RFC XXXX."

         -- EdNote: Replace XXXX with the actual RFC number &
         -- remove this note

       ::= { gBondMIB 2 }

      -- Sections of the module
      -- Structured as recommended by RFC 4181, Appendix D




Beili & Morgenstern     Expires December 7, 2007                [Page 8]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


      gBondEthObjects     OBJECT IDENTIFIER ::= { gBondEthMIB 1 }

      gBondEthConformance OBJECT IDENTIFIER ::= { gBondEthMIB 2 }

      -- Groups in the module

      gBondEthPort        OBJECT IDENTIFIER ::= { gBondEthObjects 1 }

      gBondEthBce         OBJECT IDENTIFIER ::= { gBondEthObjects 2 }

      -- Textual Conventions

      GBondEthPtmTcType ::= TEXTUAL-CONVENTION
        STATUS       current
        DESCRIPTION
          "This textual convention represents possible PTM-TC types in
          G.bond/Eth ports. The following values are defined:
            tc6465         - 64/65-octet encapsulation, as defined in
                             [802.3] Clause 61.3.3
            tcHDLC         - HDLC encapsulation, as defined in [G.998.2]
                             Annex B"
        SYNTAX      INTEGER {
          tc6465(1),
          tcHDLC(2)
        }

      -- GBS Notifications group
        -- empty --

      -- GBS group

      gBondEthPortConfTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF GBondEthPortConfEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "Table for Configuration of G.Bond/Eth GBS ports. Entries in
          this table MUST be maintained in a persistent manner"
        ::= { gBondEthPort 1 }

      gBondEthPortConfEntry OBJECT-TYPE
        SYNTAX      GBondEthPortConfEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "An entry in the G.Bond/Eth Port Configuration table.
          Each entry represents an G.Bond Ethernet port indexed by the
          ifIndex.



Beili & Morgenstern     Expires December 7, 2007                [Page 9]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


          Note that an G.Bond/Eth GBS port runs on top of a single
          or multiple BCE port(s), which are also indexed by ifIndex."
        INDEX  { ifIndex }
        ::= { gBondEthPortConfTable 1 }

      GBondEthPortConfEntry ::=
        SEQUENCE {
          gBondEthTcAdminType         GBondEthPtmTcType
        }

      gBondEthTcAdminType  OBJECT-TYPE
        SYNTAX      GBondEthPtmTcType
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION
          "Administrative (desired) PTM-TC encapsulation type of
          G.Bond/Eth port (GBS).
          Possible values are:
            tc6465(1)  - 64/65-octet encapsulation
            tcHDLC(2)  - HDLC encapsulation
          Attempts to set a port to a non-supported PTM-TC encapsulation
          type (see gBondEthTcTypesSupported) SHALL be rejected.

          Changing gBondEthTcAdminType is a traffic disruptive
          operation and as such SHALL be done when the link is Down.
          Attempts to cange this object SHALL be rejected if the link
          is Up or Initializing.

          This object maps to the WT-159 attribute aEthTcAdminType.

          This object MUST be maintained in a persistent manner."
        REFERENCE
          "[WT-159] 5.5.3.1"
        ::= { gBondEthPortConfEntry 1 }


      gBondEthPortCapabilityTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF GBondEthPortCapabilityEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "Table for Capabilities of G.Bond/Eth Ports. Entries in this
          table MUST be maintained in a persistent manner"
        ::= { gBondEthPort 2 }

      gBondEthPortCapabilityEntry OBJECT-TYPE
        SYNTAX      GBondEthPortCapabilityEntry
        MAX-ACCESS  not-accessible



Beili & Morgenstern     Expires December 7, 2007               [Page 10]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


        STATUS      current
        DESCRIPTION
          "An entry in the G.Bond/Eth Port Capability table.
          Each entry represents an G.Bond port indexed by the ifIndex.
          Note that a G.Bond GBS port runs on top of a single
          or multiple BCE port(s), which are also indexed by ifIndex."
        INDEX  { ifIndex }
        ::= { gBondEthPortCapabilityTable 1 }

      GBondEthPortCapabilityEntry ::=
        SEQUENCE {
          gBondEthTcTypesSupported         BITS
        }

      gBondEthTcTypesSupported  OBJECT-TYPE
        SYNTAX      BITS {
          tc6465(0),
          tcHDLC(1)
        }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "PTM-TC Encapsulation types supported by the G.Bond/Eth port.
          This is a bitmap of possible encapsulation types. The various
          bit positions are:
            tc6465   - GBS is capable of 64/65-octet encapsulation
            tcHDLC   - GBS is capable of HDLC encapsulation

          A desired encapsulation is determined by
          gBondEthTcAdminType, while gBondEthTcOperType reflects the
          current operating mode.

          This object maps to the WT-159 attribute
          aEthTcTypesSupported."
        REFERENCE
          "[WT-159] 5.5.3.3"
        ::= { gBondEthPortCapabilityEntry 1 }


      gBondEthPortStatusTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF GBondEthPortStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table provides overall status information of G.Bond
          ports, complementing the generic status information from the
          ifTable of IF-MIB. Additional status information about
          connected BCEs is available from the relevant line MIBs



Beili & Morgenstern     Expires December 7, 2007               [Page 11]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


          This table contains live data from the equipment. As such,
          it is NOT persistent."
        ::= { gBondEthPort 3 }

      gBondEthPortStatusEntry OBJECT-TYPE
        SYNTAX      GBondEthPortStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "An entry in the G.Bond/Eth Port Status table.
          Each entry represents an G.Bond/Eth port indexed by the
          ifIndex.
          Note that an G.Bond GBS port runs on top of a single
          or multiple BCE port(s), which are also indexed by ifIndex."
        INDEX  { ifIndex }
        ::= { gBondEthPortStatusTable 1 }

      GBondEthPortStatusEntry ::=
        SEQUENCE {
          gBondEthTcOperType            GBondEthPtmTcType,
          gBondEthInErrors              Counter32,
          gBondEthInSmallFragments      Counter32,
          gBondEthInLargeFragments      Counter32,
          gBondEthInBadFragments        Counter32,
          gBondEthInLostFragments       Counter32,
          gBondEthInLostStarts          Counter32,
          gBondEthInLostEnds            Counter32,
          gBondEthInOverflows           Counter32
        }

      gBondEthTcOperType  OBJECT-TYPE
        SYNTAX      GBondEthPtmTcType
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "Current operational encapsulation type of the G.Bond/Eth
          port.
          Possible values are:
            tc6465(1)   - GBS uses 64/65-octet encapsulation
            tcHDLC(2)   - GBS uses HDLC encapsulation

          The operational PTM-TC encapsulation type can be configured
          via gBondEthTcAdminType variable.

          This objects maps to the WT-159 aEthTcOperType."
        REFERENCE
          "[WT-159] 5.5.3.2"
        ::= { gBondEthPortStatusEntry 1 }



Beili & Morgenstern     Expires December 7, 2007               [Page 12]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


      gBondEthInErrors OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of fragments that have been received across the
          gamma interface and discarded.

          This object maps to the WT-159 attribute aEthRxErrors.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.4"
        ::= { gBondEthPortStatusEntry 2 }

      gBondEthInSmallFragments OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of fragments smaller than minFragmentSize
          (64 Bytes), that have been received across the gamma
          interface and discarded.

          This object maps to the WT-159 attribute aEthRxSmallFragments.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.5"
        ::= { gBondEthPortStatusEntry 3 }

      gBondEthInLargeFragments OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of fragments larger than maxFragmentSize
          (512 Bytes), which have been received across the gamma
          interface and discarded.

          This object maps to the WT-159 attribute aEthRxLargeFragments.




Beili & Morgenstern     Expires December 7, 2007               [Page 13]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.6"
        ::= { gBondEthPortStatusEntry 4 }

      gBondEthInBadFragments OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of fragments which do not fit into the sequence
          expected by the frame assembly function, that have been
          received across the gamma interface and discarded (the
          frame buffer is flushed to the next valid frame start).

          This object maps to the WT-159 attribute aEthRxBadFragments.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.7"
        ::= { gBondEthPortStatusEntry 5 }

      gBondEthInLostFragments OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of gaps in the sequence of fragments, which have
          been received across the gamma interface (the frame buffer is
          flushed to the next valid frame start, when fragment/fragments
          expected by the frame assembly function is/are not received).

          This object maps to the WT-159 attribute aEthRxLostFragments.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.8"
        ::= { gBondEthPortStatusEntry 6 }




Beili & Morgenstern     Expires December 7, 2007               [Page 14]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


      gBondEthInLostStarts OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of missing StartOfPacket indicators expected by the
          frame assembly function.

          This object maps to the WT-159 attribute aEthRxLostStarts.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.9"
        ::= { gBondEthPortStatusEntry 7 }

      gBondEthInLostEnds OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of missing EndOfPacket indicators expected by the
          frame assembly function.

          This object maps to the WT-159 attribute aEthRxLostEnds.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.10"
        ::= { gBondEthPortStatusEntry 8 }

      gBondEthInOverflows OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of fragments, received across the gamma interface
          and discarded, which would have caused the frame assembly
          buffer to overflow.

          This object maps to the WT-159 attribute aEthRxOverflows.

          Discontinuities in the value of this counter can occur at



Beili & Morgenstern     Expires December 7, 2007               [Page 15]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.3.11"
        ::= { gBondEthPortStatusEntry 9 }

     -- BCE group

      gBondEthBceStatusTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF GBondEthBceStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "This table provides common status information of G.Bond/Eth
          BCE ports.

          This table contains live data from the equipment. As such,
          it is NOT persistent."
        ::= { gBondEthBce 1 }

      gBondEthBceStatusEntry OBJECT-TYPE
        SYNTAX      GBondEthBceStatusEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
          "An entry in the G.Bond/Eth BCE Status table.
          Each entry represents common aspects of a G.Bond/Eth BCE port
          indexed by the ifIndex. Note that a BCE port can be stacked
          below a single GBS port, also indexed by ifIndex,
          possibly together with other BCE ports."
        INDEX  { ifIndex }
        ::= { gBondEthBceStatusTable 1 }

      GBondEthBceStatusEntry ::=
        SEQUENCE {
          gBondEthBceTcInCodingErrors        Counter32,
          gBondEthBceTcInCrcErrors           Counter32
        }

      gBondEthBceTcInCodingErrors OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of PTM-TC encapsulation errors. This counter is
          incremented for each encapsulation error detected by the
          PTM-TC receive function.



Beili & Morgenstern     Expires December 7, 2007               [Page 16]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


          This object maps to WT-159 attribute
          aChannelPtmTcRxCodingViolations.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.7.5"
        ::= { gBondEthBceStatusEntry 1 }

      gBondEthBceTcInCrcErrors OBJECT-TYPE
        SYNTAX      Counter32
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "A number of PTM-TC CRC errors. This counter is incremented
          for each CRC error detected by the PTM-TC receive function.

          This object maps to WT-159 attribute aChannelPtmTcRxCrcErrors.

          Discontinuities in the value of this counter can occur at
          re-initialization of the management system, and at other times
          as indicated by the value of ifCounterDiscontinuityTime,
          defined in IF-MIB."
        REFERENCE
          "[WT-159] 5.5.7.6"
        ::= { gBondEthBceStatusEntry 2 }


     --
     -- Conformance Statements
     --

      gBondEthGroups      OBJECT IDENTIFIER
        ::= { gBondEthConformance 1 }

      gBondEthCompliances OBJECT IDENTIFIER
        ::= { gBondEthConformance 2 }

      -- Object Groups

      gBondEthBasicGroup OBJECT-GROUP
        OBJECTS {
          gBondEthTcTypesSupported,
          gBondEthTcAdminType,
          gBondEthTcOperType,
          gBondEthInErrors,



Beili & Morgenstern     Expires December 7, 2007               [Page 17]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


          gBondEthInSmallFragments,
          gBondEthInLargeFragments,
          gBondEthInBadFragments,
          gBondEthInLostFragments,
          gBondEthInLostStarts,
          gBondEthInLostEnds,
          gBondEthInOverflows,
          gBondEthBceTcInCodingErrors,
          gBondEthBceTcInCrcErrors
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects representing management information
          for G.Bond/Eth GBS ports."
        ::= { gBondEthGroups 1 }

      gBondEthBceGroup OBJECT-GROUP
        OBJECTS {
          gBondEthBceTcInCodingErrors,
          gBondEthBceTcInCrcErrors
        }
        STATUS      current
        DESCRIPTION
          "A collection of objects representing OPTIONAL management
          information for G.Bond/Eth BCE ports."
        ::= { gBondEthGroups 2 }

     -- Compliance Statements

      gBondEthCompliance MODULE-COMPLIANCE
        STATUS      current
        DESCRIPTION
          "The compliance statement for G.Bond Ethernet interfaces.
          Compliance with the following external compliance statements
          is REQUIRED:

          MIB Module             Compliance Statement
          ----------             --------------------
          IF-MIB                 ifCompliance3
          GBOND-MIB              gBondCompliance"

        MODULE  -- this module
          MANDATORY-GROUPS {
            gBondEthBasicGroup
          }

          GROUP       gBondEthBceGroup
          DESCRIPTION



Beili & Morgenstern     Expires December 7, 2007               [Page 18]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


            "Support for this group is OPTIONAL"

          OBJECT      gBondEthTcTypesSupported
          SYNTAX      BITS {
            tc6465(0),
            tcHDLC(1)
          }
          DESCRIPTION
            "Support for all TC types is not required. However at least
            one value SHALL be supported"

          OBJECT      gBondEthTcAdminType
          MIN-ACCESS  read-only
          DESCRIPTION
            "Write access is not required (needed only for GBS
            supporting more than a single TC encapsulation type, i.e.
            tc6465 and tcHDLC"

        ::= { gBondEthCompliances 1 }
   END

7.  Security Considerations

   There is a number of managed objects defined in the GBOND-ETH-MIB
   module that have a MAX-ACCESS clause of read-write or read-create.
   Writing to these objects can have potentially disruptive effects on
   network operation, for example:

   o  Changing of gBondEthPortConfTable configuration paratemers (e.g.
      gBondEthTcAdminType) MAY lead to a complete service interruption,
      in case the specified PTM-TC encapsulation type is not supported
      by the remote end.

   The user of the GBOND-ETH-MIB module must therefore be aware that
   support for SET operations in a non-secure environment without proper
   protection can have a negative effect on network operations.

   The readable objects in the GBOND-ETH-MIB module (i.e., those with
   MAX-ACCESS other than not-accessible) may be considered sensitive in
   some environments since, collectively, they provide information about
   the performance of network interfaces and can reveal some aspects of
   their configuration.

   In such environments it is important to control also GET and NOTIFY
   access to these objects and possibly even to encrypt their values
   when sending them over the network via SNMP.

   SNMP versions prior to SNMPv3 did not include adequate security.



Beili & Morgenstern     Expires December 7, 2007               [Page 19]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


   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.

   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.

8.  IANA Considerations

   A new IANAifType value of g9982 SHALL be defined by the IANA [1] in
   the IANAifType-MIB module [IANAifType-MIB], before this document is
   published as an RFC.

9.  Acknowledgments

   This document was produced by the IETF ADSL MIB Working Group [2].

10.  References

10.1.  Normative References

   [802.3]                       IEEE, "IEEE Standard for Information
                                 technology - Telecommunications and
                                 information exchange between systems -
                                 Local and metropolitan area networks -
                                 Specific requirements - Part 3: Carrier
                                 Sense Multiple Access with Collision
                                 Detection (CSMA/CD) Access Method and
                                 Physical Layer Specifications", IEEE
                                 Std 802.3-2005, December 2005.

   [G.998.2]                     ITU-T, "Ethernet-based multi-pair
                                 bonding", ITU-T Recommendation G.998.2,
                                 January 2005.

   [RFC2119]                     Bradner, S., "Key words for use in RFCs
                                 to Indicate Requirement Levels",



Beili & Morgenstern     Expires December 7, 2007               [Page 20]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


                                 BCP 14, RFC 2119, March 1997.

   [RFC2578]                     McCloghrie, K., Ed., Perkins, D., Ed.,
                                 and J. Schoenwaelder, Ed., "Structure
                                 of Management Information Version 2
                                 (SMIv2)", STD 58, RFC 2578, April 1999.

   [RFC2579]                     McCloghrie, K., Ed., Perkins, D., Ed.,
                                 and J. Schoenwaelder, Ed., "Textual
                                 Conventions for SMIv2", STD 58,
                                 RFC 2579, April 1999.

   [RFC2580]                     McCloghrie, K., Perkins, D., and J.
                                 Schoenwaelder, "Conformance Statements
                                 for SMIv2", STD 58, RFC 2580,
                                 April 1999.

   [RFC3410]                     Case, J., Mundy, R., Partain, D., and
                                 B. Stewart, "Introduction and
                                 Applicability Statements for Internet-
                                 Standard Management Framework",
                                 RFC 3410, December 2002.

   [WT-159]                      Morgenstern, M., Beili, E., and N.
                                 Nair, "Management Framework for xDSL
                                 Bonding", DSL Forum technical
                                 report WT-159, May 2007.

10.2.  Informative References

   [G.991.2]                     ITU-T, "Single-pair High-speed Digital
                                 Subscriber Line (SHDSL) transceivers",
                                 ITU-T Recommendation G.991.2,
                                 December 2003.

   [G.993.1]                     ITU-T, "Very High speed Digital
                                 Subscriber Line transceivers", ITU-T
                                 Recommendation G.993.1, June 2004.

   [I-D.ietf-adslmib-gbond-mib]  Beili, E., Morgenstern, M., and N.
                                 Nair, "xDSL multi-pair bonding (G.Bond)
                                 MIB", draft-ietf-adslmib-gbond-mib-00
                                 (work in progress), February 2007.

   [I-D.ietf-hubmib-efm-cu-mib]  Beili, E., "Ethernet in the First Mile
                                 Copper (EFMCu) Interfaces MIB",
                                 draft-ietf-hubmib-efm-cu-mib-07.txt
                                 (work in progress), February 2007.



Beili & Morgenstern     Expires December 7, 2007               [Page 21]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


   [IANAifType-MIB]              Internet Assigned Numbers Authority
                                 (IANA), "IANAifType Textual Convention
                                 definition",  http://www.iana.org/
                                 assignments/ianaiftype-mib.

   [RFC2863]                     McCloghrie, K. and F. Kastenholz, "The
                                 Interfaces Group MIB", RFC 2863,
                                 June 2000.

   [RFC4836]                     Beili, E., "Definitions of Managed
                                 Objects for IEEE 802.3 Medium
                                 Attachment Units (MAUs)", RFC 4836,
                                 April 2007.

URIs

   [1]  <http://www.iana.org/>

   [2]  <http://www.ietf.org/html.charters/adslmib-charter.html>

Authors' Addresses

   Edward Beili
   Actelis Networks
   25 Bazel St.
   Petach-Tikva  49103
   Israel

   Phone: +972-3-924-3491
   EMail: edward.beili@actelis.com


   Moti Morgenstern
   ECI Telecom
   30 Hasivim St.
   Petach-Tikva  49517
   Israel

   Phone: +972-3-926-6258
   EMail: moti.morgenstern@ecitele.com











Beili & Morgenstern     Expires December 7, 2007               [Page 22]

Internet-Draft             G.Bond/Ethernet MIB                 June 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.

Acknowledgement

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).







Beili & Morgenstern     Expires December 7, 2007               [Page 23]


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