IPv6 Implications for TCP/UDP Port Scanning
draft-chown-v6ops-port-scanning-implications-02

Document Type Expired Internet-Draft (individual)
Last updated 2005-10-27
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-chown-v6ops-port-scanning-implications-02.txt

Abstract

The 128 bits of IPv6 address space is considerably bigger than the 32 bits of address space in IPv4. In particular, the IPv6 subnets to which hosts attach will by default have 64 bits of host address space. As a result, traditional methods of remote TCP or UDP port scanning to discover open or running services on a host will potentially become far less computationally feasible, due to the larger search space in the subnet. This document discusses that property of IPv6 subnets, and describes related issues for site administrators of IPv6 networks to consider, which may be of importance when planning site address allocation and management strategies.

Authors

Tim Chown (tjc@ecs.soton.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)