< draft-yourtchenko-cisco-ies-09.txt   draft-yourtchenko-cisco-ies-11.txt >
Network Working Group A. Yourtchenko Network Working Group A. Yourtchenko
Internet-Draft P. Aitken Internet-Draft P. Aitken
Intended status: Informational B. Claise Intended status: Informational B. Claise
Expires: July 19, 2014 Cisco Systems, Inc. Expires: September 26, 2014 Cisco Systems, Inc.
January 15, 2014 March 25, 2014
Cisco Specific Information Elements reused in IPFIX Cisco Specific Information Elements reused in IPFIX
draft-yourtchenko-cisco-ies-09 draft-yourtchenko-cisco-ies-11
Abstract Abstract
This document describes some additional Information Elements of Cisco This document describes some additional IPFIX Information Elements in
Systems, Inc. that are not listed in RFC3954. the range of 1-127, which is the range compatible with field types
used by NetFlow version 9 in RFC3954, as specified in the IPFIX
Information Model RFC 7012.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 July 19, 2014. This Internet-Draft will expire on September 26, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 10 skipping to change at page 2, line 10
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Information Elements Overview . . . . . . . . . . . . . . . . 3 3. Information Elements Overview . . . . . . . . . . . . . . . . 3
4. Information Elements . . . . . . . . . . . . . . . . . . . . 3 4. Information Elements . . . . . . . . . . . . . . . . . . . . 4
4.1. samplingInterval . . . . . . . . . . . . . . . . . . . . 3 4.1. samplingInterval . . . . . . . . . . . . . . . . . . . . 4
4.2. samplingAlgorithm . . . . . . . . . . . . . . . . . . . . 4 4.2. samplingAlgorithm . . . . . . . . . . . . . . . . . . . . 4
4.3. engineType . . . . . . . . . . . . . . . . . . . . . . . 4 4.3. engineType . . . . . . . . . . . . . . . . . . . . . . . 4
4.4. engineId . . . . . . . . . . . . . . . . . . . . . . . . 4 4.4. engineId . . . . . . . . . . . . . . . . . . . . . . . . 5
4.5. ipv4RouterSc . . . . . . . . . . . . . . . . . . . . . . 5 4.5. ipv4RouterSc . . . . . . . . . . . . . . . . . . . . . . 5
4.6. samplerId . . . . . . . . . . . . . . . . . . . . . . . . 5 4.6. samplerId . . . . . . . . . . . . . . . . . . . . . . . . 5
4.7. samplerMode . . . . . . . . . . . . . . . . . . . . . . . 5 4.7. samplerMode . . . . . . . . . . . . . . . . . . . . . . . 5
4.8. samplerRandomInterval . . . . . . . . . . . . . . . . . . 5 4.8. samplerRandomInterval . . . . . . . . . . . . . . . . . . 6
4.9. classId . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.9. classId . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.10. samplerName . . . . . . . . . . . . . . . . . . . . . . . 6 4.10. samplerName . . . . . . . . . . . . . . . . . . . . . . . 6
4.11. flagsAndSamplerId . . . . . . . . . . . . . . . . . . . . 6 4.11. flagsAndSamplerId . . . . . . . . . . . . . . . . . . . . 6
4.12. forwardingStatus . . . . . . . . . . . . . . . . . . . . 6 4.12. forwardingStatus . . . . . . . . . . . . . . . . . . . . 6
4.13. srcTrafficIndex . . . . . . . . . . . . . . . . . . . . . 8 4.13. srcTrafficIndex . . . . . . . . . . . . . . . . . . . . . 8
4.14. dstTrafficIndex . . . . . . . . . . . . . . . . . . . . . 8 4.14. dstTrafficIndex . . . . . . . . . . . . . . . . . . . . . 8
4.15. className . . . . . . . . . . . . . . . . . . . . . . . . 8 4.15. className . . . . . . . . . . . . . . . . . . . . . . . . 8
4.16. layer2packetSectionOffset . . . . . . . . . . . . . . . . 8 4.16. layer2packetSectionOffset . . . . . . . . . . . . . . . . 9
4.17. layer2packetSectionSize . . . . . . . . . . . . . . . . . 9 4.17. layer2packetSectionSize . . . . . . . . . . . . . . . . . 9
4.18. layer2packetSectionData . . . . . . . . . . . . . . . . . 9 4.18. layer2packetSectionData . . . . . . . . . . . . . . . . . 9
5. Other Information Elements . . . . . . . . . . . . . . . . . 9 5. Other Information Elements . . . . . . . . . . . . . . . . . 9
5.1. Performance Metrics IEs . . . . . . . . . . . . . . . . . 9 5.1. Performance Metrics IEs . . . . . . . . . . . . . . . . . 9
5.2. Application Information IEs . . . . . . . . . . . . . . . 9 5.2. Application Information IEs . . . . . . . . . . . . . . . 9
5.3. IEs assigned for NetFlow v9 compatibility . . . . . . . . 9 5.3. IEs assigned for NetFlow v9 compatibility . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10 8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . 11
Appendix A. XML Specification of IPFIX Information Elements . . 11 Appendix A. XML Specification of IPFIX Information Elements . . 12
Appendix B. Changes . . . . . . . . . . . . . . . . . . . . . . 18 Appendix B. Changes . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
The section 4 of [RFC7012] defines the IPFIX Information Elements in The section 4 of [RFC7012] defines the IPFIX Information Elements in
the range of 1-127 to be compatible with the NetFlow version 9 the range of 1-127 to be compatible with the NetFlow version 9
fields, as specified in the "Cisco Systems NetFlow Services Export fields, as specified in the "Cisco Systems NetFlow Services Export
Version 9" [RFC3954]. As [RFC3954] was specified in 2004, it does Version 9" [RFC3954]. As [RFC3954] was specified in 2004, it does
not contain all NetFlow version 9 specific fields in the range 1-127. not contain all NetFlow version 9 specific fields in the range 1-127.
The question was asked whether IPFIX Devices should exclusively The question was asked whether IPFIX Devices should exclusively
report the IPFIX IANA IEs [IPFIX-IANA] ? In other words, when report the IPFIX IANA IEs [IPFIX-IANA]. In other words, when
upgrading from a NetFlow metering process to an IPFIX Metering upgrading from a NetFlow metering process to an IPFIX Metering
Process, should the IPFIX Devices stop reporting NetFlow version 9 Process, should the IPFIX Devices stop reporting NetFlow version 9
specific IEs that were not registered in IANA [IPFIX-IANA] ? specific IEs that were not registered in IANA [IPFIX-IANA]?
This document is intended to fill the gap in this IE range. That This document is intended to fill the gap in this IE range. It
way, IPFIX implementations could export all the IEs specified in describes some additional IPFIX Information Elements in the range of
IANA, regardless of the range. 1-127, which is the range compatible with field types used by NetFlow
version 9 in [RFC3954], as specified in the IPFIX Information Model
[RFC7012]. With this, IPFIX implementations could export all the
Information Elements specified in IANA [IPFIX-IANA], regardless of
the range.
This document followed the [RFC7013] rules (Guidelines for Authors
and Reviewers of IPFIX Information Elements). This document does not
extend [RFC3954]. The IPFIX Protocol ([RFC7011]) has its own
Information Model ([RFC7012], IANA [IPFIX-IANA]) which is extensible
upon application to IANA, subject to expert review by IE-doctors
([RFC7013]). This draft extends the IPFIX Information Model.
2. Terminology 2. Terminology
IPFIX-specific terminology used in this document is defined in IPFIX-specific terminology used in this document is defined in
Section 2 of [RFC7011]. As in [RFC7011], these IPFIX-specific terms Section 2 of [RFC7011]. As in [RFC7011], these IPFIX-specific terms
have the first letter of a word capitalized when used in this have the first letter of a word capitalized when used in this
document. document.
3. Information Elements Overview 3. Information Elements Overview
skipping to change at page 5, line 13 skipping to change at page 5, line 23
Status: deprecated Status: deprecated
4.5. ipv4RouterSc 4.5. ipv4RouterSc
Description: Description:
This is a platform-specific field for Catalyst 5000/Catalyst 6000 This is a platform-specific field for Catalyst 5000/Catalyst 6000
family. It is used to store the address of a router that is being family. It is used to store the address of a router that is being
shortcut when performing MultiLayer Switching. shortcut when performing MultiLayer Switching.
Abstract Data Type: ipv4Address Abstract Data Type: ipv4Address
ElementId: 43 ElementId: 43
Semantics: identifier Semantics: default
Status: deprecated Status: deprecated
Reference: [CCO-MLS] describes the MultiLayer Switching. Reference: [CCO-MLS] describes the MultiLayer Switching.
4.6. samplerId 4.6. samplerId
Description: Description:
Deprecated in favor of 302 selectorId. The unique identifier Deprecated in favor of 302 selectorId. The unique identifier
associated with samplerName. associated with samplerName.
Abstract Data Type: unsigned8 Abstract Data Type: unsigned8
ElementId: 48 ElementId: 48
skipping to change at page 9, line 39 skipping to change at page 9, line 51
Performance metrics will need a consolidation in the industry, based Performance metrics will need a consolidation in the industry, based
on RFC6390. Once this consolidation happens, via a separate document on RFC6390. Once this consolidation happens, via a separate document
the IEs 65-69 will either be assigned in the IANA registry or their the IEs 65-69 will either be assigned in the IANA registry or their
status will be deprecated. status will be deprecated.
5.2. Application Information IEs 5.2. Application Information IEs
ElementId: 101 ElementId: 101
ElementId: 94 .. 97 ElementId: 94 .. 96
Please refer to the RFC 6759 [RFC6759] Please refer to the RFC 6759 [RFC6759]
5.3. IEs assigned for NetFlow v9 compatibility 5.3. IEs assigned for NetFlow v9 compatibility
ElementId: 105..126 ElementId: 105..127
These element IDs are not covered by this draft and left "as is", These element IDs are not covered by this draft and left "as is",
i.e. for Netflow v9 compatibility. i.e. for NetFlow v9 compatibility.
6. IANA Considerations 6. IANA Considerations
This document specifies several new IPFIX Information Elements in the This document specifies several new IPFIX Information Elements in the
IPFIX Information Element registry as defined in Section 3 above. IPFIX Information Element registry as defined in Section 3 above.
The following Information Elements must be assigned: The following Information Elements must be assigned:
o IE Number 34 for the samplingInterval IE o IE Number 34 for the samplingInterval IE
o IE Number 35 for the samplingAlgorithm IE o IE Number 35 for the samplingAlgorithm IE
o IE Number 38 for the engineType IE o IE Number 38 for the engineType IE
skipping to change at page 10, line 37 skipping to change at page 10, line 45
o IE Number 103 for the layer2packetSectionSize IE o IE Number 103 for the layer2packetSectionSize IE
o IE Number 104 for the layer2packetSectionData IE o IE Number 104 for the layer2packetSectionData IE
7. Security Considerations 7. Security Considerations
This document specifies the definitions of several Information This document specifies the definitions of several Information
Elements and does not alter the security considerations of the base Elements and does not alter the security considerations of the base
protocol. Please refer to the security considerations sections of protocol. Please refer to the security considerations sections of
RFC 3954 [RFC3954] and RFC 7012 [RFC7012]. RFC 3954 [RFC3954] and RFC 7012 [RFC7012].
However, the export of the sections of the packet payload may
unintentionally change the security assumptions of other protocols.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of [RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of
the IP Flow Information Export (IPFIX) Protocol for the the IP Flow Information Export (IPFIX) Protocol for the
Exchange of Flow Information", STD 77, RFC 7011, September Exchange of Flow Information", STD 77, RFC 7011, September
2013. 2013.
8.2. Informative References 8.2. Informative References
skipping to change at page 11, line 42 skipping to change at page 11, line 47
[RFC3954] Claise, B., "Cisco Systems NetFlow Services Export Version [RFC3954] Claise, B., "Cisco Systems NetFlow Services Export Version
9", RFC 3954, October 2004. 9", RFC 3954, October 2004.
[RFC6759] Claise, B., Aitken, P., and N. Ben-Dvora, "Cisco Systems [RFC6759] Claise, B., Aitken, P., and N. Ben-Dvora, "Cisco Systems
Export of Application Information in IP Flow Information Export of Application Information in IP Flow Information
Export (IPFIX)", RFC 6759, November 2012. Export (IPFIX)", RFC 6759, November 2012.
[RFC7012] Claise, B. and B. Trammell, "Information Model for IP Flow [RFC7012] Claise, B. and B. Trammell, "Information Model for IP Flow
Information Export (IPFIX)", RFC 7012, September 2013. Information Export (IPFIX)", RFC 7012, September 2013.
[RFC7013] Trammell, B. and B. Claise, "Guidelines for Authors and
Reviewers of IP Flow Information Export (IPFIX)
Information Elements", BCP 184, RFC 7013, September 2013.
Appendix A. XML Specification of IPFIX Information Elements Appendix A. XML Specification of IPFIX Information Elements
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<fieldDefinitions xmlns="urn:ietf:params:xml:ns:ipfix-info" <fieldDefinitions xmlns="urn:ietf:params:xml:ns:ipfix-info"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:ipfix-info xsi:schemaLocation="urn:ietf:params:xml:ns:ipfix-info
ipfix-info.xsd"> ipfix-info.xsd">
<field name="samplingInterval" dataType="unsigned32" <field name="samplingInterval" dataType="unsigned32"
skipping to change at page 13, line 4 skipping to change at page 13, line 16
<field name="engineId" dataType="unsigned8" <field name="engineId" dataType="unsigned8"
group="" group=""
dataTypeSemantics="identifier" dataTypeSemantics="identifier"
elementId="39" applicability="flow" status="deprecated"> elementId="39" applicability="flow" status="deprecated">
<description> <description>
<paragraph> <paragraph>
VIP or line card slot number of the flow switching engine in a VIP or line card slot number of the flow switching engine in a
router/switch. Reserved for internal use on the collector. router/switch. Reserved for internal use on the collector.
</paragraph> </paragraph>
</description> </description>
</field> </field>
<field name="ipv4RouterSc" dataType="ipv4Address" <field name="ipv4RouterSc" dataType="ipv4Address"
group="" group=""
dataTypeSemantics="identifier" dataTypeSemantics="default"
elementId="43" applicability="flow" status="deprecated"> elementId="43" applicability="flow" status="deprecated">
<description> <description>
<paragraph> <paragraph>
This is a platform-specific field for Catalyst 5000/Catalyst This is a platform-specific field for Catalyst 5000/Catalyst
6000 family. It is used to store the address of a router that is 6000 family. It is used to store the address of a router that is
being shortcut when performing MultiLayer Switching. being shortcut when performing MultiLayer Switching.
</paragraph> </paragraph>
</description> </description>
<reference> <reference>
http://www http://www
skipping to change at page 19, line 12 skipping to change at page 19, line 23
table 1 in -07; mark 101-103 IEs as deprecated, include the paragraph table 1 in -07; mark 101-103 IEs as deprecated, include the paragraph
on IE 105..126 that are not discussed in this draft. on IE 105..126 that are not discussed in this draft.
09: now that IANA assigned the IPFIX Information Elements in draft- 09: now that IANA assigned the IPFIX Information Elements in draft-
ietf-ipfix-data-link-layer-monitoring, this draft is updated to ietf-ipfix-data-link-layer-monitoring, this draft is updated to
simplify IANA's/editor's work, with changes as follows. TBD02 became simplify IANA's/editor's work, with changes as follows. TBD02 became
409 as sectionOffset is now assigned by IANA. Removed "EDITOR's 409 as sectionOffset is now assigned by IANA. Removed "EDITOR's
NOTE" for layer2packetSectionOffset, layer2packetSectionSize, NOTE" for layer2packetSectionOffset, layer2packetSectionSize,
layer2packetSectionData, ietf-ipfix-data-link-layer-monitoring. layer2packetSectionData, ietf-ipfix-data-link-layer-monitoring.
10: reflect the comments from GEN-ART / LC reviews. Change the
wording in abstract/introduction, add required clarifications. Per
Andrew Feren, the semantic for ipv4RouterSc should be "default", not
"identifier" - fixed. Alas, unfortunately no way to affect how
xml2rfc trims the super-long URLs, so I could not make splitting of
the URLs nicer.
11: remove the sentence from 'security considerations' per thread
about Alissa Cooper's DISCUSS thread. Remove the #97, which is not
in RFC6759.
Authors' Addresses Authors' Addresses
Andrew Yourtchenko Andrew Yourtchenko
Cisco Systems, Inc. Cisco Systems, Inc.
De Kleetlaan, 7 De Kleetlaan, 7
Brussels, Diegem B-1831 Brussels, Diegem B-1831
Belgium Belgium
Phone: +32 2 704 5494 Phone: +32 2 704 5494
Email: ayourtch@cisco.com Email: ayourtch@cisco.com
 End of changes. 22 change blocks. 
28 lines changed or deleted 51 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/