Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add class_id to client schema #192

Open
wilsonianb opened this issue Oct 5, 2022 · 0 comments
Open

Add class_id to client schema #192

wilsonianb opened this issue Oct 5, 2022 · 0 comments
Labels
type: specification Changes to the specification

Comments

@wilsonianb
Copy link
Contributor

https://datatracker.ietf.org/doc/html/draft-ietf-gnap-core-protocol#section-2.3

class_id (string): An identifier string that the AS can use to
identify the client software comprising this client instance. The
contents and format of this field are up to the AS. OPTIONAL.

I'm wondering if it would be useful at to specify something like rafiki there to allow special handling of clients that are Open Payments servers.
@mkurapov mkurapov moved this to Backlog in Open Payments Jun 28, 2023
@mkurapov mkurapov added the type: specification Changes to the specification label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: specification Changes to the specification
Projects
Open Payments
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wilsonianb @mkurapov