[OPSAWG] Paul Wouters' Yes on draft-ietf-opsawg-tlstm-update-13: (with COMMENT)

2023-03-02 Thread Paul Wouters via Datatracker
Paul Wouters has entered the following ballot position for draft-ietf-opsawg-tlstm-update-13: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-tlstm-update-13.txt

2023-03-02 Thread Randy Presuhn
Hi - On 2023-03-02 7:08 AM, Joe Clarke (jclarke) wrote: - Sect 4: Added the snmpTlstmHashAlgorithms node to represent the new registry --- This is related to the issue that is still under review On this point, I would like some guidance from other MIB experts.  You have created a “dummy”

Re: [OPSAWG] Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-03-02 Thread Zaheduzzaman Sarker
Thanks Ken, LGTM. //Zahed From: Kenneth Vaughn Sent: Thursday, March 2, 2023 2:16 PM To: Zaheduzzaman Sarker Cc: The IESG ; draft-ietf-opsawg-tlstm-upd...@ietf.org ; opsawg@ietf.org ; opsawg-cha...@ietf.org Subject: Re: [OPSAWG] Zaheduzzaman Sarker's No

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-tlstm-update-13.txt

2023-03-02 Thread Joe Clarke (jclarke)
- Sect 4: Added the snmpTlstmHashAlgorithms node to represent the new registry --- This is related to the issue that is still under review On this point, I would like some guidance from other MIB experts. You have created a “dummy” node with no type to represent this. This doesn’t give

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-tlstm-update-13.txt

2023-03-02 Thread Kenneth Vaughn
I have uploaded v13 of the TLSTM Update baed on Last Call comments. I believe there is only one outstanding comment remaining, which is what should we use as the identifier of the new registry. The current draft creates a new node for this purpose but we are waiting on input from others to

[OPSAWG] I-D Action: draft-ietf-opsawg-tlstm-update-13.txt

2023-03-02 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Operations and Management Area Working Group WG of the IETF. Title : Updates to the TLS Transport Model for SNMP Author : Kenneth Vaughn

Re: [OPSAWG] Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-03-02 Thread Kenneth Vaughn
I have revised the text to read: Renegotiation of sessions is not supported as it is not supported by TLS 1.3. If a future version of TLS supports renegotiation, this RFC should be updated to indicate whether there are any additional requirements related to its use. Regards, Ken Vaughn

Re: [OPSAWG] Éric Vyncke's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-03-02 Thread Eric Vyncke (evyncke)
Thank you, Ken, for considering my review. I hope that it helps to improve (the already good) quality of the I-D Regards -éric From: Kenneth Vaughn Date: Wednesday, 1 March 2023 at 20:15 To: Eric Vyncke Cc: The IESG , "draft-ietf-opsawg-tlstm-upd...@ietf.org" , "opsawg@ietf.org" ,

Re: [OPSAWG] Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-tlstm-update-12: (with COMMENT)

2023-03-02 Thread Zaheduzzaman Sarker
Thanks for explanation. In that section, the unsafe points of 0-RTT was called out and was enforces by normative language. For the renegotiation it was not described that much, whether it is a non- preferred feature for SNMP as a whole for whatever reason, rather it is just that TLS1.3 does