< draft-ietf-ipfix-rfc5815bis-02.txt   draft-ietf-ipfix-rfc5815bis-03.txt >
IPFIX Working Group T. Dietz, Ed. IPFIX Working Group T. Dietz, Ed.
Internet-Draft NEC Europe, Ltd. Internet-Draft NEC Europe, Ltd.
Intended status: Standards Track A. Kobayashi Intended status: Standards Track A. Kobayashi
Expires: September 10, 2012 NTT PF Labs. Expires: September 27, 2012 NTT PF Labs.
B. Claise B. Claise
Cisco Systems, Inc. Cisco Systems, Inc.
G. Muenz G. Muenz
Technische Universitaet Muenchen Technische Universitaet Muenchen
March 9, 2012 March 26, 2012
Definitions of Managed Objects for IP Flow Information Export Definitions of Managed Objects for IP Flow Information Export
draft-ietf-ipfix-rfc5815bis-02.txt draft-ietf-ipfix-rfc5815bis-03.txt
Abstract Abstract
This document defines managed objects for IP Flow Information eXport This document defines managed objects for IP Flow Information eXport
(IPFIX). These objects provide information for monitoring IPFIX (IPFIX). These objects provide information for monitoring IPFIX
Exporters and IPFIX Collectors including the basic configuration Exporters and IPFIX Collectors including the basic configuration
information. information.
Status of this Memo Status of this Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 10, 2012. This Internet-Draft will expire on September 27, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 20
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IPFIX Documents Overview . . . . . . . . . . . . . . . . . . . 4 2. IPFIX Documents Overview . . . . . . . . . . . . . . . . . . . 4
3. The Internet-Standard Management Framework . . . . . . . . . . 5 3. The Internet-Standard Management Framework . . . . . . . . . . 5
4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Structure of the IPFIX MIB . . . . . . . . . . . . . . . . . . 7 5. Structure of the IPFIX MIB . . . . . . . . . . . . . . . . . . 7
5.1. The Transport Session Table . . . . . . . . . . . . . . . 7 5.1. The Transport Session Table . . . . . . . . . . . . . . . 7
5.2. The Template Table . . . . . . . . . . . . . . . . . . . . 9 5.2. The Template Table . . . . . . . . . . . . . . . . . . . . 9
5.3. The Template Definition Table . . . . . . . . . . . . . . 11 5.3. The Template Definition Table . . . . . . . . . . . . . . 11
5.4. The Export Table . . . . . . . . . . . . . . . . . . . . . 12 5.4. The Export Table . . . . . . . . . . . . . . . . . . . . . 12
5.5. The Metering Process Table . . . . . . . . . . . . . . . . 14 5.5. The Metering Process Table . . . . . . . . . . . . . . . . 15
5.6. The Observation Point Table . . . . . . . . . . . . . . . 15 5.6. The Observation Point Table . . . . . . . . . . . . . . . 16
5.7. The Selection Process Table . . . . . . . . . . . . . . . 16 5.7. The Selection Process Table . . . . . . . . . . . . . . . 17
5.8. The Statistical Tables . . . . . . . . . . . . . . . . . . 16 5.8. The Statistical Tables . . . . . . . . . . . . . . . . . . 17
5.8.1. The Transport Session Statistical Table . . . . . . . 17 5.8.1. The Transport Session Statistical Table . . . . . . . 18
5.8.2. The Template Statistical Table . . . . . . . . . . . . 17 5.8.2. The Template Statistical Table . . . . . . . . . . . . 18
5.8.3. The Metering Process Statistical Table . . . . . . . . 17 5.8.3. The Metering Process Statistical Table . . . . . . . . 18
5.8.4. The Selection Process Statistical Table . . . . . . . 17 5.8.4. The Selection Process Statistical Table . . . . . . . 18
6. Structure of the IPFIX SELECTOR MIB . . . . . . . . . . . . . 18 6. Structure of the IPFIX SELECTOR MIB . . . . . . . . . . . . . 19
6.1. The Selector Functions . . . . . . . . . . . . . . . . . . 18 6.1. The Selector Functions . . . . . . . . . . . . . . . . . . 19
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 21 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 22
7.1. Relationship to the ENTITY MIB and Interface MIB . . . . . 21 7.1. Relationship to the ENTITY MIB and Interface MIB . . . . . 22
7.2. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 21 7.2. MIB Modules Required for IMPORTS . . . . . . . . . . . . . 22
8. MIB Definitions . . . . . . . . . . . . . . . . . . . . . . . 22 8. MIB Definitions . . . . . . . . . . . . . . . . . . . . . . . 23
8.1. IPFIX MIB Definition . . . . . . . . . . . . . . . . . . . 22 8.1. IPFIX MIB Definition . . . . . . . . . . . . . . . . . . . 23
8.2. IPFIX SELECTOR MIB Definition . . . . . . . . . . . . . . 57 8.2. IPFIX SELECTOR MIB Definition . . . . . . . . . . . . . . 58
9. Security Considerations . . . . . . . . . . . . . . . . . . . 62 9. Security Considerations . . . . . . . . . . . . . . . . . . . 63
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 64 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 65 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 66
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 66 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 67
12.1. Normative References . . . . . . . . . . . . . . . . . . . 66 12.1. Normative References . . . . . . . . . . . . . . . . . . . 67
12.2. Informative References . . . . . . . . . . . . . . . . . . 67 12.2. Informative References . . . . . . . . . . . . . . . . . . 68
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 69
1. Introduction 1. Introduction
This document defines two MIB modules for monitoring IP Flow This document defines two MIB modules for monitoring IP Flow
Information eXport (IPFIX) Devices including Exporters and Information eXport (IPFIX) Devices including Exporters and
Collectors. Most of the objects defined by the IPFIX MIB module MUST Collectors. While most of the objects defined by the IPFIX MIB
be implemented. Some objects MAY be implemented corresponding to the module must be implemented, some objects may be implemented
functionality implemented in the equipment. Since the IPFIX corresponding to the functionality implemented in the equipment.
architecture [RFC5470] foresees the possibility of using Filtering Since the IPFIX architecture [RFC5470] foresees the possibility of
and/or Sampling functions to reduce the data volume, this document using Filtering and/or Sampling functions to reduce the data volume,
also provides the IPFIX SELECTOR MIB module, which contains the this document also provides the IPFIX SELECTOR MIB module, which
standardized selection methods and is controlled by IANA. The full contains the standardized selection methods and is controlled by
configuration of the IPFIX Metering Process is out of the scope of IANA. The full configuration of the IPFIX Metering Process is out of
these MIB modules. the scope of these MIB modules.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in RFC "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119]. 2119 [RFC2119].
2. IPFIX Documents Overview 2. IPFIX Documents Overview
The IPFIX protocol provides network administrators with access to IP The IPFIX protocol provides network administrators with access to IP
Flow information. The architecture for the export of measured IP Flow information. The architecture for the export of measured IP
skipping to change at page 14, line 36 skipping to change at page 14, line 36
+- ipfixExportMemberType (2) = 1 (primary) +- ipfixExportMemberType (2) = 1 (primary)
The example shows that the Exporter uses the Metering Process Cache The example shows that the Exporter uses the Metering Process Cache
9, explained below, to export IPFIX Data Records for the Transport 9, explained below, to export IPFIX Data Records for the Transport
Sessions 5 and 11. The Templates 257 and 264 defined above are Sessions 5 and 11. The Templates 257 and 264 defined above are
exported within Transport Session 5 as primary, while the secondary exported within Transport Session 5 as primary, while the secondary
Transport Session is 11. The Templates 273 and 289 are exported Transport Session is 11. The Templates 273 and 289 are exported
within Transport Session 11 as primary, while the secondary Transport within Transport Session 11 as primary, while the secondary Transport
Session is 5. Session is 5.
Here are the steps required by a manager in order to understand what
is/are the backups (if any) for Template Records exported from a
specific Exporter to a specific Collector:
1. Lookup the Collector IP address in the
ipfixTransportSessionDestinationAddress object (in the
ipfixTransportSessionTable).
2. From the same row, double check the Exporter IP address in the
ipfixTransportSessionSourceAddress object.
3. From the same row, write down the ipfixTransportSessionIndex
value.
4. Use that ipfixTransportSessionIndex value in the
ipfixTemplateTable, and look up the pairs of
(ipfixTemplateObservationDomainId, ipfixTemplateId). For there,
the manager deduces the Template Record(s) (ipfixTemplateId),
exported from the Observation Domain(s)
(ipfixTemplateObservationDomainId) on the tracked Exporter
(ipfixTransportSessionSourceAddress) to the tracked Collector
(ipfixTransportSessionDestinationAddress).
5. Reusing the same ipfixTransportSessionIndex in ipfixExportTable,
lookup the table for a value of ipfixExportMemberType equals to
"primary". Note that they could be multiple entries for which
the ipfixExportMemberType equals to "primary" in the
ipfixExportTable, so multiple iterations might be required until
the correct value of ipfixTransportSessionIndex is found.
6. From the same row, write down the ipfixExportIndex value.
7. In the ipfixExportTable, under the same three indexes values
(ipfixExportIndex, ipfixMeteringProcessCacheId, and
ipfixTransportSessionIndex), lookup the entries for which
ipfixExportMemberType is different than "primary". Write down
the associated ipfixTransportSessionIndex value.
8. From the ipfixTransportSessionTable, look up the Transport
Session details for this ipfixTransportSessionIndex value. For
example, the secondary Collector IP address and port
(ipfixTransportSessionDestinationAddress and
ipfixTransportSessionSourcePort).
5.5. The Metering Process Table 5.5. The Metering Process Table
The Metering Process, as defined in [RFC5101], consists of a set of The Metering Process, as defined in [RFC5101], consists of a set of
functions. Maintaining the Flow Records is one of them. This functions. Maintaining the Flow Records is one of them. This
function is responsible for passing the Flow Records to the Exporting function is responsible for passing the Flow Records to the Exporting
Process and also for detecting Flow expiration. The Flow Records Process and also for detecting Flow expiration. The Flow Records
that are maintained by the Metering Process can be grouped by the that are maintained by the Metering Process can be grouped by the
Observation Points at which they are observed. The instance that Observation Points at which they are observed. The instance that
maintains such a group of Flow Records is a kind of cache. For this maintains such a group of Flow Records is a kind of cache. For this
reason, the Metering Process table (ipfixMeteringProcessTable) is reason, the Metering Process table (ipfixMeteringProcessTable) is
skipping to change at page 22, line 32 skipping to change at page 23, line 32
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB -- RFC2863 FROM IF-MIB -- RFC2863
InetAddressType, InetAddress, InetPortNumber InetAddressType, InetAddress, InetPortNumber
FROM INET-ADDRESS-MIB -- RFC4001 FROM INET-ADDRESS-MIB -- RFC4001
PhysicalIndexOrZero PhysicalIndexOrZero
FROM ENTITY-MIB; -- RFC4133 FROM ENTITY-MIB; -- RFC4133
ipfixMIB MODULE-IDENTITY ipfixMIB MODULE-IDENTITY
LAST-UPDATED "201201200000Z" -- 20 January 2012 LAST-UPDATED "201203220000Z" -- 22 March 2012
ORGANIZATION "IETF IPFIX Working Group" ORGANIZATION "IETF IPFIX Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/ipfix-charter.html http://www.ietf.org/html.charters/ipfix-charter.html
Mailing Lists: Mailing Lists:
General Discussion: ipfix@ietf.org General Discussion: ipfix@ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/ipfix To Subscribe: http://www1.ietf.org/mailman/listinfo/ipfix
Archive: Archive:
http://www1.ietf.org/mail-archive/web/ipfix/current/index.html http://www1.ietf.org/mail-archive/web/ipfix/current/index.html
skipping to change at page 23, line 31 skipping to change at page 24, line 31
Phone: +32 2 704 5622 Phone: +32 2 704 5622
Email: bclaise@cisco.com Email: bclaise@cisco.com
Gerhard Muenz Gerhard Muenz
Technische Universitaet Muenchen Technische Universitaet Muenchen
Department of Informatics Department of Informatics
Chair for Network Architectures and Services (I8) Chair for Network Architectures and Services (I8)
Boltzmannstr. 3 Boltzmannstr. 3
85748 Garching 85748 Garching
Germany Germany
Phone: +49 89 289-18008
Email: muenz@net.in.tum.de Email: muenz@net.in.tum.de
URI: http://www.net.in.tum.de/~muenz"
DESCRIPTION DESCRIPTION
"The IPFIX MIB defines managed objects for IP Flow "The IPFIX MIB defines managed objects for IP Flow
Information eXport. These objects provide information about Information eXport. These objects provide information about
managed nodes supporting the IPFIX protocol, managed nodes supporting the IPFIX protocol,
for Exporters as well as for Collectors. for Exporters as well as for Collectors.
Copyright (c) 2010 IETF Trust and the persons identified as Copyright (c) 2012 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)." (http://trustee.ietf.org/license-info)."
-- Note for RFC Editor: substitute [ThisRFC] with the newly -- Note for RFC Editor: substitute [ThisRFC] with the newly
-- assigned number in the following sections. -- assigned number in the following sections.
-- Revision history -- Revision history
REVISION "201203220000Z" -- 22 March 2012
REVISION "201201200000Z" -- 20 January 2012
DESCRIPTION DESCRIPTION
"Fixed erratas from RFC 5815. Published as RFC [ThisRFC]." "Fixed errata from RFC 5815. Published as RFC [ThisRFC]."
REVISION "201004190000Z" -- 19 April 2010 REVISION "201004190000Z" -- 19 April 2010
DESCRIPTION DESCRIPTION
"Initial version, published as RFC 5815." "Initial version, published as RFC 5815."
::= { mib-2 193 } ::= { mib-2 193 }
--****************************************************************** --******************************************************************
-- Top Level Structure of the MIB -- Top Level Structure of the MIB
--****************************************************************** --******************************************************************
skipping to change at page 25, line 42 skipping to change at page 26, line 40
::= { ipfixTransportSessionEntry 1 } ::= { ipfixTransportSessionEntry 1 }
ipfixTransportSessionProtocol OBJECT-TYPE ipfixTransportSessionProtocol OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transport protocol used for receiving or transmitting "The transport protocol used for receiving or transmitting
IPFIX Messages. Protocol numbers are assigned by IANA. A IPFIX Messages. Protocol numbers are assigned by IANA. A
current list of all assignments is available from current list of all assignments is available from
<http://www.iana.org/>." <http://www.iana.org/assignments/protocol-numbers/
protocol-numbers.xml>."
REFERENCE REFERENCE
"RFC 5101, Specification of the IP Flow "RFC 5101, Specification of the IP Flow
Information Export (IPFIX) Protocol for the Exchange of IP Information Export (IPFIX) Protocol for the Exchange of IP
Traffic Flow Information, Section 10." Traffic Flow Information, Section 10."
::= { ipfixTransportSessionEntry 2 } ::= { ipfixTransportSessionEntry 2 }
ipfixTransportSessionSourceAddressType OBJECT-TYPE ipfixTransportSessionSourceAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6 (2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of address used for the source address, "The type of address used for the source address,
as specified in RFC 4001. This object is used with protocols as specified in RFC 4001. The InetAddressType supported
(specified in ipfixTransportSessionProtocol) like TCP (6) values are ipv4(1) and ipv6(2). This object is used with
and UDP (17) that have the notion of addresses. SCTP (132) protocols specified in ipfixTransportSessionProtocol) like
should use the ipfixTransportSessionSctpAssocId instead. TCP (6) and UDP (17) that have the notion of addresses.
If SCTP (132) or any other protocol without the notion of SCTP (132) should use the ipfixTransportSessionSctpAssocId
addresses is used, the object MUST be set to unknown(0)." instead. If SCTP (132) or any other protocol without the
notion of addresses is used, the object MUST be set to
unknown(0)."
::= { ipfixTransportSessionEntry 3 } ::= { ipfixTransportSessionEntry 3 }
ipfixTransportSessionSourceAddress OBJECT-TYPE ipfixTransportSessionSourceAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source address of the Exporter of the IPFIX Transport "The source address of the Exporter of the IPFIX Transport
Session. This value is interpreted according to the value of Session. This value is interpreted according to the value of
ipfixTransportSessionAddressType as specified in RFC 4001. ipfixTransportSessionAddressType as specified in RFC 4001.
This object is used with protocols (specified in This object is used with protocols (specified in
ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that ipfixTransportSessionProtocol) like TCP (6) and UDP (17) that
have the notion of addresses. SCTP (132) should use the have the notion of addresses. SCTP (132) should use the
ipfixTransportSessionSctpAssocId instead. If SCTP (132) or ipfixTransportSessionSctpAssocId instead. If SCTP (132) or
any other protocol without the notion of addresses is used, any other protocol without the notion of addresses is used,
the object MUST be set to a zero-length string." the object MUST be set to a zero-length string."
::= { ipfixTransportSessionEntry 4 } ::= { ipfixTransportSessionEntry 4 }
ipfixTransportSessionDestinationAddressType OBJECT-TYPE ipfixTransportSessionDestinationAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6 (2) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of address used for the destination address, "The type of address used for the destination address,
as specified in RFC 4001. This object is used with protocols as specified in RFC 4001. The InetAddressType supported
(specified in ipfixTransportSessionProtocol) like TCP (6) values are ipv4(1) and ipv6(2). This object is used with
and UDP (17) that have the notion of addresses. SCTP (132) protocols (specified in ipfixTransportSessionProtocol) like
should use the ipfixTransportSessionSctpAssocId instead. TCP (6) and UDP (17) that have the notion of addresses.
If SCTP (132) or any other protocol without the notion of SCTP (132) should use the ipfixTransportSessionSctpAssocId
addresses is used, the object MUST be set to unknown(0)." instead. If SCTP (132) or any other protocol without the
notion of addresses is used, the object MUST be set to
unknown(0)."
::= { ipfixTransportSessionEntry 5 } ::= { ipfixTransportSessionEntry 5 }
ipfixTransportSessionDestinationAddress OBJECT-TYPE ipfixTransportSessionDestinationAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The destination address of the Collector of the IPFIX "The destination address of the Collector of the IPFIX
Transport Session. This value is interpreted according to Transport Session. This value is interpreted according to
the value of ipfixTransportSessionAddressType, as specified the value of ipfixTransportSessionAddressType, as specified
in RFC 4001. This object is used with protocols in RFC 4001. This object is used with protocols
(specified in ipfixTransportSessionProtocol) like TCP (6) (specified in ipfixTransportSessionProtocol) like TCP (6)
and UDP (17) that have the notion of addresses. SCTP (132) and UDP (17) that have the notion of addresses. SCTP (132)
should use the ipfixTransportSessionSctpAssocId instead. should use the ipfixTransportSessionSctpAssocId instead.
If SCTP (132) or any other protocol without the notion of If SCTP (132) or any other protocol without the notion of
addresses is used, the object MUST be set to a zero-length addresses is used, the object MUST be set to a zero-length
skipping to change at page 57, line 42 skipping to change at page 58, line 49
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2 MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
TruthValue TruthValue
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF; -- RFC2580 FROM SNMPv2-CONF; -- RFC2580
ipfixSelectorMIB MODULE-IDENTITY ipfixSelectorMIB MODULE-IDENTITY
LAST-UPDATED "201201200000Z" -- 20 January 2012 LAST-UPDATED "201203220000Z" -- 22 March 2012
ORGANIZATION "IETF IPFIX Working Group" ORGANIZATION "IETF IPFIX Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/ipfix-charter.html http://www.ietf.org/html.charters/ipfix-charter.html
Mailing Lists: Mailing Lists:
General Discussion: ipfix@ietf.org General Discussion: ipfix@ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/ipfix To Subscribe: http://www1.ietf.org/mailman/listinfo/ipfix
Archive: Archive:
http://www1.ietf.org/mail-archive/web/ipfix/current/index.html http://www1.ietf.org/mail-archive/web/ipfix/current/index.html
skipping to change at page 58, line 42 skipping to change at page 59, line 49
Phone: +32 2 704 5622 Phone: +32 2 704 5622
Email: bclaise@cisco.com Email: bclaise@cisco.com
Gerhard Muenz Gerhard Muenz
Technische Universitaet Muenchen Technische Universitaet Muenchen
Department of Informatics Department of Informatics
Chair for Network Architectures and Services (I8) Chair for Network Architectures and Services (I8)
Boltzmannstr. 3 Boltzmannstr. 3
85748 Garching 85748 Garching
Germany Germany
Phone: +49 89 289-18008
Email: muenz@net.in.tum.de Email: muenz@net.in.tum.de
URI: http://www.net.in.tum.de/~muenz"
DESCRIPTION DESCRIPTION
"The IPFIX SELECTOR MIB module defined in this section "The IPFIX SELECTOR MIB module defined in this section
provides the standard Filtering and Sampling functions that provides the standard Filtering and Sampling functions that
can be referenced in the ipfixSelectionProcessTable. All can be referenced in the ipfixSelectionProcessTable. All
standard Filtering and Sampling functions MUST be registered standard Filtering and Sampling functions MUST be registered
in the subtree under object ipfixSelectorFunctions in the subtree under object ipfixSelectorFunctions
(1.3.6.1.2.1.194.1.1). The toplevel OIDs in the subtree (1.3.6.1.2.1.194.1.1). The toplevel OIDs in the subtree
under object ipfixSelectorFunctions MUST be registered in a under object ipfixSelectorFunctions MUST be registered in a
subregistry maintained by IANA at subregistry maintained by IANA at
http://www.iana.org/assignments/smi-numbers. http://www.iana.org/assignments/smi-numbers.
skipping to change at page 59, line 22 skipping to change at page 60, line 27
completeness and accuracy of the description. Requests for completeness and accuracy of the description. Requests for
MIB objects that duplicate the functionality of existing MIB objects that duplicate the functionality of existing
objects SHOULD be declined. The smallest available OID objects SHOULD be declined. The smallest available OID
SHOULD be assigned to a new MIB objects. The specification SHOULD be assigned to a new MIB objects. The specification
of new MIB objects SHOULD follow the structure specified in of new MIB objects SHOULD follow the structure specified in
RFC [ThisRFC] and MUST be published using a well- RFC [ThisRFC] and MUST be published using a well-
established and persistent publication medium. The experts established and persistent publication medium. The experts
will initially be drawn from the Working Group Chairs and will initially be drawn from the Working Group Chairs and
document editors of the IPFIX and PSAMP Working Groups. document editors of the IPFIX and PSAMP Working Groups.
Copyright (c) 2011 IETF Trust and the persons identified as Copyright (c) 2012 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)." (http://trustee.ietf.org/license-info)."
-- Revision history -- Revision history
REVISION "201201200000Z" -- 20 January 2012 REVISION "201203220000Z" -- 22 March 2012
DESCRIPTION DESCRIPTION
"Update to MIB description to reflect updated registration "Update to MIB description to reflect updated registration
of new Sampling and Filtering Functions. Published as RFC of new Sampling and Filtering Functions. Published as RFC
[ThisRFC]." [ThisRFC]."
REVISION "201003150000Z" -- 15 March 2010 REVISION "201003150000Z" -- 15 March 2010
DESCRIPTION DESCRIPTION
"Initial version, published as RFC 5815." "Initial version, published as RFC 5815."
::= { mib-2 194 } ::= { mib-2 194 }
 End of changes. 24 change blocks. 
64 lines changed or deleted 107 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/