CCAMP IETF 115

CCAMP working group agenda - IETF 115
Monday, November 7, 2022
9:30-11:30 (Meeting time) - 9:30-11:30 (UTC) Monday Session I

Presentation Start Time Duration Information
0 09:30 15 Title: Administrivia - WG Status - Reporting on WG drafts not being presented - Milestones Update - Charter Update
Presenter: Chairs

1 09:45 20 Title: A YANG Data Model for Optical Impairment-aware Topology
Draft: https://datatracker.ietf.org/doc/draft-ietf-ccamp-optical-impairment-topology-yang
Presenter: Sergio Belotti

[Fatai Zhang]: Trying to clarify the optical protection part in this presentation. The optical protection function should not be dependent on the impairment. Would it also applicable to WSON/Flexi-grid network? If yes, we may need to update RFC9094.
[Sergio Belotti]: Yes the protection is also applicable for the WSON and Flexi-grid network, We do have the description for protection in this document, with the intention to take this into account in the impairment-aware network. But we are not preventing using it in other places.
[Fatai Zhang]: People need full picture, the current status means the implementers need to look into the impairment draft when they try to do WSON protection.
[Sergio Belotti] This is the general case, not just for optical protection, both for flexi-grid and WSON.
[Daniele Ceccarelli] You will find several items that have commonalities between fixed and flexible grid tecnologies, and impairment topologies. I would need to check to see.
[Italo Busi] The question is to understand what is gneric and what is specific for optical-impairment. So far we have focused on the information that needs to be reported. We can identify which pieces of this information applies only to optical impairments and which is more generic and think about a more modular approach. At the end we just need to identify which YANG definition goes in which YANG model.
[Adrian Farrel] You mentioned protection, I’m concerned that for protection we try to keep things general, is there anything for optical that is not already provided by the general TE protection?
[Sergio Belotti] The key is impairements. The concept is always the same, but we need to have the protection be impairement-aware as described in this document.
[Adrian Farrel] So you are effectively filtering the topology available to provide protection paths to only those resources that meet the impairement constraints?
[Sergio Belotti] Yes
[Daniele Ceccarelli] If that is the case, then WSON won’t need anything additional as the information is already provided in TE. Then the impairment-aware characteristics would perfectly fit into this document.
[Italo Busi] In the YANG tree, the additional-ltp list might be generic but I am not sure there are other technologies that have different reachability for working and protection paths, this looks quite generic to WDM and maybe applicable to WSON and flexi-grid topologies. The optical impairments are specific to optical impairments topology.
[Daniele Ceccarelli]: so we are having 3 classes: generic TE, WSON-specific and then optical-impairment specific.
[Julien Meuric]: The feature here is mainly describing 1+1 protection, and this is what is usually needed for path computation. WSON is having less requirement compared with the impairment, like spectrum availability. But there may not be clear boundary between the impairment and WSON. There may be something in this document that could be used outside.
[Daniel King]: Also we had discussion on whether to merge/split between WSON/flexi-grid in topo, path computation, tunnel and other models. It would be better to organize in the same style. It is suggested to have meeting discussing it and announce it to the WG.
[Dieter Beller]: This document focuses providing protection in optical impairment scenario. We are augmenting the TE topology. The objective is to support impairment-aware path computation. We think the current content is proper and should be separate with WSON documents.
[Aihua Guo]: Agree with Dan to coordinate between WDM/Flexi-grid and impairment. Configuration of the transceivers are highlyl dependent on the performance parameters. Groupings currently defined in this document may also be splitted to ‘common grouping’ and ‘specific grouping’.

2 10:14 10 Title: A YANG Data Model for Layer 0 Types
Draft:
Presenter: Sergio Belotti/Italo Busi

