CCAMP working group agenda - IETF 119
Friday, March 22nd, 2024
9:30-11:30 (Meeting time) – Room M3
Presentation Start Time Duration Information
0 9:30 10 Title: Administrivia - WG Status - Reporting on WG drafts not
being presented
Presenter: Chairs
(for OTN slicing draft)
Aihua Guo: the feedback from teas chair is positive, and draft-liu will
be probably adopted in teas.
(for Liaison)
Scott Mansfield: IM/DM meeting is the modeling coordination among
organizations, open and welcome experts. We are working on sync YANG,
and other transport management models.
Deborah sent out the email to follow up the response to OTNT SWP.

1 9:40 13 Title: A YANG Data Model for Optical Impairment-aware Topology

Draft:https://datatracker.ietf.org/doc/draft-ietf-ccamp-optical-impairment-topology-yang

Draft: https://datatracker.ietf.org/doc/draft-ietf-ccamp-rfc9093-bis/

Presenter: Sergio Belotti (Remote)
Daniele Ceccarilli: will move the two drafts together.

2 9:56 10 Title: A YANG Data Model for WDM Tunnels and Path Computation

Draft:https://datatracker.ietf.org/doc/draft-ietf-ccamp-wdm-tunnel-yang/

Draft:https://datatracker.ietf.org/doc/draft-ietf-ccamp-optical-path-computation-yang/

Presenter: Aihua Guo

(for first draft)
Daniele Ceccarilli: In the context of pluggable scenario we were only
considering Optical Impairments and WDM interface YANG model. Thanks for
reminding that also this draft has to be considerded.
Are you proposing we move the first work without pluggable features?
Aihua Guo: Yes.
Sergio Belotti: we have a set of WDM models (9093bis, impairment, WDM
interfaces, WDM tunnel, ...) it is suggested to have pluggable reusing
these works.

3 10:08 12 Title: An update on Transport NBI Design Team Activities
Presenter: Nigel Davis and Italo Busi

Daniele Ceccarilli: [re: defining t-nbi] when proposing text please
share on the list. (Italo agrees)
Swamynathan Balasundaram: [re: inventory] just to indicate if agreed
by ivy, this (inventory UC) is what we want, probably as a subset.
Others will be a set of functions.
Nigel Davis: we intend to use the models as defined.
Daniele Ceccarilli(to AD): we are producing the work on the github and
wiki, we are not defining new models, so not targeting on RFC. However
this should be useful as it teaches how non-IETF experts our solution
works. Is there a better way to make the work more usable? For example
an informational RFC.
John Scudder: An information RFC could help. There are other alternative
publications like BCP,
Daniele Ceccarilli: BCP is perfect, would IESG accept that?
John Scudder: let's double check the charter.
Nigel Davis: the concern is about complicated figures beyond ASCII.
John Scudder: there are guidance and tools, let's take it offline.
Italo Busi: my concern with informational RFC is that we need rich
graphic tools (richer than plain SVG) and produce huge amount of
text/examples so we would face the same issue with the current I-D. A
possible compromise could be to put the huge text in github/wiki and
have a short information RFC with the summary and a pointer to the
github/wiki text for details.
Aihua Guo: good to add an overview landscape of IETF data models
relevant to Transport NBI.
Haomian Zheng:Regarding alignment of the term, how do we make it? The
work should belongs to which side?
Nigel Davis: Mapping is important, so first understand each other and
produce the mapping. I would personally work in the other body to
improve the term alignment. It would be useful to normalize the terms
and announce it to the industry.
Daniele Ceccarilli: also need to align term with other IETF work, and
higher priority than other body. Nigel Davis: agree.
Italo Busi: if IETF already has a term, we will use it, if no we take
external ones.
Oscar Gonzalez de Dios: good to add use cases, not only examples.
Nigel Davis: we will have examples which are basically use cases.
Oscar Gonzalez de Dios: operator have use cases and then vendor provides
solutions, is it doable in this work? BTW the approach to solve the use
cases may be applicable to other technologies as well.
Nigel Davis: This problem applies to all data models, we will try to
bring guidelines.
Oscar Gonzalez de Dios: If BCP is the way forward we do BCP.
John Scudder: does it mean you volunteer to generalize the document to
cover multi-technology?
Nigel Davis/Italo Busi: no volunteer, but maybe we can share this work
to other groups and call for interests to contribute together. People
can also follow the same guidelines.
John Scudder (from the chat, regarding visual figures related to
Transport NBI): This is the document I was thinking of that only has
figures in SVG: https://datatracker.ietf.org/doc/draft-ietf-detnet-yang/

4 10:28 25 Title: POI Pluggable Progress & Documents
Overview: A brief review on progress (5min) – Daniele Ceccarelli
Operator: Requirement & Use Cases (10min):
https://datatracker.ietf.org/doc/draft-poidt-ccamp-actn-poi-pluggable-usecases-gaps/
- Oscar Gonzalez de Dios (remote)
Vendor: Data Model Considerations (10min) - Reza Rokui

Daniele Ceccarilli: the work for pluggable will be 'requirement, use
case and gap analysis' and then 'model design'. Other previous works
terminate.

(regarding Oscar's presentation)
Daniele Ceccarilli: the work cleans up the requirements, and will be
used as the reference for future.

(regarding Reza's presentation)
Luis Contreras: it would be convenient to add an entry in the wiki for
the external tools used (i.e. Google Sheet)
Haomian Zheng: to confirm the scope of host, is it generalized host?
should not be restricted to router.
Reza Rokui: Yes, every possible host applies, and all kinds of
contributions are welcome.
Italo Busi: For the naming of attributes, need to clarify whether it's a
missing attributes, or a bad name.
Reza Rokui: Agree, just bring everyone be aware of this.

5 10:53 10 Title: YANG Data Model for Performance Monitoring
Draft:
https://datatracker.ietf.org/doc/draft-zheng-ccamp-client-pm-yang/
Draft:
https://datatracker.ietf.org/doc/draft-yu-performance-monitoring-yang/

Presenter: Chaode Yu (Remote)
Daniele Ceccarilli: considers the adoption of client-pm, will move on
the list.

6 10:50 10 Title: YANG Data Models for Transport TE FGNM Extension
Draft: https://datatracker.ietf.org/doc/draft-yu-ccamp-te-fgnm-yang/
Presenter: Chaode Yu (Remote)
Nigel Davis: (regarding motivation page) TMF is too broad, what is the
focus?
Chaode Yu: mainly Corba/MTOSI.
Nigel Davis: then makes sense and willing to help for T-API alignment.
Let's proceed offline.

7 11:11 10 Title: Path Computation and Control Ext. for Fine-Granularity
Transport Network
Draft:
https://datatracker.ietf.org/doc/draft-han-pce-path-computation-fg-transport/

Presenter: Liuyan Han (Remote)
Min Xiao: ITU-T SG15 consented data plane document and we confirm this
work fits in the scope of ccamp.
Italo Busi (from the chat): agree

8 11:18 10 Title: Applicability of GMPLS for fine grain Optical
Transport Network
Draft:
https://datatracker.ietf.org/doc/draft-lin-ccamp-gmpls-fgotn-applicability/

Presenter: Yi Lin (Remote)
No discussion.

9 11:26 10 Title: A YANG Data Model for Microwave Radio Link
Draft: https://datatracker.ietf.org/doc/draft-ybam-rfc8561bis/
Presenter: Scott Mansfield
No discussion.
Adjourn 11:30