This is a quick review based on first impressions.
It may be good to have a note that the existing TACACS+ port can be used for
TLS, if both ends are configured to require TLS. That means systems can use
existing firewall rules, etc. for TACACS+TLS.
Section 3.2 says:
the resumption
OPSAWG participants,
An initial draft for, among other things, adding TLS transport for TACACS+
has been submitted. It needs your scrutiny and your comments are requested.
TiA
Note that this would update RFC8907, not 8097 indicated in the header.
- Forwarded message from
Hello, WG. As promised (threatened?) I wanted to poke the WG to review this
work. The authors have done, in my opinion, a good job of simplifying the
original work down to around 16 pages of text and then the YANG module,
considerations, and examples. So, PLEASE REVIEW!
We'd like to do a
Re-,
The clarification looks good to me. fixed.
I prefer to not add a dependency to rfc6991-bis now. Thanks.
Cheers,
Med
> -Message d'origine-
> De : Rob Wilton (rwilton)
> Envoyé : mardi 5 avril 2022 11:04
> À : BOUCADAIR Mohamed INNOV/NET ; draft-
> ietf-opsawg-l2nm@ietf.org
>
Hi Rob,
Focusing on the first part of your review, except point (9).
The changes can be tracked at:
https://github.com/IETF-OPSAWG-WG/lxnm/commit/337f65012f55e71df4105481bc28fe53ac8bb302,
while the full changes made so far can be tracked at:
https://tinyurl.com/l2nm-latest
Please see
Hi Med,
Thanks, your changes all look good, but I have a bit more comment on one
specific point:
> > (3)
> > 'mac-loop-prevention': Container for MAC loop prevention.
> >
> > 'window': The timer when a MAC mobility event is detected.
> >
> > 'frequency': The number of
Hi Rob,
Many thanks for the careful AD review.
Staring with the last part. You can track the changes at:
https://tinyurl.com/l2nm-latest. Please see inline for more context.
There are also other edits that I made to fix nits, update references, etc.
Cheers,
Med
> -Message
