Bonjour Med,

And thanks for your prompt reply and proposed changes.

I have removed the comments that are agreed upon and left the ones with more 
information by me (look for EV>)

Regards

-éric

From: [email protected] <[email protected]>
Date: Tuesday, 14 January 2025 at 10:41
To: Eric Vyncke (evyncke) <[email protected]>, The IESG <[email protected]>
Cc: [email protected] 
<[email protected]>, [email protected] 
<[email protected]>, [email protected] <[email protected]>, [email protected] 
<[email protected]>
Subject: RE: Éric Vyncke's No Objection on draft-ietf-opsawg-teas-common-ac-14: 
(with COMMENT)
Hi Éric,

Thank you for the review.

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : Éric Vyncke via Datatracker <[email protected]>
> Envoyé : lundi 13 janvier 2025 17:43
> À : The IESG <[email protected]>
> Cc : [email protected]; opsawg-
> [email protected]; [email protected]; [email protected];
> [email protected]
> Objet : Éric Vyncke's No Objection on draft-ietf-opsawg-teas-
> common-ac-14: (with COMMENT)
>
>
> ### Section 4.1
>
> It is rather unclear what `server` means in this document, even
> if I can guess
> some controllers in the SP domain.

[Med] Is there any specific occurrence that you think is ambiguous?

EV> it is in the definition of `'server-assigned-reference'`

>
> ### Section 4.3

> Should there a choice on how to authenticate OSPFv3 either RFC
> 4552 or RFC 7166
> ?
>

[Med] We used to have ipsec as an option but we removed that part of the code 
it as we wanted to have something **common** for OSPF independent of the 
version.

FYI, device models implemented out there such as 
https://github.com/openconfig/public/tree/master/release/models/ospf do not 
even cover ospfv3, let alone an internal option.

EV> then it is perhaps worth mentionning the RFC 4553 (ipsec auth) is not 
supported. BTW, I also support the removal of RFC 4552 support but this should 
be mentioned.

_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to