[OPSAWG]Re: IPR POLL: draft-ietf-opsawg-tacacs-tls13

2024-09-04 Thread Thorsten Dahm
"No, I'm not aware of any IPR that applies to this draft” Am Mo., 24. Juni 2024 um 13:38 Uhr schrieb Joe Clarke (jclarke) : > We’re up to WG LC on this draft. We want to reconfirm any known IPR > related to this work: > > https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs-tls13/ > > Are y

[OPSAWG]Re: Rtgdir last call review of draft-ietf-opsawg-ntw-attachment-circuit-12

2024-09-04 Thread Joel Halpern
Thanks Med.  To confirm for everyone else.  With this hint, I was able to figure out how I got confused.  it was my error, the draft is fine. Yours, Joel On 9/4/2024 5:21 AM, mohamed.boucad...@orange.com wrote: Hi Joel, Thank you for clarifiying. Actually, we do have a list of networks, eac

[OPSAWG]Re: Secdir last call review of draft-ietf-opsawg-teas-attachment-circuit-15

2024-09-04 Thread mohamed . boucadair
Hi Tero, I made changes to follow your suggestion when appropriate. Please use the same diff to track the changes. Thanks. Cheers, Med > -Message d'origine- > De : Tero Kivinen > Envoyé : mercredi 4 septembre 2024 02:43 > À : BOUCADAIR Mohamed INNOV/NET > Cc : sec...@ietf.org; draft-

[OPSAWG]Re: Rtgdir last call review of draft-ietf-opsawg-ntw-attachment-circuit-12

2024-09-04 Thread mohamed . boucadair
Hi Joel, Thank you for clarifiying. Actually, we do have a list of networks, each composed by a list of nodes. In order to unambiguously identify an ac, we need to supply the specific network and specific node ids. These ids are provided using "nw:node-ref" (rfc8345) and passing them in the p