HTTP/2 "Dropped Frame" Frame
draft-kerwin-http2-nak-frame-02

Document Type Active Internet-Draft (individual)
Last updated 2019-08-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
Network Working Group                                          M. Kerwin
Internet-Draft                                            August 9, 2019
Intended status: Standards Track
Expires: February 10, 2020

                      HTTP/2 "Dropped Frame" Frame
                    draft-kerwin-http2-nak-frame-02

Abstract

   This document defines an extension to the Hypertext Transfer Protocol
   Version 2 (HTTP/2) that allows an endpoint to signal to its peer that
   an unsupported extension frame was discarded.

Note to Readers

   The issues list for this draft can be found at
   <https://github.com/phluid61/internet-drafts/labels/
   HTTP%2F2%20NAK%20Frame>

   The most recent (often unpublished) draft is at
   <https://phluid61.github.io/internet-drafts/http2-nak-frame/>

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 February 10, 2020.

Copyright Notice

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

Kerwin                  Expires February 10, 2020               [Page 1]
Internet-Draft               http2-nak-frame                 August 2019

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   2
   2.  Additions to HTTP/2 . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  DROPPED_FRAME . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  HTTP/2 Frame Type Registry Update . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     5.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Changelog  . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Out of the box, the Hypertext Transfer Protocol Version 2 (HTTP/2)
   [RFC7540] makes provision for extension frames to be sent on a
   connection, with or without prior agreement from either peer, with
   the assertion that "implementations MUST discard frames that have
   unknown or unsupported types" ([RFC7540], Section 5.5).  However it
   can be useful to explicitly notify the peer if such a frame is
   discarded.

   This document defines an extension to HTTP/2 that allows a peer to
   signal that a received frame was discarded, without altering the
   stream or connection state ([RFC7540], Section 5.1), and in
   particular without triggering an error condition.

1.1.  Notational Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Kerwin                  Expires February 10, 2020               [Page 2]
Internet-Draft               http2-nak-frame                 August 2019

2.  Additions to HTTP/2

   This document introduces a new HTTP/2 frame type ([RFC7540],
   Section 11.2).

2.1.  DROPPED_FRAME

   [[NOTE-1: This is an experimental value; if standardised, a permanent
   value will be assigned. --MK]]

   DROPPED_FRAME frames (type code=0xf1) can be sent on a connection at
   any time after the connection preface except in the middle of a
   header block ([RFC7540], Section 4.3) to indicate that a received
   extension frame was discarded without any other action being taken.

     +---------------+
     |   Type (8)    |
Show full document text