> 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
> > 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
talking about the right model revision.
Barbara
> From: STARK, BARBARA H
>
> > From: Toke Høiland-Jørgensen
> >
> > Juliusz Chroboczek writes:
> >
> > > Dear all,
> > >
> > > Antonin and I have spent the afternoon looking at his wor
> -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
> I’ve finally managed to rework my implementation of Babel-over-DTLS
> (spoiler: it seems to be working). Thanks to Juliusz for the help.
Cool. This is great.
> It is unclear to me how the user interface to provide certificates and private
> keys should look like, and if we prefer CA
FYI. IETF policies re "downrefs" in standards track RFCs is described in
https://tools.ietf.org/html/rfc3967 (and updated by
https://tools.ietf.org/html/rfc8067).
In short, it's not prohibited, but careful review is required.
Note RFC3967 Section 2 first bullet
There are a number of
