move AAGUID for selecting authnr into new AuthenticatorSelectionCriteria

[rlin1]

Close #441

---

Preview | Diff

[rlin1]

Close #446
Close #447

[jyasskin]

A comment is not enough to specify what these fields do.

[jyasskin]

More generally, if you actually want these fields added in a timely manner, you should send them in separate PRs so that a field that gets consensus isn't held up behind more contentious or harder-to-specify fields. Showing a unified framework for these fields in an issue could help build support for them, but even then it's wise to add them separately.

[equalsJeffH]

@jyasskin noted on call just now something about this interacting with pr #460

[equalsJeffH]

@jyasskin notes on the call just now: this PR has 3 components: AAGUID, key protection, matcher protection. all should be evaluated independently (separate PRs). matcher protection could be moved into PR #460 but not necessarily.

[selfissued]

I agree with @jyasskin that each independent piece of functionality should be placed into its own PR so that it can be evaluated independently. This was agreed to on the 24-May-17 WG call.

[rlin1]

Will close (unmerged) this PR and create individual PRs for adding aaguidList, keyProtection and matcherProtection to Authenticator SelectionCriteria.