> From: Juliusz Chroboczek
>
> > As I just replied in the other thread: The Bird implementation is
> > going to have this facility no matter what we specify in the spec, but
> > I'm fine with having it optional, or omitting it from the spec
> > entirely, as long as we don't forbid having a key-us
> As I just replied in the other thread: The Bird implementation is going
> to have this facility no matter what we specify in the spec, but I'm
> fine with having it optional, or omitting it from the spec entirely, as
> long as we don't forbid having a key-use parameter :)
It is my understanding
Juliusz Chroboczek writes:
>>> The second part of my inquiry -- how does the information model enable
>>> incremental deployment? Section 5 of draft-ietf-babel-mac.
>
>> Incremental deployment is enabled through the interfaces object
>> babel-mac-verify parameter. Set this parameter to false unt
>> The second part of my inquiry -- how does the information model enable
>> incremental deployment? Section 5 of draft-ietf-babel-mac.
> Incremental deployment is enabled through the interfaces object
> babel-mac-verify parameter. Set this parameter to false until all
> routers have key(s). Then
Juliusz Chroboczek writes:
>> Since that revision has Boolean (true/false) parameters of
>> babel-key-use-sign and babel-key-use-verify (but not key-use with values
>> of sign/verify/both), I did want to be sure we were talking about the
>> right model revision.
>
> The second part of my inquiry
> > Since that revision has Boolean (true/false) parameters of
> > babel-key-use-sign and babel-key-use-verify (but not key-use with
> > values of sign/verify/both), I did want to be sure we were talking
> > about the right model revision.
>
> The second part of my inquiry -- how does the informat
> Since that revision has Boolean (true/false) parameters of
> babel-key-use-sign and babel-key-use-verify (but not key-use with values
> of sign/verify/both), I did want to be sure we were talking about the
> right model revision.
The second part of my inquiry -- how does the information model en
BTW, I just looked at the -10 revision of
https://tools.ietf.org/html/draft-ietf-babel-information-model-10
Since that revision has Boolean (true/false) parameters of babel-key-use-sign
and babel-key-use-verify (but not key-use with values of sign/verify/both), I
did want to be sure we were tal
> -Original Message-
> From: Toke Høiland-Jørgensen
> Sent: Friday, January 17, 2020 6:27 AM
> To: Juliusz Chroboczek ; babel-us...@lists.alioth.debian.org
> Cc: STARK, BARBARA H ; ba...@ietf.org
> Subject: Re: [Babel-users] MAC rekeying in babeld and information
Juliusz Chroboczek writes:
> Dear all,
>
> Antonin and I have spent the afternoon looking at his work on MAC rekeying
> in babeld. His code is available in branch hmac-rekeying of
>
> https://github.com/MisterDA/babeld
>
> Now... we've got an issue with the information model.
>
> Following t
Dear all,
Antonin and I have spent the afternoon looking at his work on MAC rekeying
in babeld. His code is available in branch hmac-rekeying of
https://github.com/MisterDA/babeld
Now... we've got an issue with the information model.
Following the information model, Antonin adds the follow
11 matches
Mail list logo
