It is my understanding that charter documents are now documents like any other, and when uploaded through the Datatracker, can then be subject to diff. Finding it hard to figure out the differences,, I took the 2.04 and 2.03 points from Toerless which have a different amount of white space, and stuff them through diff, and I got:
obiwan-[/corp/ietf/anima](2.4.1) mcr 10009 %diff -u charter-3.txt charter-4.txt --- charter-3.txt 2019-02-19 11:16:20.737525056 -0500 +++ charter-4.txt 2019-02-19 11:16:07.821564832 -0500 @@ -25,10 +25,11 @@ ANI OAMP interfaces (Operations, Administration, Management, Provisioning), e.g. YANG models ANI deployment structure (virtualization, compounding) Variations of Voucher formats -BRSKI/Bootstrap protocol aspects (different proxies, extensions for wireless) +BRSKI/Bootstrap protocol aspects (different proxies, extensions for wireless, adaptions for different markets) GRASP extensions for common use cases (e.g. bulk transfer, DNS-SD interworking) Autonomic discovery of NOC services -Autonomic Slice Management and Autonomic SLA management. +Autonomic Multi-tenant Management and Autonomic SLA management. Design and Implementer guidelines for ASAs, ASA Lifecycle management, ASA coordination/dependency resolution. and I'm perfectly happy with the changes, and with the charter as written. I find it slightly confusing that we say that Intent is part of the framework, but that we don't work on it without a recharter, but I guess the goal is not to forget it, but not to go down a rathole. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
