tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

RFC 5650

 
 
 

Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2)

Part 10 of 10, p. 197 to 218
Prev RFC Part

 


prevText      Top      Up      ToC       Page 197 
   xdsl2ChConfProfileAtmGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2ChConfProfImaEnabled,
          xdsl2ChStatusAtmStatus
          }
      STATUS     current
      DESCRIPTION
         "The group of configuration objects required when the data
          path is ATM."
      ::= { xdsl2Groups 17 }

   xdsl2ChConfProfileMinResGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2ChConfProfMinResDataRateDs,
          xdsl2ChConfProfMinResDataRateUs
          }
      STATUS     current
      DESCRIPTION
         "The group of configuration objects required for the
          reserved data rate."
      ::= { xdsl2Groups 18 }
   xdsl2ChConfProfileOptAttrGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2ChConfProfMaxDelayVar,
          xdsl2ChConfProfInitPolicy
          }
      STATUS     current
      DESCRIPTION
         "The group of various optional channel configuration
          parameters."
      ::= { xdsl2Groups 19 }

   xdsl2LineAlarmConfTemplateGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2LAlarmConfTempLineProfile,
          xdsl2LAlarmConfTempChan1ConfProfile,
          xdsl2LAlarmConfTempChan2ConfProfile,
          xdsl2LAlarmConfTempChan3ConfProfile,
          xdsl2LAlarmConfTempChan4ConfProfile,
          xdsl2LAlarmConfTempRowStatus
          }
      STATUS     current
      DESCRIPTION
         "The group of objects in a line alarm template."

Top      Up      ToC       Page 198 
      ::= { xdsl2Groups 20 }

   xdsl2LineAlarmConfProfileGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2LineAlarmConfProfileXtucThresh15MinFecs,
          xdsl2LineAlarmConfProfileXtucThresh15MinEs,
          xdsl2LineAlarmConfProfileXtucThresh15MinSes,
          xdsl2LineAlarmConfProfileXtucThresh15MinLoss,
          xdsl2LineAlarmConfProfileXtucThresh15MinUas,
          xdsl2LineAlarmConfProfileXturThresh15MinFecs,
          xdsl2LineAlarmConfProfileXturThresh15MinEs,
          xdsl2LineAlarmConfProfileXturThresh15MinSes,
          xdsl2LineAlarmConfProfileXturThresh15MinLoss,
          xdsl2LineAlarmConfProfileXturThresh15MinUas,
          xdsl2LineAlarmConfProfileThresh15MinFailedFullInt,
          xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt,
          xdsl2LineAlarmConfProfileRowStatus
          }
      STATUS     current
      DESCRIPTION
         "The group of objects in a line alarm profile."
      ::= { xdsl2Groups 21 }

   xdsl2ChAlarmConfProfileGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations,
          xdsl2ChAlarmConfProfileXtucThresh15MinCorrected,
          xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations,
          xdsl2ChAlarmConfProfileXturThresh15MinCorrected,
          xdsl2ChAlarmConfProfileRowStatus
          }
      STATUS     current
      DESCRIPTION
         "The group of objects in a channel alarm profile."
      ::= { xdsl2Groups 22 }

   xdsl2PMLineCurrGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLCurr15MValidIntervals,
          xdsl2PMLCurr15MInvalidIntervals,
          xdsl2PMLCurr15MTimeElapsed,
          xdsl2PMLCurr15MFecs,
          xdsl2PMLCurr15MEs,
          xdsl2PMLCurr15MSes,
          xdsl2PMLCurr15MLoss,

