rfc1461.txt

中、英文RFC文档大全打包下载完全版 .

                  DEFVAL { ''h }
                  ::= { mioxPeerEntry 10 }



          -- ###########################################################
          --              Peer Encapsulation Table
          -- ###########################################################




Throop                                                         [Page 16]

RFC 1461        Multiprotocol Interconnect on X.25 MIB          May 1993


          mioxPeerEncTable OBJECT-TYPE
                  SYNTAX  SEQUENCE OF MioxPeerEncEntry
                  ACCESS  not-accessible
                  STATUS  mandatory
                  DESCRIPTION
                          "This table contains the list of
                          encapsulations used to communicate with a
                          peer.  This table has two indexes, the first
                          identifies the peer, the second
                          distinguishes encapsulation types.

                          The first index identifies the corresponding
                          entry in the mioxPeerTable.  The second
                          index gives the priority of the different
                          encapsulations.

                          The encapsulation types are ordered in
                          priority order.  For calling a peer, the
                          first entry (mioxPeerEncIndex of 1) is tried
                          first.  If the call doesn't succeed because
                          the remote host clears the call due to
                          incompatible call user data, the next entry
                          in the list is tried.  Each entry is tried
                          until the list is exhausted.

                          For answering a call, the encapsulation type
                          requested by the peer must be found the list
                          or the call will be refused.  If there are
                          no entries in this table for a peer, all
                          call requests from the peer will be refused.

                          Objects in this table can only be set when
                          the mioxPeerStatus object with the same
                          index has a value of underCreation.  When
                          that status object is set to invalid and
                          deleted, the entry in this table with that
                          peer index must also be deleted."
                  ::= { mioxPeer 2 }

          mioxPeerEncEntry OBJECT-TYPE
                  SYNTAX  MioxPeerEncEntry
                  ACCESS  not-accessible
                  STATUS  mandatory
                  DESCRIPTION
                          "Per connection information."
                  INDEX { mioxPeerIndex, mioxPeerEncIndex}
                  ::= { mioxPeerEncTable 1 }




Throop                                                         [Page 17]

RFC 1461        Multiprotocol Interconnect on X.25 MIB          May 1993


          MioxPeerEncEntry ::= SEQUENCE {
                  mioxPeerEncIndex
                          PositiveInteger,
                  mioxPeerEncType
                          INTEGER
                  }

          mioxPeerEncIndex        OBJECT-TYPE
                  SYNTAX  PositiveInteger
                  ACCESS  read-only
                  STATUS    mandatory
                  DESCRIPTION
                          "The second index in the table which
                          distinguishes different encapsulation
                          types."
                  ::= { mioxPeerEncEntry 1 }

          mioxPeerEncType OBJECT-TYPE
                  SYNTAX  INTEGER (0..256)
                  ACCESS  read-write
                  STATUS  mandatory
                  DESCRIPTION
                          "The value of the encapsulation type.  For
                          IP encapsulation this will have a value of
                          204 (hex CC).  For SNAP encapsulated
                          packets, this will have a value of 128 (hex
                          80).  For CLNP, ISO 8473, this will have a
                          value of 129 (hex 81).  For ES-ES, ISO 9542,
                          this will have a value of 130 (hex 82).  A
                          value of 197 (hex C5) identifies the Blacker
                          X.25 encapsulation.  A value of 0,
                          identifies the Null encapsulation.

                          This value can only be written when the
                          mioxPeerStatus object with the same
                          mioxPeerIndex has a value of underCreation.
                          Setting this object to a value of 256
                          deletes the entry.  When deleting an entry,
                          all other entries in the mioxPeerEncTable
                          with the same mioxPeerIndex and with an
                          mioxPeerEncIndex higher then the deleted
                          entry, will all have their mioxPeerEncIndex
                          values decremented by one."
                  ::= { mioxPeerEncEntry 2 }

          -- ###########################################################

          END



Throop                                                         [Page 18]

RFC 1461        Multiprotocol Interconnect on X.25 MIB          May 1993


