Toerless Eckert <[email protected]> wrote: > So, i hereby want to announce the two documents as adopted by ANIMA WG > with the following process guidelines:
> - The decision whether to merge or not is not final. Given how the
> documents are separate right now, it should be most easy to submit the
> -00 versions separate, but merging can happen during WG work if the
> authors/WG so prefer then (e.g.: primarily i would think to eliminate
> possible duplication).
I have renamed both documents and submitted them to DT, needs chair approval.
I seem to have permissions so I've moved the repos to anima-wg organization,
and I put them on "constrained" team group, since there was one. I added
Thomas Werner to that group.
> - I would not want to have even more scatter/gather documentation, so i
> think it should be fair game to include other informational
> "considerations" about masa and registrar than "operational" - for
> example "implementation".
That sounds great.
I see these documents as operational input to implementation decisions.
> This was a conclusion i came to when first thinking "hey, we should
> call them draft-ietf-anima-masa/brski-ops instead of
> considerations". But then i went to a drafts cache and checked if/whet
That works for me.
"draft-ietf-anima-brski-considerations"?
I guess I need to make slides for Madrid on what's there, and how we might
merge things. It would be great if others also put up a list of things they
want to add.
> other docs had choosen that title and i actually could not find any
> with -ops-, but i could find various -considerations- drafts for other
> technologies that where informational, expanding on the base spec
> technology - without being specifically constrained to necessarily
> e.g.: one topic such as "ops".
dyas-[ietf/cache/rfc](3.3.8) mcr 6016 %grep -i operational rfc-index.txt | wc -l
45
dyas-[ietf/cache/rfc](3.3.8) mcr 6017 %grep -i operational rfc-index.txt | grep
-i considerations
2541 DNS Security Operational Considerations. D. Eastlake 3rd. March
4472 Operational Considerations and Issues with IPv6 DNS. A. Durand, J.
8207 BGPsec Operational Considerations. R. Bush. September 2017. (Format:
9099 Operational Security Considerations for IPv6 Networks. É. Vyncke, K.
9317 Operational Considerations for Streaming Media. J. Holland, A.
9726 Operational Considerations for Use of DNS in Internet of Things
dyas-[ietf/cache/rfc](3.3.8) mcr 6018 %grep -i operational rfc-index.txt | grep
-i considerations | wc -l
6
I started at _sidrops_, which I think is an entire WG for operational
considerations. And I think that there are a bunch of BGP BCPs, then there
are MANRS, ARIN and RIPE BCOPs.
> - Also as a reminder: the authors are happy for other WEG members to
> join the effort as co-authors!
WG?
Or weg = away?
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
