search

oscargdd / drafts-nmop-isis-ospf-topologies

A YANG Data Model to represent Intermediate System to intermediate System (ISIS) Topology
Other
0 stars 4 forks source link

Write YANG objects #10

Open bclaise opened 1 year ago

bclaise commented 1 year ago

First, I updated the security considerations section with the right references from https://wiki.ietf.org/group/ops/yang-security-guidelines

"There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations."

If we agree that WRITE is for simulation, then we have no "negative effect on network operations".

Also, we want to add some information about the readable data (see the template)

bclaise commented 1 year ago

Discussing further with Olga. I actually wanted to write in the draft a section about "the rW, so the write capabilities of the YANG objects, is for simulation only ... and would not have any impact on the network IS-IS configuration". So that this northbound API is read-only for the network, but write, if I want to do offline simulations. However, Olga has a good point: what I can simulate if I don't have all/most of the configuration YANG parameters from the RFC9310? See section "Design of the Data Model of RFC9310", for the list of those parameters.

Regardless, we must clarify what the W means in the RW for the objects. We should collect feedback from operators: should such a techology-specific Digital Map layer be read-only for the network status, or also read-write? If read-write, for which goals? Writing to the network (I don't think this is a good idea) or read-write for simulation?