⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2265.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 5 页
字号:
                 conceptual row authorizes write access.                 The identified MIB view is that one for which the                 vacmViewTreeFamilyViewName has the same value as the                 instance of this object; if the value is the empty                 string or if there is no active MIB view having this                 value of vacmViewTreeFamilyViewName, then no access                 is granted.                "    DEFVAL      { ''H }   -- the empty string    ::= { vacmAccessEntry 6 }vacmAccessNotifyViewName OBJECT-TYPE    SYNTAX       SnmpAdminString (SIZE(0..32))    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "The value of an instance of this object identifies                 the MIB view of the SNMP context to which this                 conceptual row authorizes access for notifications.Wijnen, et. al.             Standards Track                    [Page 18]RFC 2265                    VACM for SNMPv3                 January 1998                 The identified MIB view is that one for which the                 vacmViewTreeFamilyViewName has the same value as the                 instance of this object; if the value is the empty                 string or if there is no active MIB view having this                 value of vacmViewTreeFamilyViewName, then no access                 is granted.                "    DEFVAL      { ''H }   -- the empty string    ::= { vacmAccessEntry 7 }vacmAccessStorageType OBJECT-TYPE    SYNTAX       StorageType    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "The storage type for this conceptual row.                 Conceptual rows having the value 'permanent' need not                 allow write-access to any columnar objects in the row.                "    DEFVAL      { nonVolatile }    ::= { vacmAccessEntry 8 }vacmAccessStatus OBJECT-TYPE    SYNTAX       RowStatus    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "The status of this conceptual row.                 The  RowStatus TC [RFC1903] requires that this                 DESCRIPTION clause states under which circumstances                 other objects in this row can be modified:                 The value of this object has no effect on whether                 other objects in this conceptual row can be modified.                "    ::= { vacmAccessEntry 9 }-- Information about MIB views ***************************************-- Support for instance-level granularity is optional.---- In some implementations, instance-level access control-- granularity may come at a high performance cost.  Managers-- should avoid requesting such configurations unnecessarily.vacmMIBViews     OBJECT IDENTIFIER ::= { vacmMIBObjects 5 }vacmViewSpinLock OBJECT-TYPEWijnen, et. al.             Standards Track                    [Page 19]RFC 2265                    VACM for SNMPv3                 January 1998    SYNTAX       TestAndIncr    MAX-ACCESS   read-write    STATUS       current    DESCRIPTION "An advisory lock used to allow cooperating SNMP                 Command Generator applications to coordinate their                 use of the Set operation in creating or modifying                 views.                 When creating a new view or altering an existing                 view, it is important to understand the potential                 interactions with other uses of the view.  The                 vacmViewSpinLock should be retrieved.  The name of                 the view to be created should be determined to be                 unique by the SNMP Command Generator application by                 consulting the vacmViewTreeFamilyTable.  Finally,                 the named view may be created (Set), including the                 advisory lock.                 If another SNMP Command Generator application has                 altered the views in the meantime, then the spin                 lock's value will have changed, and so this creation                 will fail because it will specify the wrong value for                 the spin lock.                 Since this is an advisory lock, the use of this lock                 is not enforced.                "    ::= { vacmMIBViews 1 }vacmViewTreeFamilyTable OBJECT-TYPE    SYNTAX       SEQUENCE OF VacmViewTreeFamilyEntry    MAX-ACCESS   not-accessible    STATUS       current    DESCRIPTION "Locally held information about families of subtrees                 within MIB views.                 Each MIB view is defined by two sets of view subtrees:                   - the included view subtrees, and                   - the excluded view subtrees.                 Every such view subtree, both the included and the                 excluded ones, is defined in this table.                 To determine if a particular object instance is in                 a particular MIB view, compare the object instance's                 OBJECT IDENTIFIER with each of the MIB view's active                 entries in this table.  If none match, then the                 object instance is not in the MIB view.  If one or                 more match, then the object instance is included in,                 or excluded from, the MIB view according to theWijnen, et. al.             Standards Track                    [Page 20]RFC 2265                    VACM for SNMPv3                 January 1998                 value of vacmViewTreeFamilyType in the entry whose                 value of vacmViewTreeFamilySubtree has the most                 sub-identifiers.  If multiple entries match and have                 the same number of sub-identifiers, then the                 lexicographically greatest instance of                 vacmViewTreeFamilyType determines the inclusion or                 exclusion.                 An object instance's OBJECT IDENTIFIER X matches an                 active entry in this table when the number of                 sub-identifiers in X is at least as many as in the                 value of vacmViewTreeFamilySubtree for the entry,                 and each sub-identifier in the value of                 vacmViewTreeFamilySubtree matches its corresponding                 sub-identifier in X.  Two sub-identifiers match                 either if the corresponding bit of the value of                 vacmViewTreeFamilyMask for the entry is zero (the                 'wild card' value), or if they are equal.                 A 'family' of subtrees is the set of subtrees defined                 by a particular combination of values of                 vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask.                 In the case where no 'wild card' is defined in the                 vacmViewTreeFamilyMask, the family of subtrees reduces                 to a single subtree.                 When creating or changing MIB views, an SNMP Command                 Generator application should utilize the                 vacmViewSpinLock to try to avoid collisions. See                 DESCRIPTION clause of vacmViewSpinLock.                 When creating MIB views, it is strongly advised that                 first the 'excluded' vacmViewTreeFamilyEntries are                 created and then the 'included' entries.                 When deleting MIB views, it is strongly advised that                 first the 'included' vacmViewTreeFamilyEntries are                 deleted and then the 'excluded' entries.                 If a create for an entry for instance-level access                 control is received and the implementation does not                 support instance-level granularity, then an                 inconsistentName error must be returned.                "    ::= { vacmMIBViews 2 }vacmViewTreeFamilyEntry OBJECT-TYPE    SYNTAX       VacmViewTreeFamilyEntryWijnen, et. al.             Standards Track                    [Page 21]RFC 2265                    VACM for SNMPv3                 January 1998    MAX-ACCESS   not-accessible    STATUS       current    DESCRIPTION "Information on a particular family of view subtrees                 included in or excluded from a particular SNMP                 context's MIB view.                 Implementations must not restrict the number of                 families of view subtrees for a given MIB view,                 except as dictated by resource constraints on the                 overall number of entries in the                 vacmViewTreeFamilyTable.                 If no conceptual rows exist in this table for a given                 MIB view (viewName), that view may be thought of as                 consisting of the empty set of view subtrees.                "    INDEX       { vacmViewTreeFamilyViewName,                  vacmViewTreeFamilySubtree                }    ::= { vacmViewTreeFamilyTable 1 }VacmViewTreeFamilyEntry ::= SEQUENCE    {        vacmViewTreeFamilyViewName     SnmpAdminString,        vacmViewTreeFamilySubtree      OBJECT IDENTIFIER,        vacmViewTreeFamilyMask         OCTET STRING,        vacmViewTreeFamilyType         INTEGER,        vacmViewTreeFamilyStorageType  StorageType,        vacmViewTreeFamilyStatus       RowStatus    }vacmViewTreeFamilyViewName OBJECT-TYPE    SYNTAX       SnmpAdminString (SIZE(1..32))    MAX-ACCESS   not-accessible    STATUS       current    DESCRIPTION "The human readable name for a family of view subtrees.                "    ::= { vacmViewTreeFamilyEntry 1 }vacmViewTreeFamilySubtree OBJECT-TYPE    SYNTAX       OBJECT IDENTIFIER    MAX-ACCESS   not-accessible    STATUS       current    DESCRIPTION "The MIB subtree which when combined with the                 corresponding instance of vacmViewTreeFamilyMask                 defines a family of view subtrees.                "    ::= { vacmViewTreeFamilyEntry 2 }Wijnen, et. al.             Standards Track                    [Page 22]RFC 2265                    VACM for SNMPv3                 January 1998vacmViewTreeFamilyMask OBJECT-TYPE    SYNTAX       OCTET STRING (SIZE (0..16))    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "The bit mask which, in combination with the                 corresponding instance of vacmViewTreeFamilySubtree,                 defines a family of view subtrees.                 Each bit of this bit mask corresponds to a                 sub-identifier of vacmViewTreeFamilySubtree, with the                 most significant bit of the i-th octet of this octet                 string value (extended if necessary, see below)                 corresponding to the (8*i - 7)-th sub-identifier, and                 the least significant bit of the i-th octet of this                 octet string corresponding to the (8*i)-th                 sub-identifier, where i is in the range 1 through 16.                 Each bit of this bit mask specifies whether or not                 the corresponding sub-identifiers must match when                 determining if an OBJECT IDENTIFIER is in this                 family of view subtrees; a '1' indicates that an                 exact match must occur; a '0' indicates 'wild card',                 i.e., any sub-identifier value matches.                 Thus, the OBJECT IDENTIFIER X of an object instance                 is contained in a family of view subtrees if, for                 each sub-identifier of the value of                 vacmViewTreeFamilySubtree, either:                   the i-th bit of vacmViewTreeFamilyMask is 0, or                   the i-th sub-identifier of X is equal to the i-th                   sub-identifier of the value of                   vacmViewTreeFamilySubtree.                 If the value of this bit mask is M bits long and                 there are more than M sub-identifiers in the                 corresponding instance of vacmViewTreeFamilySubtree,                 then the bit mask is extended with 1's to be the                 required length.                 Note that when the value of this object is the                 zero-length string, this extension rule results in                 a mask of all-1's being used (i.e., no 'wild card'),                 and the family of view subtrees is the one view                 subtree uniquely identified by the corresponding                 instance of vacmViewTreeFamilySubtree.Wijnen, et. al.             Standards Track                    [Page 23]RFC 2265                    VACM for SNMPv3                 January 1998                 Note that masks of length greater than zero length                 do not need to be supported. In this case this                 object is made read-only.                "    DEFVAL      { ''H }    ::= { vacmViewTreeFamilyEntry 3 }vacmViewTreeFamilyType OBJECT-TYPE    SYNTAX       INTEGER  { included(1), excluded(2) }    MAX-ACCESS   read-create    STATUS       current    DESCRIPTION "Indicates whether the corresponding instances of                 vacmViewTreeFamilySubtree and vacmViewTreeFamilyMask                 define a family of view subtrees which is included in                 or excluded from the MIB view.                "    DEFVAL      { included }    ::= { vacmViewTreeFamilyEntry 4 }vacmViewTreeFamilyStorageType OBJECT-TYPE    SYNTAX       StorageType    MAX-ACCESS   read-create

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -