Subject: Re: [Roll] New Version Notification for draft-ietf-roll-dao-projection-09.txt

From: "Pascal Thubert (pthubert)" <[email-masked]>
Date: Mon, 18 Nov 2019 02:18:07 +0000

Dear all

This changes adds a segment ID on top of the trackID so we can update an individual segemnet without rebuilding the whole track.
This oi sproposed to address one of Michael's comments about maintaining a PDAO route.

All the best,

Pascal

> -----Original Message-----
> From: [email-masked] <[email-masked]>
> Sent: lundi 18 novembre 2019 09:33
> To: Pascal Thubert (pthubert) <[email-masked]>; Rahul Jadhav
> <[email-masked]>; Rahul Arvind Jadhav <[email-masked]>;
> Matthew Gillmore <[email-masked]>
> Subject: New Version Notification for draft-ietf-roll-dao-projection-09.txt
> 
> 
> A new version of I-D, draft-ietf-roll-dao-projection-09.txt
> has been successfully submitted by Pascal Thubert and posted to the IETF
> repository.
> 
> Name:		draft-ietf-roll-dao-projection
> Revision:	09
> Title:		Root initiated routing state in RPL
> Document date:	2019-11-17
> Group:		roll
> Pages:		31
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-roll-dao-projection-
> 09.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-roll-dao-projection/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-roll-dao-projection-09
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-roll-dao-
> projection
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-dao-projection-09
> 
> Abstract:
>    This document enables a RPL Root to install and maintain Projected
>    Routes within its DODAG, along a selected set of nodes that may or
>    may not include self, for a chosen duration.  This potentially
>    enables routes that are more optimized or resilient than those
>    obtained with the classical distributed operation of RPL, either in
>    terms of the size of a source-route header or in terms of path
>    length, which impacts both the latency and the packet delivery ratio.
>    Projected Routes may be installed in either Storing and Non-Storing
>    Modes Instances of the classical RPL operation, resulting in
>    potentially hybrid situations where the mode of some Projected Routes
>    is different from that of the other routes in the RPL Instance.
> 
> 
> 
> 
> 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