RFC 7824 on Privacy Considerations for DHCPv6

rfc-editor@rfc-editor.org Tue, 17 May 2016 22:24 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF8012DAB6; Tue, 17 May 2016 15:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 mNHHXXUigFww; Tue, 17 May 2016 15:24:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8462612DAAC; Tue, 17 May 2016 15:24:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A56DF180005; Tue, 17 May 2016 15:24:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7824 on Privacy Considerations for DHCPv6
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160517222417.A56DF180005@rfc-editor.org>
Date: Tue, 17 May 2016 15:24:17 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/_S9JQ4l-96sHXP_2UGN_alb6ahM>
Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 22:24:30 -0000

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

        
        RFC 7824

        Title:      Privacy Considerations for DHCPv6 
        Author:     S. Krishnan, T. Mrugalski, S. Jiang
        Status:     Informational
        Stream:     IETF
        Date:       May 2016
        Mailbox:    suresh.krishnan@ericsson.com, 
                    tomasz.mrugalski@gmail.com, 
                    jiangsheng@huawei.com
        Pages:      18
        Characters: 42561
        Updates/Obsoletes/SeeAlso:   None

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

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

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

DHCPv6 is a protocol that is used to provide addressing and
configuration information to IPv6 hosts.  This document describes the
privacy issues associated with the use of DHCPv6 by Internet users.
It is intended to be an analysis of the present situation and does
not propose any solutions.

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