RFC 5157: IPv6 Implications for Network Scanning
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7707.
Current version: RFC 7707 — Network Reconnaissance in IPv6 Networks
In plain English — editorial summary, not part of the RFC
The much larger default 64-bit subnet address space of IPv6 should in principle make traditional network (port) scanning techniques used by certain network worms or scanning tools less effective. While traditional network scanning probes (whether by individuals or automated via network worms) may become less common, administrators should be aware that attackers may use other techniques to discover IPv6 addresses on a target network, and thus they should also be aware of measures that are available to mitigate them. This informational document discusses approaches that administrators could take when planning their site address allocation and management strategies as part of a defence-in-depth approach to network security. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5157
- Published
- March 2008
- Authors
- T. Chown
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 13
- Also known as
- —
- Obsoleted by:
- RFC 7707
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5156Special-Use IPv6 AddressesObsoleted
April 2008
- RFC 5153IP Flow Information Export (IPFIX) Implementation GuidelinesCurrent
April 2008
- RFC 5136Defining Network CapacityCurrent
February 2008
- RFC 5180IPv6 Benchmarking Methodology for Network Interconnect DevicesCurrent
May 2008
- RFC 5181IPv6 Deployment Scenarios in 802.16 NetworksCurrent
May 2008
- RFC 5132IP Multicast MIBCurrent
December 2007
- RFC 5110Overview of the Internet Multicast Routing ArchitectureCurrent
January 2008
- RFC 5103Bidirectional Flow Export Using IP Flow Information Export (IPFIX)Current
January 2008
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?