Transceivers capabilities attributes and OTSi configured parameters

[sergiobelotti]

Added groupings to define: a) common attributes capabilities related to operational mode b) common attributes capabilities in addition to operational modes related parameters. c) configured OTSi parameters related to operational modes parameters d) configured OTSi parameters in addition to operational modes related parameters.

The intent is to provide common structure for both topology model and interface model.

[sergiobelotti]

General comment:

More references are needed to where attributes and identities are defined

Yes, this is correct. Let's do it step by step to add the needed reference.

[ggrammel]

Hi Sergio,

Thanks for catching this. Suggestion is:

min OSNR: if received OSNR at minimum Rx-power is lower than MIN-OSNR, an increased level of bit-errors post-FEC need to be expected.

From: sergiobelotti notifications@github.com Reply-To: ietf-ccamp-wg/ietf-ccamp-layer0-types-ext reply@reply.github.com Date: Thursday, September 17, 2020 at 17:11 To: ietf-ccamp-wg/ietf-ccamp-layer0-types-ext ietf-ccamp-layer0-types-ext@noreply.github.com Cc: Gert Grammel ggrammel@juniper.net, Comment comment@noreply.github.com Subject: Re: [ietf-ccamp-wg/ietf-ccamp-layer0-types-ext] Transceivers capabilities attributes and OTSi configured parameters (#4)

[External Email. Be cautious of content]

@sergiobelotti commented on this pull request.

---

In ietf-layer0-types-ext.yanghttps://github.com/ietf-ccamp-wg/ietf-ccamp-layer0-types-ext/pull/4#discussion_r490330912:

• leaf max-polarization-dependent-loss {

• type decimal64 {

• fraction-digits 2;

• }

• units dB ;

• description "Polarization dependent loss";

• }

• leaf available-modulation-type {

• type identityref {

• base modulation;

• }

• config false;

• description

• "Modulation type the specific tranceiver in the list can support";

• }

• leaf osnr-margin {

suggested definition: min OSNR: if received OSNR is lower than MIN-OSNR then an increased level of bit-errors post-FEC need to be expected.

Thanks Gert , I like the definition. Moreover , as suggested by Colin, min OSNR be should be done in function of receive power. Use min OSNR at minimum power.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/ietf-ccamp-wg/ietf-ccamp-layer0-types-ext/pull/4#discussion_r490330912, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADTQOVHK3LSF3JZ3NSDE3YTSGIRKXANCNFSM4OFQJS4Q.

Juniper Business Use Only

[sergiobelotti]

if received OSNR at minimum Rx-power is lower than MIN-OSNR, an increased level of bit-errors post-FEC need to be expected.

@ggrammel : Thanks Gert: updated accordingly