[Openid-specs-ab] Issue #2165: E.164 phone number example is not accurately representing E.164 format (openid/connect)

[Kyoho Satsumi]

New issue 2165: E.164 phone number example is not accurately representing E.164 format
https://bitbucket.org/openid/connect/issues/2165/e164-phone-number-example-is-not

Kyoho Satsumi:

In section 5.1, phone\_number member description:

> End-User's preferred telephone number. [E.164](https://openid.net/specs/openid-connect-core-1_0.html#E.164) \[E.164\] is RECOMMENDED as the format of this Claim, for example, `+1 (425) 555-1212` or `+56 (2) 687 2400`. If the phone number contains an extension, it is RECOMMENDED that the extension be represented using the [RFC 3966](https://openid.net/specs/openid-connect-core-1_0.html#RFC3966) \[RFC3966\] extension syntax, for example, `+1 (604) 555-1234;ext=5678`.

While OIDC spec recommends E.164, the example shown here \(including spaces, parentheses, and hyphens\) is different from widely recognized E.164 format \(no space/parenthesis/hyphen\) , which I think it is confusing. 

Here are couple of sources I found that explain E.164 formatting:

* [https://help.twilio.com/articles/223183008-Formatting-International-Phone-Numbers](https://help.twilio.com/articles/223183008-Formatting-International-Phone-Numbers)
* [https://www.twilio.com/docs/glossary/what-e164](https://www.twilio.com/docs/glossary/what-e164)
* [https://voipstudio.com/blog/what-is-the-e-164-format-and-how-to-use-it-correctly/](https://voipstudio.com/blog/what-is-the-e-164-format-and-how-to-use-it-correctly/)
* [https://github.com/google/libphonenumber?tab=readme-ov-file#quick-examples](https://github.com/google/libphonenumber?tab=readme-ov-file#quick-examples)

Is it possible to fix these examples in the errata?

Section 5.6.2.1. Example of Aggregated Claims and 5.6.2.2. Example of Distributed Claims also have phone number examples, which might want to be fixed together if this issue is approved.