[Taps] YANG updates

["Holland, Jake" <[e-mail]>]

Hi taps,

It turns out sometimes forcing functions can do some work even
when the trigger is cancelled.  I have a few minor yang updates,
plus a question (in #4):


1. Tooling update

I cleaned up the make process for the yang module draft a bit, while
still keeping the structure of importing external files + automated
validation.

This version only requires pyang and rsync to build if you're not
validating, and adds in a requirement for the yanglint executable
(included with libyang), but only if you use 'make yanglint' or
set "VALIDATE_YANG=1" as an environment variable.  In return, it
removes my extra c file that linked to libyang.

It also no longer auto-builds its dependencies, it just complains
if you don't have the requirements installed.

The current Makefile points to my i-d-template fork that has these
changes, since otherwise it won't build a proper draft:
https://github.com/GrumpyOldTroll/ietf-taps-yang/blob/master/Makefile#L11

I've sent a pull request to merge the cleanup upstream:
https://github.com/martinthomson/i-d-template/pull/193

As far as I know, nobody has reviewed it, so it could use some
sanity-checking and probably some feedback.  Good chance some changes
would be in order, if only I knew what they were.


2. Theresa made a pull request to make the identity and algorithm
in the security container optional:
https://github.com/GrumpyOldTroll/ietf-taps-yang/commit/265e3a0219e115a181618915a73b893409ef5a29

It sounded plausible to me, so I pulled it.  (But not before checking
whether 'mandatory false' should be added also, and finding that I get
warnings from yanglint if I try making it explicit, so it's better as
written.)  Thanks Theresa!


3. I think I also addressed one of the 4 issues Theresa opened after
Montreal, by adding a constraint that there must be at least 1 remote
or local endpoint in a preconnection and adding a negative test for it:
https://github.com/GrumpyOldTroll/ietf-taps-yang/commit/886b5ee1e4a37c59c74c9b60b1dfbdd7097d156f

And thanks for the review and for opening the issues, Theresa!


4. I think in Montreal, Tommy suggested to me offline that I transfer the
ietf-taps-yang repo to https://github.com/ietf-tapswg.

I'll go ahead and do that if I get a couple of "yes, go ahead"s, but I
thought I'd check first, because right now I think I don't have consensus,
so much as a vague memory of a mumbled suggestion that I'm only 70%
certain I understood correctly.  I think it makes sense, but I don't want
to surprise anyone or clutter things up if people believe it needs work
before going there.

So does it sound right to just transfer the repo now?


Best regards,
Jake