HTTP/2 Configuration Profile for the Internet of Things
draft-montenegro-httpbis-h2ot-profile-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network Working Group                                      G. Montenegro
Internet-Draft                                                 Microsoft
Intended status: Informational                               S. Cespedes
Expires: September 11, 2017                               NIC Labs Chile
                                                               S. Loreto
                                                                Ericsson
                                                              R. Simpson
                                                        General Electric
                                                          March 10, 2017

        HTTP/2 Configuration Profile for the Internet of Things
                draft-montenegro-httpbis-h2ot-profile-00

Abstract

   This document define an HTTP/2 configuration profile for IoT.

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 http://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 September 11, 2017.

Copyright Notice

   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

Montenegro, et al.     Expires September 11, 2017               [Page 1]
Internet-Draft                H2oT Profile                    March 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Configuration Profile of HTTP/2 for IoT . . . . . . . . . . .   2
   3.  Negotiation of HTTP/2 for IoT . . . . . . . . . . . . . . . .   3
   4.  Implementation Considerations . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Unlike HTTP/1.X, HTTP/2 is suitable for many IoT applications.  Even
   though IoT was not the primary scenario when HTTP/2 was designed, the
   protocol is compact, configurable and flexible.  The use of header
   compression as well as the binary encoding of the protocol reduces
   the size of HTTP/2 flows as compared to HTTP/1.1.  HTTP/2's ability
   to reuse connections for multiple streams reduces connection
   establishment overhead, such as TCP connection establishment and TLS
   session establishment.  HTTP/2 has been found to be amenable to
   implementation on class 2 devices, per the constrained device
   classification in section 3 of [RFC7228].  Furthermore, initial
   efforts have resulted in successful experiments on class 1 devices.

   This document discusses how to configure HTTP/2 so as to adapt it
   better to IoT scenarios, including those in which the devices running
   the protocol have constrained resources.

2.  Configuration Profile of HTTP/2 for IoT

   HTTP/2 has many negotiable settings that can improve its performance
   for IoT applications by reducing bandwidth, codespace, and RAM
   requirements.  Specifically, the following settings and values have
   been found to be useful in IoT applications:

   o  SETTINGS_HEADER_TABLE_SIZE: this setting allows hosts to limit the
      size of the header compression table used for decoding, reducing
      required RAM, but potentially increasing bandwidth requirements.
      Initial value per HTTP/2 is 4096.  IoT scenarios might benefit
Show full document text