Re: RFC 7721 on Security and Privacy Considerations for IPv6 Address Generation Mechanisms
RFC Editor <rfc-editor@rfc-editor.org> Wed, 16 March 2016 19:25 UTC
Return-Path: <rfc-ed@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D3912DACD; Wed, 16 Mar 2016 12:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 TGjSXgdp5bym; Wed, 16 Mar 2016 12:25:35 -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 70DD012DAD3; Wed, 16 Mar 2016 12:25:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 6000) id 5397418046A; Wed, 16 Mar 2016 12:24:46 -0700 (PDT)
Date: Wed, 16 Mar 2016 12:24:46 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: Re: RFC 7721 on Security and Privacy Considerations for IPv6 Address Generation Mechanisms
Message-ID: <20160316192446.GE23558@rfc-editor.org>
References: <20160309202144.17B9D187E25@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160309202144.17B9D187E25@rfc-editor.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TbQxXQMoCC7vCIxmcdnMLvUBlbU>
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2016 19:25:37 -0000
As suggested by https://mailarchive.ietf.org/arch/msg/ietf-announce/JKvBKTnlJAq8j-AGlZJHOhVRMfg, this RFC announcement is being resent. On Wed, Mar 09, 2016 at 12:21:44PM -0800, RFC Editor wrote: > A new Request for Comments is now available in online RFC libraries. > > > RFC 7721 > > Title: Security and Privacy Considerations for > IPv6 Address Generation Mechanisms > Author: A. Cooper, F. Gont, D. Thaler > Status: Informational > Stream: IETF > Date: March 2016 > Mailbox: alcoop@cisco.com, > fgont@si6networks.com, > dthaler@microsoft.com > Pages: 18 > Characters: 43381 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-6man-ipv6-address-generation-privacy-08.txt > > URL: https://www.rfc-editor.org/info/rfc7721 > > DOI: http://dx.doi.org/10.17487/RFC7721 > > This document discusses privacy and security considerations for > several IPv6 address generation mechanisms, both standardized and > non-standardized. It evaluates how different mechanisms mitigate > different threats and the trade-offs that implementors, developers, > and users face in choosing different addresses or address generation > mechanisms. > > This document is a product of the IPv6 Maintenance 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 >