[Openid-specs-ab] Issue #2109: [Federation] List Endpoint response format (openid/connect)

[Michael Fraser]

New issue 2109: [Federation] List Endpoint response format
https://bitbucket.org/openid/connect/issues/2109/federation-list-endpoint-response-format

Michael Fraser:

Under section 8.3 \([https://openid.net/specs/openid-federation-1\_0.html#name-subordinate-listings](https://openid.net/specs/openid-federation-1_0.html#name-subordinate-listings)\) the list endpoint is defined and an issue is flagged inside the spec around the size of the response 

> the list contained in the result MAY be a very large list.

I would argue this is something best solved through pagination inside the spec instead of simply just acknowledging it as an issue. 

I would propose adding two optional pagination keys to the request \(size and page\) and adjust the response to the following

```
200 OK
Content-Type: application/json

{
  "page": 0,
  "size": 5,
  "content": [
    "https://ntnu.andreas.labs.uninett.no/",
    "https://blackboard.ntnu.no/openid/callback",
    "https://serviceprovider.andreas.labs.uninett.no/application17"
  ]
}
```

I would like to know people’s thoughts on this, thanks