IPv6 hosts detection
draft-li-6man-6hosts-detection-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IPv6 Maintenance                                                   J. Li
Internet-Draft                                                     J. Fu
Intended status: Standards Track                                   X. Li
Expires: January 14, 2021                                       Y. Cheng
                                                            China Mobile
                                                           July 13, 2020

                          IPv6 hosts detection
                   draft-li-6man-6hosts-detection-00

Abstract

   The management of hosts and risks is important for enterprises that
   have large scale IP space.  For IPv4, it won't take too long even to
   scan the entire Internet address space.  For IPv6, further
   consideration is needed.  A narrow range of IPv6 address is preferred
   for scanning.  And in order to shorten the time for IPv6 scanning, a
   very specific IPv6 address list is highly needed.

   This document proposes a solution to solve the problem.  At first,
   append the information of the collection point address to the Router
   Advertisement packet sent by the router, and announce this address
   information to all nodes in the subnet.  Then, each host node report
   its own IPv6 address information to the designated collection point
   by using Echo Reply message.  After that, the corresponding
   collection point device should save these information.  In this way,
   online IPv6 address information in the current network can be quickly
   collected on the collection point device.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119][RFC8174].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Li, et al.              Expires January 14, 2021                [Page 1]
Internet-Draft              6hosts detection                   July 2020

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 14, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Message Formats . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Router Advertisement Option Formats . . . . . . . . . . .   3
     3.2.  Echo Reply Message Format . . . . . . . . . . . . . . . .   4
   4.  Online Address Collection . . . . . . . . . . . . . . . . . .   5
     4.1.  Router Specification  . . . . . . . . . . . . . . . . . .   5
       4.1.1.  Router Configuration Variables  . . . . . . . . . . .   5
       4.1.2.  Router Advertisement Message Content  . . . . . . . .   6
     4.2.  Host Specification  . . . . . . . . . . . . . . . . . . .   6
       4.2.1.  Processing Received Router Advertisements and Sending
               Echo Reply  . . . . . . . . . . . . . . . . . . . . .   6
     4.3.  Collection Point Specification  . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   IP scanning is widely used in cybersecurity to find out online hosts
   and detect risks.  Detection for online IPv6 hosts quickly and
   effectively is much more complicated than IPv4.  Complications arise
Show full document text