9. Updating RFC 8928

Ce document met a jour IPv6 Neighbor Discovery et les specifications 6LoWPAN/RPL associees afin qu'un noeud puisse enregistrer un IPv6 prefix aupres de routeurs voisins. Les details de protocole essentiels sont conserves ci-dessous depuis le texte RFC.

9.  Updating RFC 8928

   "Address-Protected Neighbor Discovery for Low-Power and Lossy
   Networks" [RFC8928] was defined to protect the ownership of unicast
   IPv6 addresses that are registered with [RFC8505].

   With Address-Protected Neighbor Discovery (AP-ND) [RFC8928], it is
   possible for a node to autoconfigure a pair of public and private
   keys and use them to sign the registration of addresses that are
   either autoconfigured or obtained through other methods.

   The first-hop router (the 6LR) can then validate a registration and
   perform source address validation on packets coming from the sender
   node (the 6LN).

   As multiple nodes may register the same prefix, the method specified
   in [RFC8928] cannot be used with node-local autoconfigured keypairs,
   which protect a single ownership only.

   For a prefix, as for an anycast or a multicast address, it is still
   possible to leverage AP-ND [RFC8928] to enforce the right to
   register.  If AP-ND [RFC8928] is used, a keypair MUST be created and
   associated with the prefix before the prefix is deployed, and a ROVR
   MUST be generated from that keypair as specified in [RFC8928].  The
   prefix and the ROVR MUST then be installed in the 6LBR at the first
   registration, or by an external mechanism such as IP Address
   Management (IPAM) or DHCPv6 snooping prior to the first registration.
   This way, the 6LBR can recognize the prefix on the future
   registrations and validate the right to register based on the ROVR.

   The keypair MUST then be provisioned in each node that needs to
   register the prefix or a prefix within, so the node can follow the
   steps in [RFC8928] to register the prefix.

   Upon receiving an NA message with the status set to 5 "Validation
   Requested", the node that registered the address or prefix performs
   the proof of ownership based on that longest prefix match.