Minutes IETF106: opsawg
minutes-106-opsawg-00

What: Combined OpsAWG / OpsArea
When: 10:00-12:00 Wednesday Morning session I
Where: Collyer

OpsAWG Section
--------------------

Administrivia  - scribes, minutes, etc.
Tianran / Joe
5 minutes

Layer 3 VPN Network Model
Oscar Gonz¨¢lez de Dios/Qin Wu
Draft:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-l3sm-l3nm/
15 minutes

Auto-assign can be the default behavior
Ignas as operator: Making auto-assign the default will clash with many
deployments; should be an option Oscar: how to make that auto-assignment
happen; leave RT/RD blank or explicitly set auto-assign? Qin: no strong
preference for explicit or implicit auto-assign; document needs to Tim Carey:
We do see in zero-touch the need for the controllers to assign. Leaving the
blank is the auto-assignment. Auto-assignment is done via a profile/policy.
Joe: will send comments to list (on L3SM integration)

A Framework for Automating Service and Network Management with YANG
Qin Wu
Draft:
https://datatracker.ietf.org/doc/draft-wu-model-driven-management-virtualization/
10 minutes

Laurent: Interaction between Service Level and Network level misleading; you
don't decomission the service in the network level; should be within the
lifecycle of the service level Qin: Will shore up service lifecycle

Laurent: Good examples; maybe go for operations and show which models can be
used for those operations Qin: Will work through that Joe: Not on mic; agree
with this comment.  Showing operator use cases and how they map to YANG models
will be very helpful

Yang data model for TACACS+
Bo Wu
Draft:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs-yang/
5 minutes

Joe: Will follow up with YANG doctors to see if we can do anything with respect
to augment ietf-system Dymytro: Follow up with ietf-system authors to see when
the next version of ietf-system will be published Bo: Will follow up

In-situ Flow Information Telemetry
Haoyu Song
Draft:
https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/
15 minutes

Diego Lopez: Closed loop is misleading; about automatic control
Haoyu: Clarified in draft
Diego: Still not clear, needs a better term to avoid ambiguity
Haoyu: Closed-loop only exists in a given domain
Frank: the scope is large.
China Mobile: useful work and gives some examples.
China Telecom: support the adoption of the work.
Chair: How many of you have read this document? quite a lot.
Chair: How many of you think this is a useful work and the working group could
work on it? still many, 20+.

A YANG Module for uCPE Management
Dmytro Shytyi
Draft:
https://datatracker.ietf.org/doc/draft-shytyi-opsawg-vysm/
10 minutes

Dean: How is this different from RFC8530 [YANG Model for Logical Network
Elements] Dmytro: Not familiar (or don't remember)

Qin: Some similar work in teas working group
Dmytro: Working with the teas work; augmenting it

Dmytro: Corss work going on with ETSI?

Tim (from Jabber): Does the authors intend to use other virtualization
technologies than VMs like Docker, etc Tim (from Jabber): I would also ask that
can't the ETSI NFV SOL drafts be used to solve this problem? If ETSI has solved
the problem why do we need to duplicate this for a very specific problem domain

Sampled Traffic Streaming
Andrew Gray
Draft:
https://datatracker.ietf.org/doc/draft-gray-sampled-streaming/
10 minutes

Frank: Compare to 5476
Ignas: Please schedule a side meeting here in S'pore to discuss this work

In-situ OAM Deployment
Frank Brockners
Draft:
https://datatracker.ietf.org/doc/draft-brockners-opsawg-ioam-deployment/
5 minute

Multiple at mic: useful work, but could use more concrete recommendations. 
That may require more experience before those recommendations can be made It
may be that this document lives and evolves over time as more experience is
learned with IOAM

MUD (D)TLS profiles for IoT devices
Tirumaleswar Reddy
Draft:
https://datatracker.ietf.org/doc/draft-reddy-opsawg-mud-tls/
5 minutes

Eliot to comment on mic, but we had to push this to the list

Ops-Area Section
---------------------
Administrivia - scribes, minutes, etc.
Warren / Ignas
15 minutes

[Short mic time due to long opsawg]

Service Assurance for Intent-based Networking (SAIN)
Benoit Claise
Draft:
https://datatracker.ietf.org/doc/draft-claise-opsawg-service-assurance-architecture/
15 minute

Dean: This is a problem to solve; confusing autonomic and intent-based
Jeff: How do you model data received from CLI, telemetry, SNMP, etc. in a
coherent way Robin: More layers are introduced that add complexity to the
existing layers already present in the IETF

Rajiv: Architecture very useful; from a perspective of config there has not
been an effort to model the assurance aspect and create that hierarchy
 Contain and define service assurance (do you mean network, security, etc.)?
Figure out a hierachy and model that hierarchy
Physical vs. logical awareness is important
Benoit: API is there to augment those sub-service types
Alex Clemm: service assurance and the dependency graph could be split for more
reuse

Open Mic