Consider adding pagination for other responses that need it

[lj-raidiam]

Consider extending scope of this specification by covering two additional endpoints Federation Historical Keys Response and Trust Marked Entities Listing Response. Feedback appreciated.

[MichaelFraser1999]

I can absolutely see the value for pagination in the trust marked entities listing gaining pagination - that could very easily become a huge list. I'm thinking for API certification in ecosystems with 10s of thousands of participants.

Historical keys, I'm less convinced we'll see that list grow egregiously in the wild. I'm also hesitant to add pagination to a JWK set - this would almost certainly not mesh too well with existing JOSE implementations (I know for a fact that I've never considered pagination in my past implementations)

[selfissued]

We discussed this on the 2-Jan-25 working group call. It's not clear that there's an actual need for pagination for the Trust Marked Entities Listing Response, since it's returning a list of URLs - not full Trust Marks or Entity Configurations. When would the list size become unacceptable?

[peppelinux]

It makes sense to have it for the trust-marked list as well.
We can consider that the draft was originally created for the listing endpoint, whether it is for subordinate listing or trust-marked listing.

for the historical keys I agree with @MichaelFraser1999