[Int-area] RFC 8386 on Privacy Considerations for Protocols Relying on IP Broadcast or Multicast
rfc-editor@rfc-editor.org Thu, 17 May 2018 15:42 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 845C912EB6D; Thu, 17 May 2018 08:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjzKEcGr8w_3; Thu, 17 May 2018 08:42:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E78012EB7A; Thu, 17 May 2018 08:42:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 87CB9B8127A; Thu, 17 May 2018 08:42:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, int-area@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180517154210.87CB9B8127A@rfc-editor.org>
Date: Thu, 17 May 2018 08:42:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/ONiGA29Egp0sMt6Yno4FzMKwL0c>
Subject: [Int-area] RFC 8386 on Privacy Considerations for Protocols Relying on IP Broadcast or Multicast
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 15:42:31 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8386
Title: Privacy Considerations for Protocols Relying
on IP Broadcast or Multicast
Author: R. Winter,
M. Faath,
F. Weisshaar
Status: Informational
Stream: IETF
Date: May 2018
Mailbox: rolf.winter@hs-augsburg.de,
faath@conntac.net,
fabian.weisshaar@hs-augsburg.de
Pages: 13
Characters: 32238
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-intarea-broadcast-consider-09.txt
URL: https://www.rfc-editor.org/info/rfc8386
DOI: 10.17487/RFC8386
A number of application-layer protocols make use of IP broadcast or
multicast messages for functions such as local service discovery or
name resolution. Some of these functions can only be implemented
efficiently using such mechanisms. When using broadcast or multicast
messages, a passive observer in the same broadcast or multicast
domain can trivially record these messages and analyze their content.
Therefore, designers of protocols that make use of broadcast or
multicast messages need to take special care when designing their
protocols.
This document is a product of the Internet Area Working Group Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC