Privacy considerations for protocols relying on IP broadcast and multicast
draft-ietf-intarea-broadcast-consider-08

Document Type Active Internet-Draft (intarea WG)
Last updated 2018-01-19
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Juan-Carlos Zúñiga
Shepherd write-up Show (last changed 2017-08-30)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Unknown
Telechat date On agenda of 2018-01-25 IESG telechat
Has enough positions to pass.
Responsible AD Suresh Krishnan
Send notices to Juan-Carlos Zuniga <juancarlos.zuniga@sigfox.com>
IANA IANA review state Version Changed - Review Needed
IANA action state None
Internet Engineering Task Force                                R. Winter
Internet-Draft                   University of Applied Sciences Augsburg
Intended status: Informational                                  M. Faath
Expires: July 23, 2018                                      Conntac GmbH
                                                            F. Weisshaar
                                 University of Applied Sciences Augsburg
                                                        January 19, 2018

    Privacy considerations for protocols relying on IP broadcast and
                               multicast
                draft-ietf-intarea-broadcast-consider-08

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, designers of protocols that make use
   broadcast/multicast messages 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 July 23, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Winter, et al.            Expires July 23, 2018                 [Page 1]
Internet-Draft      Broadcast privacy considerations        January 2018

   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
   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  . . . . . . .   4
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Privacy considerations  . . . . . . . . . . . . . . . . . . .   5
     2.1.  Message frequency . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Persistent identifiers  . . . . . . . . . . . . . . . . .   5
     2.3.  Anticipate user behavior  . . . . . . . . . . . . . . . .   6
     2.4.  Consider potential correlation  . . . . . . . . . . . . .   7
     2.5.  Configurability . . . . . . . . . . . . . . . . . . . . .   7
   3.  Operational considerations  . . . . . . . . . . . . . . . . .   8
   4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Other considerations  . . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   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.  It appears that an increasing
   number of applications make use of it as suggested by experimental
   results obtained on campus networks including the IETF meeting
   network [TRAC2016].  This trend is not entirely surprising.  As RFC
   919 [RFC0919] puts it, "The use of broadcasts [...] is a good base
   for many applications".  Broadcast and multicast functionality in a
Show full document text