DHCPv6_PD, PDP and NDP Implementation in IoT Router (DANIR)
draft-shytyi-v6ops-danir-05

Document Type Expired Internet-Draft (individual)
Authors Dmytro Shytyi  , Alexandre Petrescu 
Last updated 2020-11-21 (latest revision 2020-05-20)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) 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-shytyi-v6ops-danir-05.txt

Abstract

This document provides a description of the implementation of Dynamic Host Configuration Protocol version 6 Prefix Delegation, Neighbour Discovery Protocol and of the use of the Packet Data Protocol in an Internet of Things Router. This Internet of Things Router is connected on a cellular network; it is a DHCPv6-PD Client and it requests a /56 pool of prefixes from the server; the DHCPv6-PD server is placed in the PGW and is a part of the cellular infrastructure. After the pool of prefixes is delegated, the Internet of Things Router derives sub-prefixes from the prefix pool; each one of these sub-prefixes is aimed at one ingress interface. After the Internet of Things Router finishes the network prefix assignment procedure, it advertises the network prefixes on the ingress links by using the Neighbour Discovery protocol. Finally, when Hosts receive the sub-prefixes via Router Adverticement messages, they configure the Global Unique Address with the Stateless Address Auto-configuration protocol.

Authors

Dmytro Shytyi (ietf.dmytro@shytyi.net)
Alexandre Petrescu (alexandre.petrescu@cea.fr)

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