Top      Up      ToC       Page 199 
          xdsl2PMLCurr15MUas,
          xdsl2PMLCurr1DayValidIntervals,
          xdsl2PMLCurr1DayInvalidIntervals,
          xdsl2PMLCurr1DayTimeElapsed,
          xdsl2PMLCurr1DayFecs,
          xdsl2PMLCurr1DayEs,
          xdsl2PMLCurr1DaySes,
          xdsl2PMLCurr1DayLoss,
          xdsl2PMLCurr1DayUas
          }
      STATUS     current
      DESCRIPTION
         "The group of objects that report the line-level
          counters for current PM intervals."
      ::= { xdsl2Groups 23 }

   xdsl2PMLineInitCurrGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLInitCurr15MValidIntervals,
          xdsl2PMLInitCurr15MInvalidIntervals,
          xdsl2PMLInitCurr15MTimeElapsed,
          xdsl2PMLInitCurr15MFullInits,
          xdsl2PMLInitCurr15MFailedFullInits,
          xdsl2PMLInitCurr1DayValidIntervals,
          xdsl2PMLInitCurr1DayInvalidIntervals,
          xdsl2PMLInitCurr1DayTimeElapsed,
          xdsl2PMLInitCurr1DayFullInits,
          xdsl2PMLInitCurr1DayFailedFullInits
          }
      STATUS     current
      DESCRIPTION
         "The group of objects that report the full
          initialization counters for current PM intervals."
      ::= { xdsl2Groups 24 }

   xdsl2PMLineInitCurrShortGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLInitCurr15MShortInits,
          xdsl2PMLInitCurr15MFailedShortInits,
          xdsl2PMLInitCurr1DayShortInits,
          xdsl2PMLInitCurr1DayFailedShortInits
          }
      STATUS     current
      DESCRIPTION
         "The group of objects that report the short
          initialization counters for current PM intervals."

Top      Up      ToC       Page 200 
      ::= { xdsl2Groups 25 }

   xdsl2PMLineHist15MinGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLHist15MMonitoredTime,
          xdsl2PMLHist15MFecs,
          xdsl2PMLHist15MEs,
          xdsl2PMLHist15MSes,
          xdsl2PMLHist15MLoss,
          xdsl2PMLHist15MUas,
          xdsl2PMLHist15MValidInterval
          }
      STATUS     current
      DESCRIPTION
         "The group of line-level PM counters for the previous
          15-minute intervals."
      ::= { xdsl2Groups 26 }

   xdsl2PMLineHist1DayGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLHist1DMonitoredTime,
          xdsl2PMLHist1DFecs,
          xdsl2PMLHist1DEs,
          xdsl2PMLHist1DSes,
          xdsl2PMLHist1DLoss,
          xdsl2PMLHist1DUas,
          xdsl2PMLHist1DValidInterval
          }
      STATUS     current
      DESCRIPTION
         "The group of line-level PM counters for the previous
          24-hour intervals."
      ::= { xdsl2Groups 27 }

   xdsl2PMLineInitHist15MinGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLInitHist15MMonitoredTime,
          xdsl2PMLInitHist15MFullInits,
          xdsl2PMLInitHist15MFailedFullInits,
          xdsl2PMLInitHist15MValidInterval
          }
      STATUS     current
      DESCRIPTION
         "The group of PM counters for the previous 15-minute
          interval full initializations."

Top      Up      ToC       Page 201 
      ::= { xdsl2Groups 28 }

   xdsl2PMLineInitHist15MinShortGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLInitHist15MShortInits,
          xdsl2PMLInitHist15MFailedShortInits
          }
      STATUS     current
      DESCRIPTION
         "The group of PM counters for the previous 15-minute
          interval short initializations."
      ::= { xdsl2Groups 29 }

   xdsl2PMLineInitHist1DayGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLInitHist1DMonitoredTime,
          xdsl2PMLInitHist1DFullInits,
          xdsl2PMLInitHist1DFailedFullInits,
          xdsl2PMLInitHist1DValidInterval
          }
      STATUS     current
      DESCRIPTION
         "The group of PM counters for the previous 24-hour
          interval full initializations."
      ::= { xdsl2Groups 30 }

   xdsl2PMLineInitHist1DayShortGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMLInitHist1DShortInits,
          xdsl2PMLInitHist1DFailedShortInits
          }
      STATUS     current
      DESCRIPTION
         "The group of PM counters for the previous 24-hour
          interval short initializations."
      ::= { xdsl2Groups 31 }

   xdsl2PMChCurrGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMChCurr15MValidIntervals,
          xdsl2PMChCurr15MInvalidIntervals,
          xdsl2PMChCurr15MTimeElapsed,
          xdsl2PMChCurr15MCodingViolations,
          xdsl2PMChCurr15MCorrectedBlocks,

