One document matched: draft-cui-softwire-mesh-mib-00.txt
Softwire Y. Cui
Internet-Draft J. Dong
Intended status: Informational Tsinghua University
Expires: September 8, 2011 March 7, 2011
Softwire Mesh Management Information Base(MIB)
draft-cui-softwire-mesh-mib-00
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines
objects for managing softwire mesh.
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 September 8, 2011.
Copyright Notice
Copyright (c) 2011 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
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Cui & Dong Expires September 8, 2011 [Page 1]
Internet-Draft Softwire Mesh MIB March 2011
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4
6.2. The swmInfo Subtree . . . . . . . . . . . . . . . . . . . 4
6.3. The swmVIfInfo Subtree . . . . . . . . . . . . . . . . . . 4
6.4. The swmNLRINHInfo Subtree . . . . . . . . . . . . . . . . 4
6.5. The swmBGPNeighInfo Subtree . . . . . . . . . . . . . . . 4
6.6. The swmConformance Subtree . . . . . . . . . . . . . . . . 4
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 4
7.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 4
7.2. Relationship to the IF-MIB . . . . . . . . . . . . . . . . 5
7.3. MIB modules required for IMPORTS . . . . . . . . . . . . . 5
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
9. Security Considerations . . . . . . . . . . . . . . . . . . . 21
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
11.1. Normative References . . . . . . . . . . . . . . . . . . . 22
11.2. Informative References . . . . . . . . . . . . . . . . . . 22
11.3. URL References . . . . . . . . . . . . . . . . . . . . . . 23
Cui & Dong Expires September 8, 2011 [Page 2]
Internet-Draft Softwire Mesh MIB March 2011
1. Introduction
Softwire mesh framework RFC 5565 [RFC5565]is a tunneling mechanism
which enables connectivity between islands of IPv4, IPv6 or dual-
stack networks across single IPv4 or IPv6 backbone networks. In
softwire mesh solution, extended multiprotocol-BGP (MP-BGP)is used to
set up tunnels and advertise prefixes among address family border
routers (AFBRs).
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols. In particular it defines
objects for managing the softwire mesh.
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. Terminology
This document uses terminology from the softwire mesh framework
[RFC5565].
4. 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].
5. Overview
The softwire mesh MIB provides a way to configure and manage the
softwire mesh objects through SNMP. It's a basis for manage and
control softwire mesh framework.
Cui & Dong Expires September 8, 2011 [Page 3]
Internet-Draft Softwire Mesh MIB March 2011
6. Structure of the MIB Module
6.1. Textual Conventions
The following textual conventions are defined:
swmTunnelType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for tunnel type will be used."
SYNTAX INTEGER {
gre(1), -- GRE encapsulation
l2tpv3(2), -- L2TPv3 encapsulation
ip-ip(3) -- IP-IP
}
6.2. The swmInfo Subtree
The subtree provides basic softwire mesh information about the
router.
6.3. The swmVIfInfo Subtree
The subtree provides softwire mesh virtual interface information
about the router.
6.4. The swmNLRINHInfo Subtree
The subtree provides softwire mesh NLRI-NH information about the
router.
6.5. The swmBGPNeighInfo Subtree
The subtree provides softwire mesh NLRI-NH information about the
router.
6.6. The swmConformance Subtree
The subtree provides conformance information of MIB objects.
7. Relationship to Other MIB Modules
7.1. Relationship to the SNMPv2-MIB
The 'system' group in the SNMPv2-MIB [RFC3418] is defined as being
mandatory for all systems, and the objects apply to the entity as a
whole. The 'system' group provides identification of the management
entity and certain other system-wide data. The softwire-mesh-MIB
Cui & Dong Expires September 8, 2011 [Page 4]
Internet-Draft Softwire Mesh MIB March 2011
does not duplicate those objects.
7.2. Relationship to the IF-MIB
The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing softwire mesh that
are modeled as virtual interfaces.
7.3. MIB modules required for IMPORTS
The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and
INET-ADDRESS-MIB [RFC4001].
8. Definitions
SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN
IMPORTS
TruthValue, TEXTUAL-CONVENTION
TimeStamp
FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, mib-2, Unsigned32, Counter32,
Counter64
FROM SNMPv2-SMI
InterfaceIndex
FROM IF-MIB
InetAddressIPv4, InetAddressIPv6, InetAddressPrefixLength
FROM INET-ADDRESS-MIB
swmMIB MODULE-IDENTITY
LAST-UPDATED "201103040000Z" -- Mar 4, 2011
ORGANIZATION "Softwire Working Group"
CONTACT-INFO "
Yong Cui
Email: yong@csnet1.cs.tsinghua.edu.cn
Jiang Dong
Email: dongjiang@csnet1.cs.tsinghua.edu.cn
Cui & Dong Expires September 8, 2011 [Page 5]
Internet-Draft Softwire Mesh MIB March 2011
Email comments directly to ther softwire WG Mailing
List at softwires@ietf.org
"
DESCRIPTION
"This MIB module contains managed object definitions for
the softwire mesh framework."
REVISION "201103040000Z"
DESCRIPTION
"draft-00 version"
::= {transmission xxx} --xxx to be replaced with correct value
-- Textual conventions
swmTunnelType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the TC for tunnel type will be used."
SYNTAX INTEGER {
gre(1), -- GRE encapsulation
l2tpv3(2), -- L2TPv3 encapsulation
ip-ip(3) -- IP-IP
}
-- Top level components of this MIB
-- Tables, Scalars
swmInfo OBJECT IDENTIFIER
::= { swmMIB 1 }
swmVIfInfo OBJECT IDENTIFIER
::= { swmMIB 2 }
swmNLRINHInfo OBJECT IDENTIFIER
::= { swmMIB 3 }
swmBGPNeighInfo OBJECT IDENTIFIER
::= { swmMIB 4 }
-- Conformance
swmConformance OBJECT IDENTIFIER
::= { swmMIB 5 }
-- swmInfo
-- swmState
swmState OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
Cui & Dong Expires September 8, 2011 [Page 6]
Internet-Draft Softwire Mesh MIB March 2011
DESCRIPTION
"Represents whether the mesh function of the router has
been started. If the BGP open is sent and softwire
mesh capability is negotiated, the mesh function could
be considered to be started."
::= { swmInfo 1 }
-- softwire mesh lastchange
swmLastChange OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the swmState change
its state."
::= { swmInfo 2 }
-- End of swmInfo
-- softwire Mesh Virtual Interface information
-- softwire Mesh Virtual Interface Tunnel information
swmVIfTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF swmVIFTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and config the softwire
mesh virtual inerface tunnel information. It shows what
kind of tunnels can be used in the router."
::= { swmVIfInfo 1 }
swmVIfTunnelEntry OBJECT-TYPE
SYNTAX swm4over6VIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display and config the softwire
mesh virtual inerface tunnel information."
INDEX { swmVIfTunnelType }
::= { swmVIfTunnelTable 1 }
swmVIfTunnelEntry ::=
SEQUENCE {
swmVIfTunnelType swmTunnelType,
}
Cui & Dong Expires September 8, 2011 [Page 7]
Internet-Draft Softwire Mesh MIB March 2011
swmVIfTunnelType OBJECT-TYPE
SYNTAX swmTunnelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the kind of tunneling type that the server
supports."
::= { swmVIfTunnelEntry 1 }
-- End of softwire Mesh Virtual Interface
-- softwire Mesh 4over6 Virtual Interface Table
swm4over6VIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm4over6VIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the
softwire mesh 4over6 virtual inerface information.
This table is used to count the 4over6 information."
::= { swmVIfInfo 2 }
swm4over6VIfEntry OBJECT-TYPE
SYNTAX swm4over6VIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display and control the softwire
mesh 4over6 virtual inerface information."
INDEX { swm4over6VIfIndex }
::= { swm4over6VIfTable 1 }
swm4over6VIfEntry ::=
SEQUENCE {
swm4over6VIfIndex InterfaceIndex,
swm4over6VIfInIPv4Packets Counter32,
swm4over6VIfOutIPv6Packets Counter32,
swm4over6VIfInIPv6Packets Counter32,
swm4over6VIfOutIPv4Packets Counter32,
swm4over6VIfInIPv4Bytes Counter64,
swm4over6VIfOutIPv6Bytes Counter64,
swm4over6VIfInIPv6Bytes Counter64,
swm4over6VIfOutIPv6Bytes Counter64,
swm4over6VIfMtu Unsigned32
}
swm4over6VIfIndex OBJECT-TYPE
Cui & Dong Expires September 8, 2011 [Page 8]
Internet-Draft Softwire Mesh MIB March 2011
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique index for the conceptual row indentifying a
softwire mesh 4over6 virtural information within this
table."
::= { swm4over6VIfEntry 1 }
swm4over6VIfInIPv4Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv4 Packets recieved by the
virtual interface. These IPv4 packets will be
encapsulated with an IPv6 header according to 4over6
encapsulation table. If these packets need to be
fragmented, the number counted here is the packets
after fragmentation."
::= { swm4over6VIfEntry 2 }
swm4over6VIfOutIPv6Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Packets send by the virtual
interface. These IPv6 packets are encapsulated packets
from IPv4 packets according to 4over6 encapsulation
table."
::= { swm4over6VIfEntry 3 }
swm4over6VIfInIPv6Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Packets recieved by the
virtual interface. These IPv6 packets will be
decapsulated to IPv4 packets."
::= { swm4over6VIfEntry 4 }
swm4over6VIfOutIPv4Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Cui & Dong Expires September 8, 2011 [Page 9]
Internet-Draft Softwire Mesh MIB March 2011
"Represents number of IPv4 Packets send by the virtual
interface. These IPv4 packets are decapsulated packets
from encapsulated IPv6 packets"
::= { swm4over6VIfEntry 5 }
swm4over6VIfInIPv4Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv4 Bytes recieved by the virtual
interface. These IPv4 packets will be encapsulated with
an IPv6 header according to 4over6 encapsulation table."
::= { swm4over6VIfEntry 6 }
swm4over6VIfOutIPv6Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Bytes send by the virtual
interface. These IPv6 packets are encapsulated packets
from IPv4 packets according to 4over6 encapsulation
table."
::= { swm4over6VIfEntry 7 }
swm4over6VIfInIPv6Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Bytes recieved by the virtual
interface. These IPv6 packets will be decapsulated to
IPv4 packets."
::= { swm4over6VIfEntry 8 }
swm4over6VIfOutIPv4Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv4 Bytes send by the virtual
interface. These IPv4 packets are decapsulated packets
from encapsulated IPv6 packets"
::= { swm4over6VIfEntry 9 }
swm4over6VIfMtu OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
Cui & Dong Expires September 8, 2011 [Page 10]
Internet-Draft Softwire Mesh MIB March 2011
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Represents the 4over6 virtual interface MTU."
DEFVAL {1460}
::= { swm4over6VIfEntry 10 }
-- End of softwire Mesh 4over6 Virtual Interface Table
-- softwire Mesh 6over4 Virtual Interface Table
swm6over4VIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm6over4VIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the
softwire mesh 6over4 virtual inerface information.
This table is used to count the 6over4 information."
::= { swmVIfInfo 3 }
swm6over4VIfEntry OBJECT-TYPE
SYNTAX swm6over4VIfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display and control the softwire
mesh 6over4 virtual inerface information."
INDEX { swm6over4VIfIndex }
::= { swm6over4VIfTable 1 }
swm6over4VIfEntry ::=
SEQUENCE {
swm6over4VIfIndex InterfaceIndex,
swm6over4VIfInIPv6Packets Counter32,
swm6over4VIfOutIPv4Packets Counter32,
swm6over4VIfInIPv4Packets Counter32,
swm6over4VIfOutIPv6Packets Counter32,
swm6over4VIfInIPv6Bytes Counter64,
swm6over4VIfOutIPv4Bytes Counter64,
swm6over4VIfInIPv4Bytes Counter64,
swm6over4VIfOutIPv4Bytes Counter64,
swm6over4VIfMtu Unsigned32
}
swm6over4VIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS not-accessible
Cui & Dong Expires September 8, 2011 [Page 11]
Internet-Draft Softwire Mesh MIB March 2011
STATUS current
DESCRIPTION
"A unique index for the conceptual row indentifying a
softwire mesh 6over4 virtural information within this
table."
::= { swm6over4VIfEntry 1 }
swm6over4VIfInIPv6Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Packets recieved by the
virtual interface. These IPv6 packets will be
encapsulated with an IPv4 header according to 6over4
encapsulation table. If these packets need to be
fragmented, the number counted here is the IPv6 packets
after fragmentation."
::= { swm6over4VIfEntry 2 }
swm6over4VIfOutIPv4Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv4 Packets send by the virtual
interface. These IPv4 packets are encapsulated packets
from IPv6 packets according to 6over4 encapsulation
table."
::= { swm6over4VIfEntry 3 }
swm6over4VIfInIPv4Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv4 Packets recieved by the
virtual interface. These IPv4 packets will be
decapsulated to IPv6 packets according to softwire mesh
framework."
::= { swm6over4VIfEntry 4 }
swm6over4VIfOutIPv6Packets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Packets send by the virtual
Cui & Dong Expires September 8, 2011 [Page 12]
Internet-Draft Softwire Mesh MIB March 2011
interface. These IPv6 packets are decapsulated packets
from encapsulated IPv4 packets"
::= { swm6over4VIfEntry 5 }
swm6over4VIfInIPv6Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Bytes recieved by the virtual
interface. These IPv6 packets will be encapsulated with
an IPv4 header according to 6over4 encapsulation table."
::= { swm6over4VIfEntry 6 }
swm6over4VIfOutIPv4Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv4 Bytes send by the virtual
interface. These IPv4 packets are encapsulated packets
from IPv6 packets according to 6over4 encapsulation
table."
::= { swm6over4VIfEntry 7 }
swm6over4VIfInIPv4Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv4 Bytes recieved by the virtual
interface. These IPv4 packets will be decapsulated to
IPv6 packets."
::= { swm6over4VIfEntry 8 }
swm6over4VIfOutIPv6Bytes OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents number of IPv6 Bytes send by the virtual
interface. These IPv6 packets are decapsulated packets
from encapsulated IPv4 packets"
::= { swm6over4VIfEntry 9 }
swm6over4VIfMtu OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-write
Cui & Dong Expires September 8, 2011 [Page 13]
Internet-Draft Softwire Mesh MIB March 2011
STATUS current
DESCRIPTION
"Represents the 6over4 virtual interface MTU."
DEFVAL {1460}
::= { swm6over4VIfEntry 10 }
-- End of softwire Mesh 6over4 Virtual Interface Table
--swmNLRINHInfo
-- swm4over6NLRINHTable
swm4over6NLRINHTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm4over6NLRINHEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the
softwire mesh 4over6 NLRI-NH information."
::= { swmNLRINHInfo 1 }
swm4over6NLRINHEntry OBJECT-TYPE
SYNTAX swm4over6NLRINHEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display and control the
softwire mesh 4over6 encapsulation information."
INDEX { swm4over6NLRINHIPv4Dst,
swm4over6NLRINHIPv4Mask
}
::= { swm4over6NLRINHTable 1 }
swm4over6NLRINHEntry ::=
SEQUENCE {
swm4over6NLRINHIPv4Dst InetAddressIPv4,
swm4over6NLRINHIPv4Mask InetAddressPrefixLength,
swm4over6NLRINHIPv6Dst InetAddressIPv6
}
swm4over6NLRINHIPv4Dst OBJECT-TYPE
SYNTAX InetAddressIPv4
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The destination IPv4 address that decide which
destination IPv6 address will be encapsulated."
::= { swm4over6NLRINHEntry 1 }
Cui & Dong Expires September 8, 2011 [Page 14]
Internet-Draft Softwire Mesh MIB March 2011
swm4over6NLRINHIPv4Mask OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The prefix length of destination IPv4 address."
::= { swm4over6NLRINHEntry 2 }
swm4over6NLRINHIPv6Dst OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The destination IPv6 address that will be encapsulated
according to the destination IPv4 address."
::= { swm4over6NLRINHEntry 3 }
-- End of swm4over6NLRINHTable
-- swm6over4NLRINHTable
swm6over4NLRINHTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm6over4NLRINHEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the
softwire mesh 6over4 encapsulation information."
::= { swmNLRINHInfo 2 }
swm6over4NLRINHEntry OBJECT-TYPE
SYNTAX swm6over4NLRINHEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display and control the softwire
mesh 6over4 encapsulation information."
INDEX { swm6over4NLRINHIPv6Dst,
swm6over4NLRINHIPv6Mask
}
::= { swm6over4NLRINHTable 1 }
swm6over4NLRINHEntry ::=
SEQUENCE {
swm6over4NLRINHIPv6Dst InetAddressIPv6,
swm6over4NLRINHIPv6Mask InetAddressPrefixLength,
swm6over4NLRINHIPv4Dst InetAddressIPv4
}
Cui & Dong Expires September 8, 2011 [Page 15]
Internet-Draft Softwire Mesh MIB March 2011
swm6over4NLRINHIPv6Dst OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The destination IPv6 address that decide which
destination IPv4 address will be encapsulated."
::= { swm6over4NLRINHEntry 1 }
swm6over4NLRINHIPv6Mask OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The prefix length of destination IPv6 address."
::= { swm6over4NLRINHEntry 2 }
swm6over4NLRINHIPv4Dst OBJECT-TYPE
SYNTAX InetAddressIPv4
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The destination IPv4 address that will be encapsulated
according to the destination IPv6 address."
::= { swm6over4NLRINHEntry 3 }
-- End of swm6over4NLRINHTable
-- swmBGPNeighInfo
-- swm4over6BGPNeighTable
swm4over6BGPNeighTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm4over6BGPNeighEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the
softwire mesh 4over6 BGP neighbor information."
::= { swmBGPNeighInfo 1 }
swm4over6BGPNeighEntry OBJECT-TYPE
SYNTAX swm4over6BGPNeighEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the softwire mesh 4over6
BGP neighbor information."
Cui & Dong Expires September 8, 2011 [Page 16]
Internet-Draft Softwire Mesh MIB March 2011
INDEX { swm4over6BGPNeighIPv6Address }
::= { swm4over6BGPNeighTable 1 }
swm4over6BGPNeighEntry ::=
SEQUENCE {
swm4over6BGPNeighIPv6Address InetAddressIPv6
swm4over6BGPNeighTunnelTable swmTunnelType
}
swm4over6BGPNeighIPv6Address OBJECT-TYPE
SYNTAX InetAddressIPv6
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IPv6 address of the router's 4over6 BGP neighbor."
::= { swm4over6BGPNeighEntry 1 }
-- softwire Mesh 4over6 bgp neighbor's Tunnel information
swm4over6BGPNeighTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm4over6BGPNeighTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display softwire mesh virtual
inerface tunnel information of the 4over6 bgp neighbor."
::= { swm4over6BGPNeighEntry 2 }
swm4over6BGPNeighTunnelEntry OBJECT-TYPE
SYNTAX swm4over6BGPNeighTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the softwire mesh virtual
inerface tunnel information of neighbor."
INDEX { swm4over6BGPNeighTunnelType }
::= { swm4over6BGPNeighTunnelTable 1 }
swm4over6BGPNeighTunnelEntry ::=
SEQUENCE {
swm4over6BGPNeighTunnelType swmTunnelType,
}
swm4over6BGPNeighTunnelType OBJECT-TYPE
SYNTAX swmTunnelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Cui & Dong Expires September 8, 2011 [Page 17]
Internet-Draft Softwire Mesh MIB March 2011
"Represents the kind of tunneling type that the server's
4over6 BGP neighbor supports."
::= { swm4over6BGPNeighTunnelEntry 1 }
-- End of softwire Mesh 4over6 bgp neighbor's Tunnel information
-- End of swm4over6BGPNeighTable
-- swm6over4BGPNeighTable
swm6over4BGPNeighTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm6over4BGPNeighEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the
softwire mesh 6over4 BGP neighbor information."
::= { swmBGPNeighInfo 2 }
swm6over4BGPNeighEntry OBJECT-TYPE
SYNTAX swm6over4BGPNeighEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the softwire mesh 6over4
BGP neighbor information."
INDEX { swm6over4BGPNeighIPv4Address }
::= { swm6over4BGPNeighTable 1 }
swm6over4BGPNeighEntry ::=
SEQUENCE {
swm6over4BGPNeighIPv4Address InetAddressIPv6
swm6over4BGPNeighTunnelTable swmTunnelType
}
swm6over4BGPNeighIPv4Address OBJECT-TYPE
SYNTAX InetAddressIPv4
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IPv4 address of the router's 6over4 BGP neighbor."
::= { swm6over4BGPNeighEntry 1 }
-- softwire Mesh 6over4 bgp neighbor's Tunnel information
swm6over4BGPNeighTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF swm6over4BGPNeighTunnelEntry
MAX-ACCESS not-accessible
Cui & Dong Expires September 8, 2011 [Page 18]
Internet-Draft Softwire Mesh MIB March 2011
STATUS current
DESCRIPTION
"A table of objects that display softwire mesh virtual
inerface tunnel information of the 6over4 bgp neighbor."
::= { swm6over4BGPNeighEntry 2 }
swm6over4BGPNeighTunnelEntry OBJECT-TYPE
SYNTAX swm6over4BGPNeighTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the softwire mesh virtual
inerface tunnel information of 6over4 bgp neighbor."
INDEX { swm6over6BGPNeighTunnelType }
::= { swm6over4BGPNeighTunnelTable 1 }
swm6over4BGPNeighTunnelEntry ::=
SEQUENCE {
swm6over4BGPNeighTunnelType swmTunnelType,
}
swm6over4BGPNeighTunnelType OBJECT-TYPE
SYNTAX swmTunnelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the kind of tunneling type that the server's
6over4 BGP neighbor supports."
::= { swm6over4BGPNeighTunnelEntry 1 }
-- End of softwire Mesh 6over4 bgp neighbor's Tunnel information
-- End of swm6over4BGPNeighTable
-- Module Conformance Statement
swmGroups OBJECT IDENTIFIER
::= { swmConformance 1 }
swmCompliances OBJECT IDENTIFIER
::= { swmConformance 2 }
swmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the softwire
mesh MIB."
Cui & Dong Expires September 8, 2011 [Page 19]
Internet-Draft Softwire Mesh MIB March 2011
MODULE -- this module
MANDATORY-GROUPS { swmInfoGroup,
swmVIfGroup,
swmNLRINHGroup,
swmBGPNeighGroup }
::= { swmCompliances 1 }
swmInfoGroup OBJECT-GROUP
OBJECTS {
swmState,
swmLastChange
}
STATUS current
DESCRIPTION
"The collection of objects which are used to show
basic softwire mesh information."
::= { swmGroups 1 }
swmVIfGroup OBJECT-GROUP
OBJECTS {
swmVIfTunnelType
swm4over6VIfIndex,
swm4over6VIfInIPv4Packets,
swm4over6VIfOutIPv6Packets,
swm4over6VIfInIPv6Packets,
swm4over6VIfOutIPv4Packets,
swm4over6VIfInIPv4Bytes,
swm4over6VIfOutIPv6Bytes,
swm4over6VIfInIPv6Bytes,
swm4over6VIfOutIPv6Bytes,
swm4over6VIfMtu,
swm6over4VIfIndex,
swm6over4VIfInIPv6Packets,
swm6over4VIfOutIPv4Packets,
swm6over4VIfInIPv4Packets,
swm6over4VIfOutIPv6Packets,
swm6over4VIfInIPv6Bytes,
swm6over4VIfOutIPv4Bytes,
swm6over4VIfInIPv4Bytes,
swm6over4VIfOutIPv4Bytes,
swm6over4VIfMtu
}
STATUS current
DESCRIPTION
"The collection of objects which are used to display
and control softwire mesh virtual interface."
::= { swmGroups 2 }
Cui & Dong Expires September 8, 2011 [Page 20]
Internet-Draft Softwire Mesh MIB March 2011
swmNLRINHGroup OBJECT-GROUP
OBJECTS {
swm4over6NLRINHIPv4Dst,
swm4over6NLRINHIPv4Mask,
swm4over6NLRINHIPv6Dst,
swm6over4NLRINHIPv6Dst,
swm6over4NLRINHIPv6Mask,
swm6over4NLRINHIPv4Dst
}
STATUS current
DESCRIPTION
"The collection of objects which are used to display
and control softwire mesh encapsulation information."
::= { swmGroups 3 }
swmBGPNeighGroup OBJECT-GROUP
OBJECTS {
swm4over6BGPNeighIPv6Address,
swm4over6BGPNeighTunnelType,
swm6over4BGPNeighIPv4Address,
swm6over4BGPNeighTunnelType
}
STATUS current
DESCRIPTION
"The collection of objects which are used to display
softwire mesh BGP neighbor information."
::= { swmGroups 4 }
END
9. Security Considerations
TBD
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
---------- -----------------------
swmMIB { transmission XXX }
11. References
Cui & Dong Expires September 8, 2011 [Page 21]
Internet-Draft Softwire Mesh MIB March 2011
11.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.
[RFC4925] Li, X., Dawkins, S., Ward, D., and A. Durand,
"Softwire Problem Statement", RFC 4925, July 2007.
[RFC5512] Mohapatra, P. and E. Rosen, "The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the
BGP Tunnel Encapsulation Attribute", RFC 5512,
April 2009.
[RFC5565] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire
Mesh Framework", RFC 5565, June 2009.
11.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.
[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.
Cui & Dong Expires September 8, 2011 [Page 22]
Internet-Draft Softwire Mesh MIB March 2011
11.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".
Authors' Addresses
Yong Cui
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-6260-3059
EMail: yong@csnet1.cs.tsinghua.edu.cn
Jiang Dong
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
P.R.China
Phone: +86-10-6278-5822
EMail: dongjiang@csnet1.cs.tsinghua.edu.cn
Cui & Dong Expires September 8, 2011 [Page 23]
| PAFTECH AB 2003-2026 | 2026-04-24 08:10:22 |