OBJECT marsMcsForceWaitTimer
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsLmtToMissRedirMapTimer
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsIdleTimer
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsMcGrpRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsBackupMarsRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcPartyAddrType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcCtrlType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcIdleTimer
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcRevalidate
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcEncapsType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcNegotiatedMtu
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT marsMcsVcRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { marsMcsCompliances 1 }
marsMcsGroup OBJECT-GROUP
OBJECTS {
marsMcsAddr,
marsMcsDefaultMarsAddr,
marsMcsRegistration,
marsMcsSsn ,
marsMcsDefaultMtu,
marsMcsFailureTimer,
marsMcsRetranDelayTimer,
marsMcsRdmMulReqAddRetrTimer,
marsMcsRdmVcRevalidateTimer,
marsMcsRegisterRetrInterval,
marsMcsRegisterRetrLimit,
marsMcsRegWithMarsRdmTimer,
marsMcsForceWaitTimer,
marsMcsIdleTimer,
marsMcsLmtToMissRedirMapTimer,
marsMcsRowStatus,
marsMcsMcGrpRowStatus,
marsMcsVcPartyAddrType,
marsMcsBackupMarsRowStatus,
marsMcsVcType,
marsMcsVcCtrlType,
marsMcsVcIdleTimer,
marsMcsVcRevalidate,
marsMcsVcEncapsType,
marsMcsVcNegotiatedMtu,
marsMcsVcRowStatus,
marsMcsStatTxReqMsgs,
marsMcsStatTxMservMsgs,
marsMcsStatTxUnservMsgs,
marsMcsStatRxMultiMsgs,
marsMcsStatRxSjoinMsgs,
marsMcsStatRxSleaveMsgs,
marsMcsStatRxNakMsgs,
marsMcsStatRxMigrateMsgs,
marsMcsStatFailMultiMsgs
}
STATUS current
DESCRIPTION
"A collection of objects to be implemented in a MIB
for the management of MARS multicast servers (MCS)."
::= { marsMcsGroups 1 }
END
4. Acknowledgments
This document is a product of the IETF's Internetworking Over NBMA
Networks (ion) Working Group. The original work of the MARS MIB
developement was sponsored by Science Applications International
Corporation (SAIC).
The author would like to recognize Grenville Armitage (Bellcore), Ken
Carlberg (SAIC), Ramesh Uppuluri (Fore Systems), and Radha Gowda
SYNNET), and Bill Willcox (Fujitsu Nexion) for their support and
comments in completing the MARS MIB. Also thanks to Bert Wijnen (IBM)
for his thorough review of the MARS MIB.
5. References
[1] Armitage, G., "Support for Multicast over UNI 3.0/3.1
based ATM Networks", RFC2022, November 1996.
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", RFC1902,
January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Textual Conventions for Version 2 of the of the
Simple Network Management Protocol (SNMPv2)", RFC1903, January
1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Conformance Statements for Version 2 of the of the
Simple Network Management Protocol (SNMPv2)", RFC1904, January
1996.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC1157, May 1990.
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC1905, January 1996.
[7] McCloghrie, K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC1213, March 1991.
[8] SNMPv3 Working Group, Blumenthal, U., and B. Wijnen, "User-based
Security Model (USM) for version 3 of Simple Network Management
Protocol (SNMPv3)", RFC2274, January 1998.
[9] SNMPv3 Working Group, Wijnen, B., Presuhn, R., and K.
McCloghire, "View-based Access Control Model (VACM) for the
Simple Network Management Protocol (SNMP)", RFC2275, January
1998.
6. Security Considerations
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
object may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
SNMPv1 by itself is such an insecure environment. 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 SET
(change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC2274 [8] and the View-based
Access Control Model RFC2275 [9] is recommended.
It is then a customer/user responsibility to ensure that the SNMP
entity giving access to this MIB, is properly configured to give
access to those objects only to those principals (users) that have a
legitimate rights to indeed SET (change/create/delete) them.
Note: read-access in fact may also need access-control.
7. Authors' Addresses
Chris Chung
Independent Consultant
EMail: chihschung@aol.com
Maria Greene (editor)
Independent Contractor
EMail: maria@xedia.com
8. Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.