.g. prefer the one with longest TTL, or one that worked before (for a JP
implementation that can monitor which "sessions" went well or which not.)
Esko
-Original Message-
From: Anima On Behalf Of Michael Richardson
Sent: Wednesday, January 4, 2023 20:36
To: Brian E Carpenter ; anima@ietf
Brian E Carpenter wrote:
> M_FLOOD includes a TTL.
> "The message MUST contain a time-to-live (ttl) for the validity of the
> contents, given as a positive integer value in milliseconds. There is
> no default; zero indicates an indefinite lifetime."
Sure, so after that time,
M_FLOOD includes a TTL.
"The message MUST contain a time-to-live (ttl) for the validity of the
contents, given as a positive integer value in milliseconds. There is
no default; zero indicates an indefinite lifetime."
In any case, floods must be ignored after their TTL expires, obviously.
I see
I've opened ticket:
https://github.com/anima-wg/constrained-voucher/issues/260
Assume that a Join Proxy is receiving GRASP M_FLOOD messages on it's uplink
(ACP) side.
What should it do when it receives announcements from multiple Registrars
(distinct v6 locators). Where does it connect to?
