http2 window size use case
draft-chen-httpbis-window-size-use-case-00

Document Type Active Internet-Draft (individual)
Authors chenmeiling  , Li Su 
Last updated 2020-12-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
httpbis                                                          M. Chen
Internet-Draft                                                    Li. Su
Intended status: Informational                              China Mobile
Expires: June 17, 2021                                 December 14, 2020

                       http2 window size use case
               draft-chen-httpbis-window-size-use-case-00

Abstract

   This document presents an use case which actually happening in our
   network, when window_size_increment in the window update frame less
   than 128 bytes and the increased window size also less than 128
   bytes, then network connection will come to an error.

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on June 17, 2021.

Copyright Notice

   Copyright (c) 2020 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
   (https://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.

Chen & Su                 Expires June 17, 2021                 [Page 1]
Internet-Draft         http2 window size use case          December 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Use Case  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   The following content is from RFC 7540[RFC7540]

   When an HTTP/2 connection is first established, new streams are
   created with an initial flow-control window size of 65,535 octets.
   The connection flow-control window is also 65,535 octets.  Both
   endpoints can adjust the initial window size for new streams by
   including a value for SETTINGS_INITIAL_WINDOW_SIZE in the SETTINGS
   frame that forms part of the connection preface.  The connection
   flow-control window can only be changed using WINDOW_UPDATE frames.

   SETTINGS_INITIAL_WINDOW_SIZE (0x4): Indicates the sender's initial
   window size (in octets) for stream-level flow control.  The initial
   value is 2^16-1 (65,535) octets.

   Window Size Increment defined in the Window_update is 31, the legal
   range for the increment to the flow-control window is 1 to 2^31-1
   (2,147,483,647) octets.

   RFC 7540 just Specifies the maximum value of Window and the Window
   Size Increment, But there is no obvious rule about minimum values.

2.  Terminology

   The readers should be familiar with the terms defined in.

   In addition, this document makes use of the following terms:

   Window_update:  The WINDOW_UPDATE frame (type=0x8) is used to
      implement flow control;

3.  Use Case

   This section describes use case which happens between two different
   manufacturers.  They both use HTTP2.0 protocol to transmit messages.
   We found this phenomenon, one issues a regular registration request,

Chen & Su                 Expires June 17, 2021                 [Page 2]
Internet-Draft         http2 window size use case          December 2020

   the other one receives the request, but judged to be attack
   behaviour.

 +---------+                        +----------+
 | Sender  |                        |Receiver  |
 |         |                        |          |
 +----+----+                        +-----+----+
      |    Reqistration request           |
      +----------------------------------->
      |                                   |
      |                                   |
      +----------------------------------->
Show full document text