Registration Policy for TCP Header Flags
draft-kuehlewind-tcpm-flags-registry-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-17
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. Kuehlewind
Internet-Draft                                                  Ericsson
Intended status: Standards Track                       November 18, 2019
Expires: May 21, 2020

                Registration Policy for TCP Header Flags
                draft-kuehlewind-tcpm-flags-registry-00

Abstract

   RFC2780 specifies the registration policy for reserved TCP header
   flags as Standards Action.  RFC3168 created an IANA registry for
   these header flags and registered bit 8 (CWR) and 9 (ECE).  This
   draft changes the registration policy of the registration to IETF
   Review as usually new TCP mechanisms that could use the remaining
   reserved flags will be first specified as experimental.  Not noting
   any of those experiments in the registry would undermine the purpose
   of having a registry.  However, care must be taken, as only a few
   reserved flags are left and if a new (experimental) mechanism sees
   deployment in the Internet, the flag cannot be unassigned anymore or
   used for something else.

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 May 21, 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Kuehlewind                Expires May 21, 2020                  [Page 1]
Internet-Draft      Registration Policy for TCP Flags      November 2019

   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
   2.  Notation  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Registration Policy for TCP Header Flags  . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Consideration  . . . . . . . . . . . . . . . . . . .   4
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [RFC2780] specifies the registration policy for reserved TCP header
   flags as Standards Action.  In section 9.2 (Reserved Bits in TCP
   Header) is says:

    "The reserved bits in the TCP header are assigned following a Standards Action process."

   Earlier on, in section 2 (Temporary Assignments) it also says

    "From time to time temporary assignments are made in the values for fields in these headers for use in experiments.  IESG Approval is required for any such temporary assignments."

   However, it does not specify what exactly is meant with a temporary
   assignment and how this could work for TCP header given they can
   hardly be re-purposed once deployed on the Internet.

   [RFC3168] created a IANA registry for these header flags and
   registered bit 8 (CWR) and 9 (ECE).  [RFC3540] assigned bit 7 to the
   experimental ECN Nonce extension and [RFC8311] recently declared
   RFC3540 as historic and changed the assignment to reserved, as ECN
   Nonce was not deployed on the Internet.  The purpose of RFC8311 was
   to concentrate updates to Standard Track RFCs in one document in oder
   to enable new experimentation with various ECN-related mechanisms.
   However, RFC8311 does not provide any recommendation of the use of
   bit 7 and the TCP flags registry.

Kuehlewind                Expires May 21, 2020                  [Page 2]
Internet-Draft      Registration Policy for TCP Flags      November 2019

2.  Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text