TIM Italy and TIM Brasil contributions proposal

[paulocesardiaslima]

TIM Italy and TIM Brasil reviews points and contributions proposal:

Suggest to converge on a YAML from previous proposal A+B+C:
A) Proposal by TEF (Telefonica Proposal #3)
B) Proposal by DT (Initial content for Number Verify #2)
C) Proposal initially by TIM Brasil (IP and Port header input parameters)

Review points include in new YAML file version regarding path /authorize:
IP and Port as optional input header parameters
oAuth2 already mapped in DT (Initial content for Number Verify #2)
Error code handling according to CAMARA others API (e.g., the Traffic Influence API)

[monamok]

Hello @paulocesardiaslima.
Please find my comments here:
camaraproject#2 (comment)

We have been discussing in several meetings about what the API should include and the idea is to have an independent simple API with specific resources (and NOT general resourses such as /userinfo that offers MC) where the authentication/authorization and getting the token will be handled outside of the API and the API just handles the verification part. The goal is not to define an authentication flow but a verification API.

Please check out the comments in this PR. From Telefonica we're against duplicating MC solution. It doesn't follow the commonalities decisions and it's against the whole idea of CAMARA.