[dnssd] RFC 8882 on DNS-Based Service Discovery (DNS-SD) Privacy and Security Requirements

rfc-editor@rfc-editor.org Thu, 10 September 2020 17:07 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5663A0E9D; Thu, 10 Sep 2020 10:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 USAvTCCqpR16; Thu, 10 Sep 2020 10:07:56 -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 AD2B13A0E98; Thu, 10 Sep 2020 10:07:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 51F89F40752; Thu, 10 Sep 2020 10:07:34 -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, dnssd@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200910170734.51F89F40752@rfc-editor.org>
Date: Thu, 10 Sep 2020 10:07:34 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/Ykze_5dCg74jSTYX_BGnvEQ_ku4>
Subject: [dnssd] =?utf-8?q?RFC_8882_on_DNS-Based_Service_Discovery_=28DNS?= =?utf-8?q?-SD=29_Privacy_and_Security_Requirements?=
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2020 17:08:00 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8882

        Title:      DNS-Based Service Discovery (DNS-SD) Privacy 
                    and Security Requirements 
        Author:     C. Huitema, D. Kaiser
        Status:     Informational
        Stream:     IETF
        Date:       September 2020
        Mailbox:    huitema@huitema.net, 
                    daniel.kaiser@uni.lu
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnssd-prireq-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8882

        DOI:        10.17487/RFC8882

DNS-SD (DNS-based Service Discovery) normally discloses information
about devices offering and requesting services. This information
includes hostnames, network parameters, and possibly a further
description of the corresponding service instance. Especially when
mobile devices engage in DNS-based Service Discovery at a public
hotspot, serious privacy problems arise. We analyze the requirements
of a privacy-respecting discovery service.

This document is a product of the Extensions for Scalable DNS Service Discovery 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