Re: [netconf] RFC6241/RFC7952 model-level interop?

[Kent Watsen <[e-mail]>]

All.

I've created trackers for NETCONF-next and RESTCONF-next here:

  - https://github.com/netconf-wg/netconf-next
  - https://github.com/netconf-wg/restconf-next


Robert, please add your request to the netconf-next issue tracker.

Thanks,
Kent



> On Mar 2, 2019, at 8:57 AM, Martin Bjorklund <[e-mail]> wrote:
> 
> Kent Watsen <[e-mail] <mailto:[e-mail]>> wrote:
>> Hi Robert,
>> 
>> There is currently no plan to do this, nor is there an rfc6241bis in sight,
>> though one may be prompted by the YANG-next discussion happening
>> in NETMOD.
>> 
>> Options (open to comments):
>> 
>> a) file an Errata
> 
> An RFC errata is not appropriate for enhancing an existing module with
> new definitions.
> 
>> b) file a feature request (start a NETCONF-next issue tracker?) 
> 
> It is probably a good idea to have such a tracker.
> 
>> c) submit an I-D that *updates* just this aspect of RFC 6241
>> d) submit an I-D for rfc6241bis  (we're probably not ready for this yet)
>> e) any other choices?
> 
> 
> /martin
> 
> 
>> 
>> Kent
>> 
>> 
>>> On Feb 28, 2019, at 11:04 AM, Robert Varga <[e-mail]> wrote:
>>> 
>>> Hello,
>>> 
>>> as an implementer of both RFC6241 and RFC7952, I would find it very
>>> useful if there were an ietf-netconf.yang which includes the annotation
>>> definition of edit-config's operation attribute (Section 7.2).
>>> 
>>> Are there any plans for RFC6241bis or similar, bringing only an update
>>> to ietf-netconf.yang?
>>> 
>>> Thanks,
>>> Robert
>>> 
>>> _______________________________________________
>>> netconf mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/netconf
>> 
>> _______________________________________________
>> netconf mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/netconf
>> 
> 
> _______________________________________________
> netconf mailing list
> [e-mail] <mailto:[e-mail]>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>