Browse Prior Art Database

Revision of the tcpControlBits IP Flow Information Export (IPFIX) Information Element (RFC7125)

IP.com Disclosure Number: IPCOM000234887D
Original Publication Date: 2014-Feb-01
Included in the Prior Art Database: 2014-Feb-12
Document File: 12 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Trammell: AUTHOR [+2]

Abstract

As defined in the IANA IPFIX Information Element Registry [IANA-IPFIX], taken from [RFC5102], the tcpControlBits Information Element for IPFIX [RFC7011] only covers the original 6 bits from [RFC0793]. To allow IPFIX to be used to measure the use of ECN, and to bring the IPFIX Information Element definition in line with the current definition of the TCP Flags header field, it is necessary to revise this definition.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

Internet Engineering Task Force (IETF)                       B. Trammell Request for Comments: 7125                                    ETH Zurich Category: Informational                                        P. Aitken ISSN: 2070-1721                                       Cisco Systems, Inc                                                            February 2014

                      Revision of the tcpControlBits          IP Flow Information Export (IPFIX) Information Element

Abstract

   This document revises the tcpControlBits IP Flow Information Export    (IPFIX) Information Element as originally defined in RFC 5102 to    reflect changes to the TCP Flags header field since RFC 793.

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/rfc7125.

Copyright Notice

   Copyright (c) 2014 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.

Trammell & Aitken             Informational                     [Page 1]
 RFC 7125                  IPFIX tcpControlBits             February 2014

 1.  Introduction

   Octets 12 and 13 (counting from zero) of the TCP header encode the    data offset (header length) in 4 bits, as well as 12 bits of flags.    The least significant 6 bits of these were defined in [RFC0793] as    URG, ACK, PSH, RST, SYN, and FIN for TCP control.  Subsequently,    [RFC3168] defined the CWR and ECE flags for Explicit Congestion    Notification (ECN) negotiation a...