Closed italobusi closed 2 years ago
As discussed during CCAMP IETF 112 meeting, we will have another update of this document and later discuss how to split it
Comment from @aguoietf :
If we look at the current flex grid and wson path computation - they are identical. Therefore I think a better strategy is to combine these two and have a common path computation model for both flex grid and wson. We can add flex-grid- or wson-specific constructs onto the common model using augments (or even within the same model by switch-case statement) if there is a need.
See: https://github.com/aguoietf/ietf-ccamp-optical-path-computation/pull/18#pullrequestreview-898977312
Comment from @aguoietf :
If we look at the current flex grid and wson path computation - they are identical. Therefore I think a better strategy is to combine these two and have a common path computation model for both flex grid and wson. We can add flex-grid- or wson-specific constructs onto the common model using augments (or even within the same model by switch-case statement) if there is a need.
See: #18 (review)
The augmentations related with TE labels are not in common between WSON and flexi-grid models, but I would agree that all the other augmentations would be in common between WSON and flexi-grid models ...
An alternative approach could be to have a common l0-path-computation model with all the common augmentations to be further augmented by wson-path-computation and flexi-grid-path-computation models with the specific augmentations (most likely only those related to the TE labels)
Feedbacks from IETF 113 discussion:
https://notes.ietf.org/notes-ietf-113-ccamp
I think we can close this issue
Discuss how many documents (1,2 or 3) should developed: