Re: [CCAMP] Optical pluggables - Gap analysis and Data modelling

[Gert Grammel <[e-mail]>]

Daniele,

Sorry for including some graphics in the email but you can find the references there as well. When checking the sheet called “Scope of IETF Pluggable work” in https://docs.google.com/spreadsheets/d/1atqBARO76hzRp5ETHzsOYLsfabHQbulf0AtbVAMV66A/edit - gid=1168079582<https://docs.google.com/spreadsheets/d/1atqBARO76hzRp5ETHzsOYLsfabHQbulf0AtbVAMV66A/edit#gid=1168079582and>, I was wondering if it is accurately describing what this is about.

  1.  It is true that https://github.com/ietf-ccamp-wg/draft-ietf-ccamp-optical-impairment-topology-yang is a network model but https://datatracker.ietf.org/doc/draft-ietf-ccamp-dwdm-if-param-yang/ that is associated (i.e. same parameter definitions) belongs to a device model. On what basis is the claim that IETF Pluggable Modeling is a Network Model (left picture at bottom)?
[FXBM3m7wAAAABJRU5ErkJggg==]



2.  In the same picture it is also stated that “In context of IETF pluggable modelling, Optical pluggable is **the** device”. That may cause some confusion, https://datatracker.ietf.org/doc/html/rfc6241 states: “A device MUST support at least one NETCONF session and SHOULD support multiple sessions.” Similarly, OpenConfig has a “Device” container (see https://karneliuk.com/wp-content/uploads/2018/07/128_net_01_oc_yang.png that reflects RFC6241.  So for defining the scope it would be clearer to say Optical pluggable is an optical-terminal” (TBC name for further discussion).

 [A diagram of a company  Description automatically generated]


  1.  The figure on the right (starting from column J) is similarly confusing. The “thin arrow” between “domain controller” (=netconf client?) points to a single entry point of the host (=device). What is unclear is the “thick arrow” from the domain controller to the “Coherent Plug Data on Host” It would needs further explanation.

[Dy4xC6fep4r9AAAAAElFTkSuQmCC]

  1.  The “Scope of IETF Plugable Work” (starting from: C46) in the black box is very focussed on IDs. We don’t know yet how exactly things needs to be modeled and the discussion about telemetry/alarms suggest that more than IDs are needed. My suggestion is to swap host-ID and media-ID with “host-properties” and “media-properties” which would be more general and include the use of IDs.
[NyBJJjzEBJ23mJE24m829p7npI2E5VgKb+CaiaGsExmPcjB0+exGljnVEkwjBIiLFitZyCqs1+ci9Ys3t1y25rzV+OmWBdCAAAiAAAiAAAiAAAiAAAiAAAl2IwP8DvA3uE1V8QscAAAAASUVORK5CYII=]


Cheers

Gert



Juniper Business Use Only

From: CCAMP <[e-mail]> on behalf of Daniele Ceccarelli (dceccare) <dceccare=[e-mail]>
Date: Thursday, 4. April 2024 at 11:02
To: [e-mail] <[e-mail]>
Subject: Re: [CCAMP] Optical pluggables - Gap analysis and Data modelling
[External Email. Be cautious of content]

Hi Reza, all,

Italo, Sergio and I took a first stab at the shared google doc.
Please find a suggested updated of the interfaces picture in the tab “scope of IETF pluggable work).

Here is the link to the doc for easier access to all the working group.

https://docs.google.com/spreadsheets/d/1atqBARO76hzRp5ETHzsOYLsfabHQbulf0AtbVAMV66A/edit#gid=1168079582<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1atqBARO76hzRp5ETHzsOYLsfabHQbulf0AtbVAMV66A/edit*gid=1168079582__;Iw!!NEt6yMaO-gk!A-2RE0vjxtLcarKoC2-v-78aez5lBzvkbPDv2Qf6VTjd12uO_j3GMxqh6GCGRfCtZLL9YuTYEJANfkCplFmtQrw92NulSj-F$>

Thanks
Daniele

From: Rokui, Reza <[e-mail]>
Sent: Sunday, March 31, 2024 9:27 PM
To: CCAMP Working Group <[e-mail]>; [e-mail]; Rokui, Reza <[e-mail]>; Davis, Nigel <[e-mail]>
Subject: Optical pluggables - Gap analysis and Data modelling

All,

I am not able to attend tomorrow’s meeting.
FYI, Nigel and I worked on the attributes last week and it is in much better shape. We plan to do further improvements.
You should be able to access it. Please take a look.

Reza


Sent from my iPhone