Well, I have not thought about the OP to ask the user to pass the data
to the RP leveraging required/optional fields information. Thanks for
the clarification.
Martin Atkins wrote:
Enis Soztutar wrote:
As far as I understand, the distinction between sreg.required and
sreg.optional is enti
Enis Soztutar wrote:
>
> As far as I understand, the distinction between sreg.required and
> sreg.optional is entirely in the responsibility of the consumer and
> there is not reason for the protocol to include this arbitrary division.
> An OP implementation will just merge the two fields and t
