The IP Over NBMA (ION) Archive

Cell Relay Retreat>ION Archive>month:1996-Jun> msg00143



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

comments on draft-ietf-iplpdn-frmib-dte-07.txt

  • From: roy.spitzer@adn.alcatel.com (Roy Spitzer) (by way of fred@cisco.com (FredBaker))
  • Date: Mon, 17 Jun 1996 12:22:53 -0700

Carolyn, Fred, and Charles,

I am sorry that these comments are so late.  I just found out about this
new iteration of RFC1315 at the last Frame Relay Forum meeting from Andy
Malis.  At the same time our offices was moving and I just was able to retrieve
a copy of the proposed MIB for the Montreal IETF June 24, 1996.

How do I get on the proper distribution list for these discussions.  Andy
gave me ion and it did not seem right.  Please forward this mail to the
proper distribution list.

Comments:

1.      We believe that a definition of frTrapState at the interface
        basis is more useful for some vendors than for all interfaces.
        Some interfaces may be managed by different agents than others.
        I would suggest that frDlcmiTrapState be added to the frDlcmiTable.

2.      The frDlcmiTable does not support bidirectional signalling.  Will
        this be a problem for the future?  Currently, I know of no DTE
        vendor that supports bidirectional signalling.

3.      frClcmiAddressLen is not adequate.  Since the MIB is going to be
        changed, I suggest the same definition as frLportAddrDLCILen from
        RFC 1604 be used.

4.      The MIB does not support different quality of service parameter
        (CIR, Bc, Be) on a per direction basis.  Is this a problem for the
        future.

5.      The following statistics would be helpful in the frDlcmiTable:

  frDlcmiLinkRelErrors OBJECT-TYPE
     SYNTAX  Counter32
     MAX-ACCESS  read-only
     STATUS  current
     DESCRIPTION
             "The number of user-side local in-channel
             signaling link reliability errors (i.e., non-
             receipt of Status/Status Enquiry messages or
             invalid sequence numbers in a Link Integrity
             Verification Information Element) for this UNI/NNI
             logical port.  If the logical port is not
             performing user-side procedures, then this value
             is equal to noSuchName."
     REFERENCE "ITU Q.933 Annex A and ANSI T1.617 Annex D"
     ::= { frDlcmiEntry 13 }

  frDlcmiProtErrors OBJECT-TYPE
     SYNTAX  Counter32
     MAX-ACCESS  read-only
     STATUS  current
     DESCRIPTION
             "The number of user-side local in-channel
             signaling protocol errors (i.e., protocol
             discriminator, message type, call reference, and
             mandatory information element errors) for this
             UNI/NNI logical port.  If the logical port is not
             performing user-side procedures, then this value
             is equal to noSuchName."
     REFERENCE "ITU Q.933 Annex A and ANSI T1.617 Annex D"
     ::= {frDlcmiEntry 14 }

  frDlcmiChanInactive OBJECT-TYPE
     SYNTAX  Counter32
     MAX-ACCESS  read-only
     STATUS  current
     DESCRIPTION
             "The number of times the user-side channel was
             declared inactive (i.e., N392 errors in N393
             events) for this UNI/NNI logical port. If the
             logical port is not performing user-side
             procedures, then this value is equal to
             noSuchName."
     REFERENCE "ITU Q.933 Annex A and ANSI T1.617 Annex D"
     ::= { frDlcmiEntry 15 }

6.      What is the interrelationship between frCircuitMulticast and
        frDlcmiMulticast?  Can frCircuitMulticast be set to anything
        other than unicast if frDlcmiMulticast is nonBroadcast?  Can the
        same interface have both unicast and multicast DLCI?  If so,
        what is the setting of frDlcmiMulticst set?

7.      What provisions are being made for SVCs or is it out of the
        scope of this MIB modification?

8.      The following statistics would be useful either as part of frDlcmiTable
        or part of a separate table:

   frErrorUserLinkRelErrors OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION -- (from RFC1604 frMgtVCSigUserLinkRelErrors)
             "The number of user-side local in-channel
             signaling link reliability errors (i.e., non-
             receipt of Status/Status Enquiry messages or
             invalid sequence numbers in a Link Integrity
             Verification Information Element) for this UNI/NNI
             logical port.  If the logical port is not
             performing user-side procedures, then this value
             is equal to noSuchName."
       REFERENCE "ITU Q.933 Annex A and ANSI T1.617 Annex D"
       ::= { frErrorEntry 1 }

  frErrorUserProtErrors   OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION  -- (from RFC1604 frMgtVCSigUserProtErrors   )
             "The number of user-side local in-channel
             signaling protocol errors (i.e., protocol
             discriminator, message type, call reference, and
             mandatory information element errors) for this
             UNI/NNI logical port.  If the logical port is not
             performing user-side procedures, then this value
             is equal to noSuchName."
       REFERENCE "ITU Q.933 Annex A and ANSI T1.617 Annex D"
       ::= { frErrorEntry 2 }

  frErrorChanInactive   OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION  -- (from RFC1604  frMgtVCSigUserChanInactive )
             "The number of times the user-side channel was
             declared inactive (i.e., N392 errors in N393
             events) for this UNI/NNI logical port. If the
             logical port is not performing user-side
             procedures, then this value is equal to
             noSuchName."
       REFERENCE "ITU Q.933 Annex A and ANSI T1.617 Annex D"
       ::= { frErrorEntry 3 }

  frErrorRcvdShort   OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
           "The number of frames that were to short to be legal
            frame relay frames"
       ::= { frErrorEntry 4 }

  frErrorRcvdLong   OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
            "The number of frames that were longer than the length
             specified in the ifTable by ifMtu for this interface."
       ::= { frErrorEntry 5 }


   frErrorRcvdIllegalDLCI   OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
           "The number of frames received with an illegal Data Link
            Connection Identifier (DLCI)."
       ::= { frErrorEntry 6 }

  frErrorRcvdUnknownDLCI   OBJECT-TYPE
       SYNTAX Counter32
       MAX-ACCESS read-only
       STATUS current
       DESCRIPTION
           "The number of frames received with an unknown Data Link
            Connection Identifier (DLCI)."
       ::= { 6fdnVsFrErrorEntry 7 }

Regards,
Roy Spitzer

==========================================================================

Roy Spitzer                             Roy.Spitzer@adn.alcatel.com
Alcatel Data Networks                   (703) 724-2412
44983 Knoll Square                      FAX: (703) 724-2005
Ashburn, VA 20147