Dear all,
We have created a new version of the draft
*draft-ietf-opsawg-scheduling-oam-tests
(https://datatracker.ietf.org/doc/draft-ietf-opsawg-scheduling-oam-tests/
<https://datatracker.ietf.org/doc/draft-ietf-opsawg-scheduling-oam-tests/>)*.
Here, we are sharing a summary of the work completed so far regarding the
repository *draft-contreras-opsawg-scheduling-oam-tests*.
- *Total closed issues:* 20
- Key areas addressed include:
- Clarifications on the use of the YANG model.
- Editorial improvements and formatting.
- Handling of schema-mount, normative references, and imports of
OAM models.
- Coverage of input/output parameters and resolution of conflicts
among scheduled OAM tasks.
- Updates to align with related drafts and RFCs.
- *Open issues:* 2
- *#5:* Alignment with draft *“Guidelines for Characterizing OAM”* –
pending terminology review.
- *#25:* Consider using templates (NETMOD) – currently under
discussion with examples provided.
Our understanding is that the template draft
(*https://datatracker.ietf.org/doc/draft-tt-netmod-yang-config-templates
<https://datatracker.ietf.org/doc/draft-tt-netmod-yang-config-templates/>/
<https://datatracker.ietf.org/doc/draft-tt-netmod-yang-config-templates/>*)
does not apply to our proposal. The template concept (when finalized) could
be used by our YANG model like any other.
We can define an “OAM Test Template” as follows:
<templates xmlns="urn:ietf:params:xml:ns:yang:ietf-config-template">
<template>
<id>oam-unitary-test-schedule</id>
<content>
<oam-unitary-tests xmlns="urn:example:oam-unitary-tests">
<oam-unitary-test>
<name>*ping</name>
<ne-config>
<ne-id>eth*</ne-id>
</ne-config>
<period-start>2025-10-01T08:00:00Z</period-start>
<frequency>hourly</frequency>
</oam-unitary-test>
</oam-unitary-tests>
</content>
</template>
</templates>
It could be used by a controller, but we understand this usage is not part
of our document. We want to get the group feedback before closing this
issue, but we understand that the schema mount presented in the document
covers our objective.
- *Next steps:*
- Continue reviewing open issues and integrate feedback for a new
version before Montreal.
- Update the document based on the group feedback
- Prepare updates to the draft ensuring consistency with related IETF
work.
- Update TWAMP example in the draft.
- Maintain alignment with evolving drafts such as
*ietf-netmod-schedule-yang*.
Regards,
Qin, Luis and Victor
_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
