The Wire Image of a Network Protocol
draft-iab-wire-image-00

Document Type Active Internet-Draft
Last updated 2018-10-10
Stream IAB
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream IAB state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
Network Working Group                                        B. Trammell
Internet-Draft                                             M. Kuehlewind
Intended status: Informational                                ETH Zurich
Expires: April 13, 2019                                 October 10, 2018

                  The Wire Image of a Network Protocol
                        draft-iab-wire-image-00

Abstract

   This document defines the wire image, an abstraction of the
   information available to an on-path non-participant in a networking
   protocol.  This abstraction is intended to shed light on the
   implications on increased encryption has for network functions that
   use the wire image.

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 13, 2019.

Copyright Notice

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

Trammell & Kuehlewind    Expires April 13, 2019                 [Page 1]
Internet-Draft                 Wire Image                   October 2018

1.  Introduction

   A protocol specification defines a set of behaviors for each
   participant in the protocol: which lower-layer protocols are used for
   which services, how messages are formatted and protected, which
   participant sends which message when, how each participant should
   respond to each message, and so on.

   Implicit in a protocol specification is the information the protocol
   radiates toward nonparticipant observers of the messages sent among
   participants, often including participants in lower layer protocols.
   Any information that has a clear definition in the protocol's message
   format(s), or is implied by that definition, and is not
   cryptographically confidentiality-protected can be unambiguously
   interpreted by those observers.

   This information comprises the protocol's wire image, which we define
   and discuss in this document.  It is the wire image, not the
   protocol's specification, that determines how third parties on the
   network paths among protocol participants will interact with that
   protocol.

   The increasing deployment of transport-layer security [RFC8226] to
   protect application-layer headers and payload, as well as the
   definition and deployment of QUIC [I-D.ietf-quic-transport], a
   transport protocol which encrypts most of its own control
   information, bring new relevance to this question.  QUIC is, in
   effect, the first IETF-defined transport protocol to take care of the
   minimization of its own wire image, to prevent ossification and
   improve end-to-end privacy by reducing information radiation.

   The flipside of this trend is the impact of a less visible wire image
   on various functions driven by third-party observation of the wire
   image.  [RFC8404] examines this issue from a network operator's
   viewpoint, and [I-D.ietf-tsvwg-transport-encrypt] focuses on
   transport-layer implications of increasing encryption.
   [I-D.ietf-quic-manageability] is, in part, a third-party user's guide
   to the QUIC wire image.  In contrast to those documents, this draft
   treats the wire image as a pure abstraction, with the hope that it
   can shed some light on these discussions.

2.  Definition

   More formally, the wire image of the set of protocols in use for a
   communication observed at a given point in the network consists of
   the sequence of packets sent by each participant in the
   communication, each expressed as a sequence of bits with the
   associated arbitrary-precision time at which the packet was observed.

Trammell & Kuehlewind    Expires April 13, 2019                 [Page 2]
Internet-Draft                 Wire Image                   October 2018

3.  Discussion

   This definition appears at first glance to be so impractically formal
Show full document text