Top      Up      ToC       Page 202 
          xdsl2PMChCurr1DayValidIntervals,
          xdsl2PMChCurr1DayInvalidIntervals,
          xdsl2PMChCurr1DayTimeElapsed,
          xdsl2PMChCurr1DayCodingViolations,
          xdsl2PMChCurr1DayCorrectedBlocks
          }
      STATUS     current
      DESCRIPTION
         "The group of objects that report the channel-level
          counters for current PM intervals."
      ::= { xdsl2Groups 32 }

   xdsl2PMChHist15MinGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMChHist15MMonitoredTime,
          xdsl2PMChHist15MCodingViolations,
          xdsl2PMChHist15MCorrectedBlocks,
          xdsl2PMChHist15MValidInterval
          }
      STATUS     current
      DESCRIPTION
         "The group of objects that report the channel-level
          counters for previous 15-minute PM intervals."
      ::= { xdsl2Groups 33 }

   xdsl2PMChHist1DGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2PMChHist1DMonitoredTime,
          xdsl2PMChHist1DCodingViolations,
          xdsl2PMChHist1DCorrectedBlocks,
          xdsl2PMChHist1DValidInterval
          }
      STATUS     current
      DESCRIPTION
        "The group of objects that report the channel-level
        counters for previous 24-hour PM intervals."
      ::= { xdsl2Groups 34 }

   xdsl2ScalarSCGroup OBJECT-GROUP
      OBJECTS
          {
          xdsl2ScalarSCMaxInterfaces,
          xdsl2ScalarSCAvailInterfaces
          }
      STATUS     current
      DESCRIPTION

Top      Up      ToC       Page 203 
         "The group of objects that report the available memory
          resources for DELT processes."
      ::= { xdsl2Groups 35 }

   xdsl2ThreshNotificationGroup NOTIFICATION-GROUP
      NOTIFICATIONS
      {
      xdsl2LinePerfFECSThreshXtuc,
      xdsl2LinePerfFECSThreshXtur,
      xdsl2LinePerfESThreshXtuc,
      xdsl2LinePerfESThreshXtur,
      xdsl2LinePerfSESThreshXtuc,
      xdsl2LinePerfSESThreshXtur,
      xdsl2LinePerfLOSSThreshXtuc,
      xdsl2LinePerfLOSSThreshXtur,
      xdsl2LinePerfUASThreshXtuc,
      xdsl2LinePerfUASThreshXtur,
      xdsl2LinePerfCodingViolationsThreshXtuc,
      xdsl2LinePerfCodingViolationsThreshXtur,
      xdsl2LinePerfCorrectedThreshXtuc,
      xdsl2LinePerfCorrectedThreshXtur,
      xdsl2LinePerfFailedFullInitThresh,
      xdsl2LinePerfFailedShortInitThresh
      }
      STATUS      current
      DESCRIPTION
         "This group supports notifications of significant
          conditions associated with DSL lines."
      ::= { xdsl2Groups 36 }

   xdsl2StatusChangeNotificationGroup NOTIFICATION-GROUP
      NOTIFICATIONS
      {
      xdsl2LineStatusChangeXtuc,
      xdsl2LineStatusChangeXtur
      }
      STATUS      current
      DESCRIPTION
         "This group supports notifications of thresholds crossing
          associated with DSL lines."
      ::= { xdsl2Groups 37 }

END

4.  Implementation Analysis

   A management application intended to manage ADSL links (e.g.,
   G.992.1) with this MIB module MUST be modified to adapt itself to

Top      Up      ToC       Page 204 
   certain differences between RFC 2662 [RFC2662] and this MIB module,
   including the following aspects:

   o  Though the configuration templates/profiles allow referring to 1-4
      bearer channels, ADSL links are limited to two channels at most.

   o  Though the channel configuration profile allows higher data rates,
      ADSL links are limited to downstream/upstream data rate as assumed
      in RFC 2662 [RFC2662].

   o  The Impulse Noise Protection (INP) configuration parameters are
      given by minimum protection and maximum delay parameters.

   o  The line configuration profile includes a sub-table that addresses
      mode-specific parameters.  For ADSL links, the management
      application SHOULD create a row in that table for the ADSL modes
      only.

   o  The line configuration profile includes parameters that are
      irrelevant for ADSL links.  Similarly, many status parameters in
      the MIB are irrelevant for certain ADSL modes.  Therefore, it is
      advised to consult with ITU G.997.1 standard [G.997.1] regarding
      the scope and relevance of each parameter in this MIB.

