What: Miuntes of Joint OpsAWG / OpsArea
When: 09:30 - 11:30 Tuesday Session I, Mar 28, 2023
Where: G412-G413

Notetakers: Rob, Henk

OpsAWG Section

Export of On-Path Delay in IPFIX, Thomas Graf, 5 min
I-D:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-on-path-telemetry

Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-export-of-on-path-delay-in-ipfix-02.pdf

No questions.
Joe: Great to see some implementation as well, appreciate that.

Updates and Next Steps for IPFIX drafts, Mohamed Boucadair,15 min
I-Ds: https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc7125-update/

https://datatracker.ietf.org/doc/draft-boucadair-opsawg-ipfix-tcpo-v6eh/

https://datatracker.ietf.org/doc/draft-boucadair-opsawg-tsvwg-udp-ipfix/

https://datatracker.ietf.org/doc/draft-boucla-opsawg-ipfix-fixes/
Presentatiom:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-updates-and-next-steps-for-rfc7125-update-and-companion-i-ds-00.pdf

Med(pres): Simple-IPFIXes may not become an I-D
Thomas: IPv6 EH there can be only one occurrence. Consider multiple
types in a package.
Rob: Be quick with process, because this is useful
Chair ACTION: WGLC for RFC 7125-update

A Data Manifest for Contextualized Telemetry Data, Jean Quilbeuf, 15 min

I-D:
https://datatracker.ietf.org/doc/draft-claise-opsawg-collected-data-manifest/

Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-a-data-manifest-for-contextualized-telemetry-data-00.pdf

Rob: YANG Packages was stuck due design time of schema amount. The aim
is that the packages can describe the mounted schema which might be
described as design time. But using schema mount could also increase
complexity.
Joe: Number of strings that look kind of nebulous creates mixed
feelings.
Jean: Inventory part is not ready yet. Want to be able to look up the
manifest by using the name of the device in the telemetry data.
Joe: Agrees on inventory, but without additional guidance what "this
should be" it cannot be tied to something specific
Jean: Defined in the platform manifest, and leaf ref from the data
manifest.
Thomas Graf: Another choice would be to use the IP address that is
exposing the metrics, but a router may use many IP addresses, and hence
using a SysName seems preferable.
Bo Wu: We have been working on network inventory, but also in CCAMP.
This work is going on. If the inventory can be reused that would be
good.
Italo(from chat): +1 to Bo
Joe(chair): We will raise the adoption question on the list

IP Flow Information Export (IPFIX) Information Elements Extension for
Forwarding Exceptions, Venkata Munukutla, 10 min
I-D:
https://datatracker.ietf.org/doc/draft-mvmd-opsawg-ipfix-fwd-exceptions/

Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-ip-flow-information-export-ipfix-information-elements-extension-for-forwarding-exceptions-01.pdf

No questions/comments.
Poll: "Raise hand, if you tink that this work is interesting".
Result: A reasonable number of people think that this work is
interesting. (in room result 13 raised, 4 not raised)

Attachment Circuits & SAPs, Mohamed Boucadair, 15 min
I-Ds:
https://datatracker.ietf.org/doc/draft-boro-opsawg-ntw-attachment-circuit/

https://datatracker.ietf.org/doc/draft-boro-opsawg-teas-attachment-circuit/

https://datatracker.ietf.org/doc/draft-boro-opsawg-teas-common-ac/
Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-attachment-circuits-saps-00.pdf

Italo: Grouping is useful to do. SAP -- > what is the difference between
an AC and a link?
Med: Some speific items really have to focus on defining the object,
e.g. if the link is physical. Definition is more important than term
that definition is tied to.
Rob: What is the scope of this work, is it just a new model, or is it
creating bis versions of existing models.
Med: At the moment, a new module augmenting the existing models, but may
be interested in creating bis versions in future.
Rob: One advantage of the OpenConfig approach is that allow the models
to move more quickly, where as the IETF process is slower. We should
find an approach in the middle that allows the IETF models to evolve
more quickly.
Med: I agree.
Adrian Farrel (from chat): I'd like to see the ORAN draft presented in
TEAS before OPSAWG adopts. There seems to be a lot of overlap with
ongoing work in TEAS

An Inventory Management Model for Enterprise Networks, Bo Wu, 10 min
I-D:
https://datatracker.ietf.org/doc/draft-wzwb-opsawg-network-inventory-management/

Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-an-inventory-management-model-for-enterprise-networks-00.pdf

Alex Clemm: I think that this is import work.
Marisol: I want to note the overlap with DLMO. No overlap with
inventory. Objective of DLMO is to decouple from the inventory (i.e., it
should remain separate just be referenced)
Bo: I understand your concerns, but modelling from software, but
licences might apply to sofrware, and can identify the root cause.
Olga: Good to use network-topology, be careful about layering, in
particular links, where they belong. Make clear if it’s operational
status.
Rob: Inventory YANG is happening in different places/WG. Maybe setting
up another side meeting is useful. Joining the inventory mailing
list is also really usful to faciliate more synergy.
Diego: What exactly is "inventory"? That "muddy" scope definition is not
the basis for a set of fundamental requrirements.

Data Model for Lifecycle Management and Operations, Marisol Palmero, 5
min
I-D: https://datatracker.ietf.org/doc/draft-palmero-opsawg-dmlmo/
Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-data-model-for-lifecycle-management-and-operations-01.pdf

Joe: I-D is in WGAC and will also expire in CW 14.
Diego: we are trying to decouple this from vendor discussions, making a
clear separiation.
Joe: we already talked about abtracting out the inventory.

Green Networking Metrics, Alexander Clemm, 10 min
I-D: https://datatracker.ietf.org/doc/draft-cx-green-metrics
Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-green-networking-metrics-00.pdf

Jean: one issue was that if you publish in real-time that implies some
security considerations
Éric(from chat): not so much security (CPE consumption) but privacy
indeed
Alex: some of them are already addressed in the SecCon
Rob: Metrics off the device seem to be a feasible first step independent
of the place where this work happens.
MCR(from chat): OPSAWG might be the right place, but OPSAWG has
significantly negative cycles available right now.
Poll: Raise Hand, if you think OPSAWG is the right place to work on
this?
Result: Considerable amout thinks OPSAWG is the right place (in room
result 37 raised, 4 not raised)

An Overview of Energy-related Effort within the IETF, Toerless Eckert, 5
min
I-D:
https://datatracker.ietf.org/doc/draft-eckert-ietf-and-energy-overview/

Presentation:
https://datatracker.ietf.org/meeting/116/materials/slides-116-opsawg-ietf-and-energy-overview-00.pdf

Marisol(from chat): there are two side meetings on Thursday related to
netzero and environment impact as a follow up from the Workshops
happening in Dec -22

=== Exceeds time ===

A Policy-based Network Access Control
Qiufang Ma
10 min
https://datatracker.ietf.org/doc/draft-ma-opsawg-ucl-acl/

A YANG Data Model for Network Diagnosis by scheduling sequences of OAM
tests
Luis M. Contreras
10 min
https://datatracker.ietf.org/doc/draft-contreras-opsawg-scheduling-oam-tests/

Incident Management for Network Services
Chong Feng
15 min
https://datatracker.ietf.org/doc/draft-feng-opsawg-incident-management/

Ops-Area Section

Administrivia - scribes, minutes, etc.
Warren / Rob
5 minutes

Modeling the Digital Map based on RFC8345: Sharing Experience, Benoit
Claise, 10 minutes

Henk: Already discussed that 15 years ago, should reuse material from
that time.

Open Mic