All of the edits related to idnits have been addressed in
draft-ietf-opsawg-tlstm-update-10. As discussed below, I tweaked the wording
for SnmpTLSAddress to require conformance to 1123 and 5890 when it is intended
to represent a hostname and I made those normative references. The only issues
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This 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
Sure, this would be fine. And I’ve seen the back and forth with IANA.
Joe
From: thomas.g...@swisscom.com
Date: Saturday, October 8, 2022 at 2:28 AM
To: Joe Clarke (jclarke) , opsawg-cha...@ietf.org
Cc: opsawg@ietf.org , pierre.franc...@insa-lyon.fr
, benoit.cla...@huawei.com
Subject: RE:
Hi, authors:
I have read the latest version of this draft, it is well written, thank for
that.
Here is the identified minor issues during document shepherd review of
draft-ietf-opsawg-sbom-access-11:
1. Abstract said:
"
It may optionally be discovered through manufacturer usage
Dear Joe,
My apology for late reply. That works for us.
We are in touch with IANA and the IPFIX doctors to clarify the points raised by
Med in regards to the srhFlagsIPv6 and the srhSegmentEndpointBehavior registry.
Once this has been clarified we will publish -02 version.
We would like