5.  Security Considerations

   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

Top      Up      ToC       Page 205 
   environment without proper protection can have a negative effect on
   network operations.  These are the tables and objects and their
   sensitivity/vulnerability:

   o  xdsl2LineTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2LineConfTemplate

      *  xdsl2LineConfFallbackTemplate

      *  xdsl2LineAlarmConfTemplate

      *  xdsl2LineCmndConfPmsf

      *  xdsl2LineCmndConfLdsf

      *  xdsl2LineCmndConfBpsc

      *  xdsl2LineCmndAutomodeColdStart

      *  xdsl2LineCmndConfReset


      Unauthorized changes to xdsl2LineConfTemplate could have a major
      adverse operational effect on many lines simultaneously.

      Unauthorized changes to xdsl2LineConfFallbackTemplate could have a
      major adverse operational effect on many lines simultaneously.

      Unauthorized changes to xdsl2LineAlarmConfTemplate could have a
      contrary effect on notifications.

      Unauthorized changes to xdsl2LineCmndConfPmsf could have an
      adverse affect on the power consumption of a line and may disrupt
      an operational service.

      Unauthorized changes to xdsl2LineCmndConfLdsf could cause an
      unscheduled line test to be carried out on the line.

      Unauthorized changes to xdsl2LineCmndConfBpsc could cause an
      unscheduled bits-per-subcarrier measurement to be carried out on
      the line.

      Unauthorized changes to xdsl2LineCmndAutomodeColdStart could cause
      an unscheduled cold reset to the line.

Top      Up      ToC       Page 206 
      Unauthorized changes to xdsl2LineCmndConfReset could cause a
      unscheduled retrain of a line.

   o  xdsl2LineSegmentTable

      This table contains one object, xdsl2LineSegmentRowStatus, that
      supports SET operations.  Unauthorized changes could result in
      measurement results being deleted prematurely.

   o  xdsl2SCStatusTable

      This table contains one object, xdsl2SCStatusRowStatus, that
      supports SET operations.  Unauthorized changes could result in
      line test results being deleted prematurely.


   o  xdsl2LineConfTemplateTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2LConfTempLineProfile

      *  xdsl2LConfTempChan1ConfProfile

      *  xdsl2LConfTempChan1RaRatioDs

      *  xdsl2LConfTempChan1RaRatioUs

      *  xdsl2LConfTempChan2ConfProfile

      *  xdsl2LConfTempChan2RaRatioDs

      *  xdsl2LConfTempChan2RaRatioUs

      *  xdsl2LConfTempChan3ConfProfile

      *  xdsl2LConfTempChan3RaRatioDs

      *  xdsl2LConfTempChan3RaRatioUs

      *  xdsl2LConfTempChan4ConfProfile

      *  xdsl2LConfTempChan4RaRatioDs

      *  xdsl2LConfTempChan4RaRatioUs

      *  xdsl2LConfTempRowStatus

Top      Up      ToC       Page 207 
      Unauthorized changes to xdsl2LConfTempLineProfile,
      xdsl2LConfTempChan1ConfProfile, xdsl2LConfTempChan2ConfProfile,
      xdsl2LConfTempChan3ConfProfile, or xdsl2LConfTempChan4ConfProfile
      could have an adverse operational effect on several lines; could
      change several lines over to running in unwanted levels of
      operation; or could result in several services undergoing changes
      in the number of channels that carry the service.

      Unauthorized changes to xdsl2LConfTempChan1RaRatioDs,
      xdsl2LConfTempChan2RaRatioDs, xdsl2LConfTempChan3RaRatioDs, or
      xdsl2LConfTempChan4RaRatioDs would alter the relative rate
      allocations among all channels belonging to a line.  This could
      have an adverse operational effect on several lines.

      Unauthorized changes to xdsl2LConfTempRowStatus could result in
      templates being created or brought into service prematurely, or
      they could result in templates being inadvertently deleted or
      taken out of service.

   o  xdsl2LineConfProfTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2LConfProfScMaskDs

      *  xdsl2LConfProfScMaskUs

      *  xdsl2LConfProfRfiBandsDs

      *  xdsl2LConfProfRaModeDs

      *  xdsl2LConfProfRaModeUs

      *  xdsl2LConfProfRaUsNrmDs

      *  xdsl2LConfProfRaUsNrmUs

      *  xdsl2LConfProfRaUsTimeDs

      *  xdsl2LConfProfRaUsTimeUs

      *  xdsl2LConfProfRaDsNrmDs

      *  xdsl2LConfProfRaDsNrmUs

      *  xdsl2LConfProfRaDsTimeDs

