Re: [Roll] term for async msg

Re: [Roll] term for async msg - storing-rootack

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 22 May 2020 05:30 UTC

IronPort-PHdr: 9a23:QKvvCRQbMTs8GI67ZGGUJoT6VNpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESQBN+J6v9YhazRqa+zEWAD4JPUtncEfdQMUhIekswZkkQmB9LNEkz0KvPmLklYVMRPXVNo5Te3ZE5SHsutZlDOrDu19zFBUhn6PBB+c+LyHIOahs+r1ue0rpvUZQgAhDe0bb5oahusqgCEvcgNiowkIaE0mRY=
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] term for async msg - storing-rootack
Thread-Index: AQHWLzY9XhGoqjVWd0eZK9P4fmVklaizlc9G
Date: Fri, 22 May 2020 05:30:34 +0000
Message-ID: <617E9429-BD80-44A2-B2A4-2B8D6A5519EE@cisco.com>
References: <BM1PR01MB40204DF7ED2661CDB4C4B267A9B70@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <BM1PR01MB40204DF7ED2661CDB4C4B267A9B70@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: multipart/alternative; boundary="_000_617E9429BD8044A2B2A42B8D6A5519EEciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 174e72ca-61a1-470a-e0d6-08d7fe11406b
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2020 05:30:34.4245 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 5BVhNMpAgkAR46azm/e5prnBxO3xN5+uQHhUCV+J9qasZ0fKd6j1durSGcT6D08ljJYIR0Z8sAgNRPsq1NX7jg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3565
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/17JYC7DVprt5_JSnOGe-ZLNsaX8>
Subject: Re: [Roll] term for async msg - storing-rootack
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2020 05:30:40 -0000

Hello Rahul

The closest to what the message is really intended to do the better, like naming a function in C. What is this for?

I understand that it is an indication that the path is available.

Now we need to think that the message is only needed if there is no other message that would come down anyway like a DAR sac for attached nodes or some upper layer thing.

We also need to wonder about keep alive.

Take care,

Pascal

Le 21 mai 2020 à 08:24, Rahul Jadhav <nyrahul@outlook.com> a écrit :


Hello All,

This is about using an appropriate name/term for the message sent from root to the node. The draft targets this msg as an indication for e2e path establishment for the node. However, this primitive will be useful for capability query/indication. In storing MOP this will be the only message which is directly addressed to the node from the root.

Currently, the draft calls it DAO-ACK and is not a good term.
Another term that is suggested is RootACK. Shall we call it an ACK at all?
RPL-Ping is another term.

Suggestions are welcome. Hoping to use the term finalized here in the interim slides.

Thanks,
Rahul
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll

Re: [Roll] term for async msg - storing-rootack Pascal Thubert (pthubert)
[Roll] term for async msg - storing-rootack Rahul Jadhav