RFC 7707: Network Reconnaissance in IPv6 Networks
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7707
- Published
- March 2016
- Authors
- F. Gont; T. Chown
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 38
- Also known as
- —
- Obsoletes:
- RFC 5157
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7706Decreasing Access Time to Root Servers by Running One on LoopbackObsoleted
November 2015
- RFC 7717IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)Current
December 2015
- RFC 7718Registries for the One-Way Active Measurement Protocol (OWAMP)Current
December 2015
- RFC 7719DNS TerminologyObsoleted
December 2015
- RFC 7690Close Encounters of the ICMP Type 2 Kind (Near Misses with ICMPv6 Packet Too Big (PTB))Current
January 2016
- RFC 7686The ".onion" Special-Use Domain NameCurrent
October 2015
- RFC 7683Diameter Overload Indication ConveyanceUpdated
October 2015
- RFC 7682Considerations for Internet Routing Registries (IRRs) and Routing Policy ConfigurationCurrent
December 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?