Re: RFC 7707 on Network Reconnaissance in IPv6 Networks
RFC Editor <rfc-editor@rfc-editor.org> Wed, 16 March 2016 19:25 UTC
Return-Path: <rfc-ed@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 7AF1B12D6CC; Wed, 16 Mar 2016 12:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.923
X-Spam-Level:
X-Spam-Status: No, score=-106.923 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 3nadDYIVEune; Wed, 16 Mar 2016 12:25:05 -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 629EF12D6AD; Wed, 16 Mar 2016 12:25:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 6000) id 4565218046B; Wed, 16 Mar 2016 12:24:27 -0700 (PDT)
Date: Wed, 16 Mar 2016 12:24:27 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org
Subject: Re: RFC 7707 on Network Reconnaissance in IPv6 Networks
Message-ID: <20160316192427.GD23558@rfc-editor.org>
References: <20160309202133.6D6BF180205@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160309202133.6D6BF180205@rfc-editor.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/n16gZERYI45uNa-R-THcgoKwlu0>
Cc: drafts-update-ref@iana.org, opsec@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Wed, 16 Mar 2016 19:25:07 -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:33PM -0800, RFC Editor wrote: > A new Request for Comments is now available in online RFC libraries. > > > RFC 7707 > > Title: Network Reconnaissance in IPv6 Networks > Author: F. Gont, T. Chown > Status: Informational > Stream: IETF > Date: March 2016 > Mailbox: fgont@si6networks.com, > tim.chown@jisc.ac.uk > Pages: 38 > Characters: 88281 > Obsoletes: RFC 5157 > > I-D Tag: draft-ietf-opsec-ipv6-host-scanning-08.txt > > URL: https://www.rfc-editor.org/info/rfc7707 > > DOI: http://dx.doi.org/10.17487/RFC7707 > > IPv6 offers a much larger address space than that of its IPv4 > counterpart. An IPv6 subnet of size /64 can (in theory) accommodate > approximately 1.844 * 10^19 hosts, thus resulting in a much lower host > density (#hosts/#addresses) than is typical in IPv4 networks, where a > site typically has 65,000 or fewer unique addresses. As a result, it > is widely assumed that it would take a tremendous effort to perform > address-scanning attacks against IPv6 networks; therefore, IPv6 > address-scanning attacks have been considered unfeasible. This > document formally obsoletes RFC 5157, which first discussed this > assumption, by providing further analysis on how traditional > address-scanning techniques apply to IPv6 networks and exploring some > additional techniques that can be employed for IPv6 network > reconnaissance. > > This document is a product of the Operational Security Capabilities for IP Network Infrastructure 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 >