Re: [CCAMP] Webex meeting changed: Optical impairments draft

[Gert Grammel <[e-mail]>]

We discussed today a difference in the interpretation of the model related to https://github.com/ietf-ccamp-wg/draft-ietf-ccamp-optical-impairment-topology-yang/issues/29 and its interpretation. The different interpretation lead to different computation requirements.
The design team appreciates feedback which of both Cases is preferred and what consideration led to the preference


Case A:
======
https://github.com/ietf-ccamp-wg/draft-ietf-ccamp-optical-impairment-topology-yang/issues#issuecomment-677768528 from August 20 documented the structure of the model:
+--ro supported-modes* [mode-id]
>   +--ro mode-id
>   +--ro (mode)?
>   |  +--:(G.698.2)
>   |  |  +--ro standard-mode?                standard-mode
>   |  +--:(organizational-mode)
>   |  |  +--ro operational-mode?             operational-mode
>   |  |  +--ro organization-identifier?      vendor-identifier
➢ |  +--:(explicit-mode)
➢ |    +--ro supported-standard-mode*? leafref
>   |     +--ro modulation-types                   identityref
>   |     ......

This snippet would allow to use standard mode or operational mode as a simple matching criteria for compatibility i.e. two transponders with Operational-mode=X and suitable line parameters would interoperate.
In case of “explicit” mode, the set of parameters provided, can support one or more application code/organizational mode, that means this set of parameters if applied to configure the transceiver, is aligned with one or more application code/organizational mode.
(Note that there are no additional parameters associated to the organizational mode in this case)

Case B:
======

https://github.com/ietf-ccamp-wg/draft-ietf-ccamp-optical-impairment-topology-yang/blob/master/ietf-optical-impairment-topology.tree contains additional parameters to the Operational Mode that are also replicated in the explicit mode. Those parameters are related to the min/max ranges which are allowed.

  +--ro supported-mode* [mode-id]
                +--ro mode-id                      string
                +--ro (mode)
                   +--:(G.698.2)
                   |  +--ro standard-mode?         standard-mode
                   +--:(organizational-mode)
                   |  +--ro organizational-mode
                   |     +--ro operational-mode?
                   |     |       operational-mode
                   |     +--ro organization-identifier?
                   |     |       organization-identifier
                   |     +--ro min-central-frequency?
                   |     |       frequency-thz
                   |     +--ro max-central-frequency?
                   |     |       frequency-thz
                   |     +--ro minimum-channel-spacing?
                   |     |       frequency-ghz
                   |     +--ro tx-channel-power-min?      dbm-t
                   |     +--ro tx-channel-power-max?      dbm-t
                   |     +--ro rx-channel-power-min?      dbm-t
                   |     +--ro rx-channel-power-max?      dbm-t
                   |     +--ro rx-total-power-max?        dbm-t
                   +--:(explicit-mode)
                      +--ro explicit-mode
                         +--ro supported-modes
                         |  +--ro supported-application-codes*
                         |  |       -> ../../mode-id
                         |  +--ro supported-organizational-modes*
                         |          -> ../../mode-id
                         +--ro line-coding-bitrate?
                         |       identityref
                     <snip>
                         +--ro min-central-frequency?
                         |       frequency-thz
                         +--ro max-central-frequency?
                         |       frequency-thz
                         +--ro minimum-channel-spacing?
                         |       frequency-ghz
                         +--ro tx-channel-power-min?
                         |       dbm-t
                         +--ro tx-channel-power-max?
                         |       dbm-t
                         +--ro rx-channel-power-min?
                         |       dbm-t
                         +--ro rx-channel-power-max?
                         |       dbm-t
                         +--ro rx-total-power-max?
                                 dbm-t

In this case, interoperability can only be provided if the organizational code on each side match AND all other explicit parameters defined in the organizational-code have a matching range.
(Note that min/max parameters are associated to the organizational mode AND to the explicit mode in this case)



Juniper Business Use Only