Subject: [Roll] RootAck discussion at IETF109 ROLL session

From: <[email-masked]>
Date: Sun, 29 Nov 2020 09:56:08 +0000

Hello all,

Following our ROLL session at the IETF109 meeting, I had an action point to dig up pointers to prior discussions about DAO/DAO-ACKs in storing mode and the decision to go for a RootACK.

If you want only one pointer, that would be the video of the ROLL session at the IETF103 meeting https://youtu.be/7cwhMLaddqU?t=3408 , (start time 56:45, duration about 6 mn).

More pointers below
- discussions on ML about interpretation of DAO-ACK behaviour, e.g. as far back as 2015
  https://mailarchive.ietf.org/arch/msg/roll/8jf7B4O_SSz575fjv59EMH2xs7g/
- description of the issues in draft-ietf-roll-rpl-observations, Section 4, first published in Sept 2018
  https://tools.ietf.org/html/draft-ietf-roll-rpl-observations-04
- ROLL session at IET103 meeting (Nov 5, 2018, Bangkok)
  slides: https://datatracker.ietf.org/meeting/103/materials/slides-103-roll-roll-ietf103-v2-00.pdf
  minutes: https://datatracker.ietf.org/doc/minutes-103-roll/
  Excerpt “Pascal: we could specify a mechanism to get an ACK from the root all the
  way down the DODAG. Could be a new draft. ACTION: new draft on ACK from the root?”
- Video: (from time 56:45, about 6 mn) https://youtu.be/7cwhMLaddqU?t=3408
- ensuing draft https://datatracker.ietf.org/doc/draft-jadhav-roll-storing-rootack/ first published Apr 2020

Best regards

Dominique

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.