Privacy considerations for IP broadcast and multicast protocol designers
draft-ietf-intarea-broadcast-consider-03

Document Type Active Internet-Draft (intarea WG)
Last updated 2017-05-29
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                R. Winter
Internet-Draft                   University of Applied Sciences Augsburg
Intended status: Informational                                  M. Faath
Expires: November 30, 2017                                  Conntac GmbH
                                                            F. Weisshaar
                                 University of Applied Sciences Augsburg
                                                            May 29, 2017

Privacy considerations for IP broadcast and multicast protocol designers
                draft-ietf-intarea-broadcast-consider-03

Abstract

   A number of application-layer protocols make use of IP broadcasts or
   multicast messages for functions like local service discovery or name
   resolution.  Some of these functions can only be implemented
   efficiently using such mechanisms.  When using broadcasts or
   multicast messages, a passive observer in the same broadcast/
   multicast domain can trivially record these messages and analyze
   their content.  Therefore, broadcast/multicast protocol designers
   need to take special care when designing their protocols.

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 November 30, 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

Winter, et al.          Expires November 30, 2017               [Page 1]
Internet-Draft      Broadcast privacy considerations            May 2017

   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.  Types and usage of broadcast and multicast  . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Privacy considerations  . . . . . . . . . . . . . . . . . . .   4
     2.1.  Message frequency . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Persistent identifiers  . . . . . . . . . . . . . . . . .   5
     2.3.  Anticipate user behavior  . . . . . . . . . . . . . . . .   6
     2.4.  Consider potential correlation  . . . . . . . . . . . . .   6
     2.5.  Configurability . . . . . . . . . . . . . . . . . . . . .   7
   3.  Operational considerations  . . . . . . . . . . . . . . . . .   8
   4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Other considerations  . . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Broadcast and multicast messages have a large (and to the sender
   unknown) receiver group by design.  Because of that, these two
   mechanisms are vital for a number of basic network functions such as
   auto-configuration or link-layer address lookup.  Also application
   developers use broadcast/multicast messages to implement things like
   local service or peer discovery and it appears that an increasing
   number of applications make use of it [TRAC2016].  That is not
   entirely surprising.  As RFC 919 [RFC0919] puts it, "The use of
   broadcasts [...] is a good base for many applications".  Broadcast
Show full document text