[Openid-specs-mobile-profile] Proposed close - Issue #215

[Axel.Nennker at telekom.de]

Sorry, I did not work on #215 more.

Not sure which discussions you mean. Probably the discussion in the MODRNA WG which I failed to participate in. Sorry.

The feature request to Android https://issuetracker.google.com/issues/308240647 just came up in other partnermanagement-internal issuetracker issue.

The discussion is very active e.g. in GSMA ASAC and GSMA TS.43 how an aggregator knows to which OpenId Provider to route a TS.43 token.
That discussion would be much different if the operating system provided a way for a mobile application to know the operator's openid provider.


From: Bjorn Hjelm <bjorn.hjelm at oidf.org>
Date: Tuesday, 3. June 2025 at 16:54
To: MODRNA WG <openid-specs-mobile-profile at lists.openid.net>, Nennker, Axel <Axel.Nennker at telekom.de>
Cc: Bjorn Hjelm <blhjelm at gmail.com>
Subject: Proposed close - Issue #215
Per discussions, proposed close of issue #215<https://bitbucket.org/openid/mobile/issues/215/android-carrier-openid-api>. The issue will be closed by next MODRNA WG meeting if no comments have been received.

Kind Regards,
Bjorn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20250603/aa98e400/attachment.htm>