idnits 2.17.1 draft-dietz-ipfix-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1917. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1894. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1901. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1907. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 26 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 23, 2006) is 6387 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-psamp-sample-tech' is defined on line 1828, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3917 ** Downref: Normative reference to an Informational draft: draft-ietf-ipfix-architecture (ref. 'I-D.ietf-ipfix-architecture') == Outdated reference: A later version (-12) exists of draft-ietf-ipfix-as-10 ** Downref: Normative reference to an Informational draft: draft-ietf-ipfix-as (ref. 'I-D.ietf-ipfix-as') == Outdated reference: A later version (-26) exists of draft-ietf-ipfix-protocol-23 == Outdated reference: A later version (-15) exists of draft-ietf-ipfix-info-13 == Outdated reference: A later version (-13) exists of draft-ietf-psamp-framework-10 == Outdated reference: A later version (-11) exists of draft-ietf-psamp-sample-tech-07 == Outdated reference: A later version (-09) exists of draft-ietf-psamp-protocol-06 -- Obsolete informational reference (is this intentional?): RFC 1889 (Obsoleted by RFC 3550) Summary: 7 errors (**), 0 flaws (~~), 9 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Dietz, Ed. 3 Internet-Draft NEC Europte Ltd. 4 Expires: April 26, 2007 A. Kobayashi 5 NTT PF Lab. 6 B. Claise 7 Cisco Systems 8 October 23, 2006 10 Definitions of Managed Objects for IP Flow Information Export 11 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on April 26, 2007. 38 Copyright Notice 40 Copyright (C) The Internet Society (2006). 42 Abstract 44 This document defines managed objects for IP Flow Information Export 45 (IPFIX). These objects provide information for monitoring IPFIX 46 Exporters and IPFIX Collectors including some minor configuration 47 information. 49 Table of Contents 51 1. Open Issues/TODOs . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. IPFIX Documents Overview . . . . . . . . . . . . . . . . . . . 4 57 4. The Internet-Standard Management Framework . . . . . . . . . . 4 59 5. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 6. Structure of the IPFIX MIB . . . . . . . . . . . . . . . . . . 8 62 6.1. IPFIX Exporter MIB module . . . . . . . . . . . . . . . . 9 63 6.1.1. The Reporting Group . . . . . . . . . . . . . . . . . 9 64 6.1.2. The Instance Group . . . . . . . . . . . . . . . . . . 10 65 6.1.3. The Statistics Group . . . . . . . . . . . . . . . . . 11 66 6.1.4. Textual Convention . . . . . . . . . . . . . . . . . . 11 67 6.2. IPFIX Collector MIB module . . . . . . . . . . . . . . . . 11 68 6.2.1. The Exporter Group . . . . . . . . . . . . . . . . . . 11 69 6.2.2. The Received Template Group . . . . . . . . . . . . . 11 70 6.2.3. The Template Statistics Group . . . . . . . . . . . . 11 72 7. MIB Definitions . . . . . . . . . . . . . . . . . . . . . . . 12 73 7.1. Exporter Definition . . . . . . . . . . . . . . . . . . . 12 74 7.2. Collector Definition . . . . . . . . . . . . . . . . . . . 25 76 8. Security Considerations . . . . . . . . . . . . . . . . . . . 38 78 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 80 10. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . 38 82 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38 83 11.1. Normative References . . . . . . . . . . . . . . . . . . . 38 84 11.2. Informative References . . . . . . . . . . . . . . . . . . 39 86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 87 Intellectual Property and Copyright Statements . . . . . . . . . . 42 89 1. Open Issues/TODOs 90 o Agree on the fact that only the main configuration objects are 91 writeable by this MIB. 92 o Method Table Figure -- The figure must be adjusted to not show any 93 particular OID since we don't define the methods right here. Also 94 substitute OID by name! 95 o Need to achieve a common layout and naming on the different MIB 96 parts. 97 o Need to decide how to structure the MIB (which one is the basic 98 one, which one imports the root from the basic one). 99 o Elaborate security considerations, particularly concerning SET 100 operations. 101 o Check the definitions once IPFIX-PROTO is a RFC. 102 o Capitalize all terms defined in the terminology 103 o How to integrate multiple templates for one metering process. 104 o Check usage of process id in instance table. 105 o Check if we need the new definition of session at the exporter and 106 rework the whole description of that tables. 107 o How to integrate the following table into the exporter MIB: 109 ipfixTemplateManagementTable 110 *ipfixObdomainId 111 *ipfixTemplateId 112 ipfixTemplateScopeCount <- It is used option template. 113 ipfixMaximumLength <- This value means max size of variable field. 115 The table should be linked to the current objects somehow. 116 o Include the following tables for IPFIX (* indicated index) 118 ipfixFlowCreatParameterTable 119 *ipfixMeteringProcessId 120 ipfixActiveTimeOut 121 ipfixInactiveTimeOut 122 ipfixStoreFlowEntryNumber 123 ipfixCurrentFlowEntryNumber 125 ipfixFlowKeyTable 126 *ipfixMeteringProcessId 127 *ipfixFlowKeyIndex 128 ipfixFlowKeyFieldId 130 2. Introduction 132 This document defines MIB modules for monitoring IP Flow Information 133 Export (IPFIX) Devices including Exporters and Collectors. The full 134 configuration of the IPFIX Metering Process is out of the scope this 135 MIB. However, some configuration of the Exporting Process is 136 integrated into this document. 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in RFC 2119 [RFC2119]. 142 3. IPFIX Documents Overview 144 The IPFIX protocol provides network administrators with access to IP 145 flow information. The architecture for the export of measured IP 146 flow information out of an IPFIX exporting process to a collecting 147 process is defined in [I-D.ietf-ipfix-architecture], per the 148 requirements defined in [RFC3917]. The protocol document [I-D.ietf- 149 ipfix-protocol] specifies how IPFIX data record and templates are 150 carried via a congestion-aware transport protocol from IPFIX 151 exporting processes to IPFIX collecting process. IPFIX has a formal 152 description of IPFIX information elements, their name, type and 153 additional semantic information, as specified in [I-D.ietf-ipfix- 154 info]. Finally [I-D.ietf-ipfix-as] describes what type of 155 applications can use the IPFIX protocol and how they can use the 156 information provided. It furthermore shows how the IPFIX framework 157 relates to other architectures and frameworks. 159 It is assumed that flow metering, export and collection is performed 160 according to the IPFIX architecture defined in [I-D.ietf-ipfix- 161 architecture]. Configuration of the export and collection of flow 162 information templates and records is modeled according to [I-D.ietf- 163 ipfix-protocol]. Packet selection and filtering methods that may be 164 optionally used by the IPFIX metering processare not considered in 165 this MIB module. They are defined in the Packet Sampling (PSAMP) 166 working group by the [I-D.ietf-psamp-framework], [I-D.ietf-psamp- 167 sample-tech] documents. Nevertheless the entry point for those 168 methods [I-D.ietf-psamp-mib] is given within this MIB module since 169 PSAMP export protocol [I-D.ietf-psamp-protocol] is based on the IPFIX 170 protocol. 172 4. The Internet-Standard Management Framework 174 For a detailed overview of the documents that describe the current 175 Internet-Standard Management Framework, please refer to section 7 of 176 RFC 3410 [RFC3410]. 178 Managed objects are accessed via a virtual information store, termed 179 the Management Information Base or MIB. MIB objects are generally 180 accessed through the Simple Network Management Protocol (SNMP). 181 Objects in the MIB are defined using the mechanisms defined in the 182 Structure of Management Information (SMI). This memo specifies a MIB 183 module that is compliant to the SMIv2, which is described in STD 58, 184 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 185 [RFC2580]. 187 5. Terminology 189 The definitions of the basic terms like IP Traffic Flow, Exporting 190 Process, Collecting Process, Observation Points, etc. are 191 semantically identical with those found in the IPFIX protocol 192 document [I-D.ietf-ipfix-protocol]. Some of the terms have been 193 expanded for more clarity when defining the protocol. Additional 194 terms required for the protocol has also been defined. Definitions 195 in this document and in [I-D.ietf-ipfix-architecture] are equivalent, 196 except that definitions which are only relevant to the IPFIX protocol 197 only appear here. 199 Observation Point 201 An Observation Point is a location in the network where IP packets 202 can be observed. Examples include: a line to which a probe is 203 attached, a shared medium, such as an Ethernet-based LAN, a single 204 port of a router, or a set of interfaces (physical or logical) of 205 a router. 206 Note that every Observation Point is associated with an 207 Observation Domain (defined below), and that one Observation Point 208 may be a superset of several other Observation Points. For 209 example one Observation Point can be an entire line card. That 210 would be the superset of the individual Observation Points at the 211 line card's interfaces. 213 Observation Domain 215 An Observation Domain is the largest set of Observation Points for 216 which Flow information can be aggregated by a Metering Process. 217 For example, a router line card may be an Observation Domain if it 218 is composed of several interfaces, each of which is an Observation 219 Point. In the IPFIX Message it generates, the Observation Domain 220 includes its Observation Domain ID, which is unique per Exporting 221 Process. That way, the Collecting Process can identify the 222 specific Observation Domain from the Exporter that sends the IPFIX 223 Messages. Every Observation Point is associated with an 224 Observation Domain. It is RECOMMENDED that Observation Domain IDs 225 are also unique per IPFIX Device. 227 IP Traffic Flow or Flow 229 There are several definitions of the term 'flow' being used by the 230 Internet community. Within the context of IPFIX we use the 231 following definition: 233 A Flow is defined as a set of IP packets passing an Observation 234 Point in the network during a certain time interval. All packets 235 belonging to a particular Flow have a set of common properties. 236 Each property is defined as the result of applying a function to 237 the values of: 239 1. one or more packet header field (e.g. destination IP address), 240 transport header field (e.g. destination port number), or 241 application header field (e.g. RTP header fields [RFC1889]) 242 2. one or more characteristics of the packet itself (e.g. number 243 of MPLS labels, etc...) 244 3. one or more of fields derived from packet treatment (e.g. next 245 hop IP address, the output interface, etc...) 247 A packet is defined to belong to a Flow if it completely satisfies 248 all the defined properties of the Flow. 249 This definition covers the range from a Flow containing all 250 packets observed at a network interface to a Flow consisting of 251 just a single packet between two applications. It includes 252 packets selected by a sampling mechanism. 254 Flow Record 256 A Flow Record contains information about a specific Flow that was 257 observed at an Observation Point. A Flow Record contains measured 258 properties of the Flow (e.g. the total number of bytes for all the 259 Flow's packets) and usually characteristic properties of the Flow 260 (e.g. source IP address). 262 Metering Process 264 The Metering Process generates Flow Records. Inputs to the 265 process are packet headers and characteristics observed at an 266 Observation Point, and packet treatment at the Observation Point 267 (for example the selected output interface). 268 The Metering Process consists of a set of functions that includes 269 packet header capturing, timestamping, sampling, classifying, and 270 maintaining Flow Records. 272 The maintenance of Flow Records may include creating new records, 273 updating existing ones, computing Flow statistics, deriving 274 further Flow properties, detecting Flow expiration, passing Flow 275 Records to the Exporting Process, and deleting Flow Records. 277 Exporting Process 279 The Exporting Process sends Flow Records to one or more Collecting 280 Processes. The Flow Records are generated by one or more Metering 281 Processes. 283 Exporter 285 A device which hosts one or more Exporting Processes is termed an 286 Exporter. 288 IPFIX Device 290 An IPFIX Device hosts at least one Exporting Process. It may host 291 further Exporting processes and arbitrary numbers of Observation 292 Points and Metering Process. 294 Collecting Process 296 A Collecting Process receives Flow Records from one or more 297 Exporting Processes. The Collecting Process might process or 298 store received Flow Records, but such actions are out of scope for 299 this document. 301 Collector 303 A device which hosts one or more Collecting Processes is termed a 304 Collector. 306 Template 308 Template is an ordered sequence of pairs, used to 309 completely specify the structure and semantics of a particular set 310 of information that needs to be communicated from an IPFIX Device 311 to a Collector. Each Template is uniquely identifiable by means 312 of a Template ID. 314 Template Record 315 A Template Record defines the structure and interpretation of 316 fields in a Data Record. 318 Data Record 320 A Data Record is a record that contains values of the parameters 321 corresponding to a Template Record. 323 Options Template Record 325 An Options Template Record is a Template Record that defines the 326 structure and interpretation of fields in a Data Record, including 327 defining how to scope the applicability of the Data Record. 329 Information Element 331 An Information Element is a protocol and encoding independent 332 description of an attribute which may appear in an IPFIX Record. 333 The IPFIX information model [I-D.ietf-ipfix-info] defines the base 334 set of Information Elements for IPFIX. The type associated with 335 an Information Element indicates constraints on what it may 336 contain and also determines the valid encoding mechanisms for use 337 in IPFIX. 339 Method 341 A sampling or filtering function used by a Metering Process. 342 Methods can be combined by passing the results from one function 343 as the input to the next function. 345 Instance 347 An Instance groups the different parts together. It references 348 the Methods used by the Metering Process, the Templates used to 349 export the resulting Records of the Metering Process and the 350 Collectors to which those Records are exported. 352 6. Structure of the IPFIX MIB 354 The IPFIX MIB is divided into three more or less independent modules: 355 The IPFIX Exporter MIB module used to be applied by IPFIX Exporters, 356 the IPFIX Collector MIB module to be applied by IPFIX Collectors and 357 the PSAMP MIB module that extends the IPFIX Exporter MIB module by 358 managed objects concerning packet filtering and sampling. While the 359 first two MIB modules are defined in this document, the PSAMP MIB 360 module is defined in [I-D.ietf-psamp-mib]. 362 o The IPFIX Exporter MIB module contains objects related to 363 exporting flow information with the IPFIX protocol to one or more 364 IPFIX Collectors. It contains detailed information on each 365 Collector to which information is exported and on each Template 366 that is used for this purpose by the IPFIX protocol. It also 367 contains some basic structures for describing the chain of 368 sampling or filtering Methods that optionally can be applied to 369 the flow Metering Process. Finally this MIB module provides 370 statistics on the Metering Process(es) and Exporting Process(es). 371 o The IPFIX Collector MIB contains objects related to collecting 372 flow information sent by IPFIX Exporters. It contains detailed 373 information on each Exporters from which information has been 374 received and on the Templates received from the Exporters. In 375 addition, statistics information is provided. 376 o The PSAMP MIB module part contains objects related to packet 377 filtering and sampling before they are used for creating flow 378 records. Sampling and filtering functions can be optionally 379 applied by a Metering Process. The PSAMP MIB module contains 380 objects providing statistics for sampling and filtering functions. 382 The following subsections describe all object groups in the IPFIX 383 Exproter MIB module and the IPFIX Collector MIB module. 385 6.1. IPFIX Exporter MIB module 387 6.1.1. The Reporting Group 389 The reporting group of managed objects provides information on 390 Collectors to which flow information is exported. The group contains 391 two tables, the ipfixCollectorTable and the ipfixCollectorGroupTable. 393 Each entry in the ipfixCollectorTable specifies a collector by its IP 394 address, used transport protocol and port number. Also it contains 395 the number of reports sent to this collector. The default transport 396 protocol is SCTP. 398 The ipfixCollectorGroupTable groups one or more collectors to a set 399 of collectors where flow information is sent to. Thus reporting to 400 more than one collector at the same time is possible. The 401 ipfixCollectorGroupTable contains only indexes but nevertheless it is 402 usefull since it is referenced in the ipfixInstanceTable. This table 403 groups single collectors referenced by the second index 404 (ipfixCollectorIndex) to a group of collectors that can be 405 subsequently be referenced by the first index 406 (ipfixCollectorGroupIndex). 408 6.1.2. The Instance Group 410 The instance group of managed objects provides information about 411 active Instances at the IPFIX exporter. It also allows to create new 412 instances and to terminate them. Furthermore in the instance group 413 every part from observation point to reporting is put together. 415 The group contains three tables, the ipfixInstanceTable, the 416 ipfixMethodChainTable and the ipfixTemplateTable. Each entry of the 417 ipfixInstanceTable describes an instance. The observation point is 418 given as a pointer to another object in 419 ipfixInstanceObservationPoint. This other object could be an entry 420 in the mib-II interface table or any other interface point where you 421 can observe packets. The start and stop time is stored in that table 422 and shows the time when the metering method should run. The 423 ipfixInstanceTemplateId gives the template id used to link the data 424 gathered in the metering process to an export format described in the 425 information model of the IPFIX architecture. The collectors where 426 the data packets should be sent are specified by their index in the 427 ipfixCollectorGroupTable. In addition the process id of the metering 428 process and the process id of the exporting process used for this 429 instance is saved in the instance table. Last but not least 430 statistical values about the packets observed at the observation 431 point, packets dropped during the metering process and the reports 432 sent to the collectors are maintained. 434 The ipfixMethodChainTable describes the concatenation of methods for 435 a given instance. If concatenation of methods is not supported on 436 the IPFIX device the table will hold exactly one entry per instance. 438 The methods used for the metering process of an instance can be 439 retrieved through the index given in the ipfixInstanceTable. The 440 index of the instance table is also the first index in the 441 ipfixMethodChainTable. So each method entry with the same (first) 442 index as the instance is used to produce the data record for the 443 instance. The second index is the running index for the method. The 444 method itself is represented by a pointer (OID) to a parameter set. 445 The methods are applied in the order given by this second index 446 ipfixMethodChainIndex. Assume the following table: 448 1.2.4.1.2.5.1 = 1 (second index) 449 1.2.4.1.2.5.2 = 2 (second index) 450 1.2.4.1.3.5.1 = 1.3.6.1.2.1.999.3.a.b.c.d.e 451 (pointer to a parameter set in the IPFIX PAMP extension MIB) 452 1.2.4.1.3.5.2 = 1.3.6.1.2.1.999.3.a.b.c.f.g 453 (pointer to another parameter set in the IPFIX PAMP extension MIB) 454 1.2.4.1.4.5.1 = xxx (status of the row) 455 1.2.4.1.4.5.2 = xxx (status of the row) 456 This would mean that the method and parameter set specified by 457 1.3.6.1.2.1.999.3.a.b.c.d.e is applied prior to the method and 458 parameter set specified by 1.3.6.1.2.1.999.3.a.b.c.f.g for the 459 instance with index 5. 461 In addition every entry in the method chain table contains two 462 statistical values: the packets observed at the entry point of the 463 method and the packets dropped by the method. 465 The ipfixTemplateTable lists all data templates that are used by the 466 IPFIX exporter. It has two indices. The first one is the template 467 id and the second one is just a running index for the field ids 468 listed in the table. So the ipfixTemplateEntry.4.x will list all 469 field ids used for template id 4 in the order given by x. 471 6.1.3. The Statistics Group 473 The objects of contained in the statistics conformance group are 474 spread all over the MIB. They are gathered in their own conformace 475 group to better to easily distinguish them from the vital objects. 477 6.1.4. Textual Convention 479 The IPFIX Exporter MIB defines a textual convention, the 480 PsampMethodAvailability. It is used as SYNTAX of all those objects 481 that may or may not be available in a specific implementation of the 482 MIB. This especially holds true for the sampling and filtering 483 methods specified by [I-D.ietf-psamp-mib]. 485 6.2. IPFIX Collector MIB module 487 6.2.1. The Exporter Group 489 The objects defined in the exporter group are used in the collector 490 MIB to define the exporters from which the collector receives data. 492 6.2.2. The Received Template Group 494 The received template group identifies all the templates the 495 collector has received from the exporter. It additionally links the 496 template to an exporter. 498 6.2.3. The Template Statistics Group 500 The template statistics group gathers all the objects that contain 501 statistical information about the templates a collector has received. 503 7. MIB Definitions 505 This section contains the definitions of the IPFIX-EXPORTER-MIB and 506 the IPFIX-COLLECTOR-MIB modules. Exporter-realted and Collector- 507 realted objects are defined in two separate MIB modules, because 508 commonly, a device will implement only one of them. Then either the 509 IPFIX-EXPORTER-MIB modules or the IPFIX-COLLECTOR-MIB module needs to 510 be implemented. 512 7.1. Exporter Definition 513 IPFIX-EXPORTER-MIB DEFINITIONS ::= BEGIN 515 IMPORTS 516 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, mib-2 517 FROM SNMPv2-SMI -- RFC2578 518 TEXTUAL-CONVENTION, DateAndTime, DisplayString, RowStatus, 519 TruthValue 520 FROM SNMPv2-TC -- RFC2579 521 MODULE-COMPLIANCE, OBJECT-GROUP 522 FROM SNMPv2-CONF -- RFC2580 523 InterfaceIndexOrZero 524 FROM IF-MIB -- RFC2863 525 InetAddressType, InetAddress, InetAutonomousSystemNumber 526 FROM INET-ADDRESS-MIB; -- RFC3291 528 ipfixMIB MODULE-IDENTITY 529 LAST-UPDATED "200610231200Z" -- 23 October 2006 530 ORGANIZATION "IETF IP Flow Information Export" 531 CONTACT-INFO 532 "WG charter: 533 http://www.ietf.org/html.charters/ipfix-charter.html 535 Mailing Lists: 536 General Discussion: ipfix@net.doit.wisc.edu 537 To Subscribe: majordomo@net.doit.wisc.edu 538 In Body: subscribe ipfix 539 Archive: http://ipfix.doit.wisc.edu/archive/ 541 Editor: 542 Thomas Dietz 543 NEC Europe Ltd. 544 Network Laboratories 545 Kurfuersten-Anlage 36 546 69115 Heidelberg 547 Germany 548 Phone: +49 6221 4342-128 549 Email: dietz@netlab.nec.de" 550 DESCRIPTION 551 "The IPFIX MIB defines managed objects for IP flow 552 information export. These objects provide information about 553 managed nodes supporting IP flow information export, 554 including flow information export capabilities, 555 configuration and statistics. They also allow to configure 556 IP flow information export concerning the IP interface at 557 which flow information is gathered, the flow selections 558 methods used, and the collector to which flow information is 559 exported. 561 Copyright (C) The Internet Society (2006). This version 562 of this MIB module is part of RFC yyyy; see the RFC 563 itself for full legal notices." 564 -- Editor note: check if configuration is really desired 565 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 567 -- Revision history 569 REVISION "200610231200Z" -- 23 October 2006 570 DESCRIPTION 571 "Initial version, published as RFC yyyy." 572 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 574 ::= { mib-2 999 } 575 -- 999 to be assigned by IANA. 577 -- Textual Conventions 579 PsampMethodAvailability ::= TEXTUAL-CONVENTION 580 STATUS current 581 DESCRIPTION 582 "Used to report the availability of a selection method: 584 available(1) - the method is supported and can be used 585 notAvailable(2) - the method is not available" 586 SYNTAX INTEGER { 587 available(1), 588 notAvailable(2) 589 } 591 -- Top level structure of the MIB 593 ipfixExporter OBJECT IDENTIFIER ::= { ipfixMIB 1 } 594 ipfixCollector OBJECT IDENTIFIER ::= { ipfixMIB 2 } 595 ipfixPsampExtension OBJECT IDENTIFIER ::= { ipfixMIB 3 } 596 ipfixConformance OBJECT IDENTIFIER ::= { ipfixMIB 4 } 598 ipfixExporterObjects OBJECT IDENTIFIER ::= { ipfixExporter 1 } 599 --================================================================== 600 -- Reporting Group 601 --================================================================== 603 ipfixReporting OBJECT IDENTIFIER ::= { ipfixExporterObjects 1 } 605 -- Collector Table +++++++++++++++++++++++++++++++++++++++++++++++++ 607 ipfixCollectorTable OBJECT-TYPE 608 SYNTAX SEQUENCE OF IpfixCollectorEntry 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "This table lists collectors to which reports are exported." 613 ::= { ipfixReporting 1 } 615 ipfixCollectorEntry OBJECT-TYPE 616 SYNTAX IpfixCollectorEntry 617 MAX-ACCESS not-accessible 618 STATUS current 619 DESCRIPTION 620 "Defines an entry in the ipfixCollectorTable." 621 INDEX { ipfixCollectorIndex } 622 ::= { ipfixCollectorTable 1 } 624 IpfixCollectorEntry ::= SEQUENCE { 625 ipfixCollectorIndex Integer32, 626 ipfixCollectorDstIpAddressType InetAddressType, 627 ipfixCollectorDstIpAddress InetAddress, 628 ipfixCollectorDstProtocol Integer32, 629 ipfixCollectorDstPort Integer32, 630 ipfixCollectorReportsSent Integer32 631 } 633 ipfixCollectorIndex OBJECT-TYPE 634 SYNTAX Integer32 (1..2147483647) 635 MAX-ACCESS not-accessible 636 STATUS current 637 DESCRIPTION 638 "The locally arbitrary, but unique identifier of a collector. 640 The value is expected to remain constant at least from one 641 re-initialization of the entity's network management system 642 to the next re-initialization." 643 ::= { ipfixCollectorEntry 1 } 645 ipfixCollectorDstIpAddressType OBJECT-TYPE 646 SYNTAX InetAddressType 647 MAX-ACCESS read-create 648 STATUS current 649 DESCRIPTION 650 "The IP address type of the collector." 651 ::= { ipfixCollectorEntry 2 } 653 ipfixCollectorDstIpAddress OBJECT-TYPE 654 SYNTAX InetAddress 655 MAX-ACCESS read-create 656 STATUS current 657 DESCRIPTION 658 "The IP address of the collector." 659 ::= { ipfixCollectorEntry 3 } 661 ipfixCollectorDstProtocol OBJECT-TYPE 662 SYNTAX Integer32 (0..256) 663 MAX-ACCESS read-create 664 STATUS current 665 DESCRIPTION 666 "The transport protocol used for exporting sampled packets to 667 the collector. The recommended protocols are TCP (6), UDP 668 (17) and SCTP (132). The default is SCTP." 669 DEFVAL { 132 } 670 ::= { ipfixCollectorEntry 4 } 672 ipfixCollectorDstPort OBJECT-TYPE 673 SYNTAX Integer32 (0..65535) 674 MAX-ACCESS read-create 675 STATUS current 676 DESCRIPTION 677 "The port number of the collector." 678 ::= { ipfixCollectorEntry 5 } 680 ipfixCollectorReportsSent OBJECT-TYPE 681 SYNTAX Integer32 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION 685 "The number of reports sent to the collector." 686 ::= { ipfixCollectorEntry 6 } 688 -- Collector Group Table +++++++++++++++++++++++++++++++++++++++++++ 690 ipfixCollectorGroupTable OBJECT-TYPE 691 SYNTAX SEQUENCE OF IpfixCollectorGroupEntry 692 MAX-ACCESS not-accessible 693 STATUS current 694 DESCRIPTION 695 "This table lists groups of collectors to which flow 696 records packets are exported. If flow records are 697 exported to only one collector the group consists of 698 exactly one collector." 699 ::= { ipfixReporting 2 } 701 ipfixCollectorGroupEntry OBJECT-TYPE 702 SYNTAX IpfixCollectorGroupEntry 703 MAX-ACCESS not-accessible 704 STATUS current 705 DESCRIPTION 706 "Defines an entry in the ipfixCollectorGroupTable." 707 INDEX { ipfixCollectorGroupIndex, ipfixCollectorIndex } 708 ::= { ipfixCollectorGroupTable 1 } 710 IpfixCollectorGroupEntry ::= SEQUENCE { 711 ipfixCollectorGroupIndex Integer32 712 } 714 ipfixCollectorGroupIndex OBJECT-TYPE 715 SYNTAX Integer32 (1..2147483647) 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "The locally arbitrary, but unique identifier of a collector 720 group. 722 The value is expected to remain constant at least from one 723 re-initialization of the entity's network management system 724 to the next re-initialization." 725 ::= { ipfixCollectorGroupEntry 1 } 727 -- (Data) Template Table +++++++++++++++++++++++++++++++++++++++++++ 729 ipfixTemplateTable OBJECT-TYPE 730 SYNTAX SEQUENCE OF IpfixTemplateEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "This table lists templates used by the exporter." 735 ::= { ipfixReporting 3 } 737 ipfixTemplateEntry OBJECT-TYPE 738 SYNTAX IpfixTemplateEntry 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "Defines an entry in the ipfixTemplateTable." 743 INDEX { ipfixObservationDomainId, ipfixTemplateId, 744 ipfixTemplateIndex } 745 ::= { ipfixTemplateTable 1 } 747 IpfixTemplateEntry ::= SEQUENCE { 748 ipfixTemplateId Integer32, 749 ipfixTemplateIndex Integer32, 750 ipfixTemplateFieldId Integer32, 751 ipfixTemplateFieldLength Integer32 752 } 754 ipfixTemplateId OBJECT-TYPE 755 SYNTAX Integer32 (1..2147483647) 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "The unique identifier for the template." 760 REFERENCE 761 "draft-ietf-ipfix-sample-tech-04.txt, Section 5.1" 762 -- Editor Note: get reference right! 763 ::= { ipfixTemplateEntry 1 } 765 ipfixTemplateIndex OBJECT-TYPE 766 SYNTAX Integer32 (1..2147483647) 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "The locally arbitrary, but unique identifier of a field Id 771 in the template identified by ipfixTemplateId. 773 The value is expected to remain constant at least from one 774 re-initialization of the entity's network management system 775 to the next re-initialization." 776 ::= { ipfixTemplateEntry 2 } 778 ipfixTemplateFieldId OBJECT-TYPE 779 SYNTAX Integer32 780 MAX-ACCESS read-only 781 STATUS current 782 DESCRIPTION 783 "The Field Id at position ipfixTemplateIndex in the template 784 ipfixTemplateId. This implicitly gives the data type and 785 state values that are exported." 786 REFERENCE 787 "draft-ietf-ipfix-sample-tech-04.txt, IPFIX/PSAMP INFO MODEL" 788 -- Editor Note: get reference right! 789 ::= { ipfixTemplateEntry 3 } 791 ipfixTemplateFieldLength OBJECT-TYPE 792 SYNTAX Integer32 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The Length of the Field. Used to indicate if reduced 797 encoding or variable length field is used." 798 ::= { ipfixTemplateEntry 4 } 800 --================================================================== 801 -- Instance Group 802 --================================================================== 804 ipfixInstances OBJECT IDENTIFIER ::= { ipfixExporterObjects 2 } 806 ipfixObservationDomainTable OBJECT-TYPE 807 SYNTAX SEQUENCE OF IpfixObservationDomainEntry 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "This table lists the Observation Domains used at 812 the managed node." 813 ::= { ipfixInstances 1 } 815 ipfixObservationDomainEntry OBJECT-TYPE 816 SYNTAX IpfixObservationDomainEntry 817 MAX-ACCESS not-accessible 818 STATUS current 819 DESCRIPTION 820 "Defines an entry in the ipfixObservationDomainTable." 821 INDEX { ipfixObservationDomainId } 822 ::= { ipfixObservationDomainTable 1 } 824 IpfixObservationDomainEntry ::= SEQUENCE { 825 ipfixObservationDomainId Integer32, 826 ipfixInstanceObservationPoint OBJECT IDENTIFIER, 827 ipfixInstanceStartTime DateAndTime, 828 ipfixInstanceStopTime DateAndTime 829 } 831 ipfixObservationDomainId OBJECT-TYPE 832 SYNTAX Integer32 (1..2147483647) 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "The locally arbitrary, but unique identifier of an 837 Observation Domain. 839 The value is expected to remain constant at least from one 840 re-initialization of the entity's network management system 841 to the next re-initialization." 842 ::= { ipfixObservationDomainEntry 1 } 844 ipfixInstanceObservationPoint OBJECT-TYPE 845 SYNTAX OBJECT IDENTIFIER 846 MAX-ACCESS read-create 847 STATUS current 848 DESCRIPTION 849 "The point where the packet is observed. If it is e.g, an 850 interface it points to the mib-II object of the interface." 851 ::= { ipfixObservationDomainEntry 2 } 853 ipfixInstanceStartTime OBJECT-TYPE 854 SYNTAX DateAndTime 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "The date and time when exporting for this 859 parameter set should start." 860 ::= { ipfixObservationDomainEntry 3 } 862 ipfixInstanceStopTime OBJECT-TYPE 863 SYNTAX DateAndTime 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "The date and time when exporting for this 868 parameter set should stop." 869 ::= { ipfixObservationDomainEntry 4 } 871 ipfixInstanceTable OBJECT-TYPE 872 SYNTAX SEQUENCE OF IpfixInstanceEntry 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION 876 "This table lists active instances of packet sampling at 877 the managed node." 878 ::= { ipfixInstances 2 } 880 ipfixInstanceEntry OBJECT-TYPE 881 SYNTAX IpfixInstanceEntry 882 MAX-ACCESS not-accessible 883 STATUS current 884 DESCRIPTION 885 "Defines an entry in the ipfixInstanceTable." 886 INDEX { ipfixInstanceIndex, ipfixObservationDomainId } 887 ::= { ipfixInstanceTable 1 } 889 IpfixInstanceEntry ::= SEQUENCE { 890 ipfixInstanceIndex Integer32, 891 ipfixInstanceTemplateId Integer32, 892 ipfixInstanceCollectorGroupIndex Integer32, 893 ipfixInstancePacketsObserved Integer32, 894 ipfixInstancePacketsDropped Integer32, 895 ipfixInstanceProcessId Integer32, 896 ipfixInstanceReportingProcessId Integer32, 897 ipfixInstanceReportsSent Integer32 898 } 900 ipfixInstanceIndex OBJECT-TYPE 901 SYNTAX Integer32 (1..2147483647) 902 MAX-ACCESS not-accessible 903 STATUS current 904 DESCRIPTION 905 "The locally arbitrary, but unique identifier of an 906 instance. 908 The value is expected to remain constant at least from one 909 re-initialization of the entity's network management system 910 to the next re-initialization." 911 ::= { ipfixInstanceEntry 1 } 913 ipfixInstanceTemplateId OBJECT-TYPE 914 SYNTAX Integer32 (1..2147483647) 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "The Id of a template in the template table. This implies 919 the knowledge about the method chain from the method chain 920 table. Furthermore it links the instance, method chain 921 (selector) and template together. 923 The identified template is applied to the stream of 924 filtered/sampled packets observed after applying the method 925 chain at the observation point." 926 ::= { ipfixInstanceEntry 2 } 928 ipfixInstanceCollectorGroupIndex OBJECT-TYPE 929 SYNTAX Integer32 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "The index of the collector group to which packet reports 934 are sent." 936 ::= { ipfixInstanceEntry 3 } 938 ipfixInstancePacketsObserved OBJECT-TYPE 939 SYNTAX Integer32 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The number of packets observed at the observation point." 944 ::= { ipfixInstanceEntry 4 } 946 ipfixInstancePacketsDropped OBJECT-TYPE 947 SYNTAX Integer32 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "The number of packets dropped while filtering/sampling 952 packets." 953 ::= { ipfixInstanceEntry 5 } 955 ipfixInstanceProcessId OBJECT-TYPE 956 SYNTAX Integer32 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "The process id of the metering process used by this 961 instance." 962 ::= { ipfixInstanceEntry 6 } 964 ipfixInstanceReportingProcessId OBJECT-TYPE 965 SYNTAX Integer32 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "The process id of the reporting process used by this 970 instance." 971 ::= { ipfixInstanceEntry 7 } 973 ipfixInstanceReportsSent OBJECT-TYPE 974 SYNTAX Integer32 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "The number of reports on sampled packets sent to the 979 collector." 980 ::= { ipfixInstanceEntry 8 } 982 -- Method Chain Table ++++++++++++++++++++++++++++++++++++++++++++++ 983 ipfixMethodChainTable OBJECT-TYPE 984 SYNTAX SEQUENCE OF IpfixMethodChainEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "This table contains method chains lists and connects them 989 to the instances where they are applied to different 990 observation points. The filtered/sampled packets are then 991 exported." 992 ::= { ipfixInstances 4 } 994 ipfixMethodChainEntry OBJECT-TYPE 995 SYNTAX IpfixMethodChainEntry 996 MAX-ACCESS not-accessible 997 STATUS current 998 DESCRIPTION 999 "Defines an entry in the ipfixMethodChainTable." 1000 INDEX { ipfixInstanceIndex, ipfixMethodChainIndex } 1001 ::= { ipfixMethodChainTable 1 } 1003 IpfixMethodChainEntry ::= SEQUENCE { 1004 ipfixMethodChainIndex Integer32, 1005 ipfixMethodChainMethod OBJECT IDENTIFIER, 1006 ipfixMethodChainPacketsObserved Integer32, 1007 ipfixMethodChainPacketsDropped Integer32 1008 } 1010 ipfixMethodChainIndex OBJECT-TYPE 1011 SYNTAX Integer32 (1..2147483647) 1012 MAX-ACCESS not-accessible 1013 STATUS current 1014 DESCRIPTION 1015 "The locally arbitrary, but unique identifier of a 1016 template. 1018 The value is expected to remain constant at least from one 1019 re-initialization of the entity's network management system 1020 to the next re-initialization." 1021 ::= { ipfixMethodChainEntry 2 } 1023 ipfixMethodChainMethod OBJECT-TYPE 1024 SYNTAX OBJECT IDENTIFIER 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "The method used for the template at a certain position in 1029 the method chain." 1030 ::= { ipfixMethodChainEntry 3 } 1032 ipfixMethodChainPacketsObserved OBJECT-TYPE 1033 SYNTAX Integer32 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The number of packets observed at the method entry point." 1038 ::= { ipfixMethodChainEntry 4 } 1040 ipfixMethodChainPacketsDropped OBJECT-TYPE 1041 SYNTAX Integer32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "The number of packets dropped while selecting packets." 1046 ::= { ipfixMethodChainEntry 5 } 1048 --================================================================== 1049 -- Conformance information 1050 --================================================================== 1052 ipfixCompliances OBJECT IDENTIFIER ::= { ipfixConformance 1 } 1053 ipfixGroups OBJECT IDENTIFIER ::= { ipfixConformance 2 } 1055 --================================================================== 1056 -- Compliance statements 1057 --================================================================== 1059 ipfixCompliance MODULE-COMPLIANCE 1060 STATUS current 1061 DESCRIPTION 1062 "An implementation that complies to this module must 1063 implement the objects defined in the mandatory groups 1064 ipfixGroupMetering and ipfixGroupReporting. The 1065 implementation of all other objects depends on the 1066 implementation of the corresponding functionality in the 1067 equipment." 1068 MODULE -- this module 1069 MANDATORY-GROUPS { 1070 ipfixGroupMetering, 1071 ipfixGroupReporting 1072 } 1073 GROUP ipfixGroupStatistics 1074 DESCRIPTION 1075 "These objects must be implemented if statistics are 1076 implemented on the equipment." 1077 ::= { ipfixCompliances 1 } 1079 --================================================================== 1080 -- MIB groupings 1081 --================================================================== 1083 ipfixGroupMetering OBJECT-GROUP 1084 OBJECTS { 1085 ipfixTemplateFieldId, 1086 ipfixTemplateFieldLength, 1088 ipfixMethodChainMethod, 1090 ipfixInstanceObservationPoint, 1091 ipfixInstanceStartTime, 1092 ipfixInstanceStopTime, 1093 ipfixInstanceTemplateId, 1094 ipfixInstanceCollectorGroupIndex, 1095 ipfixInstanceProcessId, 1096 ipfixInstanceReportingProcessId 1097 } 1098 STATUS current 1099 DESCRIPTION 1100 "All objects that are basic for the metering process. It 1101 contains a basic metering function (ipfixSelectAll), The 1102 template definitions needed for the export of data, the 1103 method chain that fixes the metering functions applied to 1104 the observation point and several parameters concering 1105 the export process and the collectors." 1106 ::= { ipfixGroups 1 } 1108 ipfixGroupReporting OBJECT-GROUP 1109 OBJECTS { 1110 ipfixCollectorDstIpAddressType, 1111 ipfixCollectorDstIpAddress, 1112 ipfixCollectorDstProtocol, 1113 ipfixCollectorDstPort 1114 } 1115 STATUS current 1116 DESCRIPTION 1117 "These objects define the collectors i.e., the destinations 1118 of the exporting process." 1119 ::= { ipfixGroups 2 } 1121 ipfixGroupStatistics OBJECT-GROUP 1122 OBJECTS { 1123 ipfixCollectorReportsSent, 1125 ipfixMethodChainPacketsObserved, 1126 ipfixMethodChainPacketsDropped, 1127 ipfixInstancePacketsObserved, 1128 ipfixInstanceReportsSent, 1129 ipfixInstancePacketsDropped 1130 } 1131 STATUS current 1132 DESCRIPTION 1133 "These objects contain statistical values gathered at 1134 different points in the metering process." 1135 ::= { ipfixGroups 3 } 1137 END 1139 7.2. Collector Definition 1140 IPFIX-COLLECTOR-MIB DEFINITIONS ::= BEGIN 1142 IMPORTS 1143 MODULE-IDENTITY, OBJECT-TYPE, 1144 Integer32, Counter32, Gauge32, mib-2 1145 FROM SNMPv2-SMI -- RFC2578 1146 TEXTUAL-CONVENTION, RowStatus, DateAndTime 1147 FROM SNMPv2-TC -- RFC2579 1148 MODULE-COMPLIANCE, OBJECT-GROUP 1149 FROM SNMPv2-CONF -- RFC2580 1150 InetAddressType, InetAddress 1151 FROM INET-ADDRESS-MIB; -- RFC3291 1153 ipfixMIB MODULE-IDENTITY 1154 LAST-UPDATED "200610201600Z" -- 20 October 2006 1155 ORGANIZATION "IETF IPFIX Working Group" 1156 CONTACT-INFO 1157 "WG charter: 1158 http://www.ietf.org/html.charters/ipfix-charter.html 1160 Mailing Lists: 1161 General Discussion: ipfix@ietf.org 1162 To Subscribe: majordomo@net.doit.wisc.edu 1163 In Body: subscribe ipfix 1164 Archive: http://ipfix.doit.wisc.edu/archive/ 1166 Editor: 1167 Atsushi Kobayashi 1168 NTT Information Sharing Platform Laboratories 1169 3-9-11 Midori-cho 1170 Musashino-shi 1171 180-8585 1172 Japan 1173 Phone: +81-422-59-3978 1174 Email: akoba@nttv6.net" 1176 DESCRIPTION 1177 "The IPFIX collector MIB defines managed objects that are 1178 maintained by the collecting process in traffic collector or 1179 IPFIX concentrator. These objects provide informations that 1180 are exporter's profile data and received templates. 1181 Exporter's profile has that exporter's ip address and 1182 port number. In addition, these object has statistics data 1183 per session or per templates. 1185 Copyright (C) The Internet Society (2005). This version 1186 of this MIB module is part of RFC yyyy; see the RFC 1187 itself for full legal notices." 1188 -- replace yyyy with actual RFC number & remove this noti 1190 -- Revision history 1192 REVISION "200610201600Z" -- 20 October 2006 1193 DESCRIPTION 1194 "Initial version, published as RFC yyyy." 1195 -- replace yyyy with actual RFC number & remove this notice 1197 ::= { mib-2 999 } 1198 -- 999 to be assigned by IANA. 1200 -- Top level structure of the MIB 1202 ipfixExporter OBJECT IDENTIFIER ::= { ipfixMIB 1 } 1203 ipfixCollector OBJECT IDENTIFIER ::= { ipfixMIB 2 } 1204 ipfixPsampExtension OBJECT IDENTIFIER ::= { ipfixMIB 3 } 1205 ipfixConformance OBJECT IDENTIFIER ::= { ipfixMIB 4 } 1207 ipfixCollectorObjects OBJECT IDENTIFIER ::= { ipfixCollector 1 } 1208 ipfixCollectorConformance OBJECT IDENTIFIER ::= { ipfixCollector 2 } 1210 -------------------------------------------------------------------- 1211 -- objects of receiving function 1212 -------------------------------------------------------------------- 1214 ipfixReceiving OBJECT IDENTIFIER ::= { ipfixCollectorObjects 1 } 1216 -------------------------------------------------------------------- 1217 -- 1: Exporter Table 1218 -------------------------------------------------------------------- 1220 ipfixExporterTable OBJECT-TYPE 1221 SYNTAX SEQUENCE OF 1222 IpfixExporterEntry 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION 1226 "This table lists Exporters that received by collecting 1227 process. This process manages them." 1228 ::= { ipfixReceiving 1 } 1230 ipfixExporterEntry OBJECT-TYPE 1231 SYNTAX IpfixExporterEntry 1232 MAX-ACCESS not-accessible 1233 STATUS current 1234 DESCRIPTION 1235 "Defines an entry in the ipfixExporterTable" 1236 INDEX { ipfixExporterIndex } 1237 ::= { ipfixExporterTable 1 } 1239 IpfixExporterEntry ::= 1240 SEQUENCE { 1241 ipfixExporterIndex Integer32, 1242 ipfixExporterIpAddressType InetAddressType, 1243 ipfixExporterIpAddress InetAddress, 1244 ipfixLifeTimeTemplate Integer32 1245 } 1247 ipfixExporterIndex OBJECT-TYPE 1248 SYNTAX Integer32 (1..2147483647) 1249 MAX-ACCESS not-accessible 1250 STATUS current 1251 DESCRIPTION 1252 "Locally arbitrary, but unique identifier of an entry 1253 in ipfixExporterTable. 1254 The value is expected to remain constant from a 1255 re-initialization of the entity's network management 1256 system to the next re-initialization." 1257 ::= { ipfixExporterEntry 1 } 1259 ipfixExporterIpAddressType OBJECT-TYPE 1260 SYNTAX InetAddressType 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "The IP address type of the exporter. The value for 1265 IPv4 is ipv4(1). The value for IPv6 is ipv6(2)." 1266 ::= { ipfixExporterEntry 2 } 1268 ipfixExporterIpAddress OBJECT-TYPE 1269 SYNTAX InetAddress 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The IP address of the Exporter." 1274 ::= { ipfixExporterEntry 3 } 1276 ipfixLifeTimeTemplate OBJECT-TYPE 1277 SYNTAX Integer32 1278 MAX-ACCESS read-only 1279 STATUS current 1280 DESCRIPTION 1281 "This is the time interval in seconds for the Life Time 1282 configured for the template with this session. It is only 1283 used to manage the received templates, if this protocol 1284 is UDP. The collecting process discards the template, 1285 if the templates is not refreshed within this life time." 1286 ::= { ipfixExporterEntry 4 } 1288 -------------------------------------------------------------------- 1289 -- 2: Session Table 1290 -------------------------------------------------------------------- 1292 ipfixSessionTable OBJECT-TYPE 1293 SYNTAX SEQUENCE OF 1294 IpfixSessionEntry 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 "This table lists sessions between exporting process and 1299 collecting process. This table has now, or has at some 1300 time in the past, established session." 1301 ::= { ipfixReceiving 2 } 1303 ipfixSessionEntry OBJECT-TYPE 1304 SYNTAX IpfixSessionEntry 1305 MAX-ACCESS not-accessible 1306 STATUS current 1307 DESCRIPTION 1308 "Defines an entry in the ipfixSessionTable" 1309 INDEX { 1310 ipfixExporterIndex, 1311 ipfixSessionId 1312 } 1313 ::= { ipfixSessionTable 1 } 1315 IpfixSessionEntry ::= 1316 SEQUENCE { 1317 ipfixSessionId Integer32, 1318 ipfixSessionStatus INTEGER, 1319 ipfixSessionProtocol Integer32, 1320 ipfixSessionDstPort Integer32, 1321 ipfixSessionSrcPort Integer32 1322 } 1324 ipfixSessionId OBJECT-TYPE 1325 SYNTAX Integer32 (1..2147483647) 1326 MAX-ACCESS not-accessible 1327 STATUS current 1328 DESCRIPTION 1329 "Locally arbitrary, but unique identifier of an entry 1330 in ipfixSessionTable. 1331 The value is expected to remain constant from a 1332 re-initialization of the entity's network management 1333 system to the next re-initialization." 1334 ::= { ipfixSessionEntry 1 } 1336 ipfixSessionStatus OBJECT-TYPE 1337 SYNTAX INTEGER { 1338 unknown(0), 1339 up(1), 1340 down(2) 1341 } 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 "The status of this session." 1346 ::= { ipfixSessionEntry 2 } 1348 ipfixSessionProtocol OBJECT-TYPE 1349 SYNTAX Integer32 (0..256) 1350 MAX-ACCESS read-only 1351 STATUS current 1352 DESCRIPTION 1353 "The transport protocol is used for receiving sampled 1354 packets from the Exporter. The recommended protocols 1355 are TCP (6), UDP (17) and SCTP (132). The default is 1356 SCTP." 1357 ::= { ipfixSessionEntry 3 } 1359 ipfixSessionDstPort OBJECT-TYPE 1360 SYNTAX Integer32 (0..65535) 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "The transport protocol port number of exporter which 1365 enables exporting process." 1366 ::= { ipfixSessionEntry 4 } 1368 ipfixSessionSrcPort OBJECT-TYPE 1369 SYNTAX Integer32 (0..65535) 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "The transport protocol port number of self device which 1374 enables collecting Process." 1375 ::= { ipfixSessionEntry 5 } 1377 -------------------------------------------------------------------- 1378 -- 2: Session Statistics Table 1379 -------------------------------------------------------------------- 1381 ipfixSessionStatsTable OBJECT-TYPE 1382 SYNTAX SEQUENCE OF 1383 IpfixSessionStatsEntry 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "This table lists sessions statistics between exporting 1388 process and collecting process. 1389 The collecting process manages them." 1390 ::= { ipfixReceiving 3 } 1392 ipfixSessionStatsEntry OBJECT-TYPE 1393 SYNTAX IpfixSessionStatsEntry 1394 MAX-ACCESS not-accessible 1395 STATUS current 1396 DESCRIPTION 1397 "Defines an entry in the ipfixSessionStatsTable" 1398 INDEX { ipfixExporterIndex, ipfixSessionId } 1399 ::= { ipfixSessionStatsTable 1 } 1401 IpfixSessionStatsEntry ::= 1402 SEQUENCE { 1403 ipfixSessionPackets Counter32, 1404 ipfixSessionBytes Counter32, 1405 ipfixSessionMessages Counter32, 1406 ipfixSessionDiscardMessages Counter32, 1407 ipfixSessionElapsedTime Gauge32 1408 } 1410 ipfixSessionPackets OBJECT-TYPE 1411 SYNTAX Counter32 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The number of packets received from the Exporter 1416 through this session." 1417 ::= { ipfixSessionStatsEntry 3 } 1419 ipfixSessionBytes OBJECT-TYPE 1420 SYNTAX Counter32 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "The number of bytes received from the exporter 1425 through this session." 1426 ::= { ipfixSessionStatsEntry 4 } 1428 ipfixSessionMessages OBJECT-TYPE 1429 SYNTAX Counter32 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "The number of IPFIX messages received from 1434 the exporter through this session." 1435 ::= { ipfixSessionStatsEntry 5 } 1437 ipfixSessionDiscardMessages OBJECT-TYPE 1438 SYNTAX Counter32 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "This indicates the number of received IPFIX Message that 1443 might be malformed or cant not be encoded." 1444 ::= { ipfixSessionStatsEntry 6 } 1446 ipfixSessionElapsedTime OBJECT-TYPE 1447 SYNTAX Gauge32 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "This timer indicates how long this session has been 1452 connected. This elapsed time of the session of IPFIX 1453 presents in second." 1454 ::= { ipfixSessionStatsEntry 9 } 1456 -------------------------------------------------------------------- 1457 -- 4: Observation domain statistics table 1458 -------------------------------------------------------------------- 1460 ipfixObdomainStatsTable OBJECT-TYPE 1461 SYNTAX SEQUENCE OF 1462 IpfixObdomainStatsEntry 1463 MAX-ACCESS not-accessible 1464 STATUS current 1465 DESCRIPTION 1466 "This table lists statistics objects that have data per 1467 observation domain." 1468 ::= { ipfixReceiving 4 } 1470 ipfixObdomainStatsEntry OBJECT-TYPE 1471 SYNTAX IpfixObdomainStatsEntry 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "Defines an entry in the 1476 ipfixObdomainStatsTable." 1477 INDEX { 1478 ipfixExporterIndex, ipfixSessionId, 1479 ipfixObdomainId } 1480 ::= { ipfixObdomainStatsTable 1 } 1482 IpfixObdomainStatsEntry ::= 1483 SEQUENCE { 1484 ipfixObdomainId Integer32, 1485 ipfixObdomainMessages Counter32, 1486 ipfixObdomainFlows Counter32, 1487 ipfixObdomainTemplates Counter32, 1488 ipfixObdomainLatestSeqNumber Integer32, 1489 ipfixObdomainDisorderdSeqNumbers Counter32 1490 } 1492 ipfixObdomainId OBJECT-TYPE 1493 SYNTAX Integer32(1..2147483647) 1494 MAX-ACCESS not-accessible 1495 STATUS current 1496 DESCRIPTION 1497 "It uses the observation domain id in the received 1498 IPFIX message header." 1499 ::= { ipfixObdomainStatsEntry 1 } 1501 ipfixObdomainMessages OBJECT-TYPE 1502 SYNTAX Counter32 1503 MAX-ACCESS read-only 1504 STATUS current 1505 DESCRIPTION 1506 "The number of IPFIX messages received from the Exporter." 1507 ::= { ipfixObdomainStatsEntry 3 } 1509 ipfixObdomainFlows OBJECT-TYPE 1510 SYNTAX Counter32 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "The number of flow records received from the Exporter." 1515 ::= { ipfixObdomainStatsEntry 4 } 1517 ipfixObdomainTemplates OBJECT-TYPE 1518 SYNTAX Counter32 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "The number of templates received from the Exporter." 1523 ::= { ipfixObdomainStatsEntry 5 } 1525 ipfixObdomainLatestSeqNumber OBJECT-TYPE 1526 SYNTAX Integer32 1527 MAX-ACCESS read-only 1528 STATUS current 1529 DESCRIPTION 1530 "The latest sequence number. The collecting process 1531 overwrites to this object when it receives IPFIX message." 1532 ::= { ipfixObdomainStatsEntry 6 } 1534 ipfixObdomainDisorderdSeqNumbers OBJECT-TYPE 1535 SYNTAX Counter32 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "This counter indicates inconformable numbers of sequence 1540 number. The collecting process check consistency between 1541 received sequence number and received data flows. 1542 This counter is added up this inclement, if it recognize 1543 there are some flows that have not been received." 1544 ::= { ipfixObdomainStatsEntry 7 } 1546 -------------------------------------------------------------------- 1547 -- 5: Template Record Table 1548 -------------------------------------------------------------------- 1550 ipfixTemplateTable OBJECT-TYPE 1551 SYNTAX SEQUENCE OF 1552 IpfixTemplateEntry 1553 MAX-ACCESS not-accessible 1554 STATUS current 1555 DESCRIPTION 1556 "This table lists templates that are received by the 1557 collecting process. This process manages them." 1558 ::= { ipfixReceiving 5 } 1560 ipfixTemplateEntry OBJECT-TYPE 1561 SYNTAX IpfixTemplateEntry 1562 MAX-ACCESS not-accessible 1563 STATUS current 1564 DESCRIPTION 1565 "Defines an entry in the ipfixTemplateTable" 1566 INDEX { 1567 ipfixExporterIndex, 1568 ipfixSessionId, 1569 ipfixTemplateId, 1570 ipfixTemplateIndex } 1571 ::= { ipfixTemplateTable 1 } 1573 IpfixTemplateEntry ::= 1574 SEQUENCE { 1575 ipfixTemplateId Integer32, 1576 ipfixTemplateIndex Integer32, 1577 ipfixTemplateFieldId Integer32, 1578 ipfixTemplateFieldLength Integer32 1579 } 1581 ipfixTemplateId OBJECT-TYPE 1582 SYNTAX Integer32 (1..2147483647) 1583 MAX-ACCESS not-accessible 1584 STATUS current 1585 DESCRIPTION 1586 "This number indicates the template id in the 1587 IPFIX message." 1588 ::= { ipfixTemplateEntry 1 } 1590 ipfixTemplateIndex OBJECT-TYPE 1591 SYNTAX Integer32 (1..2147483647) 1592 MAX-ACCESS not-accessible 1593 STATUS current 1594 DESCRIPTION 1595 "The ipfixTemplateIndex specifies the order in which 1596 the information element ids are used in the template 1597 record." 1598 ::= { ipfixTemplateEntry 2 } 1600 ipfixTemplateFieldId OBJECT-TYPE 1601 SYNTAX Integer32 (1..2147483647) 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "This indicates the Information Element Id at position 1606 ipfixTemplateIndex in the template ipfixTemplateId. 1607 This implicitly gives the data type and state values that 1608 are received." 1609 ::= { ipfixTemplateEntry 3 } 1611 ipfixTemplateFieldLength OBJECT-TYPE 1612 SYNTAX Integer32 1613 MAX-ACCESS read-only 1614 STATUS current 1615 DESCRIPTION 1616 "This indicates the length of each Information Element Ids. 1617 Especially, in variable length type it is specified 1618 as 65535." 1619 ::= { ipfixTemplateEntry 4 } 1621 -------------------------------------------------------------------- 1622 -- 6: Template Statistics Table 1623 -------------------------------------------------------------------- 1625 ipfixTemplateStatsTable OBJECT-TYPE 1626 SYNTAX SEQUENCE OF 1627 IpfixTemplateStatsEntry 1628 MAX-ACCESS not-accessible 1629 STATUS current 1630 DESCRIPTION 1631 "This table lists statistics objects that have data per 1632 template." 1633 ::= { ipfixReceiving 6 } 1635 ipfixTemplateStatsEntry OBJECT-TYPE 1636 SYNTAX IpfixTemplateStatsEntry 1637 MAX-ACCESS not-accessible 1638 STATUS current 1639 DESCRIPTION 1640 "Defines an entry in the ipfixTemplateStatsTable" 1641 INDEX { 1642 ipfixExporterIndex, 1643 ipfixSessionId, 1644 ipfixTemplateId } 1645 ::= { ipfixTemplateStatsTable 1 } 1647 IpfixTemplateStatsEntry ::= 1648 SEQUENCE { 1649 ipfixTempFlows Counter32, 1650 ipfixTempReceivedTime DateAndTime 1651 } 1653 ipfixTempFlows OBJECT-TYPE 1654 SYNTAX Counter32 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "The number of flow records per template received from 1659 Exporter." 1660 ::= { ipfixTemplateStatsEntry 2 } 1662 ipfixTempReceivedTime OBJECT-TYPE 1663 SYNTAX DateAndTime 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "Time that the collecting process received this template. 1668 The collecting process overwrites to this object when it 1669 receives same template." 1670 ::= { ipfixTemplateStatsEntry 3 } 1672 --================================================================== 1673 -- Conformance information 1674 --================================================================== 1676 ipfixCompliances OBJECT IDENTIFIER ::= { ipfixConformance 1 } 1677 ipfixGroups OBJECT IDENTIFIER ::= { ipfixConformance 2 } 1679 --================================================================== 1680 -- Compliance statements 1681 --================================================================== 1683 ipfixCompliance MODULE-COMPLIANCE 1684 STATUS current 1685 DESCRIPTION 1686 "An implementation that complies to this module must 1687 implement the objects defined in the mandatory groups 1688 collectGroupExporters, collectGroupTemplates. 1689 The imeplementation of all other objects depends on the 1690 imeplementation of the corresponding functionality in the 1691 equipment." 1692 MODULE -- this module 1693 MANDATORY-GROUPS { 1694 ipfixGroupExporters, 1695 ipfixGroupTemplates 1696 } 1697 GROUP ipfixGroupStatistics 1698 DESCRIPTION 1699 "These objects must be implementes if the statistics 1700 function is implemented in the equipment." 1701 ::= { ipfixCompliances 1 } 1703 --================================================================== 1704 -- MIB groupings 1705 --================================================================== 1707 ipfixGroupExporters OBJECT-GROUP 1708 OBJECTS { 1709 ipfixExporterIpAddressType, 1710 ipfixExporterIpAddress, 1711 ipfixLifeTimeTemplate, 1713 ipfixSessionProtocol, 1714 ipfixSessionDstPort, 1715 ipfixSessionSrcPort, 1716 ipfixSessionStatus 1717 } 1718 STATUS current 1719 DESCRIPTION 1720 "All objects that are basic for the management function 1721 of exporters." 1722 ::= { ipfixGroups 1 } 1724 ipfixGroupTemplates OBJECT-GROUP 1725 OBJECTS { 1726 ipfixTemplateFieldId, 1727 ipfixTemplateFieldLength 1728 } 1729 STATUS current 1730 DESCRIPTION 1731 "All objects that are basic for the management function 1732 of templates." 1733 ::= { ipfixGroups 2 } 1735 ipfixGroupStatistics OBJECT-GROUP 1736 OBJECTS { 1737 ipfixSessionPackets, 1738 ipfixSessionBytes, 1739 ipfixSessionMessages, 1740 ipfixSessionDiscardMessages, 1741 ipfixSessionElapsedTime, 1743 ipfixObdomainMessages, 1744 ipfixObdomainFlows, 1745 ipfixObdomainTemplates, 1746 ipfixObdomainLatestSeqNumber, 1747 ipfixObdomainDisorderdSeqNumbers, 1749 ipfixTempFlows, 1750 ipfixTempReceivedTime 1751 } 1753 STATUS current 1754 DESCRIPTION 1755 "All objects that are basic for the statistics function." 1756 ::= { ipfixGroups 3 } 1758 END 1760 8. Security Considerations 1762 There are a number of management objects defined in this MIB module 1763 with a MAX-ACCESS clause of read-write and/or read-create. Such 1764 objects may be considered sensitive or vulnerable in some network 1765 environments. The support for SET operations in a non-secure 1766 environment without proper protection can have a negative effect on 1767 network operations. 1769 9. IANA Considerations 1771 This document requires an OID assignment to be made by IANA: 1773 Descriptor OBJECT IDENTIFIER value 1774 ---------- ----------------------- 1775 ipfixMIB { mib-2 xxxxx } 1777 10. Acknowledgment 1779 This document is a product of the IPFIX working group. 1781 11. References 1783 11.1. Normative References 1785 [RFC3917] Quittek, J., Zseby, T., Claise, B., and S. Zander, 1786 "Requirements for IP Flow Information Export (IPFIX)", 1787 RFC 3917, October 2004. 1789 [I-D.ietf-ipfix-architecture] 1790 Sadasivan, G., "Architecture for IP Flow Information 1791 Export", draft-ietf-ipfix-architecture-12 (work in 1792 progress), September 2006. 1794 [I-D.ietf-ipfix-as] 1795 Zseby, T., "IPFIX Applicability", draft-ietf-ipfix-as-10 1796 (work in progress), August 2006. 1798 [I-D.ietf-ipfix-protocol] 1799 Claise, B., "Specification of the IPFIX Protocol for the 1800 Exchange of IP Traffic Flow Information", 1801 draft-ietf-ipfix-protocol-23 (work in progress), 1802 October 2006. 1804 [I-D.ietf-ipfix-info] 1805 Quittek, J., "Information Model for IP Flow Information 1806 Export", draft-ietf-ipfix-info-13 (work in progress), 1807 September 2006. 1809 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1810 "Structure of Management Information Version 2 (SMIv2)", 1811 STD 58, RFC 2578, April 1999. 1813 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1814 "Textual Conventions for SMIv2", STD 58, RFC 2579, 1815 April 1999. 1817 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1818 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1819 April 1999. 1821 11.2. Informative References 1823 [I-D.ietf-psamp-framework] 1824 Duffield, N., "A Framework for Packet Selection and 1825 Reporting", draft-ietf-psamp-framework-10 (work in 1826 progress), January 2005. 1828 [I-D.ietf-psamp-sample-tech] 1829 Zseby, T., "Sampling and Filtering Techniques for IP 1830 Packet Selection", draft-ietf-psamp-sample-tech-07 (work 1831 in progress), July 2005. 1833 [I-D.ietf-psamp-mib] 1834 Dietz, T. and B. Claise, "Definitions of Managed Objects 1835 for Packet Sampling", draft-ietf-psamp-mib-06 (work in 1836 progress), June 2006. 1838 [I-D.ietf-psamp-protocol] 1839 Claise, B., "Packet Sampling (PSAMP) Protocol 1840 Specifications", draft-ietf-psamp-protocol-06 (work in 1841 progress), June 2006. 1843 [RFC1889] Schulzrinne, H., Casner, S., Frederick, R., and V. 1845 Jacobson, "RTP: A Transport Protocol for Real-Time 1846 Applications", RFC 1889, January 1996. 1848 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1849 Requirement Levels", BCP 14, RFC 2119, March 1997. 1851 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1852 "Introduction and Applicability Statements for Internet- 1853 Standard Management Framework", RFC 3410, December 2002. 1855 Authors' Addresses 1857 Thomas Dietz (editor) 1858 NEC Europte Ltd. 1859 Network Laboratories 1860 Kurfuersten-Anlage 36 1861 Heidelberg 69115 1862 DE 1864 Phone: +49 6221 4342-128 1865 Email: dietz@netlab.nec.de 1867 Atsushi Kobayashi 1868 NTT Information Sharing Platform Laboratories 1869 3-9-11 Midori-cho 1870 Musashino-shi, Tokyo 180-8585 1871 JA 1873 Phone: +81-422-59-3978 1874 Email: akoba@nttv6.net 1876 Benoit Claise 1877 Cisco Systems 1878 De Kleetlaan 6a b1 1879 Degem 1831 1880 BE 1882 Phone: +32 2 704 5622 1883 Email: bclaise@cisco.com 1885 Intellectual Property Statement 1887 The IETF takes no position regarding the validity or scope of any 1888 Intellectual Property Rights or other rights that might be claimed to 1889 pertain to the implementation or use of the technology described in 1890 this document or the extent to which any license under such rights 1891 might or might not be available; nor does it represent that it has 1892 made any independent effort to identify any such rights. Information 1893 on the procedures with respect to rights in RFC documents can be 1894 found in BCP 78 and BCP 79. 1896 Copies of IPR disclosures made to the IETF Secretariat and any 1897 assurances of licenses to be made available, or the result of an 1898 attempt made to obtain a general license or permission for the use of 1899 such proprietary rights by implementers or users of this 1900 specification can be obtained from the IETF on-line IPR repository at 1901 http://www.ietf.org/ipr. 1903 The IETF invites any interested party to bring to its attention any 1904 copyrights, patents or patent applications, or other proprietary 1905 rights that may cover technology that may be required to implement 1906 this standard. Please address the information to the IETF at 1907 ietf-ipr@ietf.org. 1909 Disclaimer of Validity 1911 This document and the information contained herein are provided on an 1912 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1913 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1914 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1915 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1916 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1917 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1919 Copyright Statement 1921 Copyright (C) The Internet Society (2006). This document is subject 1922 to the rights, licenses and restrictions contained in BCP 78, and 1923 except as set forth therein, the authors retain all their rights. 1925 Acknowledgment 1927 Funding for the RFC Editor function is currently provided by the 1928 Internet Society.