Re: [Taps] April interim: - My promised review of normative arch language (derived from github).

Thanks for these details, Gorry! I finally got around to making this PR. Please take a look, and we’ll discuss tomorrow: https://github.com/ietf-tapswg/api-drafts/pull/564 Best, Tommy > On Mar 25, 2020, at 9:02 AM, Gorry Fairhurst wrote: >

Re: [Taps] April interim: - My promised review of normative arch language (derived from github).

Hi Gorry, I am much in favour with you proposal, though we can clearly define what a TAPS system is. AVE! Philipp > On 25. Mar 2020, at 17:02, Gorry Fairhurst wrote: > > As promised, > > I did a review of the arch draft and the PR that was recently done. There > were comments that reque

Re: [Taps] April interim: - My promised review of normative arch language (derived from github).

On 25/03/2020 16:30, Mirja Kuehlewind wrote: Thanks, Gorry, for this! I support the idea of having one section with normative requirement at the beginning. Would be nice if someone could put this in a PR. I guess we need to add at least one more requirement on use of security protocols at lea

Re: [Taps] April interim: - My promised review of normative arch language (derived from github).

Thanks, Gorry, for this! I support the idea of having one section with normative requirement at the beginning. Would be nice if someone could put this in a PR. I guess we need to add at least one more requirement on use of security protocols at least. Mirja On 25.03.20, 17:03, "Taps on behal

Re: [Taps] April interim: - My promised review of normative arch language (derived from github).

As promised, I did a review of the arch draft and the PR that was recently done. There were comments that requested to remove some normative language that has been implemented in the current draft - where my review agreed, I have not commented further below. However, the latest revision, also