Review issues for UE-Identification.md

[rartych]

Problem description
As indicated in #388 (comment)
The file needs to be reviewed

Expected action
This file is very 3GPP focussed. it could be more logically placed in supporting documents (and even more logically in ICM ...) Not sure if there is a reference to it somewhere.
Also UE being a Telco term, it could be renamed to 3gpp-device-identification.md (where ever you put it.

Also inside the file terminology could be aligned (API invoker -> API consumer, UE -> device, etc), depending on the objective of this document.

Additional context

[eric-murray]

I agree this document should be moved to the supporting documents folder, and not be a formal part of Commonalities specifications.

It's value will be in explaining what a networkAccessIdentifier is (though it does not use that term). But, if and when NAIs are supported, the question from API consumer's will be "How do I know the user's NAI?", rather than "What is a NAI?", and the document does not answer that.

But as CAMARA does not yet support NAIs, we can skip the question on how an API consumer determines the correct value for now.

[PedroDiez]

Agree with that. We can take the decision so far to move the document to supporting documents folder.