IP Flow Information Export (IPFIX) Information Elements Extension for TCP Connection Tracking
draft-fu-dots-ipfix-tcp-tracking-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda dots at IETF-98
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DOTS                                                                    
INTERNET-DRAFT                                                     T. Fu
Intended Status: Informational                                   C. Zhou
Expires: September 14, 2017                                     H. Zheng
                                                                  Huawei
                                                          March 13, 2017

   IP Flow Information Export (IPFIX) Information Elements Extension
                      for TCP Connection Tracking
                  draft-fu-dots-ipfix-tcp-tracking-00

Abstract

   This document proposes several new TCP connection related Information
   Elements (IEs) for the IP Flow Information Export (IPFIX) protocol. 
   The new Information Elements can be used to export certain
   characteristics regarding a TCP connection.  Through massive
   gathering of such characteristics, it can help build an image of the
   TCP traffics passing through a network.  The image will facilitate
   the detection of anomaly TCP traffic, especially attacks targeting at
   TCP.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice
 

T. Fu, et al.          Expires September 14, 2017               [Page 1]
INTERNET DRAFT      IPFIX Extension for TCP Tracking      March 13, 2017

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

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions used in this document  . . . . . . . . . . . . . .  4
     2.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Connection Sampling and new IEs  . . . . . . . . . . . . . . .  4
     3.1.  Use Cases for New IEs  . . . . . . . . . . . . . . . . . .  4
       3.1.1.  Response Time Calculation  . . . . . . . . . . . . . .  4
       3.1.2.  Symptoms of Exceptions . . . . . . . . . . . . . . . .  5
   4.  Application of the New IEs for Attack Detection  . . . . . . .  6
     4.1.  Detect Slowloris Attack  . . . . . . . . . . . . . . . . .  6
     4.2.  Detect Out-of-order Packets Attack . . . . . . . . . . . .  7
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

 

T. Fu, et al.          Expires September 14, 2017               [Page 2]
INTERNET DRAFT      IPFIX Extension for TCP Tracking      March 13, 2017

1.  Introduction

   Due to its complex stateful operations, TCP [RFC0793] is especially
   vulnerable to attacks.  The SYN Flood attack is an example, it
   involves with massive malicious clients attempting to set up
   connections with a server, but never completing the three-way
   handshake process, leaving the server-side of the connections in
   waiting states, eventually exhausting the server resources and no new
   connection can be created.

   Attack aiming at TCP can be low and slow in traffic pattern. 
   Sometimes it may not take down the server, but just impair the
Show full document text