[perpass] [rfc-editor@rfc-editor.org: RFC 7819 on Privacy Considerations for DHCP]

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 03 May 2016 19:43 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DB9A812D5C0 for <perpass@ietfa.amsl.com>; Tue, 3 May 2016 12:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mQ-cxz-ukHpA for <perpass@ietfa.amsl.com>; Tue, 3 May 2016 12:43:09 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 325F212B03A for <perpass@ietf.org>; Tue, 3 May 2016 12:43:09 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 27CC431D57; Tue, 3 May 2016 21:43:07 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id C09061908ED; Tue, 3 May 2016 21:41:29 +0200 (CEST)
Date: Tue, 3 May 2016 21:41:29 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: perpass@ietf.org
Message-ID: <20160503194129.GA25893@sources.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="HcAYCG3uE/tztfnV"
Content-Disposition: inline
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 8.4
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/yg1N0m0MdcInCpopZ5kDTT2oC1U>
Subject: [perpass] [rfc-editor@rfc-editor.org: RFC 7819 on Privacy Considerations for DHCP]
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2016 19:43:12 -0000

One more "Privacy considerations for protocol X" RFC, this time for
DHCP. I learned a lot in this RFC.
--- Begin Message ---
A new Request for Comments is now available in online RFC libraries.

        RFC 7819

        Title:      Privacy Considerations for DHCP 
        Author:     S. Jiang, S. Krishnan, T. Mrugalski
        Status:     Informational
        Stream:     IETF
        Date:       April 2016
        Mailbox:    jiangsheng@huawei.com, 
        Pages:      14
        Characters: 32944
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-dhcp-privacy-05.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7819

DHCP is a protocol that is used to provide addressing and
configuration information to IPv4 hosts.  This document discusses the
various identifiers used by DHCP and the potential privacy issues.

This document is a product of the Dynamic Host Configuration 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

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
--- End Message ---