[Adrian] Can you spend some time with YANG Dr’s for YANG versioning and revision tag? This would allow implementations to specify if they are RFC9093 or “new work”. The draft to look at is https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning/
[Fatai] Regarding the OIF 400ZR, open to have CCAMP referencing to OIF IAs if necessary. Please cite the explicit IA and its sections from OIF.
[Sergio] I agree.
[Robert Wilton] (from Chat) @Adrian, the hope is that the two core YANG module versioning drafts will go to NETMOD WG LC in the next 3-4 months, but we also thought the same thing at IETF 114 (as a contributor to this work).

3 10:24 10 Title: OTN Slicing
Draft: https://datatracker.ietf.org/doc/draft-ietf-ccamp-yang-otn-slicing/
Presenter: Aihua Guo

[Daniele Ceccarelli] Once there is any output from discussion, please share with the mailing list and keep teas in the loop.

4 10:37 10 Title: Update on Flexi-Grid drafts
Draft: https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-flexigrid-yang
Draft: https://datatracker.ietf.org/doc/draft-ietf-ccamp-flexigrid-tunnel-yang/
Presenter: Daniel King
[Gert Grammel] Why only grey interface, there are a variety of photonic interfaces, CWDM, et al.
[Daniel King] Based on the intial discussions, a grey interface was flagged as requirement in a mixed technology enviroment. It’s a good point you highlight, and something we should investigate further

5 10:47 10 Title: A YANG Data Model for Microwave Topology
Draft: https://datatracker.ietf.org/doc/draft-ietf-ccamp-mw-topo-yang/
Presenter: Italo Busi/Scott Mansfield
No discussion.

6 10:53 10 Title: A YANG Data Model for Network Inventory
Draft: https://datatracker.ietf.org/doc/draft-yg3bp-ccamp-network-inventory-yang/
Presenter: Chaode Yu
[Daniele Caccarelli] Thank you for including the ‘IP and microwave technologies’ in the ‘next steps’.
[Robert Wilton] suggest to align with open config structure if you can. It is okay to have different terms but please include the reason for doing so.
[Chaode] Yes, I agree

7 11:02 10 Title: A YANG Data Model for Optical Performance Monitoring
Draft: https://datatracker.ietf.org/doc/draft-yu-performance-monitoring-yang/
Presenter: Chaode Yu
[Robert Wilton] Is there any overlap with what is going on in ippm WG? the module name in this document (ietf-performance-monitoring) looks very generic.
[Chaode Yu] ok, we will investigate more on the ippm work.
[Dieter Beller] PM is basically provided by the devices, and you can turn it on/off on the devices. All these functionalities are described in ITU-T G.7710, I don’t know why we need another one. You may need to find in that recommendation on how to retrieve the data from devices.
[Chaode Yu] There were descriptions in multiple places like TM Forum, and not unified. PM here is trying to align with TMF, but it’s not on the device. Instead it’s to the northbound of the controller.
[Dieter Beller] This is not the question, from architectural, PM not on devices? (cut off due to time.)
[Daniele Ceccarelli] Please continue this discussion on the mailing list

8 11:18 12 Title: Conveying Transceiver-Related Information within RSVP-TE
Draft: https://datatracker.ietf.org/doc/draft-meuric-ccamp-tsvmode-signaling/
Presenter: Julien Meuric

[Haomian Zheng] Firstly, the characteristics in this document are mainly used for routing or maintenance in optical layer, they ar more proper to appear in a routing protocol instead of signalling. Secondly, changing the modulation of the transceivers on-the-fly would be dangerous.
[Julien Meuric] I agree, the idea is not to change the transceivers characterics dynamically but to ensure consistent configuration during running. Extending IGP is a more ambitious for mid-term scenarios.
[Italo] (from Chat) maybe instead of IGP, LMP or some YANG model at the controller’s NBI can be sufficient. For further discussion offline.

9 11:29 13 Title: Signaling extensions for Media Channel sub-carriers configuration
Draft: https://datatracker.ietf.org/doc/html/draft-ggalimbe-ccamp-flexigrid-carrier-label
Presenter: Gabriele Galimberti
[Gabriele Galimberti] Idea is to align with other optical layer documents.