Thanks Jean and Benoit for your clarification.
I think this manifest information is useful.
One more justification IMO might be useful.
When controller and collector are on separate servers, which is a very common
deployment, collector may not have access to the device configuration.
T.
From:
Sharing with the WG the meeting notes from the DMLMO side meeting:
https://notes.ietf.org/s/jEUXpW1XR
**IETF DMLMO side meeting (Feb/9)
Attendees
Benoit Claise Luis M Contreras Eric Vyncke Yannis Viniotis Diego Lopez Camilo
Cardona Sudhendu Kumar Marisol Palmero
Recording:
Hi Tianran,
On 2/9/2022 2:04 PM, Tianran Zhou wrote:
Hi Jean,
I am a little confused about this manifest?
Can we just read from the device about the configuration? We can get all the
running information.
I'm not sure whether this is a generic question or whether your question
relates to the
Hi Tiaran,
The value of this draft is not to expose new information via YANG but rather to
define what needs to be kept as metadata (or data manifest) to ensure that the
data can still be interpreted correctly even if the device is not present
anymore, has been updated or has a new
Hi Jean,
I am a little confused about this manifest?
Can we just read from the device about the configuration? We can get all the
running information.
Best,
Tianran
Sent from WeLink
发件人： Jean
Quilbeufmailto:jean.quilbeuf=40huawei@dmarc.ietf.org>>
收件人：
Dear All,
We are wondering whether to add information about protocols in the data
manifest draft
https://datatracker.ietf.org/doc/draft-claise-opsawg-collected-data-manifest/
Details are here
https://github.com/JeanQuilbeufHuawei/draft-collected-data-manifest/issues/9
(that git repo
