Re: [netmod] New I-D Submission: draft-bertz-netmod-commonaugment

Lyle Bertz <lyleb551144@gmail.com> writes:

> Understood.
>
> Let's discuss at the meeting though.  This was a significant issue in the
> development of the IETF DMM FPC yang files and our open source project.   I
> am open to this going in the proper direction wherever that is but wanted
> to bring the issue and a possible solution to the table.

Yes, that's fine. One way to alleviate this problem is to define a
grouping and then have multiple augments that use this grouping. We used
this approach in RFC 8022. Would this work for your use cases?

Lada

>
> Lyle
>
>
> On Tue, Mar 7, 2017 at 2:43 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
>
>> Hi,
>>
>> while the use case is clear, I believe such rather fundamental changes
>> to YANG cannot be done through extensions because otherwise the value of
>> YANG as a standard will be lost.
>>
>> Lada
>>
>> Lyle Bertz <lyleb551144@gmail.com> writes:
>>
>> > All,
>> >
>> > This is a small submission that allows a single augment statement to be
>> > used to augment multiple schema locations or, at the very least, give the
>> > YANG to language generation tools a hint that the augment is similar to
>> > other augments in the module.
>> >
>> > It can be found at
>> > https://datatracker.ietf.org/doc/draft-bertz-netmod-commonaugment/
>> >
>> > It is in direct response to issues that arose writing YANG for the IETF
>> DMM
>> > FPC specification that can be found at
>> > https://datatracker.ietf.org/doc/draft-ietf-dmm-fpc-cpdp/
>> >
>> > and also in response to issues found wrt yangtools (OpenDaylight) code
>> > generation of the FPC specification.
>> >
>> > Lyle
>> > _______________________________________________
>> > netmod mailing list
>> > netmod@ietf.org
>> > https://www.ietf.org/mailman/listinfo/netmod
>>
>> --
>> Ladislav Lhotka, CZ.NIC Labs
>> PGP Key ID: 0xB8F92B08A9F76C67
>>

-- 
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67