[OPSAWG]Re: Secdir last call review of draft-ietf-opsawg-ipfix-tcpo-v6eh-11

2024-05-13 Thread mohamed . boucadair
Hi Tero, Thank you for the review. Please see inline. Cheers, Med > -Message d'origine- > De : Tero Kivinen via Datatracker > Envoyé : jeudi 9 mai 2024 17:35 > À : sec...@ietf.org > Cc : draft-ietf-opsawg-ipfix-tcpo-v6eh@ietf.org; last- > c...@ietf.org; opsawg@ietf.org > Objet :

[OPSAWG]Re: Secdir last call review of draft-ietf-opsawg-ipfix-tcpo-v6eh-11

2024-05-14 Thread Tero Kivinen
mohamed.boucad...@orange.com writes: > > In section 8.3 change > > > > This type MUST be encoded per > >Section 6.1.1 of [RFC7011]. Reduced-Size encoding (Section > > 6.2 of > >[RFC7011]) applies to this data type. > > > > to > > > >

[OPSAWG]Re: Secdir last call review of draft-ietf-opsawg-ipfix-tcpo-v6eh-11

2024-05-15 Thread Benoit Claise
Tero, We could potentially ask the RFC-editors to do this task? Or maybe they do it automatically? Regards, Benoit On 5/14/2024 4:31 PM, Tero Kivinen wrote: mohamed.boucad...@orange.com writes: In section 8.3 change This type MUST be encoded per Se

[OPSAWG]Re: Secdir last call review of draft-ietf-opsawg-ipfix-tcpo-v6eh-11

2024-05-18 Thread Tero Kivinen
Benoit Claise writes: > We could potentially ask the RFC-editors to do this task? Or maybe > they do it automatically? I do not think they do it automatically, and usually it is better to leave that to the experts. Some of the RFC titles are long, and people who are experts on those protocols can