Subject: [v6ops] Fwd: New Version Notification for draft-shytyi-v6ops-danir-00.txt

From: Dmytro Shytyi <[email-masked]>
Date: Mon, 30 Oct 2017 12:26:09 +0100

Dear v6opsers,

We have just submitted the DANIR Internet Draft.

Comments are welcome.

Dmytro Shytyi

============ Forwarded message ============

>From : [email-masked]

To : "Dmytro Shytyi"&lt;[email-masked]&gt;, "Alexandre Petrescu"&lt;[email-masked]&gt;

Date : Mon, 30 Oct 2017 12:12:36 +0100

Subject : New Version Notification for draft-shytyi-v6ops-danir-00.txt

============ Forwarded message ============

A new version of I-D, draft-shytyi-v6ops-danir-00.txt 

has been successfully submitted by Dmytro Shytyi and posted to the 

IETF repository. 

Name:        draft-shytyi-v6ops-danir 

Revision:    00 

Title:        DHCPv6_PD, PDP and NDP Implementation in IoT Router (DANIR) 

Document date:    2017-10-30 

Group:        Individual Submission 

Pages:        17 

URL: https://www.ietf.org/internet-drafts/draft-shytyi-v6ops-danir-00.txt 

Status: https://datatracker.ietf.org/doc/draft-shytyi-v6ops-danir/ 

Htmlized: https://tools.ietf.org/html/draft-shytyi-v6ops-danir-00 

Htmlized: https://datatracker.ietf.org/doc/html/draft-shytyi-v6ops-danir-00 

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. 

 

Please note that it may take a couple of minutes from the time of submission 

until the htmlized version and diff are available at tools.ietf.org. 

The IETF Secretariat