Top      Up      ToC       Page 208 
      *  xdsl2LConfProfRaDsTimeUs

      *  xdsl2LConfProfTargetSnrmDs

      *  xdsl2LConfProfTargetSnrmUs

      *  xdsl2LConfProfMaxSnrmDs

      *  xdsl2LConfProfMaxSnrmUs

      *  xdsl2LConfProfMinSnrmDs

      *  xdsl2LConfProfMinSnrmUs

      *  xdsl2LConfProfMsgMinUs

      *  xdsl2LConfProfMsgMinDs

      *  xdsl2LConfProfCeFlag

      *  xdsl2LConfProfSnrModeDs

      *  xdsl2LConfProfSnrModeUs

      *  xdsl2LConfProfTxRefVnDs

      *  xdsl2LConfProfTxRefVnUs

      *  xdsl2LConfProfXtuTransSysEna

      *  xdsl2LConfProfPmMode

      *  xdsl2LConfProfL0Time

      *  xdsl2LConfProfL2Time

      *  xdsl2LConfProfL2Atpr

      *  xdsl2LConfProfL2Atprt

      *  xdsl2LConfProfProfiles

      *  xdsl2LConfProfDpboEPsd

      *  xdsl2LConfProfDpboEsEL

      *  xdsl2LConfProfDpboEsCableModelA

Top      Up      ToC       Page 209 
      *  xdsl2LConfProfDpboEsCableModelB

      *  xdsl2LConfProfDpboEsCableModelC

      *  xdsl2LConfProfDpboMus

      *  xdsl2LConfProfDpboFMin

      *  xdsl2LConfProfDpboFMax

      *  xdsl2LConfProfUpboKL

      *  xdsl2LConfProfUpboKLF

      *  xdsl2LConfProfUs0Mask

      *  xdsl2LConfProfForceInp

      *  xdsl2LConfProfRowStatus

      Unauthorized changes resulting in the setting of any of the above
      objects to an incorrect value could have an adverse operational
      effect on several lines.

      Also, unauthorized changes to xdsl2LConfProfRowStatus could result
      in unwanted line profiles being created or brought into service
      prematurely, or they could result in line profiles being
      inadvertently deleted or taken out of service.

   o  xdsl2LineConfProfModeSpecTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2LConfProfMaxNomPsdDs

      *  xdsl2LConfProfMaxNomPsdUs

      *  xdsl2LConfProfMaxNomAtpDs

      *  xdsl2LConfProfMaxNomAtpUs

      *  xdsl2LConfProfMaxAggRxPwrUs

      *  xdsl2LConfProfPsdMaskDs

      *  xdsl2LConfProfPsdMaskUs

Top      Up      ToC       Page 210 
      *  xdsl2LConfProfPsdMaskSelectUs

      *  xdsl2LConfProfClassMask

      *  xdsl2LConfProfLimitMask

      *  xdsl2LConfProfUs0Disable

      *  xdsl2LConfProfModeSpecRowStatus

      Unauthorized changes resulting in the setting of any of the above
      objects to an incorrect value could have an adverse operational
      effect on several lines.

      Also, unauthorized changes to xdsl2LConfProfModeSpecRowStatus
      could result in unwanted PSD configurations being created or
      brought into service prematurely, or they could result in PSD
      configurations being inadvertently deleted or taken out of
      service.

   o  xdsl2LineConfProfModeSpecBandUsTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2LConfProfUpboPsdA

      *  xdsl2LConfProfUpboPsdB

      *  xdsl2LConfProfModeSpecRowStatus

      Unauthorized changes resulting in the setting of any of the above
      objects to an incorrect value could have an adverse operational
      effect on several lines.

      Also, unauthorized changes to
      xdsl2LConfProfModeSpecBandUsRowStatus could result in unwanted PSD
      configurations being created or brought into service prematurely,
      or they could result in PSD configurations being inadvertently
      deleted or taken out of service.

   o  xdsl2ChConfProfileTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2ChConfProfMinDataRateDs

