SAVI C. An Internet-Draft J. Yang Intended status: Informational J. Wu Expires: June 26, 2011 J. Bi CERNET December 23, 2010 Definition of Managed Objects for SAVI Protocol draft-an-savi-mib-00 Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing SAVI (Source Address Validation Improvements) protocol instance. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on June 26, 2011. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as An, et al. Expires June 26, 2011 [Page 1] Internet-Draft SAVI-MIB December 2010 described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5.1. The SAVI System Table . . . . . . . . . . . . . . . . . . 4 5.2. The SAVI Interface Table . . . . . . . . . . . . . . . . . 5 5.3. The SAVI Binding Table . . . . . . . . . . . . . . . . . . 5 5.4. The SAVI Filtering Table . . . . . . . . . . . . . . . . . 6 6. Textual Conventions . . . . . . . . . . . . . . . . . . . . . 7 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 7 7.1. Relationship to the INET-ADDRESS-MIB . . . . . . . . . . . 7 7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 7 7.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 8 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 12.1. Normative References . . . . . . . . . . . . . . . . . . . 20 12.2. Informative References . . . . . . . . . . . . . . . . . . 20 12.3. URL References . . . . . . . . . . . . . . . . . . . . . . 21 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 21 An, et al. Expires June 26, 2011 [Page 2] Internet-Draft SAVI-MIB December 2010 1. Introduction The Source Address Validation Improvement protocol was developed to complement ingress filtering with finer-grained, standardized IP source address validation(refer to [SAVI-framework]).A SAVI protocol instance is located on the path of hosts' packets, enforcing the hosts' use of legitimate IP source addresses. This document defines a MIB module that can be used to manage the SAVI protocol instance. It covers both configuration and status monitoring aspects of SAVI implementations. This document uses terminology from the SAVI Protocol specification. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 4. Overview The SAVI Protocol MIB module (SAVI-MIB) is conformant to SAVI protocol, and is designed to: o Support centralized management and monitoring of SAVI protocol instance by standard SNMP protocol. o Support configuration and querying of SAVI protocol parameters. o Support configuration and querying of binding entries. Operators may insert and delete static binding entries. An, et al. Expires June 26, 2011 [Page 3] Internet-Draft SAVI-MIB December 2010 o Support querying of filtering entries. Based on SAVI protocol, attributes and objects of a SAVI protocol instance can be classified into four categories: o System attributes. These attributes are corresponding to a SAVI protocol instance, such as IP Address Assignment Methods and some constants. o Anchor attributes. These attributes are corresponding to a SAVI anchor. Anchor is defined in [SAVI-framework]. o Binding Status Table. This table contains the state of binding between source address and binding anchor (refer to [SAVI-DHCP]). o Filtering Table. This table contains the bindings between binding anchor and address, which is used to filter packets (refer to [SAVI-DHCP]). A table is designed for each category of objects. 5. Structure of the MIB Module This section presents the structure of the SAVI-MIB module. The MIB objects are derived from the SAVI protocol specification. This MIB is composed of a series of tables meant to form the base for managing SAVI entities. The following subsections describe all tables in the SAVI MIB module. 5.1. The SAVI System Table The SAVI System Table (saviObjectsSystemTable) contains the objects which are corresponding to SAVI system-wide parameters. It supports the configuration and collection of SAVI system-wide parameters. There is an entry for each IP stack, IPv4 and IPv6. The table is indexed by: o saviObjectsSystemIPVersion - The IP Version. A textual convention InetVersion defined in RFC4001 is used to represent the different version of IP protocol. It contains the following objects: o saviObjectsSystemMode - Which IP address assignment method the link is running in (refer to [SAVI-framework]). An, et al. Expires June 26, 2011 [Page 4] Internet-Draft SAVI-MIB December 2010 o saviObjectsSystemMaxDadDelay - A constant defined in SAVI protocol (refer to [SAVI-DHCP]). o saviObjectsSystemMaxDadPrepareDelay - A constant defined in SAVI protocol (refer to [SAVI-DHCP]). The MAX-ACCESS of thses objects is READ-WRITE. Network Operators may do configuration by setting these objects. 5.2. The SAVI Interface Table The SAVI Interface Table (saviObjectsIfTable) contains the objects which are corresponding to SAVI running parameters of each anchor. It supports the configuration and collection of SAVI parameters of each anchor. There is an entry for each IP stack, IPv4 and IPv6. The table is indexed by: o saviObjectsIfIPVersion - The IP Version. o saviObjectsIfIfIndex - The index value that uniquely identifies the interface to which this entry is applicable. It contains the following objects: o saviObjectsIfValidationStatus - The validation status of the interface. enable(1): check source address. disable(2): don't check source address. o saviObjectsIfTrustStatus - The trust status of the interface. o saviObjectsIfFilteringNum - The max filtering number of the Interface. The MAX-ACCESS of thses objects is READ-WRITE. Network Operators may configure by setting these objects. 5.3. The SAVI Binding Table The SAVI Binding Table (saviObjectsBindingTable) contains the objects which are corresponding to Binding State Table (BST) defined in SAVI protocol. It contains the binding parameters and state of each binding entry. It supports the collection of binding entries. And an entry can be inserted or deleted if it is a static binding entry. The table is indexed by: An, et al. Expires June 26, 2011 [Page 5] Internet-Draft SAVI-MIB December 2010 o saviObjectsBindingIpAddressType - IP address type. A textual convention InetAddressType defined in RFC4001 is used to represent the different kind of IP address. o saviObjectsBindingType - which IP address assignment method is used to create the binding entry - static(1), slaac(2), dhcp(3). o saviObjectsBindingIfIndex - The index value that uniquely identifies the interface to which this entry is applicable. o saviObjectsBindingIpAddress - The binding source IP address. A textual convention InetAddress defined in RFC4001 is used to define this object. The SAVI Binding Table contains the following objects: o saviObjectsBindingMacAddr - The binding source mac address. o saviObjectsBindingState - The state of the binding entry. o saviObjectsBindingLifetime - The remaining lifetime of the entry. o saviObjectsBindingRowStatus - The status of this row, by which new entries may be created, or old entries be deleted from this table. As defined in RFC2579, the RowStatus textual convention is used to manage the creation and deletion of conceptual rows. For SAVI Binding Table, an entry can be created or deleted only when saviObjectsBindingType=static. The MAX-ACCESS of thses objects is READ-CREATE. Network Operators may create or delete an entry by setting these objects. 5.4. The SAVI Filtering Table The SAVI Filtering Table (saviObjectsFilteringTable) contains the objects which are corresponding to Filtering Table (FT) defined in SAVI protocol. It supports the collection of filtering entries. The table is indexed by: o saviObjectsFilteringIpAddressType - IP address type. o saviObjectsFilteringIfIndex - The index value that uniquely identifies the interface to which this entry is applicable. o saviObjectsFilteringIpAddress - The source IP address. It contains the following objects: An, et al. Expires June 26, 2011 [Page 6] Internet-Draft SAVI-MIB December 2010 o saviObjectsFilteringMacAddr - The source mac address. The MAX-ACCESS of the object is READ-ONLY. 6. Textual Conventions The textual conventions used in the SAVI-MIB are as follows. The MODULE-COMPLIANCE,OBJECT-GROUP textual convention is imported from SNMPv2-CONF [RFC2580]. The MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32 textual convention is imported from SNMPv2- SMI [RFC2578]. The MacAddress,TimeInterval,RowStatus textual convention is imported from SNMPv2-TC [RFC2579]. The InetVersion,InetAddressType,InetAddress textual convention is imported from INET-ADDRESS-MIB [RFC4001]. The InterfaceIndex textual convention is imported from IF-MIB [RFC2863]. The ip textual convention is imported from IP-MIB [RFC4293]. 7. Relationship to Other MIB Modules 7.1. Relationship to the INET-ADDRESS-MIB To support extensibility, IETF defined new textual conventions to represent different IP protocol and different IP address in a unified formation in RFC4001. To support different IP version, a textual convention InetVersion is defined to represent the different version of IP protocol. To support different IP address, a generic Internet address is defined. It consists of two objects: The first one has the syntax InetAddressType, and the second object have the syntax InetAddress. The value of the first object determines how the value of the second is encoded. Since SAVI running mode and parameter is independent of IPv4 and IPv6, so different OID instances should be defined for each protocol. In SAVI-MIB definition, when IP address is used as a part of binding table, it is defined using textual conventions described in INET- ADDRESS-MIB. 7.2. Relationship to the IF-MIB The Interfaces MIB [RFC2863] defines generic managed objects for managing interfaces. This document contains the interface-specific An, et al. Expires June 26, 2011 [Page 7] Internet-Draft SAVI-MIB December 2010 extensions for managing SAVI anchors that are modeled as interfaces. The IF-MIB module is required to be supported on the SAVI device. The interface MUST be modeled as an ifEntry, and ifEntry objects such as ifIndex are to be used as per [RFC2863]. An ifIndex [RFC2863] is used as a common index for interfaces in the SAVI-MIB modules. 7.3. MIB modules required for IMPORTS The SAVI MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579],SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and INET- ADDRESS-MIB [RFC4001] . 8. Definitions SAVI-MIB DEFINITIONS ::=BEGIN IMPORTS MODULE-COMPLIANCE,OBJECT-GROUP FROM SNMPv2-CONF --RFC2580 MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32 FROM SNMPv2-SMI --RFC2578 TEXTUAL-CONVENTION,MacAddress,TimeInterval,RowStatus FROM SNMPv2-TC --RFC2579 InterfaceIndex FROM IF-MIB --RFC2863 InetVersion,InetAddressType,InetAddress FROM INET-ADDRESS-MIB --RFC4001 ip FROM IP-MIB --RFC4293 ; saviMIB MODULE-IDENTITY LAST-UPDATED "201003080037Z" --March 08,2010 ORGANIZATION "IETF SAVI Working Group" CONTACT-INFO "WG charter: http://datatracker.ietf.org/wg/savi/charter/ Editor: Changqing An CERNET Postal: Network Research Center, Tsinghua University Beijing 100084 China An, et al. Expires June 26, 2011 [Page 8] Internet-Draft SAVI-MIB December 2010 Email: acq@cernet.edu.cn Jiahai Yang CERNET Postal: Network Research Center, Tsinghua University Beijing 100084 China Email: yang@cernet.edu.cn " DESCRIPTION "This MIB Module is designed to support configuration and monitoring of SAVI protocol. " REVISION "201003080037Z" DESCRIPTION "Initial version" ::= {ip xxx} saviObjects OBJECT IDENTIFIER ::= { saviMIB 1 } -- System parameters for SAVI protocol saviObjectsSystemTable OBJECT-TYPE SYNTAX SEQUENCE OF SaviObjectsSystemEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table containing savi system-wide parameters." ::= { saviObjects 1 } saviObjectsSystemEntry OBJECT-TYPE SYNTAX SaviObjectsSystemEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing savi system-wide parameters for a particular IP version. " INDEX { saviObjectsSystemIPVersion } ::= { saviObjectsSystemTable 1 } SaviObjectsSystemEntry ::= SEQUENCE { saviObjectsSystemIPVersion InetVersion, saviObjectsSystemMode INTEGER, saviObjectsSystemMaxDadDelay TimeInterval, saviObjectsSystemMaxDadPrepareDelay TimeInterval An, et al. Expires June 26, 2011 [Page 9] Internet-Draft SAVI-MIB December 2010 } saviObjectsSystemIPVersion OBJECT-TYPE SYNTAX InetVersion MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP version " ::= { saviObjectsSystemEntry 1 } saviObjectsSystemMode OBJECT-TYPE SYNTAX INTEGER { savi-disable(1), savi-default(2), savi-dhcp-only(3), savi-slaac-only(4), savi-dhcp-slaac-mix(5) } MAX-ACCESS read-write STATUS current DESCRIPTION "IP Address Assignment Methods. " ::= { saviObjectsSystemEntry 2 } saviObjectsSystemMaxDadDelay OBJECT-TYPE SYNTAX TimeInterval MAX-ACCESS read-write STATUS current DESCRIPTION "A constant. When A gratuitous ARP Request or Duplicate Address Detection Neighbor Solicitation is received from anchor, the lifetime of the BST(Binding State Table) entry MUST be set to be MAX_ARP_DELAY or MAX_DAD_DELAY respectively. TimeInterval is defined in RFC 2579, it's a period of time, measured in units of 0.01 seconds, and the value is (0..2147483647). " ::= { saviObjectsSystemEntry 3 } saviObjectsSystemMaxDadPrepareDelay OBJECT-TYPE SYNTAX TimeInterval MAX-ACCESS read-write STATUS current DESCRIPTION "A constant. When a DHCPv4 DHCPACK or DHCPv6 REPLY message is received, the lifetime of the BST(Binding State Table) entry MUST be set to be MAX_ARP_PREPARE_DELAY or An, et al. Expires June 26, 2011 [Page 10] Internet-Draft SAVI-MIB December 2010 MAX_DAD_PREPARE_DELAY respectively. TimeInterval is defined in RFC 2579, it's a period of time, measured in units of 0.01 seconds, and the value is (0..2147483647). " ::= { saviObjectsSystemEntry 4 } -- Interface parameters for SAVI protocol saviObjectsIfTable OBJECT-TYPE SYNTAX SEQUENCE OF SaviObjectsIfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table containing SAVI parameters of each anchor." ::= { saviObjects 2 } saviObjectsIfEntry OBJECT-TYPE SYNTAX SaviObjectsIfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing SAVI running parameters of an anchor." INDEX { saviObjectsIfIPVersion, saviObjectsIfIfIndex } ::= { saviObjectsIfTable 1 } SaviObjectsIfEntry ::= SEQUENCE { saviObjectsIfIPVersion InetVersion, saviObjectsIfIfIndex InterfaceIndex, saviObjectsIfValidationStatus INTEGER, saviObjectsIfTrustStatus INTEGER, saviObjectsIfFilteringNum Unsigned32 } saviObjectsIfIPVersion OBJECT-TYPE SYNTAX InetVersion MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP version " ::= { saviObjectsIfEntry 1 } saviObjectsIfIfIndex OBJECT-TYPE An, et al. Expires June 26, 2011 [Page 11] Internet-Draft SAVI-MIB December 2010 SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex. " ::= { saviObjectsIfEntry 2 } saviObjectsIfValidationStatus OBJECT-TYPE SYNTAX INTEGER { enable(1), disable(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The validation status of the interface. enable(1), check source address. disable(2), don't check source address. " ::= { saviObjectsIfEntry 3 } saviObjectsIfTrustStatus OBJECT-TYPE SYNTAX INTEGER { no-trust(1), dhcp-trust(2), ra-trust(3), savi-savi(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "The trust status of the interface. no-trust(1), discard dhcp adv/reply and ra packet. dhcp-trust(2), permit DHCP adv/relay packet. ra-trust(3), permit ra packet. savi-savi(4), permit any packet. " ::= { saviObjectsIfEntry 4 } saviObjectsIfFilteringNum OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION An, et al. Expires June 26, 2011 [Page 12] Internet-Draft SAVI-MIB December 2010 "The max filtering number of the Interface." ::= { saviObjectsIfEntry 5 } -- Binding Status Table for SAVI protocol saviObjectsBindingTable OBJECT-TYPE SYNTAX SEQUENCE OF SaviObjectsBindingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table containing the state of binding between source address and anchor. " ::= { saviObjects 3 } saviObjectsBindingEntry OBJECT-TYPE SYNTAX SaviObjectsBindingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing the state of binding between source address and anchor. Entries are keyed on the source IP address type, binding type, anchor, and source IP address. " INDEX { saviObjectsBindingIpAddressType, saviObjectsBindingType, saviObjectsBindingIfIndex, saviObjectsBindingIpAddress } ::= { saviObjectsBindingTable 1 } SaviObjectsBindingEntry ::= SEQUENCE { saviObjectsBindingIpAddressType InetAddressType, saviObjectsBindingType INTEGER, saviObjectsBindingIfIndex InterfaceIndex, saviObjectsBindingIpAddress InetAddress, saviObjectsBindingMacAddr MacAddress, saviObjectsBindingState INTEGER, saviObjectsBindingLifetime TimeInterval, saviObjectsBindingRowStatus RowStatus } saviObjectsBindingIpAddressType OBJECT-TYPE SYNTAX InetAddressType An, et al. Expires June 26, 2011 [Page 13] Internet-Draft SAVI-MIB December 2010 MAX-ACCESS not-accessible STATUS current DESCRIPTION "IP address type of the binding source IP." ::= { saviObjectsBindingEntry 1 } saviObjectsBindingType OBJECT-TYPE SYNTAX INTEGER { static(1), slaac(2), dhcp(3) } MAX-ACCESS not-accessible STATUS current DESCRIPTION "IP address assignment methods." ::= { saviObjectsBindingEntry 2 } saviObjectsBindingIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex. " ::= { saviObjectsBindingEntry 3 } saviObjectsBindingIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The binding source IP address" ::= { saviObjectsBindingEntry 4 } saviObjectsBindingMacAddr OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The binding source mac address." ::= { saviObjectsBindingEntry 5 } saviObjectsBindingState OBJECT-TYPE SYNTAX INTEGER { An, et al. Expires June 26, 2011 [Page 14] Internet-Draft SAVI-MIB December 2010 start(1), live(2), detection(3), query(4), bound(5) } MAX-ACCESS read-create STATUS current DESCRIPTION "The state of the binding entry. " ::= { saviObjectsBindingEntry 6 } saviObjectsBindingLifetime OBJECT-TYPE SYNTAX TimeInterval MAX-ACCESS read-create STATUS current DESCRIPTION "The remaining lifetime of the entry. TimeInterval is defined in RFC 2579, it's a period of time, measured in units of 0.01 seconds, and the value is (0..2147483647). If saviObjectsBindingType=static, a value of 2147483647 represents infinity. " ::= { saviObjectsBindingEntry 7 } saviObjectsBindingRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row, by which new entries may be created, or old entries deleted from this table. An Entry can be created or deleted only when saviObjectsBindingType=static. " ::= { saviObjectsBindingEntry 8 } -- Filtering Table for SAVI protocol saviObjectsFilteringTable OBJECT-TYPE SYNTAX SEQUENCE OF SaviObjectsFilteringEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table containing the filtering entries." ::= { saviObjects 4 } An, et al. Expires June 26, 2011 [Page 15] Internet-Draft SAVI-MIB December 2010 saviObjectsFilteringEntry OBJECT-TYPE SYNTAX SaviObjectsFilteringEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry containing the filtering parameters. Entries are keyed on the source IP address type, anchor, and source IP address. " INDEX { saviObjectsFilteringIpAddressType, saviObjectsFilteringIfIndex, saviObjectsFilteringIpAddress } ::= { saviObjectsFilteringTable 1 } SaviObjectsFilteringEntry ::= SEQUENCE { saviObjectsFilteringIpAddressType InetAddressType, saviObjectsFilteringIfIndex InterfaceIndex, saviObjectsFilteringIpAddress InetAddress, saviObjectsFilteringMacAddr MacAddress } saviObjectsFilteringIpAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "IP address type of the filtering source IP" ::= { saviObjectsFilteringEntry 1 } saviObjectsFilteringIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index value that uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of the IF-MIB's ifIndex. " ::= { saviObjectsFilteringEntry 2 } saviObjectsFilteringIpAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION An, et al. Expires June 26, 2011 [Page 16] Internet-Draft SAVI-MIB December 2010 "The filtering source IP address." ::= { saviObjectsFilteringEntry 3 } saviObjectsFilteringMacAddr OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The filtering source mac address." ::= { saviObjectsFilteringEntry 4 } -- Conformance information saviConformance OBJECT IDENTIFIER ::= { saviMIB 2 } saviCompliances OBJECT IDENTIFIER ::= { saviConformance 1 } -- Compliance statements saviCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities which implement SAVI protocol. " MODULE MANDATORY-GROUPS { systemGroup, ifGroup, bindingGroup, filteringGroup } ::= { saviCompliances 1} saviGroups OBJECT IDENTIFIER ::= { saviConformance 2 } --Units of conformance systemGroup OBJECT-GROUP OBJECTS { saviObjectsSystemMode, saviObjectsSystemMaxDadDelay, saviObjectsSystemMaxDadPrepareDelay } STATUS current DESCRIPTION "The system group contains objects corrsponding to savi system parameters. " ::= {saviGroups 1} An, et al. Expires June 26, 2011 [Page 17] Internet-Draft SAVI-MIB December 2010 ifGroup OBJECT-GROUP OBJECTS { saviObjectsIfValidationStatus, saviObjectsIfTrustStatus, saviObjectsIfFilteringNum } STATUS current DESCRIPTION "The if group contains objects corresponding to the savi running parameters of each anchor. " ::= {saviGroups 2} bindingGroup OBJECT-GROUP OBJECTS { saviObjectsBindingMacAddr, saviObjectsBindingState, saviObjectsBindingLifetime, saviObjectsBindingRowStatus } STATUS current DESCRIPTION "The binding group contains the binding information of anchor and soure ip address. " ::= {saviGroups 3} filteringGroup OBJECT-GROUP OBJECTS { saviObjectsFilteringMacAddr } STATUS current DESCRIPTION "The filtering group contains the filtering information of anchor and soure ip address. " ::= {saviGroups 4} END 9. 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 environment without proper protection can have a negative effect on network operations. These are the tables and objects and their An, et al. Expires June 26, 2011 [Page 18] Internet-Draft SAVI-MIB December 2010 sensitivity/vulnerability: o saviObjectsSystemTable - Unauthorized changes to the writable objects under saviObjectsSystemTable MAY disrupt allocation of resources in the network. For example, a device's SAVI system mode be changed by set operation to SAVI-DISABLE will give chance to IP source address spoofing. o saviObjectsIfTable - Unauthorized changes to the writable objects under saviObjectsIfTable MAY disrupt allocation of resources in the network. For example, an anchor's ValidationStatus be changed by set operation to DISABLE will give chance to IP source address spoofing. o saviObjectsBindingTable - Unauthorized changes to the writable objects under this table MAY disrupt allocation of resources in the network. For example, a static binding entry is inserted to the BST will give chance to IP source address spoofing. 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 saviObjectsBindingTable, saviObjectsFilteringTable - The IP address and binding anchor information will be helpful to some attacks. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), 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). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, 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 to the objects only to those principals (users) that have legitimate An, et al. Expires June 26, 2011 [Page 19] Internet-Draft SAVI-MIB December 2010 rights to indeed GET or SET (change/create/delete) them. 10. IANA Considerations The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry: Descriptor OBJECT IDENTIFIER value ---------- ----------------------- SAVI-MIB { ip XXX } 11. Contributors 12. References 12.1. Normative References [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. [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. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005. 12.2. Informative References [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 2223, October 1997. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. An, et al. Expires June 26, 2011 [Page 20] Internet-Draft SAVI-MIB December 2010 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, June 1999. [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB Documents", BCP 111, RFC 4181, September 2005. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC4293] Routhier, S., "Management Information Base for the Internet Protocol (IP)", RFC 4293, April 2006. 12.3. URL References [idguidelines] IETF Internet Drafts editor, "http://www.ietf.org/ietf/1id-guidelines.txt". [idnits] IETF Internet Drafts editor, "http://www.ietf.org/ID-Checklist.html". [xml2rfc] XML2RFC tools and documentation, "http://xml.resource.org". [ops] the IETF OPS Area, "http://www.ops.ietf.org". [ietf] IETF Tools Team, "http://tools.ietf.org". [SAVI-framework] Jianping Wu, "Source Address Validation Improvement Protocol Framework". [SAVI-DHCP] J. Bi, J. Wu, "SAVI Solution for DHCP". Appendix A. Change Log Note to RFC Editor: if this document does not obsolete an existing RFC, please remove this appendix before publication as an RFC. Appendix B. Open Issues Note to RFC Editor: please remove this appendix before publication as an RFC. An, et al. Expires June 26, 2011 [Page 21] Internet-Draft SAVI-MIB December 2010 Authors' Addresses Changqing An CERNET Network Research Center, Tsinghua University Beijing 100084 China Phone: +86 10 62603113 EMail: acq@cernet.edu.cn Jiahai Yang CERNET Network Research Center, Tsinghua University Beijing 100084 China Phone: +86 10 62783492 EMail: yang@cernet.edu.cn Jianping Wu CERNET Network Research Center, Tsinghua University Beijing 100084 China EMail: jianping@cernet.edu.cn Jun Bi CERNET Network Research Center, Tsinghua University Beijing 100084 China EMail: junbi@cernet.edu.cn An, et al. Expires June 26, 2011 [Page 22]