Hi,
I am a Software Engineer working in Fujitsu's NMS product
supporting Netconf devices. I want a clarification in RFC 7950 on the behavior
of constraint validation in an edit-config request enforced by 'mandatory'
statement. I referred to section 8 in RFC 7950 regarding this and from what I
see, all edit-config requests should include the mandatory leafs. There is no
special behavior mentioned on edit-config's operation type as 'create' or
'merge' or 'delete' in the validation section of RFC.
This ends up in two different interpretations:
1. All edit-config requests must always include the mandatory attributes
irrespective of the operation type is create/merge
2. Edit-config requests must include the mandatory attributes only if
operation type is create and it can choose to skip if the attribute is already
present in Datastore due to previous edit-configs.
Kindly confirm which interpretation holds good. Also, I would like to
understand, if, 'mandatory' check applies to the payload during Payload Parsing
stage (mentioned in section 8.3.1 of RFC 7950) for every edit config and that
all edit config operations must include the mandatory attributes into the
payload, even if the operation is merge and the mandatory attribute exists in
the candidate store.
Kindly help to clarify.
Thanks & Regards,
Partha.
_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]