Top      Up      ToC       Page 211 
      *  xdsl2ChConfProfMinDataRateUs

      *  xdsl2ChConfProfMinResDataRateDs

      *  xdsl2ChConfProfMinResDataRateUs

      *  xdsl2ChConfProfMaxDataRateDs

      *  xdsl2ChConfProfMaxDataRateUs

      *  xdsl2ChConfProfMinDataRateLowPwrDs

      *  xdsl2ChConfProfMinDataRateLowPwrUs

      *  xdsl2ChConfProfMaxDelayDs

      *  xdsl2ChConfProfMaxDelayUs

      *  xdsl2ChConfProfMinProtectionDs

      *  xdsl2ChConfProfMinProtectionUs

      *  xdsl2ChConfProfMinProtection8Ds

      *  xdsl2ChConfProfMinProtection8Us

      *  xdsl2ChConfProfMaxBerDs

      *  xdsl2ChConfProfMaxBerUs

      *  xdsl2ChConfProfUsDataRateDs

      *  xdsl2ChConfProfDsDataRateDs

      *  xdsl2ChConfProfUsDataRateUs

      *  xdsl2ChConfProfDsDataRateUs

      *  xdsl2ChConfProfImaEnabled

      *  xdsl2ChConfProfMaxDelayVar

      *  xdsl2ChConfProfInitPolicy

      *  xdsl2ChConfProfRowStatus

Top      Up      ToC       Page 212 
      Unauthorized changes resulting in the setting of any of the above
      objects to an incorrect value could have an adverse operational
      effect on several lines.

      Also, unauthorized changes to xdsl2ChConfProfRowStatus could
      result in unwanted channel profiles being created or brought into
      service prematurely, or they could result in channel profiles
      being inadvertently deleted or taken out of service.

   o  xdsl2LineAlarmConfTemplateTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2LAlarmConfTempLineProfile

      *  xdsl2LAlarmConfTempChan1ConfProfile

      *  xdsl2LalarmConfTempChan2ConfProfile

      *  xdsl2LalarmConfTempChan3ConfProfile

      *  xdsl2LalarmConfTempChan4ConfProfile

      *  xdsl2LAlarmConfTempRowStatus

      Unauthorized changes to xdsl2LAlarmConfTempLineProfile,
      xdsl2LAlarmConfTempChan1ConfProfile,
      xdsl2LAlarmConfTempChan2ConfProfile,
      xdsl2LAlarmConfTempChan3ConfProfile, or
      xdsl2LAlarmConfTempChan4ConfProfile could have an adverse effect
      on the management of notifications generated at the scope of
      several to many lines, or they could change several to many lines
      over to running with unwanted management rates for generated
      notifications.

      Unauthorized changes to xdsl2LAlarmConfTempRowStatus could result
      in alarm templates being created or brought into service
      prematurely, or they could result in alarm templates being
      inadvertently deleted or taken out of service.

   o  xdsl2LineAlarmConfProfileTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2LineAlarmConfProfileXtucThresh15MinFecs

