Cisco Systems Export of Application Information in IP Flow Information Export (IPFIX)
RFC 6759
Document | Type |
RFC - Informational
(November 2012; Errata)
Was draft-claise-export-application-info-in-ipfix (individual in ops area)
|
|
---|---|---|---|
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text pdf html bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6759 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ron Bonica | ||
IESG note | Individual Submission, AD-sponsored, Nevil Brownlee is the document shepherd, | ||
Send notices to | n.brownlee@auckland.ac.nz |
Internet Engineering Task Force (IETF) B. Claise Request for Comments: 6759 P. Aitken Category: Informational N. Ben-Dvora ISSN: 2070-1721 Cisco Systems, Inc. November 2012 Cisco Systems Export of Application Information in IP Flow Information Export (IPFIX) Abstract This document specifies a Cisco Systems extension to the IPFIX information model specified in RFC 5102 to export application information. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6759. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Claise, et al. Informational [Page 1] RFC 6759 Export of App. Info. in IPFIX November 2012 Table of Contents 1. Introduction ....................................................3 1.1. Application Information Use Cases ..........................5 1.2. Conventions Used in This Document ..........................5 2. IPFIX Documents Overview ........................................5 3. Terminology .....................................................6 3.1. New Terminology ............................................6 4. applicationId Information Element Specification .................6 4.1. Existing Classification Engine IDs .........................7 4.2. Selector ID Length per Classification ID ..................11 4.3. Application Name Options Template Record ..................12 4.4. Resolving IANA L4 Port Discrepancies ......................13 5. Grouping Applications with Attributes ..........................13 5.1. Options Template Record for Attribute Values ..............15 6. Application ID Examples ........................................15 6.1. Example 1: Layer 2 Protocol ...............................15 6.2. Example 2: Standardized IANA Layer 3 Protocol .............16 6.3. Example 3: Proprietary Layer 3 Protocol ...................17 6.4. Example 4: Standardized IANA Layer 4 Port .................18 6.5. Example 5: Layer 7 Application ............................19 6.6. Example 6: Layer 7 Application with Private Enterprise Number (PEN) ...................................21 6.7. Example: Port Obfuscation .................................22 6.8. Example: Application Name Mapping Options Template ........23 6.9. Example: Attributes Values Options Template Record ........24 7. IANA Considerations ............................................25 7.1. New Information Elements ..................................25 7.1.1. applicationDescription .............................25 7.1.2. applicationId ......................................26 7.1.3. applicationName ....................................26 7.1.4. classificationEngineId .............................26 7.1.5. applicationCategoryName ............................29 7.1.6. applicationSubCategoryName .........................29 7.1.7. applicationGroupName ...............................29 7.1.8. p2pTechnology ......................................29 7.1.9. tunnelTechnology ...................................30 7.1.10. encryptedTechnology ...............................30 7.2. Classification Engine ID Registry .........................30 8. Security Considerations ........................................30 9. References .....................................................31Show full document text