Some more discussions on the needs of CCA/CCB configuration in FlexE management

Jiangyuanlong <[email protected]>
Newsgroups gmane.ietf.ccamp
Message-ID <3B0A1BED22CAD649A1B3E97BE5DDD68BD378FEE7@dggeml512-mbx.china.huawei.com>
Hi Qilei,

Due to the limited time in the presentation of your slides, we barely had enough time to discuss it in details.
Here I would like to reemphasize that the conclusion you reached in Page 7 (quoted below) is not reasonable:
“Whether type calendar configuration A or B is needed?
* It should be supported.
  According to the definition in FlexE IA, in static configuration: “Such a configuration would
  simply transmit the A and B calendar configurations as fixed, always indicate the
  A calendar configuration as the calendar configuration in use”.
* In order to ensure the consistency between two ends, it’s better to configure the type of cale
ndar at both ends.”

The FlexE IA specifies the A and B calendar configurations (i.e., CCA and CCB) to facilitate dynamic switching of calendar configurations.

But for the above static configuration, CCA is always in use and its values are meaningful (i.e., support a fixed active calendar configuration for verification), while CCB is never truly used (though transmitted in the overhead), and its values are undetermined in the FlexE IA. How does the far end process CCB is also unspecified in the FlexE IA. Under such a circumstance, why configure the CCB in the first place? Even if one can configure the CCB, what values should be provided for them?

Furthermore, the above IA texts also mandates that for a device working in static configuration, we cannot switch calendar configuration from CCA to CCB.

Therefore, configuring the type of calendar configuration (i.e., CCA/CCB) for a device working in static configuration is meaningless.

Kind regards,
Yuanlong

_______________________________________________
CCAMP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ccamp
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.