Top      Up      ToC       Page 213 
      *  xdsl2LineAlarmConfProfileXtucThresh15MinEs

      *  xdsl2LineAlarmConfProfileXtucThresh15MinSes

      *  xdsl2LineAlarmConfProfileXtucThresh15MinLoss

      *  xdsl2LineAlarmConfProfileXtucThresh15MinUas

      *  xdsl2LineAlarmConfProfileXturThresh15MinFecs

      *  xdsl2LineAlarmConfProfileXturThresh15MinEs

      *  xdsl2LineAlarmConfProfileXturThresh15MinSes

      *  xdsl2LineAlarmConfProfileXturThresh15MinLoss

      *  xdsl2LineAlarmConfProfileXturThresh15MinUas

      *  xdsl2LineAlarmConfProfileThresh15MinFailedFullInt

      *  xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt

      *  xdsl2LineAlarmConfProfileRowStatus

      Increasing any of the threshold values could result in a
      notification being suppressed or deferred.  Setting a threshold to
      '0' could result in a notification being suppressed.  Suppressing
      or deferring a notification could prevent the timely delivery of
      important diagnostic information.  Decreasing any of the threshold
      values could result in a notification being sent from the network
      falsely reporting a threshold crossing.

      Unauthorized changes to row status could result in unwanted line
      alarm profiles being created or brought into service.  Also,
      changes to the row status could result in line alarm profiles
      being inadvertently deleted or taken out of service.

   o  xdsl2ChAlarmConfProfileTable

      The table consists of the following objects that support SET
      operations:

      *  xdsl2ChAlarmConfProfileXtucThresh15MinCodingViolations

      *  xdsl2ChAlarmConfProfileXtucThresh15MinCorrected

      *  xdsl2ChAlarmConfProfileXturThresh15MinCodingViolations

Top      Up      ToC       Page 214 
      *  xdsl2ChAlarmConfProfileXturThresh15MinCorrected

      *  xdsl2ChAlarmConfProfileRowStatus

      *  xdsl2LineAlarmConfProfileXturThresh15MinFecs

      *  xdsl2LineAlarmConfProfileXturThresh15MinEs

      *  xdsl2LineAlarmConfProfileXturThresh15MinSes

      *  xdsl2LineAlarmConfProfileXturThresh15MinLoss

      *  xdsl2LineAlarmConfProfileXturThresh15MinUas

      *  xdsl2LineAlarmConfProfileThresh15MinFailedFullInt

      *  xdsl2LineAlarmConfProfileThresh15MinFailedShrtInt

      *  xdsl2LineAlarmConfProfileRowStatus

      Increasing any of the threshold values could result in a
      notification being suppressed or deferred.  Setting a threshold to
      '0' could result in a notification being suppressed.  Suppressing
      or deferring a notification could prevent the timely delivery of
      important diagnostic information.  Decreasing any of the threshold
      values could result in a notification being sent from the network
      falsely reporting a threshold crossing.

      Unauthorized changes to row status could result in unwanted
      channel alarm profiles being created or brought into service.
      Also, changes to the row status could result in channel alarm
      profiles being inadvertently deleted or taken out of service.

   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  xdsl2LineInventoryTable

      Access to these objects would allow an intruder to obtain
      information about which vendor's equipment is in use on the
      network.  Further, such information is considered sensitive in
      many environments for competitive reasons.

Top      Up      ToC       Page 215 
      *  xdsl2LInvG994VendorId

      *  xdsl2LInvSystemVendorId

      *  xdsl2LInvVersionNumber

      *  xdsl2LInvSerialNumber

      *  xdsl2LInvSelfTestResult

      *  xdsl2LInvTransmissionCapabilities

   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.

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

   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 only to those objects whose
   principals (users) have legitimate rights to indeed GET or SET
   (change/create/delete) them.

6.  Acknowledgments

   The authors are deeply grateful to the authors of the HDSL2 LINE MIB
   (RFC 4319), Clay Sikes and Bob Ray, for contributing to accelerating
   the work on this document.  The structure of this document as well as
   several paragraphs originate in their document.

   Other contributions and advice were received from the following:

         Randy Presuhn (Mindspring)
         Chen  Jian    (Huawei)
         Bert  Wijnen  (Lucent)
         Brian Johnson (NEC Australia)
         Andrew Cheers (NEC Australia)
         Sedat Akca    (NEC Australia)
         Victor Sperry (Calix Networks)
         Narendranath Nair (Wipro)
         Uwe Pauluhn   (Infineon)

Top      Up      ToC       Page 216 
         John D. Boyle (Alcatel)
         Edward Beili  (Actelis)
         Dan Romascanu (Avaya)
         David Harrington (Comcast)
         Smadar Tauber (RAD Data Communications)
         Richard Barnes (BBN Technologies)

7.  References