5.  Acknowledgements

   This document was produced by the x25mib working group:

               Fred Baker, ACC
               Art Berggreen, ACC
               Frank Bieser
               Gary Bjerke, Tandem
               Bill Bowman, HP
               Christopher Bucci, Datability
               Charles Carvalho, ACC
               Jeff Case, University of Tennessee at Knoxville
               Angela Chen, HP
               Carson Cheung, BNR
               Tom Daniel, Spider Systems
               Chuck Davin, MIT
               Billy Durham, Honeywell
               Richard Fox, Synoptics
               Doug Geller, Data General
               Herve Goguely, LIR Corp
               Andy Goldthorpe, British-Telecom
               Walter D. Guilarte
               David Gurevich
               Steve Huston, Consultant
               Jon Infante, ICL
               Frank Kastenholz, FTP Software
               Zbigniew Kielczewski, Eicon
               Cheryl Krupezak, Georgia Tech
               Mats Lindstrom, Diab Data AB
               Andrew Malis, BBN
               Evan McGinnis, 3Com
               Gary (G.P.)Mussar, BNR
               Chandy Nilakantan, 3Com
               Randy Pafford, Data General
               Ragnar Paulson, The Software Group Limited
               Dave Perkins, Synoptics
               Walter Pinkarschewsky, DEC
               Karen Quidley, Data General
               Chris Ranch, Novell
               Paul S. Rarey, DHL Systems Inc.
               Jim Roche, Newbridge Research
               Philippe Roger, LIR Corp.
               Timon Sloane
               Mike Shand, DEC
               Brad Steina, Microcom
               Bob Stewart, Xyplex
               Tom Sullivan, Data General
               Rodney Thayer, Sable Technology Corporation



Throop                                                         [Page 19]

RFC 1461        Multiprotocol Interconnect on X.25 MIB          May 1993


               Mark Therieau, Microcom
               Jane Thorn, Data General
               Dean Throop, Data General
               Maurice Turcotte, Racal Datacom
               Mike Zendels, Data General

6.  References

   [1] Rose M., and K. McCloghrie, "Structure and Identification of
       Management Information for TCP/IP-based internets", STD 16, RFC
       1155, Performance Systems International, Hughes LAN Systems, May
       1990.

   [2] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
       Network Management Protocol", STD 15, RFC 1157, SNMP Research,
       Performance Systems International, Performance Systems
       International, MIT Laboratory for Computer Science, May 1990.

   [3] Rose, M. and K. McCloghrie, Editors, "Towards Concise MIB
       Definitions", STD 16, RFC 1212, Performance Systems
       International, Hughes LAN Systems, March 1991.

   [4] Rose M., Editor, "Management Information Base for Network
       Management of TCP/IP-based internets", STD 17, RFC 1213.
       Performance Systems International, March 1991.

   [5] "Information processing systems - Open Systems Interconnection -
       Specification of Abstract Syntax Notation One (ASN.1)",
       International Organization for Standardization.  International
       Standard 8824, December, 1987.

   [6] Stewart, B., Editor, "Definitions of Managed Objects for RS-232-
       like Hardware Devices", RFC 1317, Xyplex, Inc., April 1992.

   [7] Throop, D., and F. Baker, "SNMP MIB extension for X.25 LAPB", RFC
       1381, Data General Corporation, Advanced Computer Communications,
       November 1992.

   [8] Throop, D., Editor, "SNMP MIB extension for the X.25 Packet
       Layer", RFC 1382, Data General Corporation, November 1991.

   [9] Malis, A., Robinson, D., and R. Ullmann "Multiprotocol
       Interconnect on X.25 and ISDN in the Packet Mode", RFC 1356, BBN
       Communications, Computervision Systems Integration, Process
       Software Corporation, August 1992.






Throop                                                         [Page 20]

RFC 1461        Multiprotocol Interconnect on X.25 MIB          May 1993


7.  Security Considerations

   Security issues are not discussed in this memo.

8.  Author's Address

   Dean D. Throop
   Data General Corporation
   62 Alexander Dr.
   Research Triangle Park, NC 27709

   Phone: [phone]
   EMail: [e-mail]






































Throop                                                         [Page 21]