Unfortunate History of Transient Numeric Identifiers
draft-irtf-pearg-numeric-ids-history-03

Document Type Active Internet-Draft (pearg RG)
Authors Fernando Gont  , Ivan Arce 
Last updated 2020-11-23 (latest revision 2020-10-21)
Replaces draft-gont-numeric-ids-history
Stream IRTF
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream IRTF state In RG Last Call
Revised I-D Needed
Consensus Boilerplate Unknown
Document shepherd Sara Dickinson
IESG IESG state I-D Exists::Revised I-D Needed
Telechat date
Responsible AD (None)
Send notices to sara@sinodun.com
Internet Research Task Force (IRTF)                              F. Gont
Internet-Draft                                              SI6 Networks
Intended status: Informational                                   I. Arce
Expires: April 24, 2021                                        Quarkslab
                                                        October 21, 2020

          Unfortunate History of Transient Numeric Identifiers
                draft-irtf-pearg-numeric-ids-history-03

Abstract

   This document analyzes the timeline of the specification and
   implementation of different types of "transient numeric identifiers"
   used in IETF protocols, and how the security and privacy properties
   of such protocols have been affected as a result of it.  It provides
   empirical evidence that advice in this area is warranted.

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 April 24, 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.

Gont & Arce              Expires April 24, 2021                 [Page 1]
Internet-Draft           Predictable Numeric IDs            October 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Threat Model  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IPv4/IPv6 Identification  . . . . . . . . . . . . . . . . . .   4
   5.  TCP Initial Sequence Numbers (ISNs) . . . . . . . . . . . . .   7
   6.  IPv6 Interface Identifiers (IIDs) . . . . . . . . . . . . . .   9
   7.  NTP Reference IDs (REFIDs)  . . . . . . . . . . . . . . . . .  12
   8.  Transport Protocol Ephemeral Port Numbers . . . . . . . . . .  12
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  14
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  14
     12.2.  Informative References . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  25

1.  Introduction

   Networking protocols employ a variety of transient numeric
   identifiers for different protocol objects, ranging from DNS
   Transaction IDs (TxIDs) to transport protocol ephemeral port numbers
   or IPv6 Interface Identifiers (IIDs).  These identifiers typically
   have specific interoperability requirements (e.g. uniqueness during a
   specified period of time), and an associated modes when such
   properties are not met [I-D.irtf-pearg-numeric-ids-generation].

   For more than 30 years, a large number of implementations of the TCP/
   IP protocol suite have been subject to a variety of attacks, with
   effects ranging from Denial of Service (DoS) or data injection, to
   information leakages that could be exploited for pervasive monitoring
   [RFC7258].  The root cause of these issues has been, in many cases,
   poor selection of numeric identifiers, usually as a result of
   insufficient or misleading specifications.

   For example, implementations have been subject to security or privacy
   issues resulting from:

   o  Predictable TCP Initial Sequence Numbers (ISNs) (see e.g.
      [Morris1985])

   o  Predictable transport protocol ephemeral port numbers (see e.g.
      [RFC6056] and [Silbersack2005])

   o  Predictable IPv4 or IPv6 Fragment Identifiers (see e.g.
      [RFC5722], [RFC6274], and [RFC7739])

Gont & Arce              Expires April 24, 2021                 [Page 2]
Internet-Draft           Predictable Numeric IDs            October 2020

   o  Predictable IPv6 IIDs (see e.g.  [RFC7721] and [RFC7707])

   o  Predictable DNS TxIDs [RFC1035]

   Recent history indicates that when new protocols are standardized or
   implemented, the security and privacy properties of the associated
Show full document text