7.1.  Normative References

   [G.992.1]      "Asymmetric digital subscriber line (ADSL)
                  transceivers", ITU-T G.992.1, 1999.

   [G.992.2]      "Splitterless asymmetric digital subscriber line
                  (ADSL) transceivers", ITU-T G.992.2, 1999.

   [G.992.3]      "Asymmetric digital subscriber line transceivers 2
                  (ADSL2)", ITU-T G.992.3, 2002.

   [G.992.4]      "Splitterless asymmetric digital subscriber line
                  transceivers 2 (Splitterless ADSL2)", ITU-T G.992.4,
                  2002.

   [G.992.5]      "Asymmetric digital subscriber line (ADSL)
                  transceivers - Extended bandwidth ADSL2 (ADSL2+)",
                  ITU-T G.992.5, 2005.

   [G.993.1]      "Very-high speed Digital Subscriber Line
                  Transceivers", ITU-T G.993.1, June 2004.

   [G.993.2]      "Very-high speed Digital Subscriber Line Transceivers
                  2 (VDSL2 draft)", ITU-T G.993.2, February 2006.

   [G.997.1]      "Physical layer management for digital subscriber line
                  (DSL) transceivers", ITU-T G.997.1, June 2006.

   [G.997.1-Am1]  "Physical layer management for digital subscriber line
                  (DSL) transceivers - Amendment 1", ITU-T G.997.1-
                  Amendment 1, December 2006.

   [RFC2119]      Bradner, S., "Key words for use in RFCs to Indicate
                  Requirement Levels", 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.

Top      Up      ToC       Page 217 
   [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.

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

   [RFC3411]      Harrington, D., Presuhn, R., and B. Wijnen, "An
                  Architecture for Describing Simple Network Management
                  Protocol (SNMP) Management Frameworks", STD 62,
                  RFC 3411, December 2002.

   [RFC3593]      Tesink, K., "Textual Conventions for MIB Modules Using
                  Performance History Based on 15 Minute Intervals",
                  RFC 3593, September 2003.

   [RFC3705]      Ray, B. and R. Abbi, "High Capacity Textual
                  Conventions for MIB Modules Using Performance History
                  Based on 15 Minute Intervals", RFC 3705,
                  February 2004.

   [T1E1.413]     J. Bingham & F. Van der Putten, "Network and Customer
                  Installation Interfaces - Asymmetric Digital
                  Subscriber Line (ADSL) Metallic Interface (T1.413
                  Issue 2)", ANSI T1E1.413-1998, June 1998.

7.2.  Informative References

   [RFC2662]      Bathrick, G. and F. Ly, "Definitions of Managed
                  Objects for the ADSL Lines", RFC 2662, August 1999.

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

   [RFC3418]      Presuhn, R., "Management Information Base (MIB) for
                  the Simple Network Management Protocol (SNMP)",
                  STD 62, RFC 3418, December 2002.

   [RFC3728]      Ray, B. and R. Abbi, "Definitions of Managed Objects
                  for Very High Speed Digital Subscriber Lines (VDSL)",
                  RFC 3728, February 2004.

Top      Up      ToC       Page 218 
   [RFC4133]      Bierman, A. and K. McCloghrie, "Entity MIB (Version
                  3)", RFC 4133, August 2005.

   [RFC4706]      Morgenstern, M., Dodge, M., Baillie, S., and U.
                  Bonollo, "Definitions of Managed Objects for
                  Asymmetric Digital Subscriber Line 2 (ADSL2)",
                  RFC 4706, November 2006.

   [TR-129]       Adams, P., "Protocol Independent Management Model for
                  Next Generation DSL Technologies", DSL Forum TR-129,
                  December 2006.

Authors' Addresses

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

   Phone: +972 3 926 6258
   Fax:   +972 3 928 7342
   EMail: moti.Morgenstern@ecitele.com


   Scott Baillie
   NEC Australia
   649-655 Springvale Road
   Mulgrave, Victoria  3170
   Australia

   Phone: +61 3 9264 3986
   Fax:   +61 3 9264 3892
   EMail: scott.baillie@nec.com.au


   Umberto Bonollo
   NEC Australia
   649-655 Springvale Road
   Mulgrave, Victoria  3170
   Australia

   Phone: +61 3 9264 3385
   Fax:   +61 3 9264 3892
   EMail: umberto.bonollo@nec.com.au