On 08/07/2017 12:39, Toerless Eckert wrote:
> Seems i dropped the ball on these:
>
> I am not sure i see the crucial need to be able to optimize the number of
> packets of periodic ACP and BRSKI announcements.
Sure, unless we plan to flood these at a high rate, it isn't important; but
it's an
On 19/06/2017 04:58, Michael Richardson wrote:
>
> Toerless Eckert wrote:
> > 2. If we send the M_FLOOD for BRSKI and ACP periodicially once every 30
> seconds,
> > i don't think that we should be worried about sending one instead of
> two packets.
>
> > From
Toerless Eckert wrote:
> 2. If we send the M_FLOOD for BRSKI and ACP periodicially once every 30
seconds,
> i don't think that we should be worried about sending one instead of two
packets.
> From grasp-13 it seems that i can only put a single grasp-message into a
Brian E Carpenter wrote:
> If the BRSKI team agree that you want a flood (i.e. unsolicited
announcement)
> for pledge<->proxy and discovery+synchronization request (i.e. solicited
> announcement) for proxy<->registrar, I will suggest complete text for
If the BRSKI team agree that you want a flood (i.e. unsolicited announcement)
for pledge<->proxy and discovery+synchronization request (i.e. solicited
announcement) for proxy<->registrar, I will suggest complete text for these,
and implement a Python demo version.
So, BRSKIsts please confirm what
On 13/06/2017 03:38, Michael Richardson wrote:
>
> {note subject line change}
>
> Brian E Carpenter wrote:
> >> 3.1.1. Proxy Discovery Protocol Details
> >>
> >> The proxy uses the GRASP M_FLOOD mechanism to announce itself. This